From: Dominic Sweetman <dom@algor.co.uk>
To: Matthew Dharm <mdharm@momenco.com>
Cc: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
Dominic Sweetman <dom@algor.co.uk>, Jun Sun <jsun@mvista.com>,
Linux-MIPS <linux-mips@linux-mips.org>
Subject: Re: Interrupt handling....
Date: Wed, 4 Sep 2002 21:08:18 +0100 (BST) [thread overview]
Message-ID: <200209042008.VAA25407@mudchute.algor.co.uk> (raw)
In-Reply-To: <20020904093627.A5241@momenco.com>
Matthew Dharm (mdharm@momenco.com) writes:
> > As I understand 0xfc00000c is the physical address. Thus you cannot
> > reach it via KSEG0/1 (although you may use XKPHYS to get there in the
> > 64-bit mode). Still ioremap() already handles the case mapping the area
> > requested in the KSEG2 space, so it should work just fine.
>
> This is the case. The board itself has up to 1G of SDRAM. Most of the
> boards we sell have a minimum of 512MB. So our I/O (PCI, external devices,
> etc.) all have physical addresses in the high-end of the address space.
Well, next time, get your board designers to think before they map...
It's generally better to map some DRAM low (for boot ROMs and other
stupid programs you don't want to make big-address aware), then remap
the whole DRAM to some very high address for Linux. Much better than
forcing you to use the TLB (or XKPHYS, if you've a 64-bit CPU) to get
at I/O.
> 64-bit mode would be great...
Bear in mind that there *isn't a 64-bit mode*. Privileged code (which
is everything except Linux applications) can always run 64-bit
instructions; all addresses are 64-bits really, it's just the
sign-extension of the registers which makes you think you've got
32-bit pointers. Usually a 64-bit CPU can access XKPHYS any time
it can access I/O registers.
--
Dominic Sweetman,
MIPS Technologies (UK) - formerly Algorithmics
The Fruit Farm, Ely Road, Chittering, CAMBS CB5 9PH, ENGLAND
phone: +44 1223 706200 / fax: +44 1223 706250 / direct: +44 1223 706205
http://www.algor.co.uk
next prev parent reply other threads:[~2002-09-04 20:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3D6E87EB.4010000@mvista.com>
2002-09-04 1:10 ` Interrupt handling Matthew Dharm
2002-09-04 9:53 ` Dominic Sweetman
2002-09-04 12:58 ` Maciej W. Rozycki
2002-09-04 16:36 ` Matthew Dharm
2002-09-04 20:08 ` Dominic Sweetman [this message]
2002-09-05 9:17 ` Maciej W. Rozycki
2002-09-04 16:40 ` Matthew Dharm
2002-09-04 17:02 ` Maciej W. Rozycki
2002-09-04 18:16 ` Matthew Dharm
2002-09-05 9:04 ` Maciej W. Rozycki
2002-09-05 16:25 Jon Burgess
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=200209042008.VAA25407@mudchute.algor.co.uk \
--to=dom@algor.co.uk \
--cc=jsun@mvista.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@ds2.pg.gda.pl \
--cc=mdharm@momenco.com \
/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