On 13.05.2008 02:59, Peter Stuge wrote:
On Mon, May 12, 2008 at 03:36:29PM -0400, Kevin O'Connor wrote:
There are several ways to support per-board info in "legacybios":
Have legacybios populate the information:
By a) compiling legacybios on a board by board basis with info for each board merged into the compile process
or b) have the info passed to legacybios from corebios in some raw format, and then have legacybios build the PC specific tables from it
or, have coreboot build the PC specific tables:
and c) put them somewhere in memory where legacybios can then copy it to the 0xf0000 segment
or d) work out some arrangement where coreboot puts them into 0xf0000 in such a way that legacybios doesn't overwrite those areas when it is also loaded into that segment.
I strongly prefer b) above over anything else. I specifically do not want coreboot to know about BIOS tables. coreboot already exports some information. If legacybios needs more information, let's add that to the coreboot tables.
We already have some (external, probably not committed) code to create per-board ACPI tables and other stuff. Having a payload generate this from e.g. the device tree needs a device tree parser in the payload, a thing I'd like to avoid for size reasons. Having a Kconfig option "Generate legacy tables" would be the way to go IMHO.
Regards, Carl-Daniel