Re: [linux-usb-devel] [ANNOUNCE] big USB patch for 2.6.0-test11

2003-12-13 Thread Alan Stern
Greg: Does this mean that the usb-2.5 repository is now essentially moribund? Should I clone the bk://linuxusb.bkbits.net/usb-devel-2.6 repository and start using that for my development work? Alan Stern --- This SF.net email is sponsored b

[linux-usb-devel] Re: your mail

2003-12-13 Thread Greg KH
On Sat, Dec 13, 2003 at 06:24:16PM -0500, John Homppi wrote: > Hi Greg, > Attached is a driver for ADU devices from Ontrak Control Systems. > I have tested it both as a module and kernel code in 2.6.0-test11 > Testing was done on two ASUS mother boards, one with an Intel chipset > and the other wit

[linux-usb-devel] (no subject)

2003-12-13 Thread John Homppi
Hi Greg, Attached is a driver for ADU devices from Ontrak Control Systems. I have tested it both as a module and kernel code in 2.6.0-test11 Testing was done on two ASUS mother boards, one with an Intel chipset and the other with a VIA chipset. Note that an official USB minor device number has not

Re: [linux-usb-devel] Problem with external USB2.0 case and LG GSA 4040-B

2003-12-13 Thread Cornelius Claussen
Hi, there was a thread about problems with the LG GSA 4040-B dvd-writer in an extermal USB 2.0 case from Genesys Logic, Inc. a few days ago. I have the same combination and the same problems and tried the second patch from the thread with 2.6.0-test11. It works way better than before, but if I c

Re: [linux-usb-devel] pl2303 driver with "dumb" devices

2003-12-13 Thread Marr
On Wednesday 10 December 2003 08:38am, Paulo Marques wrote: > Marr wrote: > > On Monday 08 December 2003 03:59pm, Alessio Sangalli wrote: > >>... > >>if I connect a usb-serial adapter to my laptop, and I connect to this > >>adapter an external serial modem, everything's perfect. But, if I > >>conne

Re: [linux-usb-devel] Status Query On My MCT-U232 Patch

2003-12-13 Thread Marr
On Friday 12 December 2003 03:22pm, Greg KH wrote: > On Thu, Nov 27, 2003 at 01:57:28AM -0500, Marr wrote: > > On Wednesday 26 November 2003 12:22pm, Greg KH wrote: > > > On Tue, Nov 25, 2003 at 02:59:52PM -0500, Marr wrote: > > > > Greg K-H et al, > > > > > > > > Greetings > > > > > > > > A li

Re: [linux-usb-devel] Re: [OOPS, usbcore, releaseintf] 2.6.0-test10-mm1

2003-12-13 Thread Oliver Neukum
Am Samstag, 13. Dezember 2003 17:40 schrieb Alan Stern: > On Sat, 13 Dec 2003, Oliver Neukum wrote: > > > > The API has an admitted weak spot when more than one driver is bound to > > > the device. No one has settled on a definite policy for how to handle > > > that situation. > > > > Right. Y

[linux-usb-devel] memory allocations in storage code path for 2.4

2003-12-13 Thread Oliver Neukum
Hi Greg, in block io or error paths we must use GFP_NOIO instead of GFP_KERNEL. Under 2.4 we cannot tell and must assume the worst, hence always use GFP_NOIO. This cset against your 2.4 BK tree does that for hcd drivers. Regards Oliver You can import this changeset into B

Re: [linux-usb-devel] Re: [OOPS, usbcore, releaseintf] 2.6.0-test10-mm1

2003-12-13 Thread Alan Stern
On Sat, 13 Dec 2003, Oliver Neukum wrote: > > The API has an admitted weak spot when more than one driver is bound to > > the device. No one has settled on a definite policy for how to handle > > that situation. > > Right. You have to disconnect all but the driver requesting the reset. For th

Re: [linux-usb-devel] Re: [OOPS, usbcore, releaseintf] 2.6.0-test10-mm1

2003-12-13 Thread Oliver Neukum
> (1) If both subsys.rwsem and dev->serialize are taken, then > subsys.rwsem must be taken first. Yes. > (2) dev->serialize atomizes changes to the struct usb_device. > > Why then is dev->serialize not taken in usb_reset_device > (except in a dud code path)? > > Also, why isn't dev->serialize

Re: [linux-usb-devel] Re: [OOPS, usbcore, releaseintf] 2.6.0-test10-mm1

2003-12-13 Thread Oliver Neukum
> The API has an admitted weak spot when more than one driver is bound to > the device. No one has settled on a definite policy for how to handle > that situation. Right. You have to disconnect all but the driver requesting the reset. > > IMHO you should do the code paths for late errors and