Re: [linux-usb-devel] Re: why firmware reload must be in kernel space

2001-12-17 Thread Matthew Dharm
Yes, Zip drives have unique serial numbers, so they're properly re-identified on resume and "reconnected" to their device node. There is some work to be done here, tho doing a suspend with a mounted fs on the device could lead to Bad Things(tm). Of course, windows has the same problem if you

Re: [linux-usb-devel] Re: why firmware reload must be in kernel space

2001-12-17 Thread Greg KH
On Mon, Dec 17, 2001 at 07:51:49PM +, Riley Williams wrote: > > Keeping that in mind, let's take some scenarios that are already here > and need to be dealt with by the USB subsystem: > > 1. Simon's laptop has no keyboard on the body of the laptop, > and is supplied with a separate

Re: [linux-usb-devel] Re: why firmware reload must be in kernel space

2001-12-17 Thread Vojtech Pavlik
On Mon, Dec 17, 2001 at 12:02:06PM -0800, Greg KH wrote: > > That deferring may not always be possible. As an example, take a system > > in use by a friend of mine, basically a laptop with the keyboard not > > part of the main unit, but on the end of a USB lead that has to be > > disconnected to

Re: [linux-usb-devel] Re: why firmware reload must be in kernel space

2001-12-17 Thread Vojtech Pavlik
On Mon, Dec 17, 2001 at 07:30:32PM +, Riley Williams wrote: > Remember, one of the basic design aims of USB was that the location a > device is plugged in is irrelevant to the user. The Linux USB drivers > need to be totally transparent to where a particular device is plugged > in, otherwise

Re: [linux-usb-devel] Re: why firmware reload must be in kernel space

2001-12-17 Thread Greg KH
On Mon, Dec 17, 2001 at 07:30:32PM +, Riley Williams wrote: > > That deferring may not always be possible. As an example, take a system > in use by a friend of mine, basically a laptop with the keyboard not > part of the main unit, but on the end of a USB lead that has to be > disconnected to

Re: [linux-usb-devel] Re: why firmware reload must be in kernel space

2001-12-17 Thread David Brownell
> [several sequences to unplug/replug same/different device while suspended] > > > The first three sequences means that we can't guarantee that on resume, > > the devices available will be identical to those on suspend. The last > > sequence means that even if it is, we may need to do more than j