[adding flashrom@flashrom.org to CC]
On 28.09.2010 22:16, Aurélien wrote:
On Tue, Sep 28, 2010 at 9:55 PM, Peter Stuge peter@stuge.se wrote:
Aurélien wrote:
I tried to make a patch which reads from /dev/mem directly in 2 ways:
- mmap()ing /dev/mem, but it seemed that it would be too specific a
modification to be accepted.
See http://stuge.se/physrd.c for a fairly generic tool to do this.
You're right, splitting the feature in two tools seems much more correct. This way we can extract the ROM image, then extract the specific payload.
Well, for that purpose it's much better to simply use flashrom.
Probably, but flashrom takes slighly more time due to various calibration routines (I could not find a way to disable those, but I didn't try very hard),
If you already have a known-good delay function with microsecond precision, you could use that instead of waiting for flashrom to calibrate its own delay loop.
and is less integrable that just reading like this. I don't need much portability between mainboards anyways.
Yes, libflashrom is still not completely done. Most of the parts are there, and we even have a bunch of different frontends, but the exported interface needs to be decided upon before we start offering libflashrom
In the general case however, you are right, the flashrom method seems much more robust.
Thanks!
Regards, Carl-Daniel