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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 2 May 2011 21:50:11 +0000 (UTC)
From:	johnlinn@...cast.net
To:	Arnd Bergmann <arnd@...db.de>
Cc:	nicolas pitre <nicolas.pitre@...aro.org>, linux@....linux.org.uk,
	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 Monday 02 May 2011 23:27:04 johnlinn@...cast.net wrote:
> > Yes we could explain hard coded numbers.  Ideally GIC driver would
> support
> > device tree it seems like to me.
> 
> > 
> > Seems like the GIC driver could remap it's own memory but maybe that
> won't
> > work across all platforms and then the platform would need to do
> it.
> 
> Why not just add a stub in the xilinx platform for now that remaps
> the
> memory using ioremap and calls the regular GIC initialization?

Seems easy enough assuming we don't need the SCU early for the core count
and can get that from the device tree.

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

-- John

> 
> That function can then easily be moved to common code when another
> platform uses 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/