commit | b9342043b49cea7ea20a32c677883847c30792e5 | [log] [tgz] |
---|---|---|
author | Mac Chiang <mac.chiang@intel.com> | Thu Jun 29 08:37:08 2023 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jul 12 03:26:17 2023 |
tree | eb8c10c28b684b38dacd2b76f1172f0d4eacb564 | |
parent | 64635d182f6e8ed9b5a7a4c2b1df0269a40c83eb [diff] |
UPSTREAM: mb/google/brya: put Bluetooth VPGIOs overridable The BT VGPIOs pad config in variant of gpio.c won't be overwritten on board eventually because no matched gpios existed here. Put BT VGPIOs in gpio_table, ensure that these were able to be overwritten. The fix included crota and omnigul BT offload work successfully. BUG=b:264834572 TEST=test Bluetooth offload playback/capture in SCO profile. (cherry picked from commit 538bcf54c630088c84114001d100605b0d31a76b) Original-Change-Id: I62cecf26abd0411f7cbb0a56b8b8f0a25d370c69 Original-Signed-off-by: Mac Chiang <mac.chiang@intel.com> Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/76247 Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Original-Reviewed-by: Eric Lai <eric_lai@quanta.corp-partner.google.com> Original-Reviewed-by: Derek Huang <derekhuang@google.com> GitOrigin-RevId: 538bcf54c630088c84114001d100605b0d31a76b Change-Id: I7f7c68cc1a3606e7c2a5d67520c688fae76a3c2a Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/coreboot/+/4675241 Tested-by: Jamie Chen <jamie_chen@compal.corp-partner.google.com> Reviewed-by: Ivan Chen <yulunchen@google.com> Commit-Queue: Ivan Chen <yulunchen@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.