good to see the boot/reboot behavior finally getting some love in the linux desktop.
with this and what systemd brings am becoming much happy.
Sadly, broken hardware (or broken BIOS that causes broken-hardware-like behavior) is the safe bet when it comes to PC. Perhaps not for any specific piece of hardware, but for a randomly-chosen PC there's a good chance that it has at least one quirk calling for a similarly ugly workaround. If the workarounds were all configurable, configuring a custom kernel would go from "slightly tedious" to "black art".
Originally Posted by droidhacker
If you read the blog post, you'll find out why they point to 0x0CF9. It's bad because it's an undocumented feature, not standardised, and strictly speaking requires a pair of magic words, though appears to work with only one written twice. That's how I read it anyhow.
Originally Posted by Detructor
Basically the way to signal a reset/reboot to the system is about as murky and abhorrent as the wireless mbus standard.