Here was my thought.
checkrom -- check a rom. Apply all the tests to the rom that coreboot/seabios would apply before running it. User is required to provide (symbolic or numeric) vendor and deviceid for the device. If there is a problem, ask the user what to do, e.g. if we have: no valid vendor info are (a la QEMU VGA BIOS) no valid vendor id no valid device id The program can talk to the user about what is going wrong. Also, the tool can output commands to be used for:
fixrom -- fix a rom. takes switches such as --vendorid --deviceid --create-info-area and others as needed.
mailrom -- given a broken rom, send mail to the author(s) about what is wrong and how to fix it :-) options: --mailbomb mail the users every day until it is fixed. Might actually get QEMU VGA BIOS repaired :-)
Thanks
ron