linux-mips
[Top] [All Lists]

Re: porting arcboot

To: linux-mips@linux-mips.org
Subject: Re: porting arcboot
From: Vivien Chappelier <vivienc@nerim.net>
Date: Mon, 10 Feb 2003 13:50:30 +0100 (CET)
Original-recipient: rfc822;linux-mips@linux-mips.org
Sender: linux-mips-bounce@linux-mips.org
---------- Forwarded message ----------
Date: Mon, 10 Feb 2003 13:49:49 +0100 (CET)
From: Vivien Chappelier <glaurung@vivienc.net1.nerim.net>
To: Guido Guenther <agx@gandalf.physik.uni-konstanz.de>
Subject: Re: porting arcboot

On Mon, 10 Feb 2003, Guido Guenther wrote:
> > Can't we read the load address (and needed space) from the elf header
> s/load address/kernel's load address/

Yes, that's what we do already. I was speaking of arcboot load address,
sorry this wasn't very clear :)

> In case we find a unique place for arcboot in the memory map of the
> different subarches.

On the O2 physical memory starts from KSEG0 (0x80000000), the kernel is
loaded there for 32-bit version or in XKPHYS (0x9800000000000000) for the
64-bit version. I don't really know where the PROM code and data is
located precisely, but loading something (arcboot or a kernel) at
0x88000000 as with ip22 is not an option; the PROM says something like
'loading there would overwrite an existing program'. Why is kernel/arcboot
loaded at 0x88000000 on ip22? Is KSEG0 an option for ip22?
BTW, what's the status of mips64/ip22? I guess the PROM doesn't support
64-bit as on the ip32, so arcboot with 64-bit support would be needed as
well, right?

Vivien.



<Prev in Thread] Current Thread [Next in Thread>