linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Wang Chao Feng" <chfwang@sina.com.cn>
To: "Gregory Allen" <gallen@arlut.utexas.edu>,
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Ethernet controller
Date: Sat, 20 Jan 2001 11:26:11 +0800	[thread overview]
Message-ID: <000401c08812$be4d4de0$12c809c0@farout> (raw)
In-Reply-To: 200101181805.MAA88737@ns5.arlut.utexas.edu


I don't think RTL8139 is a good choice because it's bad performance and it's hard to use.
In rtl8139, the data must copy from chip's fifo to your sk_buf.
In the driver of rtl8139 for linux, can can find the driver reset the chip in transmit function,
because of the bug of this chip.
When I flood ping the rtl8139 from a linux host, I find I must reset the chip every several minutes.

regards
wang


----- Original Message -----
From: Gregory Allen <gallen@arlut.utexas.edu>
To: <linuxppc-embedded@lists.linuxppc.org>
Sent: Friday, January 19, 2001 2:05 AM
Subject: Ethernet controller


>
> I am designing an embedded PPC8240 board with an ethernet interface. I am down to 2 choices: i82559 and RTL8139
>
> I prefer to avoid the BGA package of the i82559, but the RTL8139 driver support is listed as having "limited PowerPC testing". I am also curious about their relative performance.
>
> Can anyone speak to this?
>
> Thanks,
> -Greg
>
> ------
>  Gregory E. Allen, MSEE Research Engineer
>  Applied Research Laboratories:
>  The University of Texas at Austin
>
>
>

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      parent reply	other threads:[~2001-01-20  3:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-18 18:05 Ethernet controller Gregory Allen
2001-01-18 20:31 ` Dan Malek
2001-01-19 20:23 ` Ron Bianco
2001-01-20  3:26 ` Wang Chao Feng [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='000401c08812$be4d4de0$12c809c0@farout' \
    --to=chfwang@sina.com.cn \
    --cc=gallen@arlut.utexas.edu \
    --cc=linuxppc-embedded@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).