From: Armin Kuster <Darth_vapor@mvista.com>
To: Felix Radensky <felix@allot.com>
Cc: "David Müller" <d.mueller@elsoft.ch>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: ppc405_enet problems
Date: Tue, 11 Dec 2001 10:11:28 -0800 [thread overview]
Message-ID: <3C164C50.C20778D6@mvista.com> (raw)
In-Reply-To: 3C160B04.93085D47@allot.com
Felix Radensky wrote:
>
> Hi,
>
> Thanks, David and Armin for your help. I've tried the methods you suggested
> but none of them worked. The real problem in my case was the MAX_NUM_PHYS
> constant. I've noticed that after the first for loop in find_phy routine, the
> value of
> i is MAX_NUM_PHYS. So I've tried to increase the value of this constant, and
> my
> phy was (almost) discovered properly after the 5th iteration. I say almost,
> because
> I also had to change the value of phy id from 0x20005c23 to 0x20005c20 (the
> value
> reported by find_phy. Armin, can you please explain how this number was
> determined.
Felix,
I took the easy route, its just phyid1 & phyid2. The "A" version was
submitted by some one else and it might be possible to combine them into
one DP83843 stuct by using a shift factor of 8 ( 2nd eliment in the
phy_info struct" the diff between 0x20005c23 & 0x20005c20 is the model
revision number.
Maybe MAX_NUM_PHYS needs to be renamed to MAX_PHY_ADDR to be more clear.
-- armin
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-12-11 18:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-10 13:28 ppc405_enet problems Felix Radensky
2001-12-10 16:17 ` Tom Rini
2001-12-10 17:56 ` Felix Radensky
2001-12-10 20:03 ` Armin Kuster
2001-12-11 7:51 ` David Müller (ELSOFT AG)
2001-12-11 13:32 ` Felix Radensky
2001-12-11 18:11 ` Armin Kuster [this message]
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=3C164C50.C20778D6@mvista.com \
--to=darth_vapor@mvista.com \
--cc=d.mueller@elsoft.ch \
--cc=felix@allot.com \
--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).