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

2001-12-24 Thread Riley Williams
Hi Vojtech. >> USB printer drivers on Windows for some manufacturers use the device >> serial number to keep track of where the user plugged in a specific >> printer, to keep that printer's settings correct. Lots of printers >> do not have serial numbers, so those driver authors have to use the

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

2001-12-18 Thread Greg KH
On Tue, Dec 18, 2001 at 09:58:48AM +0100, [EMAIL PROTECTED] wrote: > > - USB modem: > > - Simon only has 1 modem, so no matter where he plugges it in on > > the USB topology, it will always be referenced as the same > > modem: /dev/ttyACM0 > > But will any settings he has made to

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

2001-12-18 Thread Oliver.Neukum
> - USB modem: > - Simon only has 1 modem, so no matter where he plugges it in on > the USB topology, it will always be referenced as the same > modem: /dev/ttyACM0 But will any settings he has made to his modem be restored ? If he presses suspend while his terminal program is

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

2001-12-17 Thread Riley Williams
Hi Martin. >> If we're talking USB here (and in some cases even if we're not), we >> need to deal with more than that. Specifically, we need to be able >> to deal with the following sequences: > [several sequences to unplug/replug same/different device while > suspended] >> The first three sequ

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

2001-12-17 Thread Martin Diehl
On Sun, 16 Dec 2001, Riley Williams wrote: > If we're talking USB here (and in some cases even if we're not), we need > to deal with more than that. Specifically, we need to be able to deal > with the following sequences: > [several sequences to unplug/replug same/different device while suspended