3 ms·
Many people make a distinction when the firmware is stored on the hardware and loaded by the hardware itself vs stored in the filesystem and loaded in cooperati
by toast0 4y ago
Many people make a distinction when the firmware is stored on the hardware and loaded by the hardware itself vs stored in the filesystem and loaded in cooperation between system software and the hardware.
Personally, this distinction doesn't make that much sense, if the firmware is opaque in both instances, eliminating (or vastly reducing) onboard storage seems like a cost reduction step that benefits the manufacturer and the user. [1] A more important distinction to me is if the interface documentation and drivers are open or closed.
[1] unless the device class is one that could be a boot time device, except that firmware loading would be required --- it's hard to pxe boot from a network card if it doesn't function without a firmware upload, and that's not good for users who may want to pxe boot at some point