Re: firmware status for eagle-usb-*
Josh Triplett writes:
> The driver contains code to interact with the firmware in operating the
> hardware device, just as the program contains code to interact with the
> library in performing its function. The driver does not contain all the
> code needed to manage the device; it contains code that can interact
> with the firmware. This particular driver interacts exclusively with
> the firmware, not the device (except for handing the firmware to the
> device). The driver is no more complete without the firmware than the
> program without the library.
Exactly how does the driver interact with the firmware, except as an
opaque blob when sending the firmware to the device?