From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: <linuxppc-dev@lists.linuxppc.org>, Derrik Pates <dpates@dsdk12.net>
Subject: Re: GMAC vs. SunGEM driver with 2.4.17?
Date: Wed, 2 Jan 2002 10:22:44 +0100 [thread overview]
Message-ID: <20020102092244.23085@smtp.noos.fr> (raw)
In-Reply-To: <Pine.LNX.4.40.0201012147150.6346-100000@andromeda.dsdk12.net>
>Ben? Anyone? I know the GMAC driver is supposed to eventually be phased
>out in favor of the SunGEM driver for iBooks and G4s with the GMAC
>ethernet controller, but for the time being, which is the better choice?
>For the system I'm using (a FireWire iBook), super-high performance isn't
>an issue really - since the PHY is only capable of 100Mbps anyway - but I
>figured I'd better find out.
You should be able to use sungem already. I've ported all the missing
bits (power management etc...) to it, and recently fixed the multicast
problem, so I see no reason to still use gmac.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-01-02 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-02 4:50 GMAC vs. SunGEM driver with 2.4.17? Derrik Pates
2002-01-02 9:22 ` Benjamin Herrenschmidt [this message]
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=20020102092244.23085@smtp.noos.fr \
--to=benh@kernel.crashing.org \
--cc=dpates@dsdk12.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).