From: Tom Gall <tom_gall@vnet.ibm.com>
To: Dan Malek <dan@mvista.com>
Cc: Troy Benjegerdes <hozer@drgw.net>, linuxppc-dev@lists.linuxppc.org
Subject: Power3/4 Was: Re: Fast Altivec
Date: Sun, 04 Feb 2001 14:08:22 -0600 [thread overview]
Message-ID: <3A7DB6B5.7370D32D@vnet.ibm.com> (raw)
In-Reply-To: 3A7D8C19.B829A8D0@mvista.com
Dan Malek wrote:
> I also think the POWER3/POWER4 changes are not being done correctly.
> There is too much overlap between the processor and the platform. The
> POWERx ifdefs should only be related to the processor, not how the
> platform maps stuff to PCI or other things. Since the 7450 has a 36-bit
> addressing capability, I wanted to use some of the changes along the
> POWERx
> path to help out. More on that later..........
Hi Dan,
Point well taken. That does raise the question tho as to how to manage the set
of changes necessary for the Power3 family of machines. At the moment it is nice
that one define handles issues for the entire family of boxes. But you are right
it could be split and I can see the case for making the split.
Which set of changes are you interested in using for the 7450? You say the chip
has 36 bit addressing, how does that work?
6392 messages yet to read... ug! Boy am I behind in mail since LinuxWorld...
--
Hakuna Matata,
Tom
-----------------------------------------------------------
PPC Linux Guy "My heart is human, my blood is boiling,
my brain IBM" -- Mr Roboto, Styxx
tgall@rochcivictheatre.org
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-02-04 20: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 ` Tom Gall [this message]
2001-02-04 21:08 ` Power3/4 Was: " Dan Malek
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=3A7DB6B5.7370D32D@vnet.ibm.com \
--to=tom_gall@vnet.ibm.com \
--cc=dan@mvista.com \
--cc=hozer@drgw.net \
--cc=linuxppc-dev@lists.linuxppc.org \
/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).