From: "Stefan Roese" <stefan.roese@esd-electronics.com>
To: "Linuxppc-Embedded" <linuxppc-embedded@lists.linuxppc.org>,
<benh@kernel.crashing.org>, <akuster@mvista.com>
Subject: PPC4xx enet driver problem (version 2.0)
Date: Wed, 3 Dec 2003 12:29:31 +0100 [thread overview]
Message-ID: <004901c3b990$b84d2ac0$0212000a@PCSTEFAN> (raw)
Hello!
We are trying to switch to the 2.4.23 linuxppc_2_4_devel kernel (from
2.4.21) and experience a problem with the "new" ethernet driver for the
ibm ppc4xx (version 2.0 from Benjamin Herrenschmidt). On our boards with
only one active enet interface we have no problems. But our PPC405EP
boards with 2 active enet devices, the traffic stops completely upon
initializing the 2nd devices (emac_reset_configure).
Has anybody experienced similar problems? Has anybody seen this driver
working properly with more than one ppc4xx enet devices (especially
ppc405ep)?
With the previous driver (from linuxppc_2_4_devel 2.4.21 maintained by
mvista) we had no problems with 2 enet interfaces on the ppc405ep so
far!
By the way: What is the future of the ppc4xx enet driver. I found that
the 2.5 kernel has a newer mvista driver included (modifications for
440gx, etc.). Is the driver from 2.4.23 a dead end?
Thanks and best regards,
Stefan.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-12-03 11:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-03 11:29 Stefan Roese [this message]
2003-12-03 19:35 ` PPC4xx enet driver problem (version 2.0) Eugene Surovegin
2003-12-04 15:54 ` Stefan Roese
2003-12-12 2:39 ` DaveyWu
2003-12-12 10:56 ` Stefan Roese
2003-12-12 14:45 ` Matt Porter
2003-12-12 15:37 ` tcp retrans timeout!!! Brijesh K Singh
2003-12-14 9:24 ` PPC4xx enet driver problem (version 2.0) DaveyWu
2003-12-14 23:55 ` Benjamin Herrenschmidt
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='004901c3b990$b84d2ac0$0212000a@PCSTEFAN' \
--to=stefan.roese@esd-electronics.com \
--cc=akuster@mvista.com \
--cc=benh@kernel.crashing.org \
--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).