mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Peter Mamonov <pmamonov@gmail.com>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH] Pass barebox version to kernel
Date: Tue, 27 Feb 2018 09:34:30 +0100	[thread overview]
Message-ID: <20180227083430.ze66vwf42ytipjsf@pengutronix.de> (raw)
In-Reply-To: <20180226101201.k7ync5dx3yaynslg@localhost.localdomain>

Hi Peter,

On Mon, Feb 26, 2018 at 01:12:02PM +0300, Peter Mamonov wrote:
> Hi, Sasha,
> 
> On Mon, Feb 26, 2018 at 09:23:49AM +0100, Sascha Hauer wrote:
> > When userspace is interested in the barebox version it has currently no
> > way of reliably reading it. Add it to the kernel command line as it's an
> > established way to pass information from the bootloader to the kernel.
> > If CONFIG_FLEXIBLE_BOOTARGS is enabled then the barebox version is
> > passed in the "bootloader.version=" variable.
> 
> Some time ago we solved a similar problem: a number of parameters including 
> barebox version, MAC address (which may be random due to the lack of a NIC 
> EEPROM) and some vendor specific parameters are passed to the kernel via DTB.  
> A dedicated command was implemented which can either patch the existing DTB or 
> generate an overlay DTB.  In the latter case the overlay DTB is passed to the 
> kernel with the help of a new `bootm` option. Of course the latter approach 
> requires support on the kernel side.

We could of course pass the barebox version in the /chosen node. That
would require a of_register_fixup(). Why would we need an extra command
for that?
The MAC address should already be inserted into the kernel device tree
automatically.

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

  reply	other threads:[~2018-02-27  8:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-26  8:23 Sascha Hauer
2018-02-26 10:12 ` Peter Mamonov
2018-02-27  8:34   ` Sascha Hauer [this message]
2018-02-27 19:43     ` Peter Mamonov
2018-02-28  7:34       ` 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=20180227083430.ze66vwf42ytipjsf@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=pmamonov@gmail.com \
    /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