From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Gabriel Paubert <paubert@iram.es>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
linas@austin.ibm.com, valvoline <valvoline@vrlteam.org>,
linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Broadcom BCM94306
Date: Sat, 17 Jan 2004 14:25:43 +1100 [thread overview]
Message-ID: <1074309942.8359.24.camel@gaston> (raw)
In-Reply-To: <20040116195406.GA25566@iram.es>
> Anyway, since you seem to have ties inside IBM ;-), you might
> know why they do not even give a list of differences of the
> 970 implementation. I know from another source that the 970 does
> not have BATs, but supports large pages with a size of 16MB.
Yup, it's more/less a POWER4 in this regard (which is probably
as badly documented :)
I'll check out the status of public specs, I _think_ that there is
some doc in the process of beeing cleaned up & declassified for this
chip, but I'm not 100% sure at this point.
> Now the fact that the 970 does not support backwards-endian is a very
> good thing. From time to time (although it has been less frequent
> recently) somebody suggest on the list that Linux/PPC switches to the
> dark side of the endianness. The fact that some processors don't support
> it will be a killer argument.
Hehe, you know, there isn't much risk that we take such a patch in
the first place anyway :)
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-01-17 3:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 16:11 Broadcom BCM94306 valvoline
2004-01-15 0:13 ` linas
2004-01-15 9:30 ` Segher Boessenkool
2004-01-15 11:50 ` Gabriel Paubert
2004-01-15 13:00 ` Segher Boessenkool
2004-01-15 13:12 ` Sven Luther
2004-01-15 13:18 ` Segher Boessenkool
2004-01-16 19:54 ` Gabriel Paubert
2004-01-16 23:19 ` linas
2004-01-17 3:25 ` Benjamin Herrenschmidt [this message]
2004-01-17 18:21 ` Geert Uytterhoeven
2004-01-19 14:11 ` Segher Boessenkool
2004-01-19 22:05 ` Benjamin Herrenschmidt
2004-01-20 18:01 ` Segher Boessenkool
2004-01-21 17:27 ` Gabriel Paubert
2004-01-15 13:39 ` Colin Leroy
2004-01-16 22:09 ` Gabriel Paubert
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=1074309942.8359.24.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linas@austin.ibm.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paubert@iram.es \
--cc=segher@kernel.crashing.org \
--cc=valvoline@vrlteam.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).