Hi All,
I am new to USB Device Drivers. I am theoratically aware of USB architecture and
Linux USB Subsystem. Now I want to write USB Device Driver (i.e. Client Driver) for my
USB Device. Can anyone give me right startup for this? I am looking for one sample
driver and information about how
Ganesh, Linux-USB folks,
It seems like the ipaq.[ch] serial-over-USB driver is not SMP safe. What
data do you need to track down such bugs?
This person is using a RedHat 7.3 system running kernel
2.4.18-18.7.xsmp; it has two Pentium-II processors and when he use the
ipaq driver his system locks
Ganesh, Linux-USB folks,
It seems like the ipaq.[ch] serial-over-USB driver is not SMP safe. What
data do you need to track down such bugs?
This person is using a RedHat 7.3 system running kernel
2.4.18-18.7.xsmp; it has two Pentium-II processors and when he use the
ipaq driver his
could you please ask him to try it with the latest 2.4.20-rc1?
there have been some bugfixes since 2.4.18 which could very well be
responsible for smp hangs.
unfortunate wording there :) let me rephrase: 2.4.20-rc1 contains a fix to
ipaq.c which might solve the problem.
if it still causes
I am working on a driver for the Creative Extigy, using kernel version
2.4.19. The device reports events from the IR remote via the standard USB
interrupt endpoint. I can trigger this interrupt by pressing a button on
the remote or on the device itself. In the driver, I submit an URB with a
simple
Use usb-skelton.c, It's there in your kernel source
code.
--- Rajendra Kumar [EMAIL PROTECTED]
wrote:
Hi All,
I am new to USB Device Drivers. I am theoratically
aware of USB architecture and Linux USB Subsystem.
Now I want to write USB Device Driver (i.e. Client
Driver) for my USB Device.
Oops attached below.
The scenario: I've got a WhiteHEAT plugged in, and # cu -l /dev/ttyUSB0. The far side
is sending a small text file across, which cu is displaying as it arrives. During the
transfer I
unplug the WhiteHEAT.
Sometimes I get this oops, sometimes I don't. It's always identical,
