From: Sascha Hauer <s.hauer@pengutronix.de>
To: Juergen Beisert <jbe@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 2/3] Add next generation default environment template
Date: Sun, 24 Jun 2012 14:23:48 +0200 [thread overview]
Message-ID: <20120624122348.GA24458@pengutronix.de> (raw)
In-Reply-To: <201206041047.45047.jbe@pengutronix.de>
On Mon, Jun 04, 2012 at 10:47:44AM +0200, Juergen Beisert wrote:
> Sascha Hauer wrote:
> > [...]
> > diff --git a/defaultenv-2/base/init/bootargs-base
> > b/defaultenv-2/base/init/bootargs-base new file mode 100644
> > index 0000000..8e588ad
> > --- /dev/null
> > +++ b/defaultenv-2/base/init/bootargs-base
> > @@ -0,0 +1,8 @@
> > +#!/bin/sh
> > +
> > +if [ "$1" = menu ]; then
> > + init-menu-add-entry "$0" "Base bootargs"
> > + exit
> > +fi
> > +
> > +global.linux.bootargs.base="console=ttyS0,115200"
> > [...]
>
> Seems if you want to change the console setting here, you always have to save
> the change and restart the system to take affect of the new value when
> the 'boot' command is running. Old behaviour was an immediate change without
> saving and restarting. This was a nice behaviour when one just wants to try a
> different parameter without destroying the old environment.
Late response on this one:
You don't have to restart. Instead, you can just overwrite it on the
command line and boot afterwards:
barebox: global.linux.bootargs.base=console=ttymytempconsole0,115200
barebox: boot
Some more background:
The idea is that the bootentries in /env/boot/* can be executed and
setup the boot environment, afterwards you would only run 'bootm'
without additional arguments.
For example you could execute /env/boot/nand-ubi, then your setup would
be:
bootm.image = /dev/nand0.kernel.bb
bootm.oftree =
bootm.initrd =
linux.bootargs.base = console=ttymxc0,115200
linux.bootargs.ip = ip=dhcp
linux.bootargs.root = root=ubi0:root ubi.mtd=nand0.root rootfstype=ubifs
linux.mtdparts.nand0 = mxc_nand:512k(nand0.barebox)ro,128k(nand0.bareboxenv),4M(nand0.kernel),-(nand0.root)
linux.mtdparts.nor0 = physmap-flash.0:512k(nor0.barebox)ro,128k(nor0.bareboxenv),4M(nor0.kernel),-(nor0.root)
If then you want to boot once with a devicetree without permanently
changing you environment, you could do a
barebox: global.bootm.oftree=/whatever/oftree
barebox: bootm
The possibilities are there, maybe the question is how we can simplify
(and document) them so that people are actually aware of what can be
done.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-06-24 12:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 7:04 new default environment Sascha Hauer
2012-05-16 7:04 ` [PATCH 1/3] bootm: Add default images variables Sascha Hauer
2012-05-16 7:04 ` [PATCH 2/3] Add next generation default environment template Sascha Hauer
2012-06-04 8:47 ` Juergen Beisert
2012-06-24 12:23 ` Sascha Hauer [this message]
2012-05-16 7:04 ` [PATCH 3/3] ARM pcm038: Switch to new environment Sascha Hauer
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=20120624122348.GA24458@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=jbe@pengutronix.de \
/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