12755 2018-05-16 19:49:04 +0000 Separate boot config recipes are at odds with setting APPEND at the image level 2026-01-29 16:15:06 +0000 1 1 7 Build System, Metadata & Runtime OE-Core oe-core other 6.99 x86 Multiple NEW Medium+ normal 6.99 1 bluelightning unassigned naveen.kumar.saini randy.macleod tim.orling tom.rini --- --- Don't know oldest_to_newest 80603 0 bluelightning 2018-05-16 19:49:04 +0000 As part of the work for 2.5 we made some changes in order to move the bootloader configuration out to separate recipes (grub-bootconf and systemd-bootconf); at least systemd-bootconf is reading the APPEND variable which is used to set the kernel command line. Unfortunately this is problematic in that the previous assumption was that APPEND was only read in the image context (and therefore could be effectively set from there). The following change is an example: http://cgit.openembedded.org/openembedded-core/commit/?id=cfc09de06ecc12bb42181004689e881c75072665 Cal suggested that the separate configuration wasn't used by default and thus this shouldn't be a major problem yet - I wasn't clear on the details though. Somehow this needs to be reconciled. 88751 1 tim.orling 2020-12-10 15:59:34 +0000 Naveen any thoughts on this moving forward? 96983 2 randy.macleod 2023-10-24 14:24:56 +0000 Bulk move from 4.99 or 0.00 to 5.99