Johannes Erdfelt wrote:
>
> On Fri, May 05, 2000, Johan Verrept <[EMAIL PROTECTED]> wrote:
> > Greg KH wrote:
> >
> > > Hm, actually they could just register with usb/empty or some such
> > > directory and devfsd would come along, start up a userspace program that
> > > would dump the firmware to it, then the device would reenumerate
> > > (causing the usb/empty/0 node to disappear) and some other driver would
> > > be attached to it like it happens today.
> > >
> > > That might work, I really want to move these firmware images out of
> > > kernel memory. I just see them as taking up unnecessary room.
> >
> > hehehe.
> > wait until you see the size of the SpeedTouch USB firmware... I download
> > the firmware using devfs first, then insert the module. (because of some
> > problems we'll discuss later ;)
> > btw: the SpeedTouch does not change his vendor id (or enumerate) after
> > firmware download...
>
> This could also be handled by executing a program to download the
> firmware, then when it finishes successfully, bind a driver to the
> device.
how would the binding work ?
J.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
