> But the other one was just as important: the e1000e driver should never have left its hardware configured in a mode where a single stray write could turn it into a brick.
... because, like, it's totally okay for the hardware to be bricked by a single stray write?
Make like Microsoft and blame the driver. :)
It should be a basic manufacturing test to repeatedly write pseudo-random garbage to the entire I/O register space, and check that the hardware never gets into a state that is not recoverable by either a simple power cycle, or, failing that, a factory reset.
... because, like, it's totally okay for the hardware to be bricked by a single stray write?
Make like Microsoft and blame the driver. :)
It should be a basic manufacturing test to repeatedly write pseudo-random garbage to the entire I/O register space, and check that the hardware never gets into a state that is not recoverable by either a simple power cycle, or, failing that, a factory reset.