From: Scott Feldman <sfeldma@pobox.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: Russell King <rmk+lkml@arm.linux.org.uk>,
jgarzik@pobox.com, linux-kernel@vger.kernel.org,
netdev@oss.sgi.com, greg@kroah.com, akpm@osdl.org
Subject: Re: [ANN] removal of certain net drivers coming soon: eepro100, xircom_tulip_cb, iph5526
Date: Thu, 27 Jan 2005 17:58:37 -0800 [thread overview]
Message-ID: <1106877517.18167.311.camel@localhost.localdomain> (raw)
In-Reply-To: <20050127164843.08bdb307.davem@davemloft.net>
On Thu, 2005-01-27 at 16:48, David S. Miller wrote:
> On Fri, 28 Jan 2005 00:14:30 +0000
> Russell King <rmk+lkml@arm.linux.org.uk> wrote:
>
> > The fact of the matter is that eepro100.c works on ARM, e100.c doesn't.
> > There's a message from me back on 30th June 2004 at about 10:30 BST on
> > this very list which generated almost no interest from anyone...
>
> I see. Since eepro100 just uses a fixed set of RX buffers in the
> ring (ie. the DMA links are never changed) it works.
eepro100 does a copy if pkt_len < rx_copybreak, otherwise it send up the
skb and allocates and links a new one in it's place (see
speedo_rx_link).
So I would say e100 and eepro100 are the same for >= rx_copybreak. Why
does one work and not the other? Is it because the RFD is aligned in
eepro100?
Russell, what happens with modprobe eepro100 rx_copybreak=0?
-scott
next prev parent reply other threads:[~2005-01-28 1:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 20:45 [ANN] removal of certain net drivers coming soon: eepro100, xircom_tulip_cb, iph5526 Jeff Garzik
2005-01-27 21:07 ` Christoph Hellwig
2005-02-06 18:44 ` [2.6 patch] kill IPHASE5526 Adrian Bunk
2005-01-27 22:57 ` [ANN] removal of certain net drivers coming soon: eepro100, xircom_tulip_cb, iph5526 Russell King
2005-01-27 23:31 ` David S. Miller
2005-01-28 0:14 ` Russell King
2005-01-28 0:48 ` Lennert Buytenhek
2005-01-28 0:48 ` David S. Miller
2005-01-28 1:58 ` Scott Feldman [this message]
2005-01-28 5:22 ` David S. Miller
2005-01-28 9:33 ` [ANN] removal of certain net drivers coming soon: eepro100,?xircom_tulip_cb, iph5526 Meelis Roos
2005-01-28 19:11 ` Scott Feldman
2005-02-01 12:48 ` Meelis Roos
2005-02-01 18:57 ` Scott Feldman
2005-02-01 19:09 ` linux-os
2005-02-01 19:28 ` Scott Feldman
2005-01-29 8:17 ` [ANN] removal of certain net drivers coming soon: eepro100, xircom_tulip_cb, iph5526 Greg KH
2005-01-29 20:42 ` Jason Lunz
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=1106877517.18167.311.camel@localhost.localdomain \
--to=sfeldma@pobox.com \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=greg@kroah.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=rmk+lkml@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.