NetCube-Systems-Austria/kumquat-buildroot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
e35750b524
kumquat-buildroot/package/qoriq-rcw/Config.in.host

41 lines
1.4 KiB
Plaintext
Raw Normal View History

package/qoriq-rcw: rename from package/rcw This is really only for QoriQ SoCs. Also the upstream package - despite its base name of the git repository - is "qoriq-components/rcw". Thus rename it to a more specify package name. Note that there are other rcw implementations for other platforms, and each implementation only applies to that specific platform; it hus does not make sense that there are more than one rcw enabled at the same time; so we keep using /usr/share/rcw as the install location; this also help backward compatibility with existing post-build scripts. Signed-off-by: Changming Huang <jerry.huang@nxp.com> Cc: Michael Walle <michael@walle.cc> [yann.morin.1998@free.fr: - rebase on master - incorporate changes by Michael - don't move to an 'nxp' sub-directory - reword the legacy entry; select the new package - expand commit log to explain why we keep installing in host/usr/share/rcw/ (thanks to Michael for prompting that) ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-02-07 09:38:50 +01:00
config BR2_PACKAGE_HOST_QORIQ_RCW
bool "host qoriq-rcw"
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
help
This package provides an reset configuration word(RCW)
compiler to build NXP QoriQ/LS PBL/RCW binary(s).
The package installs example configurations and scripts
for each devkit supported in the current release see
$(HOST_DIR)/share/rcw. Either a SDK or post scripts can
then use this toolset and examples.
package/qoriq-rcw: update codeaurora URLs to github NXP moved all its open source code repositories from Code Aurora Forum to github. See for example: https://github.com/nxp-imx/meta-imx/commit/39bc4d81969a40e0da660519cf4ed083b9c53097 Software packages are now grouped in several NXP github projects/organizations (nxp-imx, nxp-qoriq, ...). See: https://www.nxp.com/design/software/embedded-software/nxp-github:NXP-GITHUB The NXP code published on Code Aurora is still present (at the time of this commit) but is no longer receiving updates. It is also expected to be shut down on 2023-03-31. The Code Aurora website https://source.codeaurora.org/ currently show the following message: """ Note: Qualcomm Innovation Center Inc. maintained repositories have migrated to git.codelinaro.org. QUIC repositories on this site will not receive any updates after March 31, 2022, and will be deleted on March 31, 2023. If your project depends on these repositories, please adjust your tooling configuration to use the new, up-to-date project location. """ For this reason, the NXP recipes using codeaurora.org urls need to be updated to the correct github.com replacement. Note: this commit does not change the component version. Only the download URL is updated. The archive content is expected to be the same. Note 2: the _SITE_METHOD is also changed from "git" to the default "wget", for faster downloads. This is why the package hash has changed. Signed-off-by: Julien Olivain <ju.o@free.fr> Reviewed-by: Francois Perrad <francois.perrad@gadz.org> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-12-29 20:47:11 +01:00
https://github.com/nxp-qoriq/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
package/qoriq-rcw: rename from package/rcw This is really only for QoriQ SoCs. Also the upstream package - despite its base name of the git repository - is "qoriq-components/rcw". Thus rename it to a more specify package name. Note that there are other rcw implementations for other platforms, and each implementation only applies to that specific platform; it hus does not make sense that there are more than one rcw enabled at the same time; so we keep using /usr/share/rcw as the install location; this also help backward compatibility with existing post-build scripts. Signed-off-by: Changming Huang <jerry.huang@nxp.com> Cc: Michael Walle <michael@walle.cc> [yann.morin.1998@free.fr: - rebase on master - incorporate changes by Michael - don't move to an 'nxp' sub-directory - reword the legacy entry; select the new package - expand commit log to explain why we keep installing in host/usr/share/rcw/ (thanks to Michael for prompting that) ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-02-07 09:38:50 +01:00
if BR2_PACKAGE_HOST_QORIQ_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
package/qoriq-rcw: rename from package/rcw This is really only for QoriQ SoCs. Also the upstream package - despite its base name of the git repository - is "qoriq-components/rcw". Thus rename it to a more specify package name. Note that there are other rcw implementations for other platforms, and each implementation only applies to that specific platform; it hus does not make sense that there are more than one rcw enabled at the same time; so we keep using /usr/share/rcw as the install location; this also help backward compatibility with existing post-build scripts. Signed-off-by: Changming Huang <jerry.huang@nxp.com> Cc: Michael Walle <michael@walle.cc> [yann.morin.1998@free.fr: - rebase on master - incorporate changes by Michael - don't move to an 'nxp' sub-directory - reword the legacy entry; select the new package - expand commit log to explain why we keep installing in host/usr/share/rcw/ (thanks to Michael for prompting that) ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-02-07 09:38:50 +01:00
config BR2_PACKAGE_HOST_QORIQ_RCW_CUSTOM_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
string "RCW Source file paths"
help
Space-separated list of .rcw and .rcwi files, that will be
used to generate a RCW binary. The entire list of .rcwi files
used by the .rcw file must be specified. There must be a
single .rcw file in the list.
This is optional. If left empty, the rcw package will be
included for use in the SDK or with post scripts but no
RCW binary will not be generated.
package/qoriq-rcw: add in-tree rcw source support The qoriq-rcw repository contains the RCW source for a lot of development boards already. Add a new option BR2_PACKAGE_HOST_QORIQ_RCW_INTREE to use one of these rather than a custom one. Signed-off-by: Jerry Huang <jerry.huang@nxp.com> [Arnout: - rename the option to _RCW_INTREE; - update commit message, documentation, and internal variables accordingly; - reorganise condition tree so it becomes a little simpler; - add patsubst so the source can be specified as either %.rcw or %.bin; - always install it as PBL.bin, to be consistent with the custom option. ] Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2020-02-07 09:38:52 +01:00
config BR2_PACKAGE_HOST_QORIQ_RCW_INTREE
string "In-tree RCW name"
depends on !BR2_PACKAGE_HOST_QORIQ_RCW_CUSTOM_PATH
help
This option is used to specify the RCW binary file for board.
which is composed as platform/serdes_value/rcw_file: platform
is the platform name, serdes_value is the setting of the
Serdes, and rcw_file is the file name of RCW. For example:
"ls1028ardb/R_SQPP_0x85bb/rcw_1300_sdboot.bin"
If this option is empty, no rcw file is used.
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
endif
Reference in New Issue Copy Permalink