Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: Maciej Borzecki <maciej.borzecki@open-rnd.pl>
Cc: openembedded-core@lists.openembedded.org
Subject: using wic and extlinux together
Date: Wed, 11 Sep 2019 15:46:06 -0400	[thread overview]
Message-ID: <20190911194606.GA6574@linux-uys3> (raw)

Hi Maciej,

I'm working on an OE BSP layer and was hoping you could help direct
me somewhat. Ultimately what I'd like to do is add the string " debug
earlyprintk" to the kernel cmdline (for U-Boot). The BSP I'm working on uses
wic, and has a "--source bootimg-partition" configuration in its wic file.
This invokes scripts/lib/wic/plugins/source/bootimg-partition.py.

In theory there are two ways I could reach my goal:

1) tweak scripts/lib/wic/plugins/source/bootimg-partition.py to include the
   extra options
2) generate my own extlinux.conf file

Generating my own extlinux.conf file involves defining a bunch of
UBOOT_EXTLINUX_* variables. When I do this, the extlinux.conf file is created,
but it gets ignored/clobbered by the stuff wic does. It looks like the wic
code has an option to look for an extlinux.conf file, but for some reason it's
not finding the one OE is generating. Any idea where it is looking?

	configfile = cr.ks.bootloader.configfile
	...
	    custom_cfg = get_custom_config(configfile)

In any case, there is no apparent way to tweak what wic generates. Either wic
generates its own extlinux.conf file, or it uses the one it finds (wherever it
is looking).

Would it make sense for me (or you, if you want) to tweak
scripts/lib/wic/plugins/source/bootimg-partition.py to make use of any
UBOOT_EXTLINUX_* variables it might find when generating the extlinux.conf
file?

Best regards,
	Trevor


                 reply	other threads:[~2019-09-11 19:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190911194606.GA6574@linux-uys3 \
    --to=twoerner@gmail.com \
    --cc=maciej.borzecki@open-rnd.pl \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox