From: Dan Malek <dan@mvista.com>
To: Troy Benjegerdes <hozer@drgw.net>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Fast Altivec
Date: Sun, 04 Feb 2001 12:06:33 -0500 [thread overview]
Message-ID: <3A7D8C19.B829A8D0@mvista.com> (raw)
In-Reply-To: 20010202125143.D31120@altus.drgw.net
Troy Benjegerdes wrote:
> Heheheh, I have to ask.. is it really running that fast, and do you have all
> the neat features turned on?
It's really running that fast, in fact I may try to push it up to 800
MHz
just to see. There are switches on the board to select up to 16
different
speeds in 50 MHz increments. I have version 2.02 of the silicon now,
and you certainly don't want to use anything older than that (and in
fact you probably won't ever see any).
I have L1/L2 caches working. I started on the L3 stuff but ran out of
time for the demo. I discovered someone "fixed" my original Media-Q
graphics driver by removing all of the PowerPC big endian fixes (and did
other things like ioremap and then in/out). I spent too long sorting
this out instead of working on processor specific things.
There are a few little details that have to be fixed up on the code,
lots of PVR things and a few new bits in some registers.
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..........
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-02-04 17:06 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 [this message]
2001-02-04 20:08 ` Power3/4 Was: " Tom Gall
2001-02-04 21:08 ` 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=3A7D8C19.B829A8D0@mvista.com \
--to=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).