linux-kernel - Re: [PATCH V5 3/4] ARM: Xilinx: base header files and assembly macros

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]

Date:	Wed, 30 Mar 2011 15:29:03 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	John Linn <John.Linn@...inx.com>
Cc:	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	linux@....linux.org.uk, catalin.marinas@....com,
	glikely@...retlab.ca, jamie@...ieiles.com
Subject: Re: [PATCH V5 3/4] ARM: Xilinx: base header files and assembly macros

On Wednesday 30 March 2011, John Linn wrote:
> Yes that makes sense.  We don't have immediate plans for PCI and 
> I was assuming when we add PCI we would need to change that.  
> 
> If you think I shouldn't put it off then I'll fix it now.  My 
> preference was to get the platform supported, then add more features.

Getting it fixed properly depends a bit on the PCI implementation.
I've been planning to clean up this part of the ARM architecture
for some time and I can probably do it for one more platform when
I get to it.

My idea for the multiplatform kernel is to have a global I/O space
window (maybe 1 MB) that is in the same location in the virtual
address space all the time, so any platform that wants to support
PCI with direct-mapped I/O space can simply map it in there
at boot time.

	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/