kernel.git/drivers/usb/misc/ldusb.c, branch linux-2.6.18.y

Remove obsolete #include

2006-06-30T17:25:36Z

Signed-off-by: Jörn Engel Signed-off-by: Adrian Bunk

[PATCH] USB: convert a bunch of USB semaphores to mutexes

2006-03-20T22:49:55Z

the patch below converts a bunch of semaphores-used-as-mutex in the USB code to mutexes Signed-off-by: Arjan van de Ven Signed-off-by: Greg Kroah-Hartman

[PATCH] USB: kzalloc in ldusb

2006-03-20T22:49:53Z

another one for kzalloc Signed-off-by: Oliver Neukum Signed-off-by: Greg Kroah-Hartman

[PATCH] USB: add new device ids to ldusb

2006-02-14T05:33:39Z

Signed-off-by: Michael Hund Signed-off-by: Greg Kroah-Hartman

[PATCH] USB: remove some left over devfs droppings hanging around in the usb drivers

2006-02-01T01:23:41Z

As there is no more usb devfs support, these bits would just confuse people. Signed-off-by: Greg Kroah-Hartman

[PATCH] USB: remove .owner field from struct usb_driver

2006-01-04T21:48:34Z

It is no longer needed, so let's remove it, saving a bit of memory. Signed-off-by: Greg Kroah-Hartman

[PATCH] USB ldusb: fmt warnings fixes for 64-bit platforms

2005-09-08T23:28:27Z

Fix drivers/usb/misc/ldusb.c: In function `ld_usb_read': drivers/usb/misc/ldusb.c:467: warning: int format, different type arg (arg 4) drivers/usb/misc/ldusb.c: In function `ld_usb_write': drivers/usb/misc/ldusb.c:531: warning: int format, different type arg (arg 4) drivers/usb/misc/ldusb.c:532: warning: int format, different type arg (arg 5) drivers/usb/misc/ldusb.c:532: warning: int format, different type arg (arg 6) Signed-off-by: Alexey Dobriyan Signed-off-by: Greg Kroah-Hartman

[PATCH] USB: ldusb fixes

2005-07-29T20:12:53Z

below you will find the forgotten kmalloc check (sorry). Signed-off-by: Michael Hund Signed-off-by: Greg Kroah-Hartman Signed-off-by: Linus Torvalds

[PATCH] USB: add ldusb driver

2005-07-12T18:52:57Z

The following driver provides complete interrupt-in and interrupt-out reports (raw data) to a user program. Until now it uses the HIDIOCGDEVINFO ioctl call, because I don't know better :-(. Perhaps, it will be ok for you - and I will be happy, if you assign 8 minor numbers. I have tested it in several environments and it works very well for me. However, it has a problem with two or more devices at the same hub, if the two or more devices need 1 ms interrupt-in transfers. Unfortunately more than one interrupt-in transfer every ms isn't possible (ehci driver?). This is why the min_interrupt_in_interval and min_interrupt_out_interval are increased to 2 ms (see the corresponding module parameters). This way, I can use two devices simultaneously at the same hub. Signed-off-by: Michael Hund Signed-off-by: Greg Kroah-Hartman