On Tue, May 08, 2018 at 11:57:38AM +0100, Daniel Thompson wrote:
No sure how other OSes like Windows or ubuntu make this happen. But they do call SetVariable during runtime such as to set OsIndications or BootNext to reboot to BIOS system utility.
Sorry, just noticed no one responded to this.
The simple answer is that machines that run Windows always have a storage for the sole use of firmware - so the conflict of ownership between firmware and operating system never occurs.
Draft specs says EBBR is OS neutral, I hope we will follow the same. Then shouldn't we say use *dedicated* storage for firmware. or we are going to say, use this for windows and that for Linux. If we talk about device sharing (not now) but later it should be OS neutral.
The E in EBBR is embedded... and for some applications embedded implies significant work to reduce the BOM; cents do sometimes matter (and they certainly add up for high volume boards). This makes me very uncomfortable requiring additional storage, even for the relatively well resourced devices EBBR is likely to suit best.
I was certainly not suggesting anything else, merely pointing out why Windows platforms don't have this problem.
If the EBBR is not OS neutral, it is pointless.
/ Leif