From: Paul Mackerras <paulus@samba.org>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2004@gmx.net>,
Jeff Garzik <jgarzik@pobox.com>,
Manfred Spraul <manfred@colorfullife.com>,
linux-kernel@vger.kernel.org, Netdev <netdev@oss.sgi.com>
Subject: Re: [PATCH] [2.4] forcedeth network driver
Date: Sun, 25 Jan 2004 10:11:24 +1100 [thread overview]
Message-ID: <16402.64412.577682.141249@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20040124224635.GA3448@ucw.cz>
Vojtech Pavlik writes:
> Well, my memory may be tricking me (I'm not really sure about this), but
> I remember there was supposed to be a PPC64 northbridge with a HT link,
> made exactly for the purpose of connecting an nForce southrbridge to it.
> But it definitely is not in production yet.
The U3 northbridge in the Apple G5 powermac has a HT link coming out
of it, which connects via an AMD PCI-X tunnel chip to an Apple K2
southbridge. I have never heard of anyone using (or planning to use)
an nForce southbridge on a PPC64 system though.
Regards,
Paul.
next prev parent reply other threads:[~2004-01-24 23:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4012BF44.9@colorfullife.com>
2004-01-24 20:21 ` [PATCH] [2.4] forcedeth network driver Jeff Garzik
2004-01-24 21:55 ` Carl-Daniel Hailfinger
2004-01-24 23:57 ` Jeff Garzik
2004-01-24 22:05 ` Vojtech Pavlik
2004-01-24 22:33 ` Carl-Daniel Hailfinger
2004-01-24 22:46 ` Vojtech Pavlik
2004-01-24 23:11 ` Paul Mackerras [this message]
2004-01-27 13:30 ` Rask Ingemann Lambertsen
2004-02-05 0:52 Carl-Daniel Hailfinger
2004-02-05 9:45 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2004-01-24 17:11 Carl-Daniel Hailfinger
2004-01-24 17:58 ` Jeff Garzik
2004-01-24 21:24 ` Carl-Daniel Hailfinger
2004-01-25 0:01 ` Jeff Garzik
2004-01-24 18:59 ` Francois Romieu
2004-01-24 19:02 ` Manfred Spraul
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=16402.64412.577682.141249@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=c-d.hailfinger.kernel.2004@gmx.net \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=netdev@oss.sgi.com \
--cc=vojtech@suse.cz \
/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).