> > And the problem is not limited to devices with firmware.
> > If you have two USB disks, sda must remain sda and not
> > interchange with sdb after resumption, even if sdb would be
> > reenumerated later than sda. To do that you need to reidentify devices
> > after resumption, you cannot equate suspension with disconnection and
> > resumption with reenumeration.
> > This applies to all drivers which work with more than one device of a
> > kind. For disks the results are just more drastic, being two very dead
> > filesystems.
>
> No, I do not want to get drug into a device naming thread right now! :)
> That is a independent issue of getting the device up and running.
> Major/minor allocations are separate from usb enumeration. The fact
> that today's kernel happens to tie them together tightly is not the
> issue either. A few very good proposals on how to split this up have
> been proposed on lkml recently, I'd suggest you take them up with their
> authors...
OK, names are radioactive hazardous issues.
It was just the tip of the iceberg.
You need the ability to reidentify for simple things like setting the
correct IP on the correct network adapter, or correct resolution
on the correct camera.
You cannot avoid the issue I am afraid.
Regards
Oliver
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
