Hi there. I'm at #flashrom at freenode, but no one responds... so... can you give me a hand?
Here's the problem: http://pastebin.com/m11614dbc
Thanks!
On Mon, Nov 9, 2009 at 2:00 PM, NotLim notlim@gmail.com wrote:
Hi there. I'm at #flashrom at freenode, but no one responds... so... can you give me a hand?
Here's the problem: http://pastebin.com/m11614dbc
uh, you were doing this on a spare part right?
Please say yes.
ron
On 09.11.2009 23:35, ron minnich wrote:
On Mon, Nov 9, 2009 at 2:00 PM, NotLim notlim@gmail.com wrote:
Hi there. I'm at #flashrom at freenode, but no one responds... so... can you give me a hand?
Here's the problem: http://pastebin.com/m11614dbc
uh, you were doing this on a spare part right?
Please say yes.
This has been resolved. Everything is OK.
Note: We really should read the entire chip before any erase/write operation so that we can detect if the chip is unchanged and issue a less scary error message in that case.
Regards, Carl-Daniel
Carl-Daniel Hailfinger wrote:
Note: We really should read the entire chip before any erase/write operation so that we can detect if the chip is unchanged and issue a less scary error message in that case.
Acked-by: Stefan Reinauer stepan@coresystems.de
:-) Can this be extended? For many BIOS brands things are not completely critical unless you erase the last flash block. So maybe we could have emergency levels of green, yellow and red? :-)
Stefan