|
OK,
So, I have a device I've been trying to get supported since
4/4/2001 (look in the archives).
The BACKPACK USB adapter simply needs a EZ-USB firmware loaded
(actually it has one that is loaded to scan until a drive is connected, then the
appropriate firmware is loaded when the scan discovers the drive
type).
Where do I put this?
Last I knew, I should put it in the hotplug world. But
then the whole "why firmware reload must be in kernel space" thread made it
sound like my old attempt at a kernel module would be more appropriate. In
addition, the firmware loading aspect of the linux-hotplug is not solid yet
(they have a program (fxload) but not a defined method ( a directory that gets
scanned ?).
Then on the usb-users list another person is asking if there
is BACKPACK-USB support.
So my question is:
Ok, where do I put this NOW? Not in
the future in a new architecture, I can adapt as that happens. ACPI is not
in the kernel yet! Heck, I don't even fit the normal power specs, the
adapter depends on the bus for power, but the drive is self powered (for those
that were looking for firmware overlaying, and strangeness with powering the USB
device, there ya go)
*breathing deeply*
Ok, I'm just a bit frustrated. Still appreciate all that goes
on here. Thank all of you.
Wish all good holiday type feelings.
Just looking for guidance,
Ken Hahn
|
- Re: [linux-usb-devel] Firmware Frustration Ken Hahn
- Re: [linux-usb-devel] Firmware Frustration Oliver.Neukum
- Re: [linux-usb-devel] Firmware Frustration David Brownell
- Re: [linux-usb-devel] Firmware Frustration Ken Hahn
- Re: [linux-usb-devel] Firmware Frustration David Brownell
- Re: [linux-usb-devel] Firmware Frustration Greg KH
- Re: [linux-usb-devel] Firmware Frustration Oliver Neukum
- Re: [linux-usb-devel] Firmware Frustration Richard W. Knight
- Re: [linux-usb-devel] Firmware Frustration Richard W. Knight
