3 ms·
And we'll deal with all those old standards by having our own new standard! He discusses "open firmware", which is not Open Firmware.[1] That was a boot ROM sy
by Animats 6y ago
And we'll deal with all those old standards by having our own new standard!
He discusses "open firmware", which is not Open Firmware.[1] That was a boot ROM system from the 1990s. It was written in Forth, and was intended for use with a console interface. That's not what you want today. A good question to ask is, what do you want today at that level, and what do you not want. For example, a security oriented "cloud" company might want to load the machine, restart the machine, and freeze and dump the machine in an emergency, but not have the ability to examine or alter memory while running. Who patches a running production machine any more? Today's server firmware, with an administrative CPU that phones home and listens for commands to do who knows what, tends to have way too much capability for making small changes quietly and listening to what's going on.
[1] https://en.wikipedia.org/wiki/Open_Firmware https://en.wikipedia.org/wiki/Open_Firmware