From: Ben Gamsa <ben@somanetworks•com>
To: linuxppc-dev@ozlabs•org
Subject: Problems changing ethernet phy settings with LXT973 (and 8555)
Date: Fri, 30 May 2008 18:16:08 -0400 [thread overview]
Message-ID: <48407CA8.3030301@somanetworks.com> (raw)
I'm not sure if this is the right place to post, but it's one of the few
places that seems relevant (the other I think would be linuxppc-embedded).
Our board is using an 8555 with an LXT973 dual-phy chip hooked up to TSEC0
and TSEC1.
We're currently using 2.6.20 but I don't see any major changes in the 2.6.25
release in the area of the phy driver. We're using the gianfar driver, with
the generic phy driver. When the phy driver writes to BMCR to turn off
auto-negotiation and set the speed and duplex, it appears that none of the
writes except the RESET bit take effect. Reading back the register
immediately shows the RESET bit set, but none of the other changes (later
the RESET bit is cleared, but again, none of the changes are visible).
One possibility was that the LXT973 was wired up to come up in hardware
control mode, where it's supposed to ignore all writes (I'm not sure if
there is supposed to be an exception for the RESET bit or not in this case),
but that appears not to be the case.
I was wondering if anyone has any idea as to what might be the source of
this problem, or if anyone has any suggestions as to avenues of investigation
to track it down.
--
Ben Gamsa ben@somanetworks•com
SOMA Networks, Inc. 312 Adelaide St. W. Suite 600 Toronto, Ontario, M5V1R2
reply other threads:[~2008-05-30 22:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=48407CA8.3030301@somanetworks.com \
--to=ben@somanetworks$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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