From: Sascha Hauer <s.hauer@pengutronix.de>
To: Daniel Schultz <d.schultz@phytec.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v5] arm: boards: phytec-som-am335x: Update boot scripts
Date: Tue, 27 Jun 2017 16:36:17 +0200 [thread overview]
Message-ID: <20170627143617.4q6ufyh3uaohsa5k@pengutronix.de> (raw)
In-Reply-To: <6876fb2d-ab61-087f-22a8-b4431d09328e@phytec.de>
On Tue, Jun 27, 2017 at 11:45:44AM +0200, Daniel Schultz wrote:
> Hi Sascha,
>
> > Normally the desired behaviour is that the bootsource can be changed
> > persistently by setting nv.boot.default to the desired source. This
> > does not work when global.boot.default gets overwritten after the nvvars
> > have been read from the environment.
> >
> > This behaviour is not changed with this patch, but I would welcome a
> > patch that changes this script to the desired behaviour. This could
> > be done by changing global.boot.default only when nv.boot.default is
> > empty.
> >
>
> This is already implemented by a test above these changes, isn't it?
>
> snippet from init/bootsource:
> 1 #!/bin/sh
>
> 2
> 3 if [ -n "$nv.boot.default" ]; then
> 4 exit
> 5 fi
Yes, right, that already does it. Sorry for the noise.
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
prev parent reply other threads:[~2017-06-27 14:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 15:42 Daniel Schultz
2017-06-26 6:35 ` Sascha Hauer
2017-06-27 9:45 ` Daniel Schultz
2017-06-27 14:36 ` Sascha Hauer [this message]
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=20170627143617.4q6ufyh3uaohsa5k@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=d.schultz@phytec.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