From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Baruch Siach <baruch@tkos.co.il>
Cc: barebox@lists.infradead.org
Subject: Re: Determining barebox version from linux
Date: Thu, 23 Dec 2010 08:07:07 +0100 [thread overview]
Message-ID: <20101223070707.GK19266@game.jcrosoft.org> (raw)
In-Reply-To: <20101223061806.GA12874@jasper.tkos.co.il>
On 08:18 Thu 23 Dec , Baruch Siach wrote:
> Hi Marc,
>
> On Thu, Dec 23, 2010 at 11:03:31AM +1100, Marc Reilly wrote:
> > I want to be able to determine what version of barebox I have on my NOR
> > flash, after booting into linux.
>
> [snip]
>
> > Does anybody else accomplish this in a better way? (I don't want to pass the
> > barebox version as an arg when booting the kernel - I'd rather it be more
> > "standalone").
>
> I set the board revision number, using armlinux_set_revision(), to pass the
> version of the bootloader to the kernel, and then extract it from the
> 'Revision' field in /proc/cpuinfo. This solution is ARM specific, though.
It will be better to have a std way as you mqy ise the system_rev for other
stuff as example on some at91
I sync we could generate a /etc/version in the env and then export it in linux
via the fs
I think we could do like this
in barebox itself we keep a default read only fs (default env) that we merge
the same way as a unionfs in barebox to avoid duplication and allow non
modifable file with the rw env
and we will do it in linux also
so linux can get the data from barebox and modify it
Best Regards,
J.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2010-12-23 7:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 0:03 Marc Reilly
2010-12-23 6:18 ` Baruch Siach
2010-12-23 7:07 ` Jean-Christophe PLAGNIOL-VILLARD [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=20101223070707.GK19266@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=barebox@lists.infradead.org \
--cc=baruch@tkos.co.il \
/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