From: Antony Pavlov <antonynpavlov@gmail.com>
To: gianluca <gianlucarenzi@eurek.it>
Cc: barebox@lists.infradead.org
Subject: Re: Ethernet PHY KSZ9031 is not working
Date: Thu, 3 Mar 2016 16:52:52 +0300 [thread overview]
Message-ID: <20160303165252.0911b6cb49599a5bc06090ca@gmail.com> (raw)
In-Reply-To: <56D831C6.1010101@eurek.it>
On Thu, 3 Mar 2016 13:44:54 +0100
gianluca <gianlucarenzi@eurek.it> wrote:
> Hello list,
> It's me again! ;-)
>
> Actually I had tested 80% of the board with barebox.
...
>
> When Barebox takes control over, those pins are turned off, the device
> tree information is telling me:
>
> > `-- 2188000.ethernet
> > `-- miibus0
> > `-- phy0
> > `-- 0x00000000-0x0000003f ( 64 Bytes): /dev/phy0
> > `-- eth0
>
> but when I try to bring up the ethernet connection here is the message:
>
> > dhcp
> > warning: No MAC address set. Using random address ae:05:f1:62:bd:d8
> > ksz9031rn_phy_fixup Called
> > ksz9031rn_phy_fixup Exit
> > dhcp: Network is down
>
> And all leds in the RJ-45 JackMag are still turned off.
>
> I don't know where I can check if something goes wrong. May be a failure
> on board, but at this time this board is the ONLY BOARD I can use.
Use 'miitool -v -v' command to check your phy registers and the link status.
--
Best regards,
Antony Pavlov
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2016-03-03 13:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 12:44 gianluca
2016-03-03 13:52 ` Antony Pavlov [this message]
2016-03-03 13:47 ` gianluca
2016-03-03 15:21 ` Antony Pavlov
2016-03-04 11:12 ` Ethernet PHY KSZ9031 is not working [SOLVED] gianluca
2016-03-03 14:42 ` Ethernet PHY KSZ9031 is not working Holger Schurig
2016-03-09 8:58 ` Alexander Aring
2016-03-16 12:34 ` Holger Schurig
2016-03-03 14:53 ` Sascha Hauer
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=20160303165252.0911b6cb49599a5bc06090ca@gmail.com \
--to=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=gianlucarenzi@eurek.it \
/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