commit | 671ea3e823258ac9be828b7bfba2a00fc3c379d1 | [log] [tgz] |
---|---|---|
author | John Zhao <john.zhao@intel.com> | Fri Jan 08 22:33:04 2021 -0800 |
committer | Commit Bot <commit-bot@chromium.org> | Mon Jan 25 20:01:40 2021 +0000 |
tree | a1423715f18c4f1aff0df8ef43b1397fb8119b03 | |
parent | 4cca9695e6c3fc448237842a47f175cfe555ab51 [diff] |
UPSTREAM: ec/google/chromeec: Provide EC access for Retimer firmware update Kernel needs to access EC RFWU entry in order to retrieve from EC about port and mux info and set EC operations like modes change. This change provides EC RFWU path and update for Retimer driver usage. BUG=b:162528867 BRANCH=firmware-volteer-13672.B TEST=Booted to kernel and verified EC RFWU path from ACPI SSDT table. Change-Id: I8265106bf4812c28d6ff9a24ab543e76a8dba603 Signed-off-by: Patrick Georgi <pgeorgi@google.com> Original-Commit-Id: eec3e3b3d979d56aaea1ffc04dcd6ea86b2d7b0e Original-Signed-off-by: John Zhao <john.zhao@intel.com> Original-Change-Id: I3817d93cfdeedf15825dab6c537b151fd063338b Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/49257 Original-Reviewed-by: Tim Wawrzynczak <twawrzynczak@chromium.org> Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/coreboot/+/2645003 Reviewed-by: Patrick Georgi <pgeorgi@chromium.org> Tested-by: Patrick Georgi <pgeorgi@chromium.org> Commit-Queue: Patrick Georgi <pgeorgi@chromium.org> (cherry picked from commit 969756bb462f9d530832bd5ae1c2e55a95c419d1) Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/coreboot/+/2648087 Reviewed-by: Tim Wawrzynczak <twawrzynczak@chromium.org> Commit-Queue: Tim Wawrzynczak <twawrzynczak@chromium.org> Tested-by: Tim Wawrzynczak <twawrzynczak@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.