This is a hack to retain existing behaviour in case of ambiguities of
device names between differen targets. For now, let Broadcom have the
lowest priority.
genconfig script is to be replaced soon and the existing code makes
adding a proper check hard and we need some way to deal with the
ambiguity quickly.
Signed-off-by: Andreas Gnau <andreas.gnau@iopsys.eu>
Add hack to consume configs from custom-devices in a separate feed
custom-devices, but only in that feed and not in other feeds. There is
no value in implementing a generic solution, because the whole genconfig
system will be replaced with something else.
Signed-off-by: Andreas Gnau <andreas.gnau@iopsys.eu>
A recent change broke genconfig for targets with hyphens. Fix this.
Fixes: a22898c92b ("iop: genconfig: Get subtarget using data from OpenWrt")
Signed-off-by: Andreas Gnau <andreas.gnau@iopsys.eu>
Determine the subtarget for a given device using data generated from the
OpenWrt build system instead of parsing the image makefiles directly.
This provides correct results even when fancy tricks like includes
inside the Makefiles are used, which is the case for an upcoming feature
where additional devices can be defined in external feeds.
Signed-off-by: Andreas Gnau <andreas.gnau@iopsys.eu>
OpenWrt normalises the version number in the image name to lowercase.
For consistency set the version already in lowercase in the config so
that there is not inconsistency between the version stored in
/etc/os-release and the image name.
Signed-off-by: Andreas Gnau <andreas.gnau@iopsys.eu>
Use a new version format:
* More strict regex for filtering tags for determining version which
prevents OpenWrt and hopefully other tags from becoming the IOWRT
version
* version follows standard git-describe format with -dirty
* customerconfigs are appended to the version
Example-versions:
* 7.1.0BETA1
* 7.1.0BETA1-29-g1292f9102e-dirty
* 7.1.0BETA1-29-g1292f9102e-secureboot
* 7.1.0BETA1-29-g1292f9102e-securebooteval
Signed-off-by: Andreas Gnau <andreas.gnau@iopsys.eu>
Adapt genconfig to generate the correct config after the change to the
target-subtarget-device in target iopsys_brcm63xx_arm in feeds/targets.
Signed-off-by: Andreas Gnau <andreas.gnau@iopsys.eu>
Remove CONFIG_TARGET_MULTI_PROFILE=y and
CONFIG_TARGET_PER_DEVICE_ROOTFS=y that were hardcoded in genconfig and
genconfig_min. Since feeds/targets commit 295d1566 (treewide: Add
MULTI_PROFILE and PER_DEVICE_ROOTFS config, 2021-08-05), the options are
added in feeds/targets.
Also bring the unmaintainable copy-paste of genconfig that is
genconfig_min in sync with genconfig with regards target-specific config
options.
when concatenating configurations there has to be an empty line at
the end otherwise the last line could be combined with the next
configuration option.
In order to determine, whether we are developers or not, check the
git-remotes for SSH-URLs instead of checking for the non-existence of
any HTTP-URLs. This fixes dev-mode not being detected properly when
curious devs add other HTTP-remotes such as upstream OpenWRT.
This also makes the check consistent with the check done in the main
"iop" script in the root.
