[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50067860.qzAxcgo8L4@wuerfel>
Date: Mon, 28 Dec 2015 23:27:17 +0100
From: Arnd Bergmann <arnd@...db.de>
To: linux-arm-kernel@...ts.infradead.org, frowand.list@...il.com
Cc: Pali Rohár <pali.rohar@...il.com>,
Ivaylo Dimitrov <ivo.g.dimitrov.75@...il.com>,
Laura Abbott <lauraa@...eaurora.org>,
Tony Lindgren <tony@...mide.com>,
Sebastian Reichel <sre@...ian.org>,
Will Deacon <will.deacon@....com>,
linux-kernel@...r.kernel.org,
Devicetree Spec List <devicetree-spec@...r.kernel.org>,
Rob Herring <robherring2@...il.com>,
Pavel Machek <pavel@....cz>,
Grant Likely <grant.likely@...aro.org>,
Russell King <linux@....linux.org.uk>,
linux-omap@...r.kernel.org,
Andreas Färber <afaerber@...e.de>
Subject: Re: [PATCH 1/5] arm: devtree: Set system_rev from DT "/revision"
On Monday 28 December 2015 13:01:22 Frank Rowand wrote:
>
> Patch 2/5 copies the value from ATAG_REVISION into the fdt "/revision"
> property.
>
> If the use of /revision is limited to being a location to hold an ATAG
> value to pass to the global variable system_rev, then it would make
> sense to just copy directly from the ATAG value into system_rev in the
> same board file where you are copying the ATAGs.
Agreed. That would be simpler, and avoid a situation where someone relies
on the /revision property in DT to be set from the atags compat code
(preventing an upgrade to a newer bootloader), or on the system_rev variable
to be the same across multiple boot loaders, in the absence of other
kernel code setting it.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists