commit | 3ec9cb28882f8c05a728fc2b92c7bfe9863614ce | [log] [tgz] |
---|---|---|
author | Maximilian Brune <maximilian.brune@9elements.com> | Mon Nov 13 02:07:01 2023 +0100 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jan 24 09:06:30 2024 +0000 |
tree | 8d039494b178c3878c7bf0192fdb29a76542b293 | |
parent | fe205e18be7444d343c47aaa812db005a4dec8ce [diff] |
UPSTREAM: util/ifdtool/ifdtool.c: Add NULL check for fmapname Some boards (e.g. prodrive/hermes) that do not provide their own FMAP and therefore have been generated by the build system (+ ifdtool) experience a failure when trying to build with an IFD that contains regions which do not have equivalent fmap names (set to NULL). Therefore add a NULL check for the fmapname and ignore the region if we do not have an fmapname. (cherry picked from commit 794d1d7f6cb1092e52e24f132baf00d034591ea7) Original-Test: compile prodrive/hermes Original-Signed-off-by: Maximilian Brune <maximilian.brune@9elements.com> Original-Change-Id: Ib4589b7fdbd11d644214ca5601536e9aeb26882f Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/79010 Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Original-Reviewed-by: Lean Sheng Tan <sheng.tan@9elements.com> GitOrigin-RevId: 794d1d7f6cb1092e52e24f132baf00d034591ea7 Change-Id: I25cd45165a12a82585b922f5b6787b01ae2c191a Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/coreboot/+/5042282 Tested-by: ChromeOS Prod (Robot) <chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/coreboot/+/5199729 Auto-Submit: Phoebe Wang <phoebewang@chromium.org> Commit-Queue: Phoebe Wang <phoebewang@chromium.org> Tested-by: Phoebe Wang <phoebewang@chromium.org> Reviewed-by: Cheng Yueh <cyueh@chromium.org>
coreboot is a Free Software project aimed at replacing the proprietary BIOS (firmware) found in most computers. coreboot performs a little bit of hardware initialization and then executes additional boot logic, called a payload.
With the separation of hardware initialization and later boot logic, coreboot can scale from specialized applications that run directly firmware, run operating systems in flash, load custom bootloaders, or implement firmware standards, like PC BIOS services or UEFI. This allows for systems to only include the features necessary in the target application, reducing the amount of code and flash space required.
coreboot was formerly known as LinuxBIOS.
After the basic initialization of the hardware has been performed, any desired “payload” can be started by coreboot.
See https://www.coreboot.org/Payloads for a list of supported payloads.
coreboot supports a wide range of chipsets, devices, and mainboards.
For details please consult:
ANY_TOOLCHAIN
Kconfig option if you’re feeling lucky (no support in this case).Optional:
make menuconfig
and make nconfig
)Please consult https://www.coreboot.org/Build_HOWTO for details.
If you want to test coreboot without any risks before you really decide to use it on your hardware, you can use the QEMU system emulator to run coreboot virtually in QEMU.
Please see https://www.coreboot.org/QEMU for details.
Further details on the project, a FAQ, many HOWTOs, news, development guidelines and more can be found on the coreboot website:
You can contact us directly on the coreboot mailing list:
https://www.coreboot.org/Mailinglist
The copyright on coreboot is owned by quite a large number of individual developers and companies. Please check the individual source files for details.
coreboot is licensed under the terms of the GNU General Public License (GPL). Some files are licensed under the “GPL (version 2, or any later version)”, and some files are licensed under the “GPL, version 2”. For some parts, which were derived from other projects, other (GPL-compatible) licenses may apply. Please check the individual source files for details.
This makes the resulting coreboot images licensed under the GPL, version 2.