Journal 2TecTom's Journal: Flash embedded device drivers 3
With the current memeory prices, why don't hardware device manufactures include enough EPROM storage to be able to flash the current version of the device's driver? This would allow for faster installs and more comprehesive system recovery. As well, if there was sufficent space, you could store a diagnostics, original, reference, or signed driver there. In fact, using OTP memory would allow the system access to a copy of a secure, signed and uncorrupted driver.
Old idea of mine (Score:2)
1) What do you support? Windows 95/98/me/NT/2000/XP/2003? Linux binaries/rpm/deb/...?
2) Standards. Not a terrible problem, but it would need to be a standard process for convenience and function. How to access. How to update. How to mount...
3) Additional costs. Sure, 128 MB of flash isn't that expensive, but you also need the controller. You'd want it to be like a USB device in capability, but not mounted the same way. For some things it wouldn't be bad - a printer with 256 of
Re:Old idea of mine (Score:2)
Standards? That's up to the IEEE, isn't it?
Cost? I'd be more than willing to pay, wouldn't you?
BTW, it's kinda nice to know somebody reads these things!
Re:Old idea of mine (Score:2)
Semi-portable storage for important or private files buried in the flash memory of your video or network card.
A RAID/JBOD array of small flash components. If spread out over PCI, USB, and other buses, if could even perform decently.
Hey, it could happen.
--
I'm fond of my Computer Future [slashdot.org].
In 1993, I used FutureBASIC to dump the memory of my Mac LC II to my hard drive, and thought, "Wouldn't it be awe