NetCube-Systems-Austria/kumquat-buildroot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
18684d51f4
kumquat-buildroot/package/rcw/rcw.mk

68 lines
2.0 KiB
Makefile
Raw Normal View History

package/rcw: new package This package adds NXP Layerscape and QoriQ reset config word (RCW) / pre-bootloader (PBL) generation support. The RCW is used to setup clocking and IO allocations and then launches the next stage of boot (usually u-boot). Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-01-16 13:39:52 +01:00
################################################################################
#
# rcw
#
################################################################################
package/rcw : bump to LSDK-19.09 The new rcw.py script is python3-only, but we can use either the system-provided python3, or the one we build with host-python3 if the system does not have it already. It turns out, also, that rcw.py is using #!/usr/bin/env python3, so it will easily find it from $PATH, so we export it in the environment. Signed-off-by: Laurent Hartanerot <laurent.hartanerot@atos.net> [yann.morin.1998@free.fr: - set the proper PATH in the envioronment - do not explicitly call python3, defer to /usr/bin/env in the script - add an accompagnying comment - rewrite commit log accordingly ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-03-22 17:24:44 +01:00
RCW_VERSION = LSDK-19.09
package/rcw: new package This package adds NXP Layerscape and QoriQ reset config word (RCW) / pre-bootloader (PBL) generation support. The RCW is used to setup clocking and IO allocations and then launches the next stage of boot (usually u-boot). Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-01-16 13:39:52 +01:00
RCW_SITE = https://source.codeaurora.org/external/qoriq/qoriq-components/rcw
RCW_SITE_METHOD = git
RCW_LICENSE = BSD-3-Clause
RCW_LICENSE_FILES = LICENSE
package/rcw : bump to LSDK-19.09 The new rcw.py script is python3-only, but we can use either the system-provided python3, or the one we build with host-python3 if the system does not have it already. It turns out, also, that rcw.py is using #!/usr/bin/env python3, so it will easily find it from $PATH, so we export it in the environment. Signed-off-by: Laurent Hartanerot <laurent.hartanerot@atos.net> [yann.morin.1998@free.fr: - set the proper PATH in the envioronment - do not explicitly call python3, defer to /usr/bin/env in the script - add an accompagnying comment - rewrite commit log accordingly ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-03-22 17:24:44 +01:00
HOST_RCW_DEPENDENCIES = $(BR2_PYTHON3_HOST_DEPENDENCY)
package/rcw: add missing host-python dependency The rcw tool that compiles RCW sources file need host-python Signed-off-by: Laurent Hartanerot <laurent.hartanerot@atos.net> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-03-19 10:30:57 +01:00
package/rcw: add option to generate the RCW When the rcw tools is built, it is probably to generate the RCW (Reset Configuration Word) of the target. So it makes sense to do this directly in the Buildroot infra and install it in the images directory, just like we do for e.g. device tree blobs. Add an option BR2_PACKAGE_HOST_RCW_CUSTOM_PATH that allows to specify the source for the RCW. And while we're at it, make it possible to specify multiple .rcw and .rcwi files, just like for device trees. Signed-off-by: Jared Bents <jared.bents@rockwellcollins.com> [Arnout: * Reword help text and commit message * Remove definition of RCW_DELIVERY_FILE * Define and use RCW_FILES * Enclose everything in ifneq($(RCW_FILES),) * Enclose error in ifeq($(BR_BUILDING),y) * Add actual error message * Don't limit to only %.rcwi files * Don't delete *.bin ] Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-08-03 23:00:52 +02:00
RCW_FILES = $(call qstrip,$(BR2_PACKAGE_HOST_RCW_CUSTOM_PATH))
ifneq ($(RCW_FILES),)
package/rcw: allow not having custom rcwi files A project could quite possibly have a custom rcw file that does not rely on any custom rcw include files (rcwi). Allow the build to succeed if this is the case. Signed-off-by: Francois Gervais <fgervais@distech-controls.com> [yann.morin.1998@free.fr: install includes in a separate hook] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-02-21 15:40:23 +01:00
RCW_INCLUDES = $(filter-out %.rcw,$(RCW_FILES))
package/rcw: add option to generate the RCW When the rcw tools is built, it is probably to generate the RCW (Reset Configuration Word) of the target. So it makes sense to do this directly in the Buildroot infra and install it in the images directory, just like we do for e.g. device tree blobs. Add an option BR2_PACKAGE_HOST_RCW_CUSTOM_PATH that allows to specify the source for the RCW. And while we're at it, make it possible to specify multiple .rcw and .rcwi files, just like for device trees. Signed-off-by: Jared Bents <jared.bents@rockwellcollins.com> [Arnout: * Reword help text and commit message * Remove definition of RCW_DELIVERY_FILE * Define and use RCW_FILES * Enclose everything in ifneq($(RCW_FILES),) * Enclose error in ifeq($(BR_BUILDING),y) * Add actual error message * Don't limit to only %.rcwi files * Don't delete *.bin ] Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-08-03 23:00:52 +02:00
# Get the name of the custom rcw file from the custom list
RCW_PROJECT = $(notdir $(filter %.rcw,$(RCW_FILES)))
# Error if there are no or more than one .rcw file
ifeq ($(BR_BUILDING),y)
ifneq ($(words $(RCW_PROJECT)),1)
$(error BR2_PACKAGE_HOST_RCW_CUSTOM_PATH must have exactly one .rcw file)
endif
endif
package/rcw: allow not having custom rcwi files A project could quite possibly have a custom rcw file that does not rely on any custom rcw include files (rcwi). Allow the build to succeed if this is the case. Signed-off-by: Francois Gervais <fgervais@distech-controls.com> [yann.morin.1998@free.fr: install includes in a separate hook] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-02-21 15:40:23 +01:00
ifneq ($(RCW_INCLUDES),)
define HOST_RCW_ADD_CUSTOM_RCW_INCLUDES
mkdir -p $(@D)/custom_board
cp -f $(RCW_INCLUDES) $(@D)/custom_board
endef
HOST_RCW_POST_PATCH_HOOKS += HOST_RCW_ADD_CUSTOM_RCW_INCLUDES
endif
package/rcw: add option to generate the RCW When the rcw tools is built, it is probably to generate the RCW (Reset Configuration Word) of the target. So it makes sense to do this directly in the Buildroot infra and install it in the images directory, just like we do for e.g. device tree blobs. Add an option BR2_PACKAGE_HOST_RCW_CUSTOM_PATH that allows to specify the source for the RCW. And while we're at it, make it possible to specify multiple .rcw and .rcwi files, just like for device trees. Signed-off-by: Jared Bents <jared.bents@rockwellcollins.com> [Arnout: * Reword help text and commit message * Remove definition of RCW_DELIVERY_FILE * Define and use RCW_FILES * Enclose everything in ifneq($(RCW_FILES),) * Enclose error in ifeq($(BR_BUILDING),y) * Add actual error message * Don't limit to only %.rcwi files * Don't delete *.bin ] Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-08-03 23:00:52 +02:00
define HOST_RCW_ADD_CUSTOM_RCW_FILES
mkdir -p $(@D)/custom_board/rcw
cp -f $(filter %.rcw,$(RCW_FILES)) $(@D)/custom_board/rcw
endef
HOST_RCW_POST_PATCH_HOOKS += HOST_RCW_ADD_CUSTOM_RCW_FILES
package/rcw : bump to LSDK-19.09 The new rcw.py script is python3-only, but we can use either the system-provided python3, or the one we build with host-python3 if the system does not have it already. It turns out, also, that rcw.py is using #!/usr/bin/env python3, so it will easily find it from $PATH, so we export it in the environment. Signed-off-by: Laurent Hartanerot <laurent.hartanerot@atos.net> [yann.morin.1998@free.fr: - set the proper PATH in the envioronment - do not explicitly call python3, defer to /usr/bin/env in the script - add an accompagnying comment - rewrite commit log accordingly ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-03-22 17:24:44 +01:00
# rcw.py is a python3-only script, and we can be using either the
# system-provided python3, or our own built with host-python3.
# Fortunately, rcw.py uses #!/usr/bin/env python3, so it will
# easily find it from PATH.
package/rcw: add option to generate the RCW When the rcw tools is built, it is probably to generate the RCW (Reset Configuration Word) of the target. So it makes sense to do this directly in the Buildroot infra and install it in the images directory, just like we do for e.g. device tree blobs. Add an option BR2_PACKAGE_HOST_RCW_CUSTOM_PATH that allows to specify the source for the RCW. And while we're at it, make it possible to specify multiple .rcw and .rcwi files, just like for device trees. Signed-off-by: Jared Bents <jared.bents@rockwellcollins.com> [Arnout: * Reword help text and commit message * Remove definition of RCW_DELIVERY_FILE * Define and use RCW_FILES * Enclose everything in ifneq($(RCW_FILES),) * Enclose error in ifeq($(BR_BUILDING),y) * Add actual error message * Don't limit to only %.rcwi files * Don't delete *.bin ] Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-08-03 23:00:52 +02:00
define HOST_RCW_BUILD_CMDS
package/rcw : bump to LSDK-19.09 The new rcw.py script is python3-only, but we can use either the system-provided python3, or the one we build with host-python3 if the system does not have it already. It turns out, also, that rcw.py is using #!/usr/bin/env python3, so it will easily find it from $PATH, so we export it in the environment. Signed-off-by: Laurent Hartanerot <laurent.hartanerot@atos.net> [yann.morin.1998@free.fr: - set the proper PATH in the envioronment - do not explicitly call python3, defer to /usr/bin/env in the script - add an accompagnying comment - rewrite commit log accordingly ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-03-22 17:24:44 +01:00
PATH=$(BR_PATH) \
$(@D)/rcw.py \
package/rcw: add missing host-python dependency The rcw tool that compiles RCW sources file need host-python Signed-off-by: Laurent Hartanerot <laurent.hartanerot@atos.net> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-03-19 10:30:57 +01:00
-i $(@D)/custom_board/rcw/$(RCW_PROJECT) \
-I $(@D)/custom_board -o $(@D)/PBL.bin
package/rcw: add option to generate the RCW When the rcw tools is built, it is probably to generate the RCW (Reset Configuration Word) of the target. So it makes sense to do this directly in the Buildroot infra and install it in the images directory, just like we do for e.g. device tree blobs. Add an option BR2_PACKAGE_HOST_RCW_CUSTOM_PATH that allows to specify the source for the RCW. And while we're at it, make it possible to specify multiple .rcw and .rcwi files, just like for device trees. Signed-off-by: Jared Bents <jared.bents@rockwellcollins.com> [Arnout: * Reword help text and commit message * Remove definition of RCW_DELIVERY_FILE * Define and use RCW_FILES * Enclose everything in ifneq($(RCW_FILES),) * Enclose error in ifeq($(BR_BUILDING),y) * Add actual error message * Don't limit to only %.rcwi files * Don't delete *.bin ] Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-08-03 23:00:52 +02:00
endef
define HOST_RCW_INSTALL_DELIVERY_FILE
$(INSTALL) -D -m 0644 $(@D)/PBL.bin $(BINARIES_DIR)/PBL.bin
endef
endif
package/rcw: new package This package adds NXP Layerscape and QoriQ reset config word (RCW) / pre-bootloader (PBL) generation support. The RCW is used to setup clocking and IO allocations and then launches the next stage of boot (usually u-boot). Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-01-16 13:39:52 +01:00
# Copy source files and script into $(HOST_DIR)/share/rcw/ so a developer
# could use a post image or SDK to build/install PBL files.
define HOST_RCW_INSTALL_CMDS
mkdir -p $(HOST_DIR)/share/rcw
cp -a $(@D)/* $(HOST_DIR)/share/rcw
package/rcw: add option to generate the RCW When the rcw tools is built, it is probably to generate the RCW (Reset Configuration Word) of the target. So it makes sense to do this directly in the Buildroot infra and install it in the images directory, just like we do for e.g. device tree blobs. Add an option BR2_PACKAGE_HOST_RCW_CUSTOM_PATH that allows to specify the source for the RCW. And while we're at it, make it possible to specify multiple .rcw and .rcwi files, just like for device trees. Signed-off-by: Jared Bents <jared.bents@rockwellcollins.com> [Arnout: * Reword help text and commit message * Remove definition of RCW_DELIVERY_FILE * Define and use RCW_FILES * Enclose everything in ifneq($(RCW_FILES),) * Enclose error in ifeq($(BR_BUILDING),y) * Add actual error message * Don't limit to only %.rcwi files * Don't delete *.bin ] Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-08-03 23:00:52 +02:00
$(HOST_RCW_INSTALL_DELIVERY_FILE)
package/rcw: new package This package adds NXP Layerscape and QoriQ reset config word (RCW) / pre-bootloader (PBL) generation support. The RCW is used to setup clocking and IO allocations and then launches the next stage of boot (usually u-boot). Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-01-16 13:39:52 +01:00
endef
$(eval $(host-generic-package))
Reference in New Issue Copy Permalink