From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: [9fans] openrd mii trouble
Date: Wed, 26 Oct 2011 15:04:32 -0400 [thread overview]
Message-ID: <a96a099a4301d9f92c38416395ebda8f@brasstown.quanstro.net> (raw)
i seem to be having some funnies, espcially with port #2.
after turning on debugging, i notice that both port 0 and port
one report they're using the same phy number (blank lines
added for effect below). does anyone know if this is as
intended, or am i barking up the wrong tree?
- erik
----
Plan 9 from Bell Labs
#F0: nand addr 0xf9000000 len 536870912 width 1 interleave 0
mii
ctlrno 0 phy 8 oui 0x5043 model 0x24
ctlrno 0 phy 24 oui 0x5043 model 0x24
ether1116: dual-port phy
ctlrno 0 using ctlrno 0's phyno 8
>>oui 0x5043 phyno 8
#l0: kirkwoodmii: fd 1 speed 1000 tfc 1 rfc 1
mii done
phy dev addr 0
mii
ctlrno 1 using ctlrno 0's phyno 24
>>oui 0x5043 phyno 8
#l1: kirkwoodmii: fd 1 speed 1000 tfc 1 rfc 1
mii done
phy dev addr 0
reply other threads:[~2011-10-26 19:04 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=a96a099a4301d9f92c38416395ebda8f@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).