From: alexandre.belloni@free-electrons.com (Alexandre Belloni)
To: linux-arm-kernel@lists.infradead.org
Subject: [BUG] at91: macb: does not work
Date: Tue, 16 Jun 2015 15:31:24 +0200 [thread overview]
Message-ID: <20150616133124.GB6549@piout.net> (raw)
In-Reply-To: <5580205B.1030804@aksignal.cz>
Hi,
On 16/06/2015 at 15:10:51 +0200, Ji?? Prchal wrote :
> Hi,
> in v4.1-rc8 does not work ethernet. It normally gets up, but no data are going through.
>
> [ 4.400000] macb f802c000.ethernet (unnamed net_device) (uninitialized): invalid hw address, using random
> [ 4.510000] macb f802c000.ethernet eth0: Cadence MACB rev 0x0001010c at 0xf802c000 irq 37 (52:30:8f:6b:9c:b7)
> [ 4.520000] macb f802c000.ethernet eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=f802c000.etherne:03, irq=-1)
> [ 15.510000] macb f802c000.ethernet eth0: link up (100/Full)
>
> / # ip -s link ls eth0
> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
> link/ether a2:61:fe:17:65:b1 brd ff:ff:ff:ff:ff:ff
> RX: bytes packets errors dropped overrun mcast
> 0 0 0 0 0 0
> TX: bytes packets errors dropped carrier collsns
> 0 0 0 0 0 0
>
> In v4.0.5 it's working.
>
You probably have an issue in your device tree. I've just tested both
interfaces of my sama5d3 xplained and they are working fine.
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-06-16 13:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 13:10 [BUG] at91: macb: does not work Jiří Prchal
2015-06-16 13:24 ` Boris Brezillon
2015-06-16 13:32 ` Sylvain Rochet
2015-06-16 14:47 ` Sylvain Rochet
2015-06-16 13:32 ` Jiří Prchal
2015-06-16 13:31 ` Alexandre Belloni [this message]
2015-06-16 14:05 ` Jiří Prchal
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=20150616133124.GB6549@piout.net \
--to=alexandre.belloni@free-electrons.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.