Update to kirkstone #638
Merged
Update to kirkstone #638
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Changelog-entry: Update to kirkstone-4.0.17 Signed-off-by: Florin Sarbu <florin@balena.io>
Signed-off-by: Florin Sarbu <florin@balena.io>
Signed-off-by: Florin Sarbu <florin@balena.io>
Signed-off-by: Florin Sarbu <florin@balena.io>
Signed-off-by: Florin Sarbu <florin@balena.io>
Signed-off-by: Florin Sarbu <florin@balena.io>
Signed-off-by: Florin Sarbu <florin@balena.io>
|
@resin-jenkins retest this please |
Signed-off-by: Florin Sarbu <florin@balena.io>
Signed-off-by: Florin Sarbu <florin@balena.io>
floion
force-pushed
the
update_to_kirkstone
branch
from
755cf21
to
020b9d0
Compare
This fixes the warning: += is not a recommended operator combination, please replace it. Signed-off-by: Florin Sarbu <florin@balena.io>
With the move to kirkstone, the kernel was updated and this patch needs to be redone because in the new kernel the imx8mmn-nitrogen8mm.dtsi file has been moved to imx8mmn-nitrogen8mm_rev2.dtsi Signed-off-by: Florin Sarbu <florin@balena.io>
With the switch to kirkstone, the upstream BSP changed the u-boot config used by the machine we include in emgw3.conf Also let's use an append style for MACHINEOVERRIDES which makes it clearer Signed-off-by: Florin Sarbu <florin@balena.io>
floion
force-pushed
the
update_to_kirkstone
branch
3 times, most recently
from
6fa15d6
to
8bfc002
Compare
With the move to kirkstone we need further fixes related to upstream BSP u-boot config changes. We disable CONFIG_ENV_IS_IN_MMC as we do not use it and it also throws a compile error. Additionaly, we remove the disabling of CONFIG_CMD_SAVEENV from here as it is already disabled globally from meta-balena. And last, we update the bootscript by increasing the fdt load address in order to account for increased kernel size. Signed-off-by: Florin Sarbu <florin@balena.io>
The upstream BSP now uses imx-boot-container for mx8mm boards amongst others. Signed-off-by: Florin Sarbu <florin@balena.io>
In balenaOS we bind mount /etc/udev/rules.d for os-udevrules so we need to have OS level udev rules under /lib/udev/rules.d instead. Signed-off-by: Florin Sarbu <florin@balena.io>
…INEOVERRIDES With the switch to kirkstone, the upstream BSP changed the u-boot config used by the machine we include in nitrogen8mm-dwe.conf Also let's use an append style for MACHINEOVERRIDES which makes it clearer Signed-off-by: Florin Sarbu <florin@balena.io>
…gen8mm We need to make more space in the rootfs for this machine. Signed-off-by: Florin Sarbu <florin@balena.io>
With the move to kirkstone the initramfs size has increased. This increase should not reduce too much the available space in the rootfs partition where the initramfs bundled kernel is located. Signed-off-by: Florin Sarbu <florin@balena.io>
Reworked 0002-fixup-imx8mm-evk-fdt-addr.patch, 0003-add-imx8mm-resin-hooks.patch and bundled these 2 patches into 0001-imx8mm-lpddr4-evk-Integrate-with-BalenaOS.patch Reworked 0002-fix-return-vaue-propagatin-out-of-environ.patch Signed-off-by: Florin Sarbu <florin@balena.io>
floion
force-pushed
the
update_to_kirkstone
branch
from
8bfc002
to
5b3b4b6
Compare
With the update to kirkstone, this patch does not apply anymore. And also the original intent of this patch was to remove runtime warnings on the older kernel so we can live with just warnings if that's also the case with the kirkstone kernel. Signed-off-by: Florin Sarbu <florin@balena.io>
|
@balena-ci I self-certify! |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.