From: Gerhard Jaeger <g.jaeger@sysgo.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: [BUG] IBM440GX works too slow under nfsroot
Date: Fri, 22 Oct 2004 14:27:02 +0200 [thread overview]
Message-ID: <200410221427.02301.g.jaeger@sysgo.com> (raw)
In-Reply-To: <006101c4b831$c3d60d30$0301a8c0@chuck2>
On Friday 22 October 2004 14:22, Mark Chambers wrote:
> > > this problem has been discussed a while ago between my co-worker and
> > > Matt-Porter - first on the list and later on in private. We also have this
> > > problem on a custom board using the 440GX. It can be also seen on a Ebony
> > > (440GP) as well and on our rather old Ocotea. Our kernel originally is
> > >based
> etc.
>
> I'm just curious here - I'm not familiar with IBM processors -
> is there a separate PHY chip, and if so, what is it?
Yes, on Ebony and Ocotea we have an AMD NetPHY AM79C875KC, on
Walnut, I'm not sure, on our custom boards we have also the AMD
and a NS DP83846A, as well as DP8385...
Gerhard
next prev parent reply other threads:[~2004-10-22 12:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 23:57 [BUG] IBM440GX works too slow under nfsroot Hiroshi DOYU
2004-10-22 1:19 ` Eugene Surovegin
2004-10-22 1:26 ` Hiroshi DOYU
2004-10-22 1:33 ` Eugene Surovegin
2004-10-22 1:38 ` Hiroshi DOYU
2004-10-22 2:02 ` Eugene Surovegin
2004-10-22 6:26 ` Gerhard Jaeger
2004-10-22 8:29 ` Eugene Surovegin
2004-10-22 9:39 ` Gerhard Jaeger
2004-10-22 12:22 ` Mark Chambers
2004-10-22 12:27 ` Gerhard Jaeger [this message]
2004-10-25 1:16 ` Eugene Surovegin
2004-10-25 6:47 ` Gerhard Jaeger
2004-10-25 7:02 ` Eugene Surovegin
2004-11-08 2:55 ` Eugene Surovegin
2004-10-22 22:22 ` Matt Porter
-- strict thread matches above, loose matches on Subject: below --
2004-10-22 5:57 Daren Hayward
2004-10-22 6:30 ` Gerhard Jaeger
2004-10-22 7:36 Neil Wilson
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=200410221427.02301.g.jaeger@sysgo.com \
--to=g.jaeger@sysgo.com \
--cc=linuxppc-embedded@ozlabs.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).