From: Matt Porter <mporter@kernel.crashing.org>
To: Stefan Roese <stefan.roese@esd-electronics.com>
Cc: "'DaveyWu'" <daveywu@transengines.com>,
"'Linuxppc-Embedded'" <linuxppc-embedded@lists.linuxppc.org>,
benh@kernel.crashing.org, akuster@mvista.com
Subject: Re: PPC4xx enet driver problem (version 2.0)
Date: Fri, 12 Dec 2003 07:45:41 -0700 [thread overview]
Message-ID: <20031212074541.A32360@home.com> (raw)
In-Reply-To: <004601c3c09e$8cfea410$0212000a@PCSTEFAN>; from stefan.roese@esd-electronics.com on Fri, Dec 12, 2003 at 11:56:09AM +0100
On Fri, Dec 12, 2003 at 11:56:09AM +0100, Stefan Roese wrote:
>
> Davey!
>
> No, we didn't solve this problem so far. Eugene did some tests on an
> ppc440 board and had no problems with the multiple enet devices. So it
> seems to be 405ep related! I still have to send some debug output to
> Eugene (hopefully today)!
[I haven't followed the thread but new EMAC driver and 405EP rings
a bell]
It's possible that the new method in which OCP code handles OCP device
dependencies has a bug. 405ep is a special case since it requires
a particular EMAC device to provide MDIO operations for both EMACs.
440gp/gx don't follow this code path.
-Matt
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-12-12 14:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-03 11:29 PPC4xx enet driver problem (version 2.0) Stefan Roese
2003-12-03 19:35 ` 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 [this message]
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=20031212074541.A32360@home.com \
--to=mporter@kernel.crashing.org \
--cc=akuster@mvista.com \
--cc=benh@kernel.crashing.org \
--cc=daveywu@transengines.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=stefan.roese@esd-electronics.com \
/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).