Bug 12755

Summary: Separate boot config recipes are at odds with setting APPEND at the image level
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Paul Eggleton <bluelightning>
Component: oe-core otherAssignee: Unassigned <unassigned>
Status: NEW --- QA Contact:
Severity: normal    
Priority: Medium+ CC: naveen.kumar.saini, randy.macleod, tim.orling, tom.rini
Version: 6.99   
Target Milestone: 6.99   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know

Description Paul Eggleton 2018-05-16 19:49:04 UTC 
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.
Comment 1 Tim Orling 2020-12-10 15:59:34 UTC 
Naveen any thoughts on this moving forward?
Comment 2 Randy MacLeod 2023-10-24 14:24:56 UTC 
Bulk move from 4.99 or 0.00 to 5.99