From: Benjamin Herrenschmidt <bh40@calva.net>
To: GIANT Network Productions <gnp@jollygreen.com>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: GMAC ethernet
Date: Thu, 17 Feb 2000 11:18:08 +0100 [thread overview]
Message-ID: <20000217111808.000326@mailhost.mipsys.com> (raw)
In-Reply-To: <v04210101b4d0e527f293@[192.168.3.42]>
On Wed, Feb 16, 2000, GIANT Network Productions <gnp@jollygreen.com> wrote:
>What's the current status of the GMAC ethernet driver? I've been
>looking to do several things with an iBook that require interface
>aliases and multicast, but those features aren't currently supported.
>I've been pulling linux-pmac-benh from linuxcare.com.au, but Paul
>mentions that Ben's changes have been merged into linux-pmac-stable
>on his new status page and Ben states that he's working on
>'experimental' stuff only...
We could probably allow multicast by enabling the controller's promisc.
mode and let the kernel filter out packets. Not the most efficient thing
but at least it would work until we have some details about the chip's
hash table layout. I'll look into this, but my iBook's hard disk is dead,
I'm still waiting for a replacement.
>I'm less concerned with video performance (which seems to be where
>Paul is focusing at the moment) than with networking features - Which
>tree should I be pulling to keep better tabs on this issue?
Stick to Paul's tree. atyfb doesn't work on the iBook rage mobility yet,
but offb along with accelerated X server works for now. I'll do some work
on atyfb real soon (probably this week-end) to fix other problems, I'll
also try to fix it on the iBook. XServer acceleration already works (at
least with Xpmac).
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-02-17 10:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-16 23:54 GMAC ethernet GIANT Network Productions
2000-02-17 10:18 ` 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=20000217111808.000326@mailhost.mipsys.com \
--to=bh40@calva.net \
--cc=gnp@jollygreen.com \
--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).