Minor bug in writing_usb_driver.tmpl?

When looking at the documentation about USB probe functions in Documentation/DocBook/writing_usb_driver.tmpl it seems that the programlisting containing the skel_probe call has been updated to the 2.5 kernel probe callback API but the text above it has not been updated: - Device oper

Re: Minor bug in writing_usb_driver.tmpl?

Am Donnerstag 03 Januar 2008 schrieb Andreas Ehliar: > Am I correct in thinking that skel_probe will be called one time for > each interface available on a suitable device which is plugged in? Yes, you are correct. Or rather for each interface that matches. You can also match on interfaces' class.

Re: Kingston Datatraveler

Hi, I tried this but it has the same result. Brian On Dec 31, 2007 9:51 PM, Alan Stern <[EMAIL PROTECTED]> wrote: > On Sun, 30 Dec 2007, Brian Murphy wrote: > > > Hi, > > > > I install Win XP on the system and the drive works fine. > > > > I have tested this with both Ubuntu and Fedore destribut

[PATCH] ti_usb: termios cleanups

Remove internal NULL passing in termios code Remove all the if checks it causes Encode the baud rate back properly Clear CMSPAR as it is not supported Signed-off-by: Alan Cox <[EMAIL PROTECTED]> diff -u --new-file --recursive --exclude-from /usr/src/exclude linux.vanilla-2.6.24-rc6-mm1/drivers/u

[PATCH] mos7720: clean up termios

Remove lots of NULL checks that can no longer occur Encode the baud rate back into the termios (again someone with docs see FIXME to improve this further) Signed-off-by: Alan Cox <[EMAIL PROTECTED]> diff -u --new-file --recursive --exclude-from /usr/src/exclude linux.vanilla-2.6.24-rc6-mm1/drive

[PATCH] keyspan: Fix oops

If we get a data URB back from the hardware after we have put the tty to bed we go kaboom. Fortunately all we need to do is process the URB without trying to ram its contents down the throat of an ex-tty. Signed-off-by: Alan Cox <[EMAIL PROTECTED]> diff -u --new-file --recursive --exclude-from /u

[PATCH] io_ti: clean up termios handling

Don't pass NULL into termios functions when calling them internally Remove all the crap which then checks for NULL which can't occur now Clear CMSPAR as it is not supported Report the baud rate back to the caller properly (See FIXME someone with the docs) Signed-off-by: Alan Cox <[EMAIL PROTECTED]

[patch 2.6.24-rc6] usb gadget: fix fsl_usb2_udc potential OOPS

From: Li Yang <[EMAIL PROTECTED]> For fsl_usb2_udc driver, ep0 also has a descriptor. Current code is misleading and contains a logical mistake. Here is the patch to fix it. http://bugzilla.kernel.org/show_bug.cgi?id=9595 Signed-off-by: David Brownell <[EMAIL PROTECTED]> --- a/drivers/usb/ga

Re: [linux-usb-devel] [PATCH 0/3] ehci-hcd: complete iso urbs sooner, take 5

On Wednesday 02 January 2008, Karsten Wiese wrote: > Am Mittwoch, 2. Januar 2008 schrieb David Brownell: > > On Tuesday 01 January 2008, Karsten Wiese wrote: > > > How about: > > > Urbs stopping/starting at (uFrame % 8) != 0 can share ITDs, > > > > If there's a problem in that area, it should get

Re: [linux-usb-devel] [PATCH 0/3] ehci-hcd: complete iso urbs sooner, take 5

On Wednesday 02 January 2008, Karsten Wiese wrote: > Am Mittwoch, 2. Januar 2008 schrieb David Brownell: > > On Tuesday 01 January 2008, Karsten Wiese wrote: > > > The finishing urb doesn't recycle its last ITD, instead the starting urb > > > takes care of that. > > > > Also a different issue. Th

Issue with NEC EHCI controller on PPC440EPx-based board

Hi, We are developing a board using the AMCC PPC440EPx CPU, and we've included the NEC PD720101 host controller on the PCI bus. I've tested a similar configuration using the Sequoia reference board with a Belkin card containing the same NEC chip, and EHCI works fine there. However, on our board, I

Re: [linux-usb-devel] [PATCH 0/3] ehci-hcd: complete iso urbs sooner, take 5

Am Donnerstag, 3. Januar 2008 schrieb David Brownell: > On Wednesday 02 January 2008, Karsten Wiese wrote: > > > > Disagree: with your patches ITDs can still be removed from ehci's > > hardware schedule, while a frame is active, no? > > Which is a perfectly valid thing to do. And a frame is stil

[pl2303 regression] Linux 2.6.23 breaks gpsbabel's DG-100 support

Starting with Linux 2.6.23, I get corrupted data (lost and altered bytes) when using the Prolific PL2303 USB-serial driver with GPSBabel and the GlobalSat DG-100 GPS data logger. (I am the author of GPSBabel's DG-100 support). The appended patch applied in reverse (a partial revert to 2.6.22) make

Re: [RFC] libusb / in-kernel usb driver criteria (was: USB driver for talking to the Microchip PIC18 boot loader)

On Wed, Jan 02, 2008 at 07:59:15PM +, Paulo Marques wrote: > Xiaofan Chen wrote: >> On Dec 30, 2007 11:53 AM, mgross <[EMAIL PROTECTED]> wrote: >>> [...] >>> What is the linux-usb policies on new drivers that could be >>> implemented in user space? When does a kernel driver make sense over >>>

Re: [linux-usb-devel] [PATCH 0/3] ehci-hcd: complete iso urbs sooner, take 5

Am Donnerstag, 3. Januar 2008 schrieb Karsten Wiese: > Am Donnerstag, 3. Januar 2008 schrieb David Brownell: > > On Wednesday 02 January 2008, Karsten Wiese wrote: > > > > > > Disagree: with your patches ITDs can still be removed from ehci's > > > hardware schedule, while a frame is active, no? >

Oops in evdev_disconnect for kernel 2.6.23.12

Jan 1 17:34:39 wonderland kernel: usb 2-2: USB disconnect, address 3 Jan 1 17:34:39 wonderland kernel: usb 2-2.5: USB disconnect, address 4 Jan 1 17:34:39 wonderland kernel: drivers/input/tablet/wacom_sys.c: wacom_sys_irq - usb_submit_urb failed with result -19 Jan 1 17:34:39 wonderland kernel