>Are you saying that some form of system call is required to connect
the device to the USB Bus?
The way I understand it this is the only way it can be. There is
absolutely no difference in the way the computer is configured in the
boot loader (grub) stage. But from there on windows starts to be able to
recognize the device and linux does not. I am pretty sure that Gigabyte
has some special software installed in windows that makes the hardware
accessible (visible) in the first place. This is to say that it is not a
special feature of windows (being able to recognize the device) but the
magical activation tool of Gigabyte. Just to be sure I need to boot
another windows (without magical Gigabyte software). I couldn't do that
thus far because I need to get my hands on a usb-cd-drive first. (I
might try to put a UBCD on a flash drive and boot from there, if that works)
On 05/17/2012 06:40 PM, Anil Nair wrote:
On Thu, May 17, 2012 at 7:54 PM, Alan Stern<stern@xxxxxxxxxxxxxxxxxxx> wrote:
No. If your guess was right then no full/low-speed device would work
on that laptop, whereas obviously they do. For example, the mouse
wheel was detected normally.
The Windows screenshot showed that the touchscreen was plugged into a
hub, and the port status data from that hub under Linux showed the port
was not getting a connect signal (no D+ pullup).
Sir, Why this difference from Windows to Linux?. I was in the belief
that most of the devices work under Linux.
Are you saying that some form of system call is required to connect
the device to the USB Bus? In Windows the Device is connected to the
USB Bus; Then why this difference in working? Does the touchscreen
controller has to do anything in this? Or the USB Bus? Sorry for the
misunderstanding earlier.......:).
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
