| commit | 73acb96ab666f5016b26277b87a1663c081ccef0 | [log] [tgz] |
|---|---|---|
| author | Rob Barnes <robbarnes@google.com> | Wed Mar 08 13:54:41 2023 -0700 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Mar 21 15:45:18 2023 +0000 |
| tree | 9cd3982f35e0bda4c6ffe702332209a100f78f35 | |
| parent | 8a10b126ded398d42138da2d8883c72a180fe92e [diff] |
UPSTREAM: mb/google/dedede: Add EC_HOST_EVENT_PANIC to SCI mask Adding EC_HOST_EVENT_PANIC to SCI mask allows the EC to interrupt the Kernel when an EC panic occurs. If system safe mode is also enabled on the EC, the kernel will have a short period to extract and save info about the EC panic. BUG=b:268377440 BRANCH=firmware-dedede-13606.B TEST=Observe kernel ec panic handler run when ec panics (cherry picked from commit 074d096ffed33f5ddaa24557bb2f20f51123891d) Original-Change-Id: I24f929ae60a406d0091956dc6cab3e2876ca23e9 Original-Signed-off-by: Rob Barnes <robbarnes@google.com> Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/73618 Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Original-Reviewed-by: Karthik Ramasubramanian <kramasub@google.com> Original-Reviewed-by: Eric Lai <eric_lai@quanta.corp-partner.google.com> GitOrigin-RevId: 074d096ffed33f5ddaa24557bb2f20f51123891d Change-Id: I8332c9f60c31b4daff6fc32c3459ccec444e94fa Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/coreboot/+/4346472 Reviewed-by: Karthikeyan Ramasubramanian <kramasub@google.com> Tested-by: Rob Barnes <robbarnes@google.com> Commit-Queue: Karthikeyan Ramasubramanian <kramasub@google.com>
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.