Thank you for the info. This is very close to what I was looking for. Sorry
if this next is a stupid question, but where would I want to look to find
your patches?

 I was thinking of using the Angel loader, so my stuff should bootup very
much like the eval board (I think, I haven't got the board to play with
yet). Will the Angel loader set up the initial MMU's like you described? 
 
 The reference guides for the IXP1200 is available on the developer CD. It
is free (afaik), but I think it is necessary to register in order to get it.

 Is all this kind of information available in a document somewhere or do I
simply have to browse over the code to dig it up? For example I'm wondering
why the linker puts text at address 1020; what is in the address range 0 ->
101f? Perhaps this is BSD related info, not ARM32 specific.

Regards,
Kurt Alstrup


-----Original Message-----
From: Robert Swindells [mailto:rjs@fdy2.demon.co.uk]
Sent: Saturday, October 07, 2000 3:18 AM
To: kurt.alstrup@intel.com
Cc: port-arm32@netbsd.org
Subject: Re: Memory map guidelines



You may want to take a look at my diffs that add SA-1100 and SA-1110
support. I think they will be ready to check in soon, my assabet will
boot up to the point where it tries to mount the root device.

I couldn't find the Programmers Reference Manual on your website, so I
don't know how different the memory map on the IXP-1200 is from the
SA-1100.

All of the arm32 variants assume that the MMU is enabled before the
kernel is loaded.

On the SA-1110, the kernel is loaded at 0xc0000000, but this address has
already been remapped to 0xf0000000 by the bootloader.

The kernel then creates a new translation table which then also remaps
the peripheral devices above the end of kernel vm space.

What do you intend to use for a bootloader ?

Robert Swindells