On Thu, Mar 23, 2000 at 09:51:28PM +0000, Alex Holden wrote:
> 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.
I agree that the current way of putting the firmware in the driver isn't
the best way (makes the driver HUGE, take a look at the size of
usb-serial with all of the devices selected), and some way of having a
firmware loader would be great. The biggest problem is that of the three
devices I have right here, all 3 have a different protocol that is used
in sending the firmware down (2 of them are EZUSB devices, and they both
do things differently, due to the ability of a manufacturer to change
the EZUSB bootloader code.).
I'd be happy right now with each device having it's own loader, that way
the kernel size could shrink a bunch. It would be a good start.
Anyone have any ideas of how khubd could kick off a user space program,
or have usbdevfs do it?
greg k-h
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
