From: Benjamin Herrenschmidt <bh40@calva.net>
To: "David A. Gatwood" <dgatwood@deepspace.mklinux.org>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: Problems with Ethernet on PowerBook Wallstreet G3
Date: Wed, 12 Apr 2000 20:25:47 +0200 [thread overview]
Message-ID: <20000412202547.009139@mailhost.mipsys.com> (raw)
In-Reply-To: <Pine.LNX.3.96.1000412105423.25261A-100000@deepspace.mklinux.org>
Browsing the Darwin bmac driver source, I found some interesting comments:
/*-------------------------------------------------------------------------
* Work around a hardware bug where the controller will receive
* unicast packets not directed to the station. The hardware is
* erroneously using the hash table to qualify the unicast address.
* This routine will check that the packet is unicast, and if so,
* makes sure that the unicast address matches the station's address.
* Thus function returns true if the packet should be rejected.
*-------------------------------------------------------------------------*/
(This unicast filter workaround is enabled when the PCI device-id of the
chip is 0x10)
/*
* On the transmit side, we use the chipset interrupt. Using the
* transmit DMA interrupt (or having multiple transmit DMA entries)
* would allows us to send the next frame to the chipset prior the
* transmit fifo going empty.
* However, this aggrevates a BMac chipset bug where the next frame
going
* out gets corrupted (first two bytes lost) if the chipset had to retry
* the previous frame.
*/
/*-------------------------------------------------------------------------
* _sendDummyPacket
* ----------------
* The BMac receiver seems to be locked until we send our first packet.
*
*-------------------------------------------------------------------------*/
/*
* The BMac Ethernet controller appends two bytes to each receive
* buffer containing the buffer
* size and receive frame status.
* We locate these bytes by using the DMA residual counts.
*/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-04-12 18:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.3.96.1000412105423.25261A-100000@deepspace.mklinux.org>
2000-04-12 18:10 ` Problems with Ethernet on PowerBook Wallstreet G3 Joseph Garcia
2000-04-12 18:55 ` David A. Gatwood
2000-04-12 22:18 ` Wolfgang Denk
2000-04-12 18:25 ` Benjamin Herrenschmidt [this message]
2000-04-12 20:06 ` Michael Schmitz
[not found] <38F5A91D.1212ECEC@drea.dnd.ca>
2000-04-13 12:23 ` Wolfgang Denk
[not found] <Pine.LNX.4.10.10004130948140.10131-100000@opal.biophys.uni-duesseldorf.de>
2000-04-13 9:39 ` Wolfgang Denk
[not found] ` <38F5B1C0.FC8863EB@drea.dnd.ca>
2000-04-13 12:57 ` Joseph Garcia
2000-04-13 13:59 ` Benjamin Herrenschmidt
2000-04-13 16:47 ` David A. Gatwood
2000-04-12 22:45 Wolfgang Denk
[not found] <Pine.LNX.3.96.1000411215343.219D-100000@deepspace.mklinux.org>
2000-04-12 12:44 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2000-04-11 18:22 Wolfgang Denk
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=20000412202547.009139@mailhost.mipsys.com \
--to=bh40@calva.net \
--cc=dgatwood@deepspace.mklinux.org \
--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).