From: Benjamin Herrenschmidt <bh40@calva.net>
To: "Timothy A. Seufert" <tas@mindspring.com>,
<linuxppc-dev@lists.linuxppc.org>
Subject: Re: BMAC+ & Full Duplex
Date: Fri, 19 May 2000 21:13:18 +0200 [thread overview]
Message-ID: <20000519191318.30716@sjc2-relay.mail.digex.net> (raw)
In-Reply-To: <v04220801b54ab29142c2@10.0.0.42>
On Fri, May 19, 2000, Timothy A. Seufert <tas@mindspring.com> wrote:
>I'm pretty sure your 1999 PowerBook uses the same BMAC+ Ethernet as
>his PowerMac G3. The auto-sensing feature doesn't work with all
>Ethernet hubs/switches, which is why he's having problems and you
>aren't.
>
>I have a couple B&W G3s connected to a 5-port 100BaseT switch, and
>they successfully autonegotiate full duplex 100BaseT under both MacOS
>and Linux.
There are known auto-neg problems with Apple eth. chips. We should
provide a way to force the driver duplex and speed modes. I beleive an
ioctl along with a small command line tool would be cool, but maybe not
enough (a compile option or kernel command line args would help for
people netbooting).
I've not find "standard" ioctl I could implement for that, so I beleive
we just can invent a new one and add it to MACE, BMAC and GMAC drivers.
I'll look into this when I'm back along with some GMAC fixes.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2000-05-19 19:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <v04220801b54ab29142c2@10.0.0.42>
2000-05-19 19:13 ` Benjamin Herrenschmidt [this message]
2000-05-19 22:24 ` BMAC+ & Full Duplex Worth
2000-05-19 5:09 jeramy b smith
2000-05-19 9:00 ` Timothy A. Seufert
-- strict thread matches above, loose matches on Subject: below --
2000-05-18 21:27 Mike Hudson
2000-05-18 22:14 ` Takashi Oe
2000-05-18 22:33 ` Mike Hudson
2000-05-18 23:09 ` Takashi Oe
2000-05-20 3:25 ` Mike Hudson
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=20000519191318.30716@sjc2-relay.mail.digex.net \
--to=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=tas@mindspring.com \
/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).