On Thu, 23 Mar 2000, Alan Cox wrote:
> but firmware supplying. I don't think a usb-firware-daemon is out of the
> question.

A good place to do this would be to give usbd the capability to start a
user space firmware loader (potentially a different one for each download
protocol) with a specified bus/device number and firmware file whenever it
detects the attachment of specific vid/pid pairs before it either loads
the kernel module or starts the user space device driver required to
handle that particular device. There are a lot of ezusb based devices
being developed at the moment, and it would be a good idea to build a nice
generic solution to the firmware/driver loader problem now rather than
each device ending up having it's own loader.

--------------- Linux- the choice of a GNU generation. --------------
: Alex Holden (M1CJD)- Caver, Programmer, Land Rover nut, Radio Ham :
-------------------- http://www.linuxhacker.org/ --------------------


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to