From: Brian Lilly
Data: Thursday, May 08, 2014 3:52 AM
>To: Florian Fainelli
>Cc: Uwe Kleine-König; David S. Miller; Estevam Fabio-R49496; Jim Baxter; Li
>Frank-
>B20596; Duan Fugang-B38611; netdev; linux-kernel@vger.kernel.org; kernel
>Subject: Re: i.MX28 based system losi
Florian:
Thank you for your help.
After doubling the timeout length it worked.
I managed to get my hands on a imx28evk board and compared our
component load versus theirs, to find they have a 1.5k pull-up on
ENET_MDIO to +3.3v which wasn't present on our board. Adding a 1.5k
pull-up resistor
2014-05-07 12:16 GMT-07:00 Brian Lilly :
> Also, in 3.14, commenting out both "return -ETIMEDOUT" instances in
> fec_main.c results in a working interface.
> Please let me know if you have any questions.
At this point, you could probably instrument the interrupt handler and
see if you get
Also, in 3.14, commenting out both "return -ETIMEDOUT" instances in
fec_main.c results in a working interface.
Please let me know if you have any questions.
Thank you.
Brian Lilly
Crystalfontz America, Incorporated
12412 East Saltese Road
Spokane Valley, WA 99216
br...@crystalfontz.com
Moving forward to 3.15.0-rc4 merged with Russell's FEC patches makes it much
more noisy (http://pastebin.com/17TyyMPn):
Populating dev cache
Configuring network interfaces... [ 26.268156] fec 800f.ethernet
eth0: MDIO write timeout
[ 26.298087] fec 800f.ethernet eth0: MDIO read
Moving forward to 3.15.0-rc4 merged with Russell's FEC patches makes it much
more noisy (http://pastebin.com/17TyyMPn):
Populating dev cache
Configuring network interfaces... [ 26.268156] fec 800f.ethernet
eth0: MDIO write timeout
[ 26.298087] fec 800f.ethernet eth0: MDIO read
Also, in 3.14, commenting out both return -ETIMEDOUT instances in
fec_main.c results in a working interface.
Please let me know if you have any questions.
Thank you.
Brian Lilly
Crystalfontz America, Incorporated
12412 East Saltese Road
Spokane Valley, WA 99216
br...@crystalfontz.com
2014-05-07 12:16 GMT-07:00 Brian Lilly br...@crystalfontz.com:
Also, in 3.14, commenting out both return -ETIMEDOUT instances in
fec_main.c results in a working interface.
Please let me know if you have any questions.
At this point, you could probably instrument the interrupt handler and
see
Florian:
Thank you for your help.
After doubling the timeout length it worked.
I managed to get my hands on a imx28evk board and compared our
component load versus theirs, to find they have a 1.5k pull-up on
ENET_MDIO to +3.3v which wasn't present on our board. Adding a 1.5k
pull-up resistor
From: Brian Lilly br...@crystalfontz.com
Data: Thursday, May 08, 2014 3:52 AM
To: Florian Fainelli
Cc: Uwe Kleine-König; David S. Miller; Estevam Fabio-R49496; Jim Baxter; Li
Frank-
B20596; Duan Fugang-B38611; netdev; linux-kernel@vger.kernel.org; kernel
Subject: Re: i.MX28 based system losing
Brian,
On Tue, May 6, 2014 at 1:44 PM, Brian Lilly wrote:
> Uwe:
>
> With commit a264b981f2c76e281ef27e7232774bf6c54ec865 we're having eth0
> come up, then brought right back down with an MDIO rx timeout moments
> after. Adding back in the removed code keeps the interface alive and
> it's
2014-05-06 15:27 GMT-07:00 Brian Lilly :
> It would appear that I don't have that commit. I could move to 3.14
> to see if it makes a difference, but the last couple of responses have
> been on 3.12.18 -- or perhaps I'm missing something else.
I did miss that you were also seeing the problem in
It would appear that I don't have that commit. I could move to 3.14
to see if it makes a difference, but the last couple of responses have
been on 3.12.18 -- or perhaps I'm missing something else.
Please let me know if you have any questions.
Thank you.
Brian Lilly
Crystalfontz America,
2014-05-06 14:40 GMT-07:00 Brian Lilly :
> The PHY on board is the SMSC LAN8720
>
> With the generic PHY driver selected: http://pastebin.com/A4MH4Ptw
>
> [ 28.828761] fec 800f.ethernet eth0: Freescale FEC PHY driver
> [Generic PHY] (mii_bus:phy_addr=800f.etherne:00, irq=-1)
> [
The PHY on board is the SMSC LAN8720
With the generic PHY driver selected: http://pastebin.com/A4MH4Ptw
[ 28.828761] fec 800f.ethernet eth0: Freescale FEC PHY driver
[Generic PHY] (mii_bus:phy_addr=800f.etherne:00, irq=-1)
[ 28.840626] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not
2014-05-06 12:12 GMT-07:00 Brian Lilly :
> It is happening during boot up:
>
>
>
> Configuring network interfaces... [ 35.117114] fec 800f.ethernet
> eth0: Freescale FEC PHY driver [SMSC LAN8710/LAN8720]
Note that the SMSC PHY driver is picked up here, and that specific
driver implements a
It is happening during boot up:
Configuring network interfaces... [ 35.117114] fec 800f.ethernet
eth0: Freescale FEC PHY driver [SMSC LAN8710/LAN8720]
(mii_bus:phy_addr=800f.etherne:00, irq=-1)
[ 35.129967] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
udhcpc (v1.21.1) started
2014-05-06 11:11 GMT-07:00 Uwe Kleine-König :
> Hello Brian,
>
> On Tue, May 06, 2014 at 09:44:34AM -0700, Brian Lilly wrote:
>> With commit a264b981f2c76e281ef27e7232774bf6c54ec865 we're having eth0
>> come up, then brought right back down with an MDIO rx timeout moments
>> after. Adding back in
Hello Brian,
On Tue, May 06, 2014 at 09:44:34AM -0700, Brian Lilly wrote:
> With commit a264b981f2c76e281ef27e7232774bf6c54ec865 we're having eth0
> come up, then brought right back down with an MDIO rx timeout moments
> after. Adding back in the removed code keeps the interface alive and
> it's
Uwe:
With commit a264b981f2c76e281ef27e7232774bf6c54ec865 we're having eth0
come up, then brought right back down with an MDIO rx timeout moments
after. Adding back in the removed code keeps the interface alive and
it's working afterward without trouble. I've tested the re-inserted
code in
It would appear that I don't have that commit. I could move to 3.14
to see if it makes a difference, but the last couple of responses have
been on 3.12.18 -- or perhaps I'm missing something else.
Please let me know if you have any questions.
Thank you.
Brian Lilly
Crystalfontz America,
2014-05-06 15:27 GMT-07:00 Brian Lilly br...@crystalfontz.com:
It would appear that I don't have that commit. I could move to 3.14
to see if it makes a difference, but the last couple of responses have
been on 3.12.18 -- or perhaps I'm missing something else.
I did miss that you were also
Brian,
On Tue, May 6, 2014 at 1:44 PM, Brian Lilly br...@crystalfontz.com wrote:
Uwe:
With commit a264b981f2c76e281ef27e7232774bf6c54ec865 we're having eth0
come up, then brought right back down with an MDIO rx timeout moments
after. Adding back in the removed code keeps the interface alive
Uwe:
With commit a264b981f2c76e281ef27e7232774bf6c54ec865 we're having eth0
come up, then brought right back down with an MDIO rx timeout moments
after. Adding back in the removed code keeps the interface alive and
it's working afterward without trouble. I've tested the re-inserted
code in
Hello Brian,
On Tue, May 06, 2014 at 09:44:34AM -0700, Brian Lilly wrote:
With commit a264b981f2c76e281ef27e7232774bf6c54ec865 we're having eth0
come up, then brought right back down with an MDIO rx timeout moments
after. Adding back in the removed code keeps the interface alive and
it's
2014-05-06 11:11 GMT-07:00 Uwe Kleine-König u.kleine-koe...@pengutronix.de:
Hello Brian,
On Tue, May 06, 2014 at 09:44:34AM -0700, Brian Lilly wrote:
With commit a264b981f2c76e281ef27e7232774bf6c54ec865 we're having eth0
come up, then brought right back down with an MDIO rx timeout moments
It is happening during boot up:
snip, kernel 3.12
Configuring network interfaces... [ 35.117114] fec 800f.ethernet
eth0: Freescale FEC PHY driver [SMSC LAN8710/LAN8720]
(mii_bus:phy_addr=800f.etherne:00, irq=-1)
[ 35.129967] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
udhcpc
2014-05-06 12:12 GMT-07:00 Brian Lilly br...@crystalfontz.com:
It is happening during boot up:
snip, kernel 3.12
Configuring network interfaces... [ 35.117114] fec 800f.ethernet
eth0: Freescale FEC PHY driver [SMSC LAN8710/LAN8720]
Note that the SMSC PHY driver is picked up here, and
The PHY on board is the SMSC LAN8720
With the generic PHY driver selected: http://pastebin.com/A4MH4Ptw
[ 28.828761] fec 800f.ethernet eth0: Freescale FEC PHY driver
[Generic PHY] (mii_bus:phy_addr=800f.etherne:00, irq=-1)
[ 28.840626] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not
2014-05-06 14:40 GMT-07:00 Brian Lilly br...@crystalfontz.com:
The PHY on board is the SMSC LAN8720
With the generic PHY driver selected: http://pastebin.com/A4MH4Ptw
[ 28.828761] fec 800f.ethernet eth0: Freescale FEC PHY driver
[Generic PHY] (mii_bus:phy_addr=800f.etherne:00,
30 matches
Mail list logo
