commit | 7adebae84e6d414107f3a0eebe18c17755c58212 | [log] [tgz] |
---|---|---|
author | Edward O'Callaghan <quasisec@google.com> | Mon Dec 30 08:27:53 2019 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Jan 02 08:15:48 2020 |
tree | 3c00b75b6206d2c1816d962ee0cd647987344a38 | |
parent | 55392acd7b86e7ab5b0cb3f4be45730b8345efbc [diff] |
UPSTREAM: mainboard/google/puff: Enable net driver on pcie ep Let coreboot know there is a NIC device on the end so that the mac from vpd is set at early boot. Properly configure the link-leds in devicetree s.t. valid values are written out to the register at initialization. BUG=b:146592075,146999042,146999043 BRANCH=none TEST=Boot to kernel. Insert mac address into VPD vpd -s ethernet_mac=<address> reboot the system. Ensure we have ip address and corresponding mac address with ifconfig. Ensure ethernet controller shows up with lspci. Signed-off-by: Edward O'Callaghan <quasisec@google.com> Original-Commit-Id: 731e6288e6f6117951ca407a651e25f346843621 Original-Change-Id: I76ce6d8a5a26842fcb2544ee96567fe0da8603b1 Original-Signed-off-by: Edward O'Callaghan <quasisec@google.com> Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/38003 Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Original-Reviewed-by: Daniel Kurtz <djkurtz@google.com> Change-Id: I6e6ce69d165beb1a8750fffce047ba0865fa982f Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/coreboot/+/1985640 Reviewed-by: Edward O'Callaghan <quasisec@chromium.org> Commit-Queue: Edward O'Callaghan <quasisec@chromium.org> Tested-by: Edward O'Callaghan <quasisec@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.