From: "David S. Miller" <davem@redhat.com>
To: sparclinux@vger.kernel.org
Subject: Re: Was: Problems with bridging on Sparc64
Date: Tue, 03 Feb 2004 23:20:51 +0000 [thread overview]
Message-ID: <20040203152051.2500d47d.davem@redhat.com> (raw)
In-Reply-To: <200402031553.44155.crn@netunix.com>
On Tue, 3 Feb 2004 23:02:40 +0000
"C.Newport" <crn@netunix.com> wrote:
> You mention both sparc v9 and sparc64.
> AIUI v9 is the Sun Ultrasparc and sparc64 is the slightly different
> Fujitsu processor. We seem to refer to both under the confusing
> sparc64 header, but I do not see much testing happening on Fujitsu
> stuff. Am I misunderstanding the situation or should we consider
> getting the naming sorted out ?.
> Does anyone even have a Sparc64 (Fujitsu) machine working ?.
When we speak of sparc64 we simply mean the 64-bit Sparc userland
ABI. When we say v9 we mean sparc 32-bit ABI plus availability of
the Sparc v9 instructions.
Someone inside Fujitsu at some point got the most recent Fujitsu
chips working (they are very close, MMU/Cache programming wise,
to UltraSPARC unlike the initial fujistu 64-bit sparcs) but they
never submitted a final patch to me and all that stuff is pretty
dead these days anyways :)
next prev parent reply other threads:[~2004-02-03 23:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 15:53 Was: Problems with bridging on Sparc64 C.Newport
2004-02-03 20:18 ` Ben Collins
2004-02-03 21:21 ` Ben Collins
2004-02-03 21:26 ` C.Newport
2004-02-03 23:02 ` C.Newport
2004-02-03 23:17 ` Ben Collins
2004-02-03 23:20 ` David S. Miller [this message]
2004-02-04 0:14 ` C.Newport
2004-02-04 8:01 ` Baurjan Ismagulov
2004-02-04 13:46 ` Ben Collins
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=20040203152051.2500d47d.davem@redhat.com \
--to=davem@redhat.com \
--cc=sparclinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.