linux-kernel - Re: [RFC PATCH 4/4] ARM: Xilinx: Adding Xilinx board support

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110502230118.GE28001@n2100.arm.linux.org.uk>
Date:	Tue, 3 May 2011 00:01:18 +0100
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	johnlinn@...cast.net
Cc:	Arnd Bergmann <arnd@...db.de>,
	nicolas pitre <nicolas.pitre@...aro.org>,
	devicetree-discuss@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
	grant likely <grant.likely@...retlab.ca>,
	john linn <john.linn@...inx.com>,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [RFC PATCH 4/4] ARM: Xilinx: Adding Xilinx board support

On Mon, May 02, 2011 at 09:50:11PM +0000, johnlinn@...cast.net wrote:
> Seems easy enough assuming we don't need the SCU early for the core count
> and can get that from the device tree.

Beware.  Things may not be that trivial when you start considering some
of the weirdnesses that some vendors start coming out with.

> Since the SCU and part of the GIC end up in the same 4K page they need to be
> together (unless I'm thinking about that wrong).
> 
> SCU 0xF8000000
> GIC_CPU 0xF8000100
> GIC_DIS 0xF8001000

It is preferable to use the same mapping, as it ensures that you're not
going to create incompatible aliases.

But, before we get too bogged down with this, please realise that it is
possible to setup early mappings from the device tree for things like the
SCU.  Maybe not using ioremap(), but I'm sure we can find some way to use
the iotable_init() stuff to setup some early mappings from DT for this
stuff.
--
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/