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@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
