diff options
author | Stefan Reinauer <stefan.reinauer@coreboot.org> | 2015-05-05 13:10:04 -0700 |
---|---|---|
committer | Stefan Reinauer <stefan.reinauer@coreboot.org> | 2015-05-06 19:09:47 +0200 |
commit | 4d8b843d3740cc90c98f181d49f0d4a67cb0a1b7 (patch) | |
tree | 19306425b170975b5317a63a84b0e6f4b94b5f40 /documentation/abi-data-consumption.txt | |
parent | 29ed46caccd5cea8401c5d133895fa3a9d6f5030 (diff) |
Rename documentation -> Documentation
In order to be closer to the Linux kernel source tree
structure, rename documentation to Documentation.
Change-Id: I8690f666638ef352d201bd3c3dc1923b0d24cb12
Signed-off-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
Reviewed-on: http://review.coreboot.org/10110
Tested-by: build bot (Jenkins)
Reviewed-by: Patrick Georgi <pgeorgi@google.com>
Diffstat (limited to 'documentation/abi-data-consumption.txt')
-rw-r--r-- | documentation/abi-data-consumption.txt | 22 |
1 files changed, 0 insertions, 22 deletions
diff --git a/documentation/abi-data-consumption.txt b/documentation/abi-data-consumption.txt deleted file mode 100644 index 81442e7170..0000000000 --- a/documentation/abi-data-consumption.txt +++ /dev/null @@ -1,22 +0,0 @@ -This text describes the ABI coreboot presents to downstream users. Such -users are payloads and/or operating systems. Therefore, this text serves -at what can be relied on for downstream consumption. Anything not explicitly -listed as consumable is subject to change without notice. - -Background and Usage - -coreboot passes information to downstream users using coreboot tables. These -table definitions can be found in src/include/boot/coreboot_tables.h and -payloads/libpayload/include/coreboot_tables.h respectively within coreboot -and libpayload. One of the most vital and important pieces of information -found within these tables is the memory map of the system indicating -available and reserved memory. - -In 2009 cbmem was added to coreboot. The "CBMEM high table memory manager" -serves a way for coreboot to bookkeep its own internal data. While some -of this data may be exposed through the coreboot tables the data structures -used to manage the data within the cbmem area is subject to change. - -Provided the above, if one needs a piece of data exposed to the OS -or payload it should reside within the coreboot tables. If it isn't there -then a code change will be required to add it to the coreboot tables. |