Am 05.05.2009 19:07, schrieb Peter Stuge:
'next' foils the desirable property that single files in cbfs can be
updated in the flash chip without touching any other regions.
Two options:
1. have next point to 0xffffffff and replace the whole block it's in
2. have next point to a validated clean area (esp. no magic) and force
the next cbfs_file header there.
2. is better, but there might be the rare corner case that the intended
area is fixed memory for a new entry.
I guess we can live with that, right?
Patrick
--
coreboot mailing list: [email protected]
http://www.coreboot.org/mailman/listinfo/coreboot
