API - Revision history

Uwe: Updates, new tags.

2010-09-22T07:52:20Z

Updates, new tags.

KevinOConnor: Note new name "SeaBIOS" instead of "LegacyBIOS"

2009-03-07T16:55:04Z

Note new name "SeaBIOS" instead of "LegacyBIOS"

Uwe at 21:46, 5 October 2008

2008-10-05T21:46:56Z

Stepan at 16:09, 18 June 2008

2008-06-18T16:09:27Z

Stepan at 16:08, 18 June 2008

2008-06-18T16:08:08Z

Stepan at 16:07, 18 June 2008

2008-06-18T16:07:33Z

Stepan at 16:05, 18 June 2008

2008-06-18T16:05:44Z

Stepan at 00:50, 18 June 2008

2008-06-18T00:50:21Z

Stepan: New page: coreboot provides a couple of means to pass information on to the OS and payloads. * coreboot table * pirq table * mp table * ACPI tables * Legacy BIOS interrupt calls (with [[LegacyBIOS]...

2008-06-18T00:45:33Z

New page: coreboot provides a couple of means to pass information on to the OS and payloads. * coreboot table * pirq table * mp table * ACPI tables * Legacy BIOS interrupt calls (with [[LegacyBIOS]...

New page

coreboot provides a couple of means to pass information on to the OS and payloads.

* coreboot table
* pirq table
* mp table
* ACPI tables
* Legacy BIOS interrupt calls (with [[LegacyBIOS]])

coreboot passes control to a payload or OS in form of a self contained ELF binary.

= coreboot table =

The one central data structure in coreboot is the coreboot table. It is an extensible data structure providing the information gathered by coreboot to payloads and operating systems.

The table usually sits in memory around address 0x500. FIXME: describe how to search for the table correctly.

The table header looks like this:

<source lang="C">
struct lb_header
{
uint8_t signature[4]; /* LBIO */
uint32_t header_bytes;
uint32_t header_checksum;
uint32_t table_bytes;
uint32_t table_checksum;
uint32_t table_entries;
};
</source>

Every entry in the boot enviroment list will correspond to a boot
info record. Encoding both type and size. The type is obviously
so you can tell what it is. The size allows you to skip that
boot enviroment record if you don't know what it easy. This allows
forward compatibility with records not yet defined.

<source lang="C">
struct lb_record {
uint32_t tag; /* tag ID */
uint32_t size; /* size of record (in bytes) */
};
</source>

== Entry Types ==
<source lang="C">
#define LB_TAG_UNUSED 0x0000
#define LB_TAG_MEMORY 0x0001
#define LB_TAG_HWRPB 0x0002
#define LB_TAG_MAINBOARD 0x0003
#define LB_TAG_VERSION 0x0004
#define LB_TAG_EXTRA_VERSION 0x0005
#define LB_TAG_BUILD 0x0006
#define LB_TAG_COMPILE_TIME 0x0007
#define LB_TAG_COMPILE_BY 0x0008
#define LB_TAG_COMPILE_HOST 0x0009
#define LB_TAG_COMPILE_DOMAIN 0x000a
#define LB_TAG_COMPILER 0x000b
#define LB_TAG_LINKER 0x000c
#define LB_TAG_ASSEMBLER 0x000d
// 0x000e is used by device tree entry?
#define LB_TAG_SERIAL 0x000f
#define LB_TAG_CONSOLE 0x0010
#define LB_TAG_CMOS_OPTION_TABLE 200

#define LB_TAG_OPTION 201
#define LB_TAG_OPTION_ENUM 202
#define LB_TAG_OPTION_DEFAULTS 203
#define LB_TAG_OPTION_CHECKSUM 204

@@ Line 7: / Line 7: @@
 * [[Glossary#MPTable|MP table]]
 * [[ACPI_in_coreboot|ACPI tables]]
-* Legacy BIOS interrupt calls (with [[LegacyBIOS]])
+* Legacy BIOS interrupt calls (with [[SeaBIOS]])
 == Code execution ==

@@ Line 1: / Line 1: @@
 coreboot provides a couple of means to pass information on to the OS and payloads.
-* coreboot table
+* [[#coreboot_table|coreboot table]]
 * [[Creating_Valid_IRQ_Tables|IRQ table]]
 * [[Glossary#MPTable|MP table]]

@@ Line 2: / Line 2: @@
 * coreboot table
-* [[Creating_Valid_IRQ_Tables|pirq table]]
+* [[Creating_Valid_IRQ_Tables|IRQ table]]
-* mp table
+* [[Glossary#MPTable|MP table]]
 * [[ACPI_in_coreboot|ACPI tables]]
 * Legacy BIOS interrupt calls (with [[LegacyBIOS]])

@@ Line 33: / Line 33: @@
 </source>
-Every entry in the boot enviroment list will correspond to a boot info record. Encoding both type and size. The type is obviously so you can tell what it is. The size allows you to skip that boot enviroment record if you don't know what it easy. This allows forward compatibility with records not yet defined.
+Every entry in the boot enviroment list will correspond to a boot info record. Encoding both type and size. The type is obviously so you can tell what it is. The size allows you to skip that boot enviroment record if you don't know what it is. This allows forward compatibility with records not yet defined.
 <source lang="C">
@@ Line 62: / Line 62: @@
 #define LB_TAG_SERIAL            0x000f
 #define LB_TAG_CONSOLE           0x0010
 #define LB_TAG_CMOS_OPTION_TABLE 200
 #define LB_TAG_OPTION            201

@@ Line 1: / Line 1: @@
-= Tables =
+== Tables ==
-−
-coreboot provides a couple of means to pass information on to the OS and payloads.
 * [[#coreboot_table|coreboot table]]
@@ Line 10: / Line 9: @@
 * Legacy BIOS interrupt calls (with [[LegacyBIOS]])
-= Code Execution =
+== Code execution ==
-coreboot passes control to a payload or OS in form of a self contained ELF binary.
+coreboot passes control to a [[payloads|payload]] or OS in form of a self contained ELF binary.
-= coreboot table =
+The one central data structure in coreboot is the '''coreboot table'''. It is an extensible data structure providing the information gathered by coreboot to payloads and operating systems.
-The one central data structure in coreboot is the coreboot table. It is an extensible data structure providing the information gathered by coreboot to payloads and operating systems.
+The table usually sits in memory around address '''0x500'''. FIXME: describe how to search for the table correctly.
-−
 The table usually sits in memory around address 0x500. FIXME: describe how to search for the table correctly.
 The table header looks like this:
@@ Line 35: / Line 33: @@
 </source>
 Every entry in the boot enviroment list will correspond to a boot info record. Encoding both type and size. The type is obviously so you can tell what it is. The size allows you to skip that boot enviroment record if you don't know what it easy. This allows forward compatibility with records not yet defined.
 Every entry in the boot enviroment list will correspond to a boot
-info record.  Encoding both type and size.  The type is obviously
-so you can tell what it is.  The size allows you to skip that
-boot enviroment record if you don't know what it easy.  This allows
 forward compatibility with records not yet defined.
 <source lang="C">
@@ Line 49: / Line 42: @@
 </source>
 <source lang="C">
-#define LB_TAG_UNUSED           0x0000
+#define LB_TAG_UNUSED            0x0000
-#define LB_TAG_MEMORY           0x0001
+#define LB_TAG_MEMORY            0x0001
-#define LB_TAG_HWRPB            0x0002
+#define LB_TAG_HWRPB             0x0002
-#define LB_TAG_MAINBOARD        0x0003
+#define LB_TAG_MAINBOARD         0x0003
-#define LB_TAG_VERSION          0x0004
+#define LB_TAG_VERSION           0x0004
-#define LB_TAG_EXTRA_VERSION    0x0005
+#define LB_TAG_EXTRA_VERSION     0x0005
-#define LB_TAG_BUILD            0x0006
+#define LB_TAG_BUILD             0x0006
-#define LB_TAG_COMPILE_TIME     0x0007
+#define LB_TAG_COMPILE_TIME      0x0007
-#define LB_TAG_COMPILE_BY       0x0008
+#define LB_TAG_COMPILE_BY        0x0008
-#define LB_TAG_COMPILE_HOST     0x0009
+#define LB_TAG_COMPILE_HOST      0x0009
-#define LB_TAG_COMPILE_DOMAIN   0x000a
+#define LB_TAG_COMPILE_DOMAIN    0x000a
-#define LB_TAG_COMPILER         0x000b
+#define LB_TAG_COMPILER          0x000b
-#define LB_TAG_LINKER           0x000c
+#define LB_TAG_LINKER            0x000c
-#define LB_TAG_ASSEMBLER        0x000d
+#define LB_TAG_ASSEMBLER         0x000d
 // 0x000e is used by device tree entry?
-#define LB_TAG_SERIAL           0x000f
+#define LB_TAG_SERIAL            0x000f
-#define LB_TAG_CONSOLE          0x0010
+#define LB_TAG_CONSOLE           0x0010
 #define LB_TAG_CMOS_OPTION_TABLE 200
+#define LB_TAG_OPTION            201
-#define LB_TAG_OPTION 201
+#define LB_TAG_OPTION_ENUM       202
-#define LB_TAG_OPTION_ENUM 202
+#define LB_TAG_OPTION_DEFAULTS   203
-#define LB_TAG_OPTION_DEFAULTS 203
+#define LB_TAG_OPTION_CHECKSUM   204
-#define LB_TAG_OPTION_CHECKSUM 204
+</source>