From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Stanislaw Skowronek <sskowron@ET.PUT.Poznan.PL>,
linux-mips@linux-mips.org
Subject: Re: 32-bit ABI
Date: Sat, 24 Apr 2004 10:18:54 +0200 [thread overview]
Message-ID: <20040424081854.GB26165@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.55.0404240959200.14494@jurand.ds.pg.gda.pl>
On Sat, Apr 24, 2004 at 10:07:02AM +0200, Maciej W. Rozycki wrote:
> > > > Yeah. The weirdness is not in that part; what's weird is placing the rest
> > > > of memory somewhere else.
> > >
> > > Perhaps to be able to put iomem stuff in CKSEG1 without implying a hole
> > > in the RAM.
> >
> > The machine is running a 64-bit kernel so likely it was designed with
> > little consideration for 32-bit issues.
>
> Well, the exception arrangement requires RAM starting from the physical
> address 0. It seems natural to place RAM just there, avoiding additional
> complexity to address decoders. But then firmware has to be somewere
> around 0x1fc00000, so to support more than 508MB of RAM the designers
> would have to create a hole in RAM, which would have to be handled by the
> OS then. Thus abandoning the idea of putting RAM low, placing it
> somewhere above 0x1fffffff and just mapping some of it at 0 for the
> exceptions seems a better solution.
>
> Fortunately everything is not a PC. :-)
Actually the R10000 way to do something like this is to use the uncached
attribute like in the Origin. It allows using the same physical address
space several times for different purposes. So on node 0 of an Origin
indeed memory starts at physical address zero and there is no hole for
the firmware. IP27 is afaik the only system using this R10000 feature
which surprises me a little due to the otherwise great similarity of these
two systems.
Ralf
next prev parent reply other threads:[~2004-04-24 8:19 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-23 8:02 MC Parity Error Florian Lohoff
2004-04-23 13:11 ` Maciej W. Rozycki
2004-04-23 16:45 ` Ralf Baechle
2004-04-23 17:11 ` Maciej W. Rozycki
2004-04-23 20:43 ` Dominic Sweetman
2004-04-23 21:06 ` Maciej W. Rozycki
2004-04-24 6:28 ` 32-bit ABI Stanislaw Skowronek
2004-04-24 7:09 ` Thiemo Seufer
2004-04-24 7:17 ` Ralf Baechle
2004-04-24 7:31 ` Stanislaw Skowronek
2004-04-24 7:38 ` Ralf Baechle
2004-04-24 7:46 ` Stanislaw Skowronek
2004-04-24 7:51 ` Maciej W. Rozycki
2004-04-24 7:55 ` Ralf Baechle
2004-04-24 8:07 ` Maciej W. Rozycki
2004-04-24 8:14 ` Stanislaw Skowronek
2004-04-24 8:18 ` Ralf Baechle [this message]
2004-04-24 8:23 ` Maciej W. Rozycki
2004-04-24 8:26 ` Ralf Baechle
2004-04-24 8:49 ` Maciej W. Rozycki
2004-04-24 8:14 ` Ralf Baechle
2004-04-24 8:17 ` Stanislaw Skowronek
2004-04-24 8:26 ` Thiemo Seufer
2004-04-24 7:37 ` Thiemo Seufer
2004-04-24 7:18 ` Maciej W. Rozycki
2004-04-24 7:34 ` Stanislaw Skowronek
2004-04-24 7:44 ` Ralf Baechle
2004-04-24 7:47 ` Stanislaw Skowronek
2004-04-24 7:48 ` Maciej W. Rozycki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040424081854.GB26165@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@ds2.pg.gda.pl \
--cc=sskowron@ET.PUT.Poznan.PL \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox