From: Matej Kupljen <matej.kupljen@ultra.si>
To: linux-mips@linux-mips.org
Subject: smc91x support
Date: Thu, 10 Nov 2005 15:52:11 +0100 [thread overview]
Message-ID: <1131634331.18165.30.camel@localhost.localdomain> (raw)
Hi
On 21st september Peter Popov modified:
arch/mips/au1000/common/platform.c
With the log message:
smc91x platform support; requires patch to smc91x.h which was sent
upstream.
Any news about this?
What is the patch required for smc91x.h?
I also added support for smc91x.h to enable it on the DBAU1200,
but as I wrote in another mail, I get bad performance.
I enabled the debug mode and I now I see that I get a lot of
overruns, like:
...
[4294761.172000] eth0: RX overrun (EPH_ST 0x0001)
[4294761.190000] eth0: RX overrun (EPH_ST 0x0001)
[4294761.198000] eth0: RX overrun (EPH_ST 0x0001)
...
Is there any solution to this?
Maybe to use DDMA?
BR,
Matej
next reply other threads:[~2005-11-10 14:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-10 14:52 Matej Kupljen [this message]
2005-11-10 15:15 ` smc91x support Atsushi Nemoto
2005-11-10 15:37 ` Pantelis Antoniou
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=1131634331.18165.30.camel@localhost.localdomain \
--to=matej.kupljen@ultra.si \
--cc=linux-mips@linux-mips.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