From: Dan Malek <dan@mvista.com>
To: Tom Gall <tom_gall@vnet.ibm.com>
Cc: Troy Benjegerdes <hozer@drgw.net>, linuxppc-dev@lists.linuxppc.org
Subject: Re: Power3/4 Was: Re: Fast Altivec
Date: Sun, 04 Feb 2001 16:08:55 -0500 [thread overview]
Message-ID: <3A7DC4E7.38588294@mvista.com> (raw)
In-Reply-To: 3A7DB6B5.7370D32D@vnet.ibm.com
Tom Gall wrote:
> .... At the moment it is nice
> that one define handles issues for the entire family of boxes.
I learned years ago when I did a processor port it was important to
separate the processor and platform specific configuration definitions.
When you do that second platform that uses the same processor you will
discover how badly it was integrated :-).
> .... But you are right
> it could be split and I can see the case for making the split.
It seems like these are CHRP machines with some kind of extended address
bus mapping? We either need to devise a new configuration name or
integrate the changes with some "CHRP extension" that isn't based on
the POWERx configuration.
> Which set of changes are you interested in using for the 7450? You say the chip
> has 36 bit addressing, how does that work?
It can use a 36-bit physical address bus, so any processor register that
holds a physical address (SDR, page tables, etc) has "extended" bits
that
can be used when the proper configuration bits are set in the HID0.
I was going to use some of the I/O mapping functions (often with
comments
like "big hack" in them :-), to support this as well. Generally, I am
looking at some VM changes that allow us to support beyond 4G
virtual/physical
with 32-bit processors (other than using the HIGHMEM hack). Some of the
things in BRIDGE64 and POWERx are appropriate to use but seem to have
knowledge of the underlying platform, so a slightly different
configuration
name and minor code changes would be useful. I just started looking and
still have lots of work to do here.
> 6392 messages yet to read... ug! Boy am I behind in mail since LinuxWorld...
Heh...
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-02-04 21:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-02 16:32 Fast Altivec Dan Malek
2001-02-02 18:51 ` Troy Benjegerdes
2001-02-04 17:06 ` Dan Malek
2001-02-04 20:08 ` Power3/4 Was: " Tom Gall
2001-02-04 21:08 ` Dan Malek [this message]
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=3A7DC4E7.38588294@mvista.com \
--to=dan@mvista.com \
--cc=hozer@drgw.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=tom_gall@vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).