Hi Ron,
On 22.12.2017 03:30, ron minnich wrote:
A simple off-by-one. The driver in question always sent one byte too much which causes trouble if you accidentally write garbage to your flash chip's second status register. Some chips enable write protection that way and certain firmware doesn't work reliable any more in that state :D
Don't ask me why it writes to the status register at all by default. I don't remember.
Nico
Hello! I wouldn't want to. Incidentally I run (sometimes) Slackware64 here. Currently its at release 14.2 with the usual updates, and a heck of a lot of things in their current location.
And I noticed in that article an interesting smattering of typical English expressions. ----- Gregg C Levine gregg.drwho8@gmail.com "This signature fought the Time Wars, time and again."
On Thu, Dec 21, 2017 at 9:42 PM, Nico Huber nico.h@gmx.de wrote:
Hi Ron,
On 22.12.2017 03:30, ron minnich wrote:
A simple off-by-one. The driver in question always sent one byte too much which causes trouble if you accidentally write garbage to your flash chip's second status register. Some chips enable write protection that way and certain firmware doesn't work reliable any more in that state :D
Don't ask me why it writes to the status register at all by default. I don't remember.
Nico
-- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot