| commit | e997fa3311bb94d8d1781c4cf0363b18c9e67270 | [log] [tgz] |
|---|---|---|
| author | Zhuohao Lee <zhuohao@chromium.org> | Thu Mar 11 04:07:57 2021 |
| committer | Commit Bot <commit-bot@chromium.org> | Mon Mar 15 11:24:59 2021 |
| tree | a0fe2fcb5a05e60356ff2ef8d8a3b4d8ebbcf3bb | |
| parent | a9ace5c7e93eb4b757c1b1c13eb16830a7920063 [diff] |
UPSTREAM: rammus: get cbfs sar table name based on the sku id This patch overrides the get_wifi_sar_cbfs_filename() to return different sar table according to the sku id. BUG=b:173465272 TEST=checked bios log and the correct sar table was loaded. Change-Id: Id4c67f0a6f2f6b1fc374002893ae1957093f2f0b Signed-off-by: Patrick Georgi <pgeorgi@google.com> Original-Commit-Id: e6f12d0d5025e276b9022ee2ff9a6d4d195029e8 Original-Change-Id: Ia30d760b1a029197d470818c73bfd2c00514652d Original-Signed-off-by: Zhuohao Lee <zhuohao@chromium.org> Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/51413 Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Original-Reviewed-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/coreboot/+/2759666 Reviewed-by: Patrick Georgi <pgeorgi@chromium.org> Commit-Queue: Patrick Georgi <pgeorgi@chromium.org> Tested-by: Patrick Georgi <pgeorgi@chromium.org> (cherry picked from commit cb6bc8c28eaea5a4cb22f6780b17548e95d866fe) Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/coreboot/+/2759815 Reviewed-by: Zhuohao Lee <zhuohao@chromium.org> Commit-Queue: Zhuohao Lee <zhuohao@chromium.org> Tested-by: Zhuohao Lee <zhuohao@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.