|
Note: deloptes response to my unintentional off list message
This is correct, but eeprom is expensive, so to save cost you let your device use the PCs memory and resources. So when you start the device and load the driver. The driver requests the firmware to be loaded from the PC - this gives the device the software part to operate properly. You stop the device and it forgets everything.
firmware is correct, because it is the device specific part to operate the device specific hardware. You have to adjust the part with the loading into eeprom - just that many do not have such, because they always operate connected to the PC. It makes sense.
regards
On Sat, Mar 7, 2020 at 3:21 PM <rhkramer@gmail.com> wrote:
From the peanut gallery (at least with respect to this thread -- in other
words, at least a little "off thread" (but not quite off topic, imho):
I'm puzzled about the discussion about loading firmware with the driver (iiuc,
when the driver is loaded).
My (past?) understanding of firmware is that it is software that is loaded into
what I'll call an external device (although it could be a "smart" internal
device -- something that needs and can run some software to make it work
"properly" (for some definition of properly).
But also that it is loaded into some variation of persistent memory (eProm or
similar) -- thus, you don't have to install firmware each time you connect to a
device (well, I mean, each time the driver for a device is installed into the
"host" device), but only on rare ocassions (sp?) when the firmware needs to be
updated.
I guess the meaning of firmware has changed somewhat??
On Saturday, March 07, 2020 07:50:03 AM deloptes wrote:
|