Re: SACOM3_BASE

On Sun, Mar 05, 2006 at 12:41:55PM +0100, Peter Postma wrote:
> On Tue, Feb 21, 2006 at 10:37:46PM +0100, Peter Postma wrote:
> > On Wed, Jan 25, 2006 at 09:11:22AM +0900, IWAMOTO Toshihiro wrote:
> > > At Tue, 24 Jan 2006 21:41:26 +0100,
> > > Ignatios Souvatzis wrote:
> > > > In what address space is SACOM3_BASE valid?
> > > > 
> > > > (from sys/arch/arm/sa11x0/sa11x0_reg.h:
> > > > 	#define SACOM3_BASE             0xd000d000
> > > > )
> > > 
> > > Please look at sys/arch/hpcarm/hpcarm/hpc_machdep.c.
> > > (It might be necessary to clean up those codes...)
> > > 
> > 
> > Shouldn't this use pmap_devmap ?
> > 
> 
> Unless I'm misunderstandig pmap_devmap, the following diff should work:
> ftp://ftp.netbsd.org/pub/NetBSD/misc/peter/devmap.diff
> 
> Can someone please check if this patch is correct?

Hm. I'll try it later - with the obvious changes to move the virtual 
address away from 0xd000d000, which is apparently bad at kernel boot time
on machines that have their RAM there.[1]

Regards,
	-is

[1] SA1100 (and 1110?) have four DRAM regions:

0xc0000000 - 0xc7ffffff, 0xc8000000 - 0xcfffffff
0xd0000000 - 0xd7ffffff, 0xd8000000 - 0xdfffffff


The HP Jornada 820, which I'm trying to make runnable, uses
0xc0000000 - 0xc0ffffff and optionally
0xd0000000 - 0xd0ffffff.

	-is