Am 27.02.2010 15:41, schrieb Stefan Reinauer:
On 2/27/10 2:57 PM, Peter Stuge wrote:
Um..? Oh, ok, they aren't all bootsplash types. But, I think there should be just one meaningful parameter for each file. My point is that a bootsplash type is redundant, since a specific filename must already be used for bootsplashes. The same is true for VSA.
Since we only do name based matching in coreboot anyways, do you suggest we drop the type field?
I intend to add a header for option roms "real soon now", which contains compression type and vendor/device ids. That way, the filename can be the official filename (with version number and other information, etc) by the vendor, if available.
The remaining question is how we handle multiple boot paths (fallback/normal, for example) then. Still look for prefixes?
I even forgot a type: cpu microcode.
Sure would be nice to have the microcode uploader just fetch it from CBFS, instead of compiling it in.
Patrick