diff options
| author | Jon Murphy <jpmurphy@google.com> | 2022-06-28 10:36:23 -0600 |
|---|---|---|
| committer | Felix Held <felix-coreboot@felixheld.de> | 2022-07-04 14:02:26 +0000 |
| commit | c4e90454f4e3787c9e5d0b7aa758ee9b5757df4b (patch) | |
| tree | ad1a49b4477d62eb6604e3332b6ffc4a64daed06 /Documentation/lib | |
| parent | dc86804a7db0ac67b81803d1662608320c8838a7 (diff) | |
treewide: Unify Google branding
Branding changes to unify and update Chrome OS to ChromeOS (removing the
space).
This CL also includes changing Chromium OS to ChromiumOS as well.
BUG=None
TEST=N/A
Change-Id: I39af9f1069b62747dbfeebdd62d85fabfa655dcd
Signed-off-by: Jon Murphy <jpmurphy@google.com>
Reviewed-on: https://review.coreboot.org/c/coreboot/+/65479
Reviewed-by: Jack Rosenthal <jrosenth@chromium.org>
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Felix Singer <felixsinger@posteo.net>
Diffstat (limited to 'Documentation/lib')
| -rw-r--r-- | Documentation/lib/flashmap.md | 2 | ||||
| -rw-r--r-- | Documentation/lib/fw_config.md | 10 |
2 files changed, 6 insertions, 6 deletions
diff --git a/Documentation/lib/flashmap.md b/Documentation/lib/flashmap.md index 68d0ab5dc7..f0816cf493 100644 --- a/Documentation/lib/flashmap.md +++ b/Documentation/lib/flashmap.md @@ -4,7 +4,7 @@ [Flashmap](https://code.google.com/p/flashmap) (FMAP) is a binary format to describe partitions in a flash chip. It was added to coreboot to support the -requirements of Chromium OS firmware but then was also used in other scenarios +requirements of ChromiumOS firmware but then was also used in other scenarios where precise placement of data in flash was necessary, or for data that is written to at runtime, as CBFS is considered too fragile for such situations. The Flashmap implementation inside coreboot is the de facto standard today. diff --git a/Documentation/lib/fw_config.md b/Documentation/lib/fw_config.md index d5f0bb2d06..c9eaeecdab 100644 --- a/Documentation/lib/fw_config.md +++ b/Documentation/lib/fw_config.md @@ -8,8 +8,8 @@ BIOS image to be used across a wide variety of devices which may have key differ otherwise similar enough to use the same coreboot build target. The initial implementation is designed to take advantage of a bitmask returned by the Embedded -Controller on Google Chrome OS devices which allows the manufacturer to use the same firmware -image across multiple devices by selecting various options at runtime. See the Chromium OS +Controller on Google ChromeOS devices which allows the manufacturer to use the same firmware +image across multiple devices by selecting various options at runtime. See the ChromiumOS [Firmware Config][1] documentation for more information. This firmware configuration interface differs from the CMOS option interface in that this @@ -91,7 +91,7 @@ file in CBFS use the value it contains when matching fields and options. ### Embedded Controller -Google Chrome OS devices support an Embedded Controller interface for reading and writing the +Google ChromeOS devices support an Embedded Controller interface for reading and writing the firmware configuration value, along with other board-specific information. It is possible for coreboot to read this value at boot on systems that support this feature. @@ -101,9 +101,9 @@ possible by enabling the CBFS source and coreboot will look in CBFS first for a before asking the embedded controller. It is also possible to adjust the value in the embedded controller *(after disabling write -protection)* with the `ectool` command in a Chrome OS environment. +protection)* with the `ectool` command in a ChromeOS environment. -For more information on the firmware configuration field on Chrome OS devices see the Chromium +For more information on the firmware configuration field on ChromeOS devices see the Chromium documentation for [Firmware Config][1] and [Board Info][2]. [1]: http://chromium.googlesource.com/chromiumos/docs/+/master/design_docs/firmware_config.md |