ExternalVendorCode/heads
1
0
Fork 0
mirror of https://github.com/linuxboot/heads.git synced 2024-12-21 05:53:14 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
449977b617
heads/modules/coreboot

257 lines
10 KiB
Makefile
Raw Normal View History

non-coreboot-builds: do not error if CONFIG_COREBOOT_VERSION is not set Signed-off-by: Trammell hudson <hudson@trmm.net>
2020-11-25 13:43:07 +00:00
ifeq "$(CONFIG_COREBOOT)" "y"
Allow using files other than coreboot.rom Talos 2 will need signed ROM with ECC and an analogous separate bootblock file. Signed-off-by: Sergii Dmytruk <sergii.dmytruk@3mdeb.com>
2021-07-20 20:48:08 +00:00
CONFIG_COREBOOT_ROM ?= coreboot.rom
CONFIG_COREBOOT_BOOTBLOCK ?=
Support targeting PowerPC 64 This prepares most of the modules to be build for it. Signed-off-by: Sergii Dmytruk <sergii.dmytruk@3mdeb.com>
2021-07-18 17:34:20 +00:00
ifeq "$(CONFIG_TARGET_ARCH)" "x86"
COREBOOT_TARGET := i386
LINUX_IMAGE_FILE := bzImage
modules/coreboot: Delete unused remnants of using musl toolchain At one time coreboot was built using Heads' musl toolchain, but this was later reverted. coreboot builds with its own toolchain again. CROSS= has no effect on coreboot proper (only exception is PPC64 skiboot payload). It was added to coreboot by a patch that was deleted in 8e44853. COREBOOT_IASL was set to the default, that was only needed when the toolchain was being overridden to override iasl back to the coreboot one. ppc64 still specifies CROSS= since skiboot is unable to find coreboot's toolchain from XGCCPATH but checks CROSS. This builds skiboot with the Heads toolchain as before. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-08-10 18:01:02 +00:00
COREBOOT_TARGET_CROSS :=
Support targeting PowerPC 64 This prepares most of the modules to be build for it. Signed-off-by: Sergii Dmytruk <sergii.dmytruk@3mdeb.com>
2021-07-18 17:34:20 +00:00
else ifeq "$(CONFIG_TARGET_ARCH)" "ppc64"
COREBOOT_TARGET := ppc64
LINUX_IMAGE_FILE := zImage
modules/coreboot: Clarify PPC64 toolchain comments CROSS= is needed for skiboot on PPC64 due to different endianness relative to coreboot. The talos_2 fork doesn't share the toolchain because it is the only _fork_, not board, to be precise. We could add more boards using that fork without having to create a shared toolchain, it only matters if we add another fork or start building boards from the upstream release too. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-08-11 17:03:58 +00:00
# skiboot payload needs the Heads toolchain as it is little-endian (like
# Linux), but coreboot is big-endian on PPC64.
modules/coreboot: Delete unused remnants of using musl toolchain At one time coreboot was built using Heads' musl toolchain, but this was later reverted. coreboot builds with its own toolchain again. CROSS= has no effect on coreboot proper (only exception is PPC64 skiboot payload). It was added to coreboot by a patch that was deleted in 8e44853. COREBOOT_IASL was set to the default, that was only needed when the toolchain was being overridden to override iasl back to the coreboot one. ppc64 still specifies CROSS= since skiboot is unable to find coreboot's toolchain from XGCCPATH but checks CROSS. This builds skiboot with the Heads toolchain as before. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-08-10 18:01:02 +00:00
COREBOOT_TARGET_CROSS := CROSS=$(CROSS)
Support targeting PowerPC 64 This prepares most of the modules to be build for it. Signed-off-by: Sergii Dmytruk <sergii.dmytruk@3mdeb.com>
2021-07-18 17:34:20 +00:00
else
$(error "$(CONFIG_TARGET_ARCH) target isn't supported by this module")
endif
modules/coreboot: Define each coreboot version as a separate module Define a separate module for each coreboot version, so the module used to build the ROM will optionally be able to reference the toolchain from a different module. This will allow coreboot fork builds to use the toolchain from the corresponding release. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-08-10 20:48:05 +00:00
# Each coreboot version is defined as a separate module, but only the needed
# modules become dependencies of the current board. One coreboot version is
# selected for the toolchain build and firmware build. These can be the same
# (when using a coreboot release) or different (when using a fork that reuses a
# release's toolchain).
# Define a coreboot module. Parameters:
# $1 - module version
# $2 - toolchain coreboot version - if nonempty, uses the toolchain from this
# version (use for forks to avoid building extra copies of the same
# toolchain)
#
# For a coreboot release:
# - the version is the coreboot release version
# - set coreboot-<version>_hash to the tarball hash
# - set coreboot-blobs-<version>_hash to the blobs tarball hash
#
# For a git fork:
# - the version is the name of the fork (just controls the build directory used)
# - set coreboot-<version>_repo to the git repo address
# - set coreboot-<version>_commit_hash to the git commit
define coreboot_module =
coreboot-$(1)_version := $(1)
coreboot-$(1)_module_file := coreboot
coreboot-$(1)_base_dir := coreboot-$(1)
coreboot-$(1)_dir := coreboot-$(1)/$(BOARD)
coreboot-$(1)_toolchain := $(2)
# These are ignored if this version is a git fork
coreboot-$(1)_tar := coreboot-$(1).tar.xz
coreboot-$(1)_url := https://www.coreboot.org/releases/coreboot-$(1).tar.xz
# These are only used for releases, git forks don't use upstream blobs
coreboot-blobs-$(1)_version := $(1)
coreboot-blobs-$(1)_module_file := coreboot
coreboot-blobs-$(1)_dir := coreboot-$(1)/3rdparty
coreboot-blobs-$(1)_tar := coreboot-blobs-$(1).tar.xz
coreboot-blobs-$(1)_url := https://www.coreboot.org/releases/coreboot-blobs-$(1).tar.xz
coreboot-blobs-$(1)_tar_opt := --strip 2
endef
# coreboot releases
coreboot-4.11_hash := 97fd859b4c39a25534fe33c30eb86e54a233952e08a024c55858d11598a8ad87
coreboot-blobs-4.11_hash := aa7855c5bd385b3360dadc043ea6bc93f564e6e4840d9b3ee5b9e696bbd055db
$(eval $(call coreboot_module,4.11,))
coreboot-4.19_hash := 65ccb2f46535b996e0066a1b76f81c8cf1ff3e27df84b3f97d8ad7b3e7cf0a43
coreboot-blobs-4.19_hash := 30214caed07b25f11e47bec022ff6234841376e36689eb674de2330a3e980cbc
$(eval $(call coreboot_module,4.19,))
coreboot-4.20.1_hash := b41539a8c2eab2fec752157eb4acbd0e2a637a7203530c12e66b43a5c3c3a931
coreboot-blobs-4.20.1_hash := 30f9d8618e78d483d0903976982485e70825ca3469efd17902c9246aaefd7c4a
$(eval $(call coreboot_module,4.20.1,))
# coreboot git forks
modules/coreboot: Clarify PPC64 toolchain comments CROSS= is needed for skiboot on PPC64 due to different endianness relative to coreboot. The talos_2 fork doesn't share the toolchain because it is the only _fork_, not board, to be precise. We could add more boards using that fork without having to create a shared toolchain, it only matters if we add another fork or start building boards from the upstream release too. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-08-11 17:03:58 +00:00
# talos_2 could use the 4.20.1 toolchain, but it's the only ppc64 fork, so
modules/coreboot: Don't try to share toolchain for talos_2 fork The skiboot build fails to find the toolchain when it's not in the default location. There is only one ppc64 board anyway, so there's no point trying to share a toolchain for now. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-08-11 13:32:30 +00:00
# there is no point preparing another coreboot module that won't be shared with
# anything.
modules/coreboot: Define each coreboot version as a separate module Define a separate module for each coreboot version, so the module used to build the ROM will optionally be able to reference the toolchain from a different module. This will allow coreboot fork builds to use the toolchain from the corresponding release. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-08-10 20:48:05 +00:00
coreboot-talos_2_repo := https://github.com/Dasharo/coreboot
Talos-2: bring changes to a working state outside of usage of GPG key material backup as of now - Closes https://github.com/linuxboot/heads/pull/1452 - coreboot: Take Talos II 0.7 release coreboot config file that was inside of cbfs and use it as a base upstream. - linux: Readd sysctl and proc requirements for cbmem to work. TODO: fix gpg2 module so that the following doesn't happen (a ppc64 thing. Can't figure out why): ``` Adding generated key to current firmware and re-flashing... Board talos-2 detected, continuing... 37281653053696daf2e40a8efe9451b557d9d6ab586830dc85f814bf2e03a05f /tmp/talos-2.rom Initializing Flash Programmer Reading old flash contents. Please wait... Flashing: [##################################################\] (100%) Verifying flash contents. Please wait... The flash contents were verified and the image was flashed correctly. Signing boot files and generating checksums... 180726119: 000E452213510000005A gpg: error running '//bin/dirmngr': probably not installed gpg: failed to start dirmngr '//bin/dirmngr': Configuration error gpg: can't connect to the dirmngr: Configuration error gpg: no default secret key: No dirmngr gpg: signing failed: No dirmngr ``` dirmngr is deactivated per configure statement --disable-dirmngr, and works as expected on x86 Signed-off-by: Thierry Laurion <insurgo@riseup.net>
2023-11-16 21:36:16 +00:00
coreboot-talos_2_commit_hash := fc47236e9877f4113dfcce07fa928f52d4d2c8ee
modules/coreboot: Don't try to share toolchain for talos_2 fork The skiboot build fails to find the toolchain when it's not in the default location. There is only one ppc64 board anyway, so there's no point trying to share a toolchain for now. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-08-11 13:32:30 +00:00
$(eval $(call coreboot_module,talos_2,))
modules/coreboot: Define each coreboot version as a separate module Define a separate module for each coreboot version, so the module used to build the ROM will optionally be able to reference the toolchain from a different module. This will allow coreboot fork builds to use the toolchain from the corresponding release. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-08-10 20:48:05 +00:00
modules/coreboot: Update Purism coreboot to 24e2f7e4 This is 4.21-Purism-1 plus a fix for native graphics init on Mini v1/v2: HDMI1 is enabled so passive DisplayPort to DVI/HDMI adapters will work. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-08-31 21:16:19 +00:00
# Similarly, purism is based on 4.21, but nothing builds against 4.21 itself
modules/coreboot: Don't try to share toolchain for purism yet Nothing else shares the 4.20.1 toolchain yet, and upcoming forks are based on older releases. We'll share it when other boards update to 4.20.1. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-08-11 18:48:19 +00:00
# or any other fork - no benefit to sharing the toolchain yet.
modules/coreboot: Define each coreboot version as a separate module Define a separate module for each coreboot version, so the module used to build the ROM will optionally be able to reference the toolchain from a different module. This will allow coreboot fork builds to use the toolchain from the corresponding release. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-08-10 20:48:05 +00:00
coreboot-purism_repo := https://source.puri.sm/firmware/coreboot.git
modules/coreboot: Update Purism branch to 4.21-Purism-2 Includes support for Librem 11. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-09-14 19:27:26 +00:00
coreboot-purism_commit_hash := 0d57cff58fba2f3a4d3a714a4eae65753e58c6ff
modules/coreboot: Don't try to share toolchain for purism yet Nothing else shares the 4.20.1 toolchain yet, and upcoming forks are based on older releases. We'll share it when other boards update to 4.20.1. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-08-11 18:48:19 +00:00
$(eval $(call coreboot_module,purism,))
modules/coreboot: Define each coreboot version as a separate module Define a separate module for each coreboot version, so the module used to build the ROM will optionally be able to reference the toolchain from a different module. This will allow coreboot fork builds to use the toolchain from the corresponding release. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-08-10 20:48:05 +00:00
nv41/ns50: coreboot+coreboot patch+CircleCI config: adapt to have nv41/ns50 build on top of #1417 and #1462
2023-08-18 15:39:48 +00:00
#Nitrokey nv41/ns50 are based on Dasharo coreboot port,
# with patches staging under coreboot-clevo_release
coreboot-nitrokey_repo := https://github.com/dasharo/coreboot
coreboot-nitrokey: update dasharo to v1.7.2 * remove all previous coreboot patches (as they are already included) * to be investigated: linux trampoline patch * add new patch to hardcode sleep configuration * activate smmstore as dasharo vendor code requires it Signed-off-by: Markus Meissner <coder@safemailbox.de>
2023-12-18 19:43:17 +00:00
coreboot-nitrokey_commit_hash := 1bcb338682b612cfcca8bba02846f78139b2e0c8
nv41/ns50: coreboot+coreboot patch+CircleCI config: adapt to have nv41/ns50 build on top of #1417 and #1462
2023-08-18 15:39:48 +00:00
coreboot-nitrokey_patch_version := clevo_release
#We use clevo_release's crossgcc for now, unshared but between nitropad nv41/ns50
$(eval $(call coreboot_module,nitrokey,))
modules/coreboot: Define each coreboot version as a separate module Define a separate module for each coreboot version, so the module used to build the ROM will optionally be able to reference the toolchain from a different module. This will allow coreboot fork builds to use the toolchain from the corresponding release. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-08-10 20:48:05 +00:00
# Check that the board configured the coreboot version correctly
ifeq "$(CONFIG_COREBOOT_VERSION)" ""
Fix CircleCI build problems (#808) * CircleCI: debian:10 docker based. Give possitility to override CACHE_VERSION through CircleCI when needed * Makefile: fix #799 with implementation of @osresearch's recommended https://github.com/osresearch/heads/issues/799#issuecomment-673059028 * modules/coreboot : indentation fix and putting version hashes together to facilitate future maintainership.
2020-08-20 19:15:46 +00:00
$(error "$(BOARD): does not specify coreboot version under CONFIG_COREBOOT_VERSION")
modules/coreboot: Define each coreboot version as a separate module Define a separate module for each coreboot version, so the module used to build the ROM will optionally be able to reference the toolchain from a different module. This will allow coreboot fork builds to use the toolchain from the corresponding release. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-08-10 20:48:05 +00:00
else ifeq "$(coreboot-$(CONFIG_COREBOOT_VERSION)_dir)" ""
$(error "$(BOARD): coreboot version $(CONFIG_COREBOOT_VERSION) not known"
coreboot: 4.8.1 fixed in Makefile, coreboot module and board configs (coreboot_481) to facilitate newer coreboot version integration and testing without breaking old fixed boards
2020-07-10 13:44:01 +00:00
endif
modules/coreboot: Define each coreboot version as a separate module Define a separate module for each coreboot version, so the module used to build the ROM will optionally be able to reference the toolchain from a different module. This will allow coreboot fork builds to use the toolchain from the corresponding release. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-08-10 20:48:05 +00:00
coreboot_module := coreboot-$(CONFIG_COREBOOT_VERSION)
modules-y += $(coreboot_module)
# Don't make everyone type $($(coreboot_module)_dir)
coreboot_dir := $($(coreboot_module)_dir)
coreboot_base_dir := $($(coreboot_module)_base_dir)
modules/coreboot: Clean up module, don't share git build directories Remove coreboot 4.8.1, 4.13, and 4.17, which were all unused. Remove extra copies of EXTRA_FLAGS which duplicated the common definition. The only difference was -Wno-error=address-of-packed-member, the warning is now disabled entirely everywhere with -Wno-address-of-packed-member. Use separate coreboot_version values for talos_2, nitrokey, and purism, which gives each a separate build directory. Move conditional blob definitions out of each coreboot version. Fix condition for coreboot-blobs - whether a module is a git clone actually depends on non-empty <module>_repo, not <module>_version==git. Fix the test so git versions of coreboot can have arbitrary names. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-08-10 17:35:04 +00:00
fixup modules/coreboot: Fix purism-blobs dependency for librem_l1um Two := assignments were factored out together, the second overwrote the first. Fix to +=, and remove the nitrokey assignment since it came from a branch. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-08-11 14:51:59 +00:00
$(coreboot_module)_depends += $(if $(CONFIG_PURISM_BLOBS), purism-blobs)
nv41/ns50: coreboot+coreboot patch+CircleCI config: adapt to have nv41/ns50 build on top of #1417 and #1462
2023-08-18 15:39:48 +00:00
$(coreboot_module)_depends += $(if $(CONFIG_NITROKEY_BLOBS), nitrokey-blobs)
checkout coreboot from github, rather than downloading release file
2016-08-19 15:31:07 +00:00
musl-cross-make: replace all cross compilers with musl-cross-make Signed-off-by: Trammell Hudson <hudson@trmm.net>
2020-01-08 16:08:15 +00:00
# coreboot builds are specialized on a per-target basis.
Make coreboot building modular to support multiple boards. This touches most of the module configurations since the coreboot build process had to add a few new features. The Linux kernel could make use of it as well if we need separate x230/chell/qemu kernels, for instance.
2016-11-23 17:11:08 +00:00
# The builds are done in a per-target subdirectory
x230 build works on the NERF tree (#305) Fix FAST=1 builds to actually be fast.
2018-02-05 16:56:15 +00:00
CONFIG_COREBOOT_CONFIG ?= config/coreboot-$(BOARD).config
Make coreboot building modular to support multiple boards. This touches most of the module configurations since the coreboot build process had to add a few new features. The Linux kernel could make use of it as well if we need separate x230/chell/qemu kernels, for instance.
2016-11-23 17:11:08 +00:00
force re-configuration when linux or coreboot config files change (#397)
2018-05-03 20:47:09 +00:00
# Ensure that touching the config file will force a rebuild
$(build)/$(coreboot_dir)/.configured: $(CONFIG_COREBOOT_CONFIG)
modules/coreboot: Clean up module, don't share git build directories Remove coreboot 4.8.1, 4.13, and 4.17, which were all unused. Remove extra copies of EXTRA_FLAGS which duplicated the common definition. The only difference was -Wno-error=address-of-packed-member, the warning is now disabled entirely everywhere with -Wno-address-of-packed-member. Use separate coreboot_version values for talos_2, nitrokey, and purism, which gives each a separate build directory. Move conditional blob definitions out of each coreboot version. Fix condition for coreboot-blobs - whether a module is a git clone actually depends on non-empty <module>_repo, not <module>_version==git. Fix the test so git versions of coreboot can have arbitrary names. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-08-10 17:35:04 +00:00
EXTRA_FLAGS ?= -fdebug-prefix-map=$(pwd)=heads -gno-record-gcc-switches -Wno-error=packed-not-aligned -Wno-address-of-packed-member
coreboot flags to strip build paths (issue #95)
2017-01-29 01:21:47 +00:00
modules/coreboot: Reuse release toolchain for fork builds Reuse the toolchain from a coreboot release for fork builds. Either the fork or the release can be built first, in either case the release's toolchain is built at the default location and reused for later builds. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-08-10 20:49:58 +00:00
# Select the coreboot version to use for the toolchain
ifeq "$($(coreboot_module)_toolchain)" ""
# Use the same module
coreboot_toolchain_module := $(coreboot_module)
else
# Use a different module
coreboot_toolchain_module := coreboot-$($(coreboot_module)_toolchain)
modules-y += $(coreboot_toolchain_module)
# The toolchain module won't build anything for this board, we just need
# the module prepped so we can hook up the toolchain target
$(coreboot_toolchain_module)_output := .nobuild
$(coreboot-toolchain_module)_configure := echo -e 'all:\n\ttouch .nobuild' > Makefile.nobuild
$(coreboot-toolchain_module)_target := -f Makefile.nobuild
endif
modules/coreboot: Define each coreboot version as a separate module Define a separate module for each coreboot version, so the module used to build the ROM will optionally be able to reference the toolchain from a different module. This will allow coreboot fork builds to use the toolchain from the corresponding release. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-08-10 20:48:05 +00:00
$(coreboot_module)_configure := \
Use defconfig for coreboot builds
2018-08-13 14:26:08 +00:00
mkdir -p "$(build)/$(coreboot_dir)" \
Expand @VAR@ placeholders in configuration files This makes configs much less dependent on directory layout. As of this commit the following variables are supported: * @BOARD_BUILD_DIR@ - absolute path under build/ * @BLOB_DIR@ - absolute path to blobs/ Signed-off-by: Sergii Dmytruk <sergii.dmytruk@3mdeb.com>
2022-08-16 16:39:33 +00:00
&& $(call install_config,$(pwd)/$(CONFIG_COREBOOT_CONFIG),$(build)/$(coreboot_dir)/.config) \
Add CONFIG_BRAND_NAME and allow overriding in Makefile with BRAND_NAME Use CONFIG_BRAND_NAME to control the brand name displayed in the UI. Override by setting BRAND_NAME when building, either in the Makefile or on the command line. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-06-21 18:19:41 +00:00
&& echo 'CONFIG_LOCALVERSION="$(BRAND_NAME)-$(HEADS_GIT_VERSION)"' >> $(build)/$(coreboot_dir)/.config \
Inject Heads version string into coreboot LOCALVERSION... (#859) * config/coreboot-*: drop CONFIG_LOCALVERSION Will be injected as part of the build using $(HEADS_GIT_VERSION) Signed-off-by: Matt DeVillier <matt.devillier@puri.sm> * modules/coreboot: inject $(HEADS_GIT_VERSION) as CONFIG_LOCALVERSION Needed for fwupd to handle board updates Signed-off-by: Matt DeVillier <matt.devillier@puri.sm> * modules/coreboot: override SMBIOS ProductName with $(BOARD) Signed-off-by: Matt DeVillier <matt.devillier@puri.sm> * Use $(BOARD)-$(HEADS_GIT_VERSION) as basis for output filename makes builds uniquely identifiable based on board and version. Signed-off-by: Matt DeVillier <matt.devillier@puri.sm>
2020-10-21 15:04:27 +00:00
&& echo 'CONFIG_MAINBOARD_SMBIOS_PRODUCT_NAME="$(BOARD)"' >> $(build)/$(coreboot_dir)/.config \
Use defconfig for coreboot builds
2018-08-13 14:26:08 +00:00
&& $(MAKE) olddefconfig \
-C "$(build)/$(coreboot_base_dir)" \
obj="$(build)/$(coreboot_dir)" \
Fix DOTCONFIG in coreboot module and clean up configs
2018-10-27 21:03:45 +00:00
DOTCONFIG="$(build)/$(coreboot_dir)/.config" \
use BUILD_TIMELESS to avoid timestamps in coreboot when not in a git tree (issue #104)
2017-02-01 18:39:56 +00:00
BUILD_TIMELESS=1 \
coreboot flags to strip build paths (issue #95)
2017-01-29 01:21:47 +00:00
CFLAGS_x86_32="$(EXTRA_FLAGS)" \
CFLAGS_x86_64="$(EXTRA_FLAGS)" \
Make coreboot building modular to support multiple boards. This touches most of the module configurations since the coreboot build process had to add a few new features. The Linux kernel could make use of it as well if we need separate x230/chell/qemu kernels, for instance.
2016-11-23 17:11:08 +00:00
modules/coreboot: Use a specific file to mark the toolchain build Use .heads-toolchain to mark that the toolchain was built rather than .xcompile. coreboot doesn't generate .xcompile until the build step, so all modules had to build successfully before we would stop trying to to rebuild the toolchain. Build steps should generally produce the indicated outputs too, which was not occurring here. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-08-10 21:14:42 +00:00
# Create a dependency from coreboot to the toolchain. Use .heads-toolchain to
# mark that the toolchain was built.
COREBOOT_TOOLCHAIN=$(build)/$($(coreboot_toolchain_module)_base_dir)/.heads-toolchain
modules/coreboot: Reuse release toolchain for fork builds Reuse the toolchain from a coreboot release for fork builds. Either the fork or the release can be built first, in either case the release's toolchain is built at the default location and reused for later builds. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-08-10 20:49:58 +00:00
$(COREBOOT_TOOLCHAIN): $(build)/$($(coreboot_toolchain_module)_base_dir)/.canary
$(MAKE) -C "$(build)/$($(coreboot_toolchain_module)_base_dir)" CPUS=$(CPUS) "crossgcc-$(COREBOOT_TARGET)"
modules/coreboot: Use a specific file to mark the toolchain build Use .heads-toolchain to mark that the toolchain was built rather than .xcompile. coreboot doesn't generate .xcompile until the build step, so all modules had to build successfully before we would stop trying to to rebuild the toolchain. Build steps should generally produce the indicated outputs too, which was not occurring here. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-08-10 21:14:42 +00:00
touch "$@"
modules/coreboot: Reuse release toolchain for fork builds Reuse the toolchain from a coreboot release for fork builds. Either the fork or the release can be built first, in either case the release's toolchain is built at the default location and reused for later builds. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-08-10 20:49:58 +00:00
$(build)/$(coreboot_dir)/.configured: $(COREBOOT_TOOLCHAIN)
# Build with the cross toolchain from the toolchain module (which might be the
# same coreboot module or a different one).
modules/coreboot: Define each coreboot version as a separate module Define a separate module for each coreboot version, so the module used to build the ROM will optionally be able to reference the toolchain from a different module. This will allow coreboot fork builds to use the toolchain from the corresponding release. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-08-10 20:48:05 +00:00
$(coreboot_module)_target := \
Use defconfig for coreboot builds
2018-08-13 14:26:08 +00:00
-C "$(build)/$(coreboot_base_dir)" \
obj="$(build)/$(coreboot_dir)" \
Fix DOTCONFIG in coreboot module and clean up configs
2018-10-27 21:03:45 +00:00
DOTCONFIG="$(build)/$(coreboot_dir)/.config" \
modules/coreboot: Reuse release toolchain for fork builds Reuse the toolchain from a coreboot release for fork builds. Either the fork or the release can be built first, in either case the release's toolchain is built at the default location and reused for later builds. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-08-10 20:49:58 +00:00
XGCCPATH="$(build)/$($(coreboot_toolchain_module)_base_dir)/util/crossgcc/xgcc/bin/" \
modules/coreboot: Delete unused remnants of using musl toolchain At one time coreboot was built using Heads' musl toolchain, but this was later reverted. coreboot builds with its own toolchain again. CROSS= has no effect on coreboot proper (only exception is PPC64 skiboot payload). It was added to coreboot by a patch that was deleted in 8e44853. COREBOOT_IASL was set to the default, that was only needed when the toolchain was being overridden to override iasl back to the coreboot one. ppc64 still specifies CROSS= since skiboot is unable to find coreboot's toolchain from XGCCPATH but checks CROSS. This builds skiboot with the Heads toolchain as before. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-08-10 18:01:02 +00:00
$(COREBOOT_TARGET_CROSS) \
use BUILD_TIMELESS to avoid timestamps in coreboot when not in a git tree (issue #104)
2017-02-01 18:39:56 +00:00
BUILD_TIMELESS=1 \
coreboot flags to strip build paths (issue #95)
2017-01-29 01:21:47 +00:00
CFLAGS_x86_32="$(EXTRA_FLAGS)" \
CFLAGS_x86_64="$(EXTRA_FLAGS)" \
limit parallel make load (issue #131)
2017-03-21 18:29:07 +00:00
$(MAKE_JOBS)
Make coreboot building modular to support multiple boards. This touches most of the module configurations since the coreboot build process had to add a few new features. The Linux kernel could make use of it as well if we need separate x230/chell/qemu kernels, for instance.
2016-11-23 17:11:08 +00:00
modules/coreboot: Define each coreboot version as a separate module Define a separate module for each coreboot version, so the module used to build the ROM will optionally be able to reference the toolchain from a different module. This will allow coreboot fork builds to use the toolchain from the corresponding release. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-08-10 20:48:05 +00:00
$(coreboot_module)_output := $(CONFIG_COREBOOT_ROM)
$(coreboot_module)_output += $(CONFIG_COREBOOT_BOOTBLOCK)
use externally built coreboot compilers
2018-09-18 19:59:48 +00:00
parallel make fixes and hacks, which seem to work and reduce excessive remaking (issue #394)
2018-05-02 15:38:39 +00:00
# Force a rebuild if the inputs have changed
$(build)/$(coreboot_dir)/.build: \
Support targeting PowerPC 64 This prepares most of the modules to be build for it. Signed-off-by: Sergii Dmytruk <sergii.dmytruk@3mdeb.com>
2021-07-18 17:34:20 +00:00
$(build)/$(BOARD)/$(LINUX_IMAGE_FILE) \
parallel make fixes and hacks, which seem to work and reduce excessive remaking (issue #394)
2018-05-02 15:38:39 +00:00
$(build)/$(BOARD)/initrd.cpio.xz \
ensure that both coreboot.rom and linuxboot.rom are built in a parallel build (#394)
2018-05-02 18:53:54 +00:00
# This produces a ROM image that is written with the flashrom program
Inject Heads version string into coreboot LOCALVERSION... (#859) * config/coreboot-*: drop CONFIG_LOCALVERSION Will be injected as part of the build using $(HEADS_GIT_VERSION) Signed-off-by: Matt DeVillier <matt.devillier@puri.sm> * modules/coreboot: inject $(HEADS_GIT_VERSION) as CONFIG_LOCALVERSION Needed for fwupd to handle board updates Signed-off-by: Matt DeVillier <matt.devillier@puri.sm> * modules/coreboot: override SMBIOS ProductName with $(BOARD) Signed-off-by: Matt DeVillier <matt.devillier@puri.sm> * Use $(BOARD)-$(HEADS_GIT_VERSION) as basis for output filename makes builds uniquely identifiable based on board and version. Signed-off-by: Matt DeVillier <matt.devillier@puri.sm>
2020-10-21 15:04:27 +00:00
ifneq ($(CONFIG_COREBOOT),)
Allow using files other than coreboot.rom Talos 2 will need signed ROM with ECC and an analogous separate bootblock file. Signed-off-by: Sergii Dmytruk <sergii.dmytruk@3mdeb.com>
2021-07-20 20:48:08 +00:00
Inject Heads version string into coreboot LOCALVERSION... (#859) * config/coreboot-*: drop CONFIG_LOCALVERSION Will be injected as part of the build using $(HEADS_GIT_VERSION) Signed-off-by: Matt DeVillier <matt.devillier@puri.sm> * modules/coreboot: inject $(HEADS_GIT_VERSION) as CONFIG_LOCALVERSION Needed for fwupd to handle board updates Signed-off-by: Matt DeVillier <matt.devillier@puri.sm> * modules/coreboot: override SMBIOS ProductName with $(BOARD) Signed-off-by: Matt DeVillier <matt.devillier@puri.sm> * Use $(BOARD)-$(HEADS_GIT_VERSION) as basis for output filename makes builds uniquely identifiable based on board and version. Signed-off-by: Matt DeVillier <matt.devillier@puri.sm>
2020-10-21 15:04:27 +00:00
$(build)/$(BOARD)/$(CB_OUTPUT_FILE): $(build)/$(coreboot_dir)/.build
Allow using files other than coreboot.rom Talos 2 will need signed ROM with ECC and an analogous separate bootblock file. Signed-off-by: Sergii Dmytruk <sergii.dmytruk@3mdeb.com>
2021-07-20 20:48:08 +00:00
# Use coreboot.rom, because custom output files might not be processed by cbfstool
ensure that both coreboot.rom and linuxboot.rom are built in a parallel build (#394)
2018-05-02 18:53:54 +00:00
"$(build)/$(coreboot_dir)/cbfstool" "$(dir $<)coreboot.rom" print
Allow using files other than coreboot.rom Talos 2 will need signed ROM with ECC and an analogous separate bootblock file. Signed-off-by: Sergii Dmytruk <sergii.dmytruk@3mdeb.com>
2021-07-20 20:48:08 +00:00
$(call do-copy,$(dir $<)$(CONFIG_COREBOOT_ROM),$@)
@touch $@ # update the time stamp
ifneq ($(CONFIG_COREBOOT_BOOTBLOCK),)
$(build)/$(BOARD)/$(CB_BOOTBLOCK_FILE): $(build)/$(coreboot_dir)/.build
$(call do-copy,$(dir $<)$(CONFIG_COREBOOT_BOOTBLOCK),$@)
ensure that both coreboot.rom and linuxboot.rom are built in a parallel build (#394)
2018-05-02 18:53:54 +00:00
@touch $@ # update the time stamp
Inject Heads version string into coreboot LOCALVERSION... (#859) * config/coreboot-*: drop CONFIG_LOCALVERSION Will be injected as part of the build using $(HEADS_GIT_VERSION) Signed-off-by: Matt DeVillier <matt.devillier@puri.sm> * modules/coreboot: inject $(HEADS_GIT_VERSION) as CONFIG_LOCALVERSION Needed for fwupd to handle board updates Signed-off-by: Matt DeVillier <matt.devillier@puri.sm> * modules/coreboot: override SMBIOS ProductName with $(BOARD) Signed-off-by: Matt DeVillier <matt.devillier@puri.sm> * Use $(BOARD)-$(HEADS_GIT_VERSION) as basis for output filename makes builds uniquely identifiable based on board and version. Signed-off-by: Matt DeVillier <matt.devillier@puri.sm>
2020-10-21 15:04:27 +00:00
endif
use coreboot from git instead of downloading it, move blobs into this module file
2016-08-14 20:03:11 +00:00
Allow using files other than coreboot.rom Talos 2 will need signed ROM with ECC and an analogous separate bootblock file. Signed-off-by: Sergii Dmytruk <sergii.dmytruk@3mdeb.com>
2021-07-20 20:48:08 +00:00
endif
Helpful targets
2018-02-13 18:20:04 +00:00
#
# Helpful target for reconfiguring the coreboot target
#
modules/ coreboot+linux: add helpers to edit config in place + save in oldconfig/defconfig formats both linux/coreboot: - save_in_defconfig_format_in_place : takes whatever coreboot config file for a make BOARD=xyz statement and saves it in defconfig - save_in_oldefconfig_format_in_place : takes whatever coreboot config file for a make BOARD=xyz statement and saves it in oldefconfig linux: - linux.prompt_for_new_config_options_for_kernel_version_bump: - The most useful helper as of now when doing kernel version bump. - Requires to save current kernel config in oldconfig (make BOARD=xyz linux.save_in_oldefconfig_format_in_place) first, then bump kernel version in board config and then use that helper to review new options and save in tree.
2023-04-19 14:04:53 +00:00
coreboot.save_in_defconfig_format_in_place:
mkdir -p "$(build)/$(coreboot_dir)" && \
cp "$(pwd)/$(CONFIG_COREBOOT_CONFIG)" "$(build)/$(coreboot_dir)/.config" && \
Helpful targets
2018-02-13 18:20:04 +00:00
$(MAKE) \
parallel make fixes and hacks, which seem to work and reduce excessive remaking (issue #394)
2018-05-02 15:38:39 +00:00
-C "$(build)/$(coreboot_base_dir)" \
Use defconfig for coreboot builds
2018-08-13 14:26:08 +00:00
DOTCONFIG="$(build)/$(coreboot_dir)/.config" \
modules/ coreboot+linux: add helpers to edit config in place + save in oldconfig/defconfig formats both linux/coreboot: - save_in_defconfig_format_in_place : takes whatever coreboot config file for a make BOARD=xyz statement and saves it in defconfig - save_in_oldefconfig_format_in_place : takes whatever coreboot config file for a make BOARD=xyz statement and saves it in oldefconfig linux: - linux.prompt_for_new_config_options_for_kernel_version_bump: - The most useful helper as of now when doing kernel version bump. - Requires to save current kernel config in oldconfig (make BOARD=xyz linux.save_in_oldefconfig_format_in_place) first, then bump kernel version in board config and then use that helper to review new options and save in tree.
2023-04-19 14:04:53 +00:00
olddefconfig && \
Use defconfig for coreboot builds
2018-08-13 14:26:08 +00:00
$(MAKE) \
-C "$(build)/$(coreboot_base_dir)" \
modules/ coreboot+linux: add helpers to edit config in place + save in oldconfig/defconfig formats both linux/coreboot: - save_in_defconfig_format_in_place : takes whatever coreboot config file for a make BOARD=xyz statement and saves it in defconfig - save_in_oldefconfig_format_in_place : takes whatever coreboot config file for a make BOARD=xyz statement and saves it in oldefconfig linux: - linux.prompt_for_new_config_options_for_kernel_version_bump: - The most useful helper as of now when doing kernel version bump. - Requires to save current kernel config in oldconfig (make BOARD=xyz linux.save_in_oldefconfig_format_in_place) first, then bump kernel version in board config and then use that helper to review new options and save in tree.
2023-04-19 14:04:53 +00:00
DOTCONFIG="$(build)/$(coreboot_dir)/.config" \
savedefconfig && \
mv "$(build)/$(coreboot_base_dir)/defconfig" "$(pwd)/$(CONFIG_COREBOOT_CONFIG)"
coreboot.save_in_oldconfig_format_in_place:
mkdir -p "$(build)/$(coreboot_dir)" && \
cp "$(pwd)/$(CONFIG_COREBOOT_CONFIG)" "$(build)/$(coreboot_dir)/.config" && \
coreboot+linux modules: add modules target helpers to edit configs (oldconfig/defconfig) Most useful to me are: coreboot.modify_and_save_defconfig_in_place coreboot.modify_and_save_oldconfig_in_place linux.modify_and_save_oldconfig_in_place linux.modify_and_save_defconfig_in_place Which permit to take current in tree configs and translate them into other format. This is useful when trying to version bump and build. Also add helpers to save in versioned version to facilitate change tracking: linux.generate_and_save-versioned-oldconfig linux.regenerate_and_save_versioned_defconfig
2023-04-19 14:04:53 +00:00
$(MAKE) \
-C "$(build)/$(coreboot_base_dir)" \
modules/ coreboot+linux: add helpers to edit config in place + save in oldconfig/defconfig formats both linux/coreboot: - save_in_defconfig_format_in_place : takes whatever coreboot config file for a make BOARD=xyz statement and saves it in defconfig - save_in_oldefconfig_format_in_place : takes whatever coreboot config file for a make BOARD=xyz statement and saves it in oldefconfig linux: - linux.prompt_for_new_config_options_for_kernel_version_bump: - The most useful helper as of now when doing kernel version bump. - Requires to save current kernel config in oldconfig (make BOARD=xyz linux.save_in_oldefconfig_format_in_place) first, then bump kernel version in board config and then use that helper to review new options and save in tree.
2023-04-19 14:04:53 +00:00
DOTCONFIG="$(build)/$(coreboot_dir)/.config" \
olddefconfig \
&& mv "$(build)/$(coreboot_dir)/.config" "$(pwd)/$(CONFIG_COREBOOT_CONFIG)"
coreboot+linux modules: add modules target helpers to edit configs (oldconfig/defconfig) Most useful to me are: coreboot.modify_and_save_defconfig_in_place coreboot.modify_and_save_oldconfig_in_place linux.modify_and_save_oldconfig_in_place linux.modify_and_save_defconfig_in_place Which permit to take current in tree configs and translate them into other format. This is useful when trying to version bump and build. Also add helpers to save in versioned version to facilitate change tracking: linux.generate_and_save-versioned-oldconfig linux.regenerate_and_save_versioned_defconfig
2023-04-19 14:04:53 +00:00
modules/ coreboot+linux: add helpers to edit config in place + save in oldconfig/defconfig formats both linux/coreboot: - save_in_defconfig_format_in_place : takes whatever coreboot config file for a make BOARD=xyz statement and saves it in defconfig - save_in_oldefconfig_format_in_place : takes whatever coreboot config file for a make BOARD=xyz statement and saves it in oldefconfig linux: - linux.prompt_for_new_config_options_for_kernel_version_bump: - The most useful helper as of now when doing kernel version bump. - Requires to save current kernel config in oldconfig (make BOARD=xyz linux.save_in_oldefconfig_format_in_place) first, then bump kernel version in board config and then use that helper to review new options and save in tree.
2023-04-19 14:04:53 +00:00
coreboot.modify_defconfig_in_place:
mkdir -p "$(build)/$(coreboot_dir)" && \
cp "$(pwd)/$(CONFIG_COREBOOT_CONFIG)" "$(build)/$(coreboot_dir)/.config" && \
coreboot+linux modules: add modules target helpers to edit configs (oldconfig/defconfig) Most useful to me are: coreboot.modify_and_save_defconfig_in_place coreboot.modify_and_save_oldconfig_in_place linux.modify_and_save_oldconfig_in_place linux.modify_and_save_defconfig_in_place Which permit to take current in tree configs and translate them into other format. This is useful when trying to version bump and build. Also add helpers to save in versioned version to facilitate change tracking: linux.generate_and_save-versioned-oldconfig linux.regenerate_and_save_versioned_defconfig
2023-04-19 14:04:53 +00:00
$(MAKE) \
-C "$(build)/$(coreboot_base_dir)" \
modules/ coreboot+linux: add helpers to edit config in place + save in oldconfig/defconfig formats both linux/coreboot: - save_in_defconfig_format_in_place : takes whatever coreboot config file for a make BOARD=xyz statement and saves it in defconfig - save_in_oldefconfig_format_in_place : takes whatever coreboot config file for a make BOARD=xyz statement and saves it in oldefconfig linux: - linux.prompt_for_new_config_options_for_kernel_version_bump: - The most useful helper as of now when doing kernel version bump. - Requires to save current kernel config in oldconfig (make BOARD=xyz linux.save_in_oldefconfig_format_in_place) first, then bump kernel version in board config and then use that helper to review new options and save in tree.
2023-04-19 14:04:53 +00:00
DOTCONFIG="$(build)/$(coreboot_dir)/.config" \
coreboot+linux modules: add modules target helpers to edit configs (oldconfig/defconfig) Most useful to me are: coreboot.modify_and_save_defconfig_in_place coreboot.modify_and_save_oldconfig_in_place linux.modify_and_save_oldconfig_in_place linux.modify_and_save_defconfig_in_place Which permit to take current in tree configs and translate them into other format. This is useful when trying to version bump and build. Also add helpers to save in versioned version to facilitate change tracking: linux.generate_and_save-versioned-oldconfig linux.regenerate_and_save_versioned_defconfig
2023-04-19 14:04:53 +00:00
menuconfig \
&& $(MAKE) \
-C "$(build)/$(coreboot_base_dir)" \
modules/ coreboot+linux: add helpers to edit config in place + save in oldconfig/defconfig formats both linux/coreboot: - save_in_defconfig_format_in_place : takes whatever coreboot config file for a make BOARD=xyz statement and saves it in defconfig - save_in_oldefconfig_format_in_place : takes whatever coreboot config file for a make BOARD=xyz statement and saves it in oldefconfig linux: - linux.prompt_for_new_config_options_for_kernel_version_bump: - The most useful helper as of now when doing kernel version bump. - Requires to save current kernel config in oldconfig (make BOARD=xyz linux.save_in_oldefconfig_format_in_place) first, then bump kernel version in board config and then use that helper to review new options and save in tree.
2023-04-19 14:04:53 +00:00
DOTCONFIG="$(build)/$(coreboot_dir)/.config" \
coreboot+linux modules: add modules target helpers to edit configs (oldconfig/defconfig) Most useful to me are: coreboot.modify_and_save_defconfig_in_place coreboot.modify_and_save_oldconfig_in_place linux.modify_and_save_oldconfig_in_place linux.modify_and_save_defconfig_in_place Which permit to take current in tree configs and translate them into other format. This is useful when trying to version bump and build. Also add helpers to save in versioned version to facilitate change tracking: linux.generate_and_save-versioned-oldconfig linux.regenerate_and_save_versioned_defconfig
2023-04-19 14:04:53 +00:00
DEFCONFIG="$(pwd)/$(CONFIG_COREBOOT_CONFIG)" \
modules/ coreboot+linux: add helpers to edit config in place + save in oldconfig/defconfig formats both linux/coreboot: - save_in_defconfig_format_in_place : takes whatever coreboot config file for a make BOARD=xyz statement and saves it in defconfig - save_in_oldefconfig_format_in_place : takes whatever coreboot config file for a make BOARD=xyz statement and saves it in oldefconfig linux: - linux.prompt_for_new_config_options_for_kernel_version_bump: - The most useful helper as of now when doing kernel version bump. - Requires to save current kernel config in oldconfig (make BOARD=xyz linux.save_in_oldefconfig_format_in_place) first, then bump kernel version in board config and then use that helper to review new options and save in tree.
2023-04-19 14:04:53 +00:00
savedefconfig
coreboot+linux modules: add modules target helpers to edit configs (oldconfig/defconfig) Most useful to me are: coreboot.modify_and_save_defconfig_in_place coreboot.modify_and_save_oldconfig_in_place linux.modify_and_save_oldconfig_in_place linux.modify_and_save_defconfig_in_place Which permit to take current in tree configs and translate them into other format. This is useful when trying to version bump and build. Also add helpers to save in versioned version to facilitate change tracking: linux.generate_and_save-versioned-oldconfig linux.regenerate_and_save_versioned_defconfig
2023-04-19 14:04:53 +00:00
coreboot.modify_and_save_oldconfig_in_place:
modules/ coreboot+linux: add helpers to edit config in place + save in oldconfig/defconfig formats both linux/coreboot: - save_in_defconfig_format_in_place : takes whatever coreboot config file for a make BOARD=xyz statement and saves it in defconfig - save_in_oldefconfig_format_in_place : takes whatever coreboot config file for a make BOARD=xyz statement and saves it in oldefconfig linux: - linux.prompt_for_new_config_options_for_kernel_version_bump: - The most useful helper as of now when doing kernel version bump. - Requires to save current kernel config in oldconfig (make BOARD=xyz linux.save_in_oldefconfig_format_in_place) first, then bump kernel version in board config and then use that helper to review new options and save in tree.
2023-04-19 14:04:53 +00:00
mkdir -p "$(build)/$(coreboot_dir)" && \
coreboot+linux modules: add modules target helpers to edit configs (oldconfig/defconfig) Most useful to me are: coreboot.modify_and_save_defconfig_in_place coreboot.modify_and_save_oldconfig_in_place linux.modify_and_save_oldconfig_in_place linux.modify_and_save_defconfig_in_place Which permit to take current in tree configs and translate them into other format. This is useful when trying to version bump and build. Also add helpers to save in versioned version to facilitate change tracking: linux.generate_and_save-versioned-oldconfig linux.regenerate_and_save_versioned_defconfig
2023-04-19 14:04:53 +00:00
$(MAKE) menuconfig \
-C "$(build)/$(coreboot_base_dir)" \
obj="$(build)/$(coreboot_dir)" \
DOTCONFIG="$(pwd)/$(CONFIG_COREBOOT_CONFIG)"
use coreboot-4.5 release with a patch against the source tree (issue #102)
2017-02-01 16:50:52 +00:00
# if we are not building from a git checkout,
# we must also download the coreboot-blobs tree
modules/coreboot: Define each coreboot version as a separate module Define a separate module for each coreboot version, so the module used to build the ROM will optionally be able to reference the toolchain from a different module. This will allow coreboot fork builds to use the toolchain from the corresponding release. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-08-10 20:48:05 +00:00
ifeq "$($(coreboot_module)_repo)" ""
x230 build works on the NERF tree (#305) Fix FAST=1 builds to actually be fast.
2018-02-05 16:56:15 +00:00
modules/coreboot: Define each coreboot version as a separate module Define a separate module for each coreboot version, so the module used to build the ROM will optionally be able to reference the toolchain from a different module. This will allow coreboot fork builds to use the toolchain from the corresponding release. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-08-10 20:48:05 +00:00
coreboot-blobs_module := coreboot-blobs-$(CONFIG_COREBOOT_VERSION)
use coreboot-4.5 release with a patch against the source tree (issue #102)
2017-02-01 16:50:52 +00:00
modules/coreboot: Define each coreboot version as a separate module Define a separate module for each coreboot version, so the module used to build the ROM will optionally be able to reference the toolchain from a different module. This will allow coreboot fork builds to use the toolchain from the corresponding release. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-08-10 20:48:05 +00:00
$(coreboot_module)_depends += $(coreboot-blobs_module)
modules-y += $(coreboot-blobs_module)
use coreboot-4.5 release with a patch against the source tree (issue #102)
2017-02-01 16:50:52 +00:00
use coreboot from git instead of downloading it, move blobs into this module file
2016-08-14 20:03:11 +00:00
## there is nothing to build for the blobs, this should be
## made easier to make happen
modules/coreboot: Define each coreboot version as a separate module Define a separate module for each coreboot version, so the module used to build the ROM will optionally be able to reference the toolchain from a different module. This will allow coreboot fork builds to use the toolchain from the corresponding release. Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
2023-08-10 20:48:05 +00:00
$(coreboot-blobs_module)_output := .built
$(coreboot-blobs_module)_configure := echo -e 'all:\n\ttouch .built' > Makefile
use coreboot from git instead of downloading it, move blobs into this module file
2016-08-14 20:03:11 +00:00
use coreboot-4.5 release with a patch against the source tree (issue #102)
2017-02-01 16:50:52 +00:00
endif
non-coreboot-builds: do not error if CONFIG_COREBOOT_VERSION is not set Signed-off-by: Trammell hudson <hudson@trmm.net>
2020-11-25 13:43:07 +00:00
endif
Reference in New Issue Copy Permalink