was reading kernel code and found this gem. yay for efipic.twitter.com/C3m5aZULCu
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
It's so depressing that OS/kernel devs consider running bios/efi firmware (after OS has taken over) acceptable.
I suspect it's less "acceptable" and more "resigned to accepting it, because the alternatives are harder"
Seems like, for device drivers, developer doing the RE & devel could run it in virtual env, log what it does, and then throw it away.
For board-specific stuff, could run in virtualization/emu at runtime & subject it to normal mmu permissions.
Ok, what does this gain you? What do you do when your firmware crashes? What do you do when the firmware bricks itself (the set variable bug)?
1. Immunity to buggy firmware introducing mem corruption or vulns. 2. Reset or disable the device. 3. Vars are all virtual; you can reset at every init.
1. It can still trash various board level devices 2. Uh, what? How do you reset the firmware? (Answer: You reboot the PC) 3. This defeats the entire reason of writing firmware vars which is reconfiguring it and/or preserving data across boots
1. Depends on what you allow it access to. 2. You run the virtualized reset code or use pm interfaces to hard power-cycle the specific device. 3. Yes, getting rid of statefullness is part of the point.
except, you know, I *want* to be able to adjust the boot options from within my OS
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.