[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151127195148.GB30871@n2100.arm.linux.org.uk>
Date: Fri, 27 Nov 2015 19:51:48 +0000
From: Russell King - ARM Linux <linux@....linux.org.uk>
To: Pali Rohár <pali.rohar@...il.com>
Cc: "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Ivaylo Dimitrov <ivo.g.dimitrov.75@...il.com>,
Laura Abbott <lauraa@...eaurora.org>,
Arnd Bergmann <arnd@...db.de>,
Tony Lindgren <tony@...mide.com>,
Sebastian Reichel <sre@...ian.org>,
Will Deacon <will.deacon@....com>,
linux-kernel@...r.kernel.org, Rob Herring <robherring2@...il.com>,
Pavel Machek <pavel@....cz>,
Grant Likely <grant.likely@...aro.org>,
linux-omap@...r.kernel.org, Frank Rowand <frowand.list@...il.com>,
Andreas Färber <afaerber@...e.de>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 5/5] arm: boot: store ATAGs structure into DT
"/chosen/linux,atags" entry
On Fri, Nov 27, 2015 at 01:27:23PM +0000, Russell King - ARM Linux wrote:
> It is possible to redirect any program to open any other file. You can
> do it via a LD preload, and intercepting the open(), and possibly the
> read() calls if you want to do something more fancy. The down-side is
> that you have to arrange for the preloaded object to be used by the
> linker, and the additional overhead it places on the intercepted
> functions.
Another idea if people don't like the preload idea.
We could create a zero-sized /proc/atags, and then use a bind mount in
userspace to bind some other file containing the required information
on top. That could even be the atag blob from /sys/firmware/whatever.
The N700 (or whatever platform needs it) could be responsible for
creating the zero-sized /proc/atags so that we don't have it everywhere.
--
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
--
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