From: Sascha Hauer <s.hauer@pengutronix.de>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] mii-tool: make the 'No MII transceiver present!' message more clear
Date: Wed, 2 Jul 2014 07:46:50 +0200 [thread overview]
Message-ID: <20140702054650.GT14257@pengutronix.de> (raw)
In-Reply-To: <1404248665-15430-1-git-send-email-antonynpavlov@gmail.com>
On Wed, Jul 02, 2014 at 01:04:25AM +0400, Antony Pavlov wrote:
> Suppose you have two network controllers.
> The first one is ENC28J60 (it is in low power mode
> after start) the second one is always-enabled eth1.
>
> As ENC28J60 is in low power mode before enc28j60_eth_open()
> is called. ENC28J60's mii traceiver is in low power mode too
> so the mii traceiver's register are inaccessable.
>
> Here is a sample log just after barebox start:
>
> barebox:/ miitool
> miibus0: registered phy as /dev/phy0
> No MII transceiver present!.
> miibus1: registered phy as /dev/phy1
> phy1: eth1: negotiated 100baseTx-FD, link ok
> barebox:/ miitool
> No MII transceiver present!.
> phy1: eth1: negotiated 100baseTx-FD, link ok
>
> The 'No MII transceiver present!.' message is confusing here.
>
> This patch fixes the problem so the miitool output
> looks like this:
>
> barebox:/ miitool
> phy0: spieth0: No MII transceiver present!.
> phy1: eth1: negotiated 100baseTx-FD, link ok
>
> Signed-off-by: Antony Pavlov <antonynpavlov@gmail.com>
> ---
Applied, thanks
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2014-07-02 5:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 21:04 Antony Pavlov
2014-07-02 5:46 ` Sascha Hauer [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=20140702054650.GT14257@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.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