On Wed, Feb 15, 2012 at 1:02 AM, Jimmy Christensen
<email address hidden> wrote:
> Jiandong, I am also trying to get the fermi module to work on arm
> (Pandaboard), I have a funny issue, I never get a /dev/nwfermi device,
> even though the module builds and logs messages about the monitor when I
> plug in the USB..
>
> After digging a bit, it seems that the fermi_probe function is called
> twice, first time it finds the endpoint, second time, the interface-
> address is 0x200 higher and two endpoints, none of which are bulk-in is
> found:
>
> [ 86.137359] usb 1-1.2: new high speed USB device number 4 using ehci-omap
> [ 86.266906] usb 1-1.2: New USB device found, idVendor=0424, idProduct=2517
> [ 86.274658] usb 1-1.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> [ 86.287048] hub 1-1.2:1.0: USB hub found
> [ 86.291595] hub 1-1.2:1.0: 7 ports detected
> [ 86.583038] usb 1-1.2.1: new full speed USB device number 5 using ehci-omap
> [ 86.715240] usb 1-1.2.1: New USB device found, idVendor=1926, idProduct=0068
> [ 86.723114] usb 1-1.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> [ 86.731689] usb 1-1.2.1: Product: Touchscreen
> [ 86.736358] usb 1-1.2.1: Manufacturer: NextWindow
> [ 86.743133] nw_fermi: fermi_probe called with interface ea8cec00 and device id struct c0735634
> [ 86.752349] nw_fermi: Num endpoints: 1
> [ 86.756347] nw_fermi: Endpoint 0 (00000081)
> [ 86.760894] nw_fermi: Direction- In: 1
> [ 86.765319] nw_fermi: Direction-Out: 0
> [ 86.769500] nw_fermi: Bulk transfer: 1
> [ 86.773712] nw_fermi: Max packet size: 64
> [ 86.778839] input: Nextwindow Fermi Touchscreen as /devices/virtual/input/input1
> [ 86.788757] nwfermi 1-1.2.1:1.0: NextWindow Fermi device now attached to nwfermi-192
> [ 86.797668] nw_fermi: fermi started bulk_reads error code 0
> [ 86.803863] nw_fermi: nwfermi started..
> [ 86.808868] nw_fermi: fermi_probe called with interface eb5aa000 and device id struct c0735634
> [ 86.818176] nw_fermi: Num endpoints: 2
> [ 86.822174] nw_fermi: Endpoint 0 (00000082)
> [ 86.822265] nw_fermi: Direction- In: 1
> [ 86.830993] nw_fermi: Direction-Out: 0
> [ 86.835205] nw_fermi: Bulk transfer: 0
> [ 86.839385] nw_fermi: Max packet size: 64
> [ 86.843963] nw_fermi: Endpoint 1 (00000002)
> [ 86.843963] nw_fermi: Direction- In: 0
> [ 86.852691] nw_fermi: Direction-Out: 0
> [ 86.856903] nw_fermi: Bulk transfer: 0
> [ 86.861175] nw_fermi: Max packet size: 64
> [ 86.866241] input: Nextwindow Fermi Touchscreen as /devices/virtual/input/input2
> [ 86.875366] nwfermi 1-1.2.1:1.1:: NextWindow Fermi device now attached to nwfermi-193
> [ 86.884338] nw_fermi: fermi started bulk_reads error code -22
> [ 86.884338] nw_fermi: Could not start bulk reads.
>
> But alas, no /dev/nw* devices.. The same driver on my x86 machine seems
> to work perfectly.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/811760
>
> Title:
> Need nwfermi_daemon for armel
>
> Status in Nextwindow Fermi Driver:
> New
>
> Bug description:
> Event though the kernel driver and X11 driver are available in source
> from and I can build for armel by myself, one key component
> nwfermi_daemon source is still missing. According to code, seems this
> saemon coverting hidraw data to standard linux event data, which can
> by recognized by GUI system like X11.
>
> Need at lease the armel daemon to be provided if sourcce can't be
> opened so that it can be used with ARM system.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nwfermi/+bug/811760/+subscriptions
Did you check if module are loaded by lsmod?
Next thing to check is that since this dev node should be created by
udev and I remember there is a udev rule in the package, which has to
be in place too.
btw, what version of Ubuntu are you running? armel or armhf? I am
going to try out precise armhf soon, let's see if it works for me ...
On Wed, Feb 15, 2012 at 1:02 AM, Jimmy Christensen virtual/ input/input1 virtual/ input/input2 /bugs.launchpad .net/bugs/ 811760 /bugs.launchpad .net/nwfermi/ +bug/811760/ +subscriptions
<email address hidden> wrote:
> Jiandong, I am also trying to get the fermi module to work on arm
> (Pandaboard), I have a funny issue, I never get a /dev/nwfermi device,
> even though the module builds and logs messages about the monitor when I
> plug in the USB..
>
> After digging a bit, it seems that the fermi_probe function is called
> twice, first time it finds the endpoint, second time, the interface-
> address is 0x200 higher and two endpoints, none of which are bulk-in is
> found:
>
> [ 86.137359] usb 1-1.2: new high speed USB device number 4 using ehci-omap
> [ 86.266906] usb 1-1.2: New USB device found, idVendor=0424, idProduct=2517
> [ 86.274658] usb 1-1.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> [ 86.287048] hub 1-1.2:1.0: USB hub found
> [ 86.291595] hub 1-1.2:1.0: 7 ports detected
> [ 86.583038] usb 1-1.2.1: new full speed USB device number 5 using ehci-omap
> [ 86.715240] usb 1-1.2.1: New USB device found, idVendor=1926, idProduct=0068
> [ 86.723114] usb 1-1.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> [ 86.731689] usb 1-1.2.1: Product: Touchscreen
> [ 86.736358] usb 1-1.2.1: Manufacturer: NextWindow
> [ 86.743133] nw_fermi: fermi_probe called with interface ea8cec00 and device id struct c0735634
> [ 86.752349] nw_fermi: Num endpoints: 1
> [ 86.756347] nw_fermi: Endpoint 0 (00000081)
> [ 86.760894] nw_fermi: Direction- In: 1
> [ 86.765319] nw_fermi: Direction-Out: 0
> [ 86.769500] nw_fermi: Bulk transfer: 1
> [ 86.773712] nw_fermi: Max packet size: 64
> [ 86.778839] input: Nextwindow Fermi Touchscreen as /devices/
> [ 86.788757] nwfermi 1-1.2.1:1.0: NextWindow Fermi device now attached to nwfermi-192
> [ 86.797668] nw_fermi: fermi started bulk_reads error code 0
> [ 86.803863] nw_fermi: nwfermi started..
> [ 86.808868] nw_fermi: fermi_probe called with interface eb5aa000 and device id struct c0735634
> [ 86.818176] nw_fermi: Num endpoints: 2
> [ 86.822174] nw_fermi: Endpoint 0 (00000082)
> [ 86.822265] nw_fermi: Direction- In: 1
> [ 86.830993] nw_fermi: Direction-Out: 0
> [ 86.835205] nw_fermi: Bulk transfer: 0
> [ 86.839385] nw_fermi: Max packet size: 64
> [ 86.843963] nw_fermi: Endpoint 1 (00000002)
> [ 86.843963] nw_fermi: Direction- In: 0
> [ 86.852691] nw_fermi: Direction-Out: 0
> [ 86.856903] nw_fermi: Bulk transfer: 0
> [ 86.861175] nw_fermi: Max packet size: 64
> [ 86.866241] input: Nextwindow Fermi Touchscreen as /devices/
> [ 86.875366] nwfermi 1-1.2.1:1.1:: NextWindow Fermi device now attached to nwfermi-193
> [ 86.884338] nw_fermi: fermi started bulk_reads error code -22
> [ 86.884338] nw_fermi: Could not start bulk reads.
>
> But alas, no /dev/nw* devices.. The same driver on my x86 machine seems
> to work perfectly.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Need nwfermi_daemon for armel
>
> Status in Nextwindow Fermi Driver:
> New
>
> Bug description:
> Event though the kernel driver and X11 driver are available in source
> from and I can build for armel by myself, one key component
> nwfermi_daemon source is still missing. According to code, seems this
> saemon coverting hidraw data to standard linux event data, which can
> by recognized by GUI system like X11.
>
> Need at lease the armel daemon to be provided if sourcce can't be
> opened so that it can be used with ARM system.
>
> To manage notifications about this bug go to:
> https:/
Did you check if module are loaded by lsmod?
Next thing to check is that since this dev node should be created by
udev and I remember there is a udev rule in the package, which has to
be in place too.
btw, what version of Ubuntu are you running? armel or armhf? I am
going to try out precise armhf soon, let's see if it works for me ...