From: Pantelis Antoniou <pantelis.antoniou@gmail.com>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: matej.kupljen@ultra.si, linux-mips@linux-mips.org
Subject: Re: smc91x support
Date: Thu, 10 Nov 2005 17:37:08 +0200 [thread overview]
Message-ID: <200511101737.09316.pantelis.antoniou@gmail.com> (raw)
In-Reply-To: <20051111.001543.93019156.anemo@mba.ocn.ne.jp>
On Thursday 10 November 2005 17:15, Atsushi Nemoto wrote:
> >>>>> On Thu, 10 Nov 2005 15:52:11 +0100, Matej Kupljen <matej.kupljen@ultra.si> said:
>
> matej> What is the patch required for smc91x.h?
>
> I also want to know about the patch.
>
> matej> I also added support for smc91x.h to enable it on the DBAU1200,
> matej> but as I wrote in another mail, I get bad performance. I
> matej> enabled the debug mode and I now I see that I get a lot of
> matej> overruns, like:
> matej> ...
> matej> [4294761.172000] eth0: RX overrun (EPH_ST 0x0001)
> matej> [4294761.190000] eth0: RX overrun (EPH_ST 0x0001)
> matej> [4294761.198000] eth0: RX overrun (EPH_ST 0x0001)
> matej> ...
>
> matej> Is there any solution to this?
>
> I have similar problem on my several custom boards with SMC91C111. I
> see so many RX overrun, but I can not see why it happens. Forcing to
> 10Mbps/HalfDuplex reduced the overrun count (and works better than
> 100Mbps), but it is not preferable, of course ...
>
> ---
I'm afraid there's not much that you can do...
The old driver just didn't report the overruns. The generic one
does, that's why you see the overrun error.
And yes performance is bad with this chip. I'm not sure if DMA would
help much, since the overrun occurs because the chip does not have
enough internal buffers. I don't think that we can service the interrupts
fast enough to prevent the overruns...
IMHO the only solution is to use a decent chip...
> Atsushi Nemoto
>
>
Regards
Pantelis
next prev parent reply other threads:[~2005-11-10 15:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-10 14:52 smc91x support Matej Kupljen
2005-11-10 15:15 ` Atsushi Nemoto
2005-11-10 15:37 ` Pantelis Antoniou [this message]
2005-11-10 17:44 ` Matej Kupljen
2005-11-11 1:36 ` Atsushi Nemoto
2005-11-10 15:29 ` Pete Popov
2005-11-10 17:52 ` Matej Kupljen
2005-11-10 17:56 ` Peter Popov
2006-01-04 21:23 ` Matej Kupljen
2006-01-05 2:42 ` Pete Popov
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=200511101737.09316.pantelis.antoniou@gmail.com \
--to=pantelis.antoniou@gmail.com \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-mips@linux-mips.org \
--cc=matej.kupljen@ultra.si \
/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