linux-kernel - Re: [PATCH 5/6] MN10300: Add the MN10300/AM33 architecture to the kernel [try #5]

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]

Message-ID: <4094.1194869944@redhat.com>
Date:	Mon, 12 Nov 2007 12:19:04 +0000
From:	David Howells <dhowells@...hat.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	dhowells@...hat.com, Andrew Morton <akpm@...ux-foundation.org>,
	torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
	linux-am33-list@...hat.com
Subject: Re: [PATCH 5/6] MN10300: Add the MN10300/AM33 architecture to the kernel [try #5]

Alan Cox <alan@...rguk.ukuu.org.uk> wrote:

> > Some are part of the CPU core and affect things like CPU core itself, CPU
> > caches, MMU/TLB and exceptions/interrupts.  Others are on-silicon devices
> > such as the serial ports, the bus controller, the SDRAM controller.
> 
> How are they addressed - as CPU registers or as memory/IO space ?

Well, they're all accessed as memory locations within a special range of
addresses (all of 0xCxxxxxxx and 0xDxxxxxxx).  This includes the magic CPU
registers.  This is hard coded by the CPU before the MMU gets its hands on the
addresses, AFAIK.

I also wondered what about the boot wrapper (the kernel decompressor):  Is that
permitted to use readb() and co?

David
-
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/