From: holgerschurig@gmail.com (Holger Schurig)
To: linux-arm-kernel@lists.infradead.org
Subject: iMX6Q FEC: transmit queue 0 timed out
Date: Mon, 2 Jun 2014 16:11:10 +0200 [thread overview]
Message-ID: <CAOpc7mHJ5CqCcB1rE3b8q58HDdSWeG41PTAMwgeARAL_hgUt_g@mail.gmail.com> (raw)
In-Reply-To: <20140602133352.GC933@n2100.arm.linux.org.uk>
> On the Microsom, I need:
>
> MX6QDL_PAD_GPIO_16__ENET_REF_CLK 0xc0000000
>
> Does that work for you?
Still works in Barebox, but in Linux:
/ # ifconfig eth0 192.168.233.198
fec 2188000.ethernet eth0: MDIO write timeout
fec 2188000.ethernet eth0: MDIO read timeout
fec 2188000.ethernet eth0: MDIO write timeout
fec 2188000.ethernet eth0: could not attach to PHY
ifconfig: SIOCSIFFLAGS: Connection timed out
/ #
I see that some in-Linux-tree DTS have this value, others have
0x4001b0a8 (one in-barebox-tree DTS has a simple 0x1b0b0). Both SION
settings create the same error at ifup time for me. And Barebox
doesn't care for any of them, continue to do TFTP all the time.
next prev parent reply other threads:[~2014-06-02 14:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 12:27 iMX6Q FEC: transmit queue 0 timed out Holger Schurig
2014-06-02 12:42 ` Russell King - ARM Linux
2014-06-02 13:15 ` Holger Schurig
2014-06-02 13:33 ` Russell King - ARM Linux
2014-06-02 14:11 ` Holger Schurig [this message]
2014-06-03 3:22 ` fugang.duan at freescale.com
2014-06-03 15:45 ` Holger Schurig
[not found] ` <a97d34741f694cd2b89b4c7f0bebc114@BLUPR03MB373.namprd03.prod.outlook.com>
2014-06-04 11:50 ` Holger Schurig
2014-06-04 13:50 ` Russell King - ARM Linux
2014-07-16 8:41 ` Holger Schurig
2014-07-22 8:15 ` Shawn Guo
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=CAOpc7mHJ5CqCcB1rE3b8q58HDdSWeG41PTAMwgeARAL_hgUt_g@mail.gmail.com \
--to=holgerschurig@gmail.com \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).