linux-kernel - Re: [PATCH RFC v1] ARM: olpc: Add support for calling into the XO-1.75's OpenFirmware (OFW)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 5 Aug 2011 20:22:13 +0100
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Andres Salomon <dilinger@...ued.net>
Cc:	linux-arm-kernel@...ts.infradead.org,
	Grant Likely <grant.likely@...retlab.ca>, dsd@...top.org,
	linux-kernel@...r.kernel.org,
	Haojian Zhuang <haojian.zhuang@...vell.com>,
	Mitch Bradley <wmb@...top.org>,
	"H. Peter Anvin" <hpa@...or.com>, eric.y.miao@...il.com
Subject: Re: [PATCH RFC v1] ARM: olpc: Add support for calling into the
	XO-1.75's OpenFirmware (OFW)

On Thu, Aug 04, 2011 at 04:25:51PM -0700, Andres Salomon wrote:
> Add support for saving OFW's cif, and later calling into it to run OFW
> commands from the kernel.  OFW remains resident in memory after boot,
> and the physical/virtual addresses are passed in a boot tag.

If you have open firmware, then you probably have a device tree being
passed to the kernel.  In that case, there aren't any boot tags being
passed.  So I think this patch is rather inconsistent.

Also I believe we had decided that ARM is not going to support the
runtime bits of DT/open firmware stuff.  Unless open firmware is aware
of the setup of the kernel mappings (which would then tie it directly
to the running kernel) it can't access any hardware resources.  I'm
not willing to have external binary blobs (whether or not the source
is available) having a dependency on the setup of the kernel page
tables.  Given that we are consolidating across all platforms, it's
likely that we will want to change the virtual address layout over time
and to have some external binary blob is just going to be a complete
nightmare.

So I really don't like this idea.  At all.
--
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/