From: Michael Graichen <michael.graichen@hotmail.com>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>,
"barebox@lists.infradead.org" <barebox@lists.infradead.org>,
Sascha Hauer <s.hauer@pengutronix.de>
Subject: AW: Read Barebox Infos from Linux
Date: Tue, 22 Feb 2022 11:57:59 +0000 [thread overview]
Message-ID: <AM9P192MB08709FA612A57392AE63B854AB3B9@AM9P192MB0870.EURP192.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <bde9d08d-43da-c3eb-6362-09c33ab8e172@pengutronix.de>
Hey Ahmed and Sascha,
Thanks for your reply.
This is all meant to work with devicetree support. Not x86/efi systems?
Best regards
Michael
________________________________________
Von: Ahmad Fatoum <a.fatoum@pengutronix.de>
Gesendet: Montag, 21. Februar 2022 14:59
An: Michael Graichen; barebox@lists.infradead.org
Betreff: Re: Read Barebox Infos from Linux
Hi Michael,
On 21.02.22 14:04, Michael Graichen wrote:
> Hey,
>
> I was just wondering if it is possibe to read the Barebox log messages or the Barebox version from within Linux?
That's what CONFIG_FS_PSTORE_CONSOLE does, see
https://www.barebox.org/doc/latest/filesystems/pstore.html
> Barebox version from within Linux?
Yes, check out /proc/device-tree/chosen/barebox-version
If you are curious what else barebox is fixing up into the device tree,
try of_diff - +
This will apply all DT fixups to a copy of the barebox device tree and
show a diff before and after, e.g.
chosen {
+ barebox-version = "barebox-2021.05.0-20220126-2";
+ bootargs = "console=ttymxc1,115200n8";
+ reset-source = "POR";
+ reset-source-instance = <0x0>;
+ bootsource = "/soc/bus@2100000/mmc@2198000";
};
Cheers,
Ahmad
>
> Best regards
> Michael
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
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:[~2022-02-22 11:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 13:04 Michael Graichen
2022-02-21 13:59 ` Ahmad Fatoum
2022-02-22 11:57 ` Michael Graichen [this message]
2022-02-23 8:14 ` Sascha Hauer
2022-02-21 14:01 ` 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=AM9P192MB08709FA612A57392AE63B854AB3B9@AM9P192MB0870.EURP192.PROD.OUTLOOK.COM \
--to=michael.graichen@hotmail.com \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@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