On Thu, May 04, 2000, Greg KH <[EMAIL PROTECTED]> wrote:
> On Thu, May 04, 2000 at 11:31:51PM +0100, Alan Cox wrote:
> > > And I can get devfsd to run it for me when I press the hotsync button by
> > > adding this line to /etc/devfsd.conf:
> > > REGISTER usb/tty/1 EXECUTE sudo -u mcelrath
>~mcelrath/bin/visor-sync
> > >
> > > With these two things I can now hotsync simply by pressing the hotsync
> > > button.
> >
> > Very nice indeed. So is devfsd enough to avoid writing another daemon and
> > sending it change messages. At least if we expand the info passed a little ?
>
> I don't know.
> What node would devices that don't have their firmware downloaded to
> them yet open up?
>
> 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.
>
> Time to take Johannes' patch and try it out...
This could easily be handled in userspace with my driver binding patch
and some extra glue in devfsd.
Once it sees a device with matching characteristics, execute a program
to download the firmware and when it reenumerates, it'll go through the
same process again, but it has something which is different this time
and gets a "normal" kernel driver.
JE
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
