Am 28.04.2009 04:00, schrieb Kevin O'Connor:
I'm not convinced that cbfs_optionrom is the right path. I envision storing splash screens, config files, and disk images in addition to option roms. I don't want to add cbfs support for each new file.
Quite simple: There will be a generic header for everything that doesn't require special handling. And that header comes with a compression field, too.
As for special handling: Payloads are stored in SELF format, and thus "special" Stages are internal to coreboot. Whatever helps coreboot is fine here. Option ROMs contain the vid/did as fields for faster retrieval.
We might want to define a couple of file types (those IDs you use with "cbfstool" as the last argument) for various purposes (eg. the one you mentioned above), but they all would use the same "default" file header.
Once we go the "use filenames to select" route, we're awfully close to the PRECOMPRESSED_PAYLOAD mess in coreboot-v2 configuration. I'd like to avoid that by keeping all matter related to compression within cbfs.
Patrick