On Tue, Mar 30, 2004 at 08:18:12PM +0200, Olaf Hering wrote:
>  On Tue, Mar 30, Greg KH wrote:
> 
> > On Tue, Mar 30, 2004 at 05:58:31PM +0200, Olaf Hering wrote:
> > > 
> > > WHY is all the vendor, product, serial and what not info still dynamic?
> > > How can the info change during the "lifetime" of an attached USB device?
> > 
> > Because the device can change those strings at any time if it wants to
> > (and I've seen devices that do just that.) So we can't cache the data,
> > and must ask the device every time for the string.
> 
> What devices?

I don't remember, but I think a large number of USB printers had big
problems.  They changed their serial number and product strings
depending on the way the printer was configured.  Nasty buggers.

> And why would that matter during the hot phase of the hardware
> detection, when usb, scsi, input or block agent runs?

One of the hotplug scripts care about the serial number or product
string of the device?  Is this something other than udev asking for it?

> So far this sort of thing has only caused trouble, it doesnt help
> anyone.  Please rewrite the parts of the USB stack to make the info
> static.

I have not seen any reports, other than broken usb-storage devices.  We
tried to make these strings static a long time ago in 2.2/early 2.4
timeframe and too many problem devices cropped up, so we went back to
the (simpler) method of not caching anything.

What kind of problems have you seen reported?

thanks,

greg k-h


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to