From: "Greg KH" <[EMAIL PROTECTED]>
> On Wed, Apr 18, 2001 at 03:48:09AM -0700, Adam J. Richter wrote:
> > ftp://ftp.yggdrasil.com/private/adam/ezusb/nofirmware-linux-2.4.3.patch
> > contains my first effort at removing the ezusb firmware from the kernel
> > and removal of code that is no longer used as a result. The patch
> > is against 2.4.3.
> Great job, it actually works! :)
> I tried out the whiteheat.firmware, whiteheat_debug.firmware,
> keyspan_pda.firmware, and the keyspan_usb19.firmware and they all seemed
> to work just fine.
Okay, I missed part of this discussion yesterday, so
my comments may be slightly off.
It seems that this effort is to move the firmware from
the kernel into user space?
That doesn't make a lot of sense to me (although I
see the savings of code size for the kernel); it seems
like this makes it the user space apps' jobs to load
the firmware to use the driver. This would seem to
break a lot of user space apps that would otherwise
run unchanged on a ezusb-based serial port;
the whiteheat ports in my case.
Also, moving the firmware away from the kernel
would seem to prevent using those ports as
serial consoles because the firmware wouldn't load
until after init was running sometime, instead of at
kernel boot.
Am I correct? Or am I missing vital info?
On that note, is there an archive somewhere that I'm
not aware of?
..Stu
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
