From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: Second ethernet on kirkwood does not work when probed through DT
Date: Sat, 06 Jul 2013 23:22:22 +0200 [thread overview]
Message-ID: <51D88A8E.1060104@gmail.com> (raw)
In-Reply-To: <20130706215426.6e666d6af0dc6c9ea5fe32cd@openwrt.org>
On 07/06/2013 09:54 PM, Jonas Gorski wrote:
> Hello Sebastian,
>
> using your DT patches[1] (on top of 3.10) I can't get the second
> ethernet to work on my kirkwood board.
Hi Jonas,
next time please name your board, because there are plenty of it.
Kirkwood is just the SoC used on them.
> in my dts file I use:
>
> &mdio { status = "okay"; };
>
> ð0 { status = "okay"; ethernet0-port at 0 { speed =<1000>; duplex
> =<1>; }; };
>
I guess you are using Iomega IX2 200?
> ð1 { status = "okay"; ethernet1-port at 1 { speed =<1000>; duplex
> =<1>; }; };
>
> (Both macs are connected to a switch, so use a fixed link, and no
> phy).
>
> Eth1 gets probed fine, but never gets a link when brought up, and
> trying to bring it down again hangs the board hard.
>
> Using Florian's older patches, it is brought up fine and works (after
> adapting the node names of course).
>
> Also I noticed that you named eth1's ethernet1-port node wrongly in
> (at least) your kirkwood conversion patch[2]; you used
>
> ð1 { status = "okay"; ethernet1-port at 0 { must be @1--^ phy-handle
> =<ðphy1>; }; };
Can you please try to leave ethernet1-port at 0 and match
the one in kirkwood.dtsi?
Both "ports" need reg = <0> as there is two controllers
with one port at 0 on Kirkwood.
If that works, please address a mail to ARM mailing list
where you describe the issue and propose the patch.
Sebastian
> which results in a null pointer access on boot:
>
> ... [ 12.627136] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0
> with MAC address ... [ 12.635955] Unable to handle kernel NULL
> pointer dereference at virtual address 00000000 [ 12.644100] pgd =
> c0004000 [ 12.646821] [00000000] *pgd=00000000 [ 12.650418]
> Internal error: Oops: 5 [#1] ARM [ 12.654702] Modules linked in: [
> 12.657778] CPU: 0 PID: 1 Comm: swapper Not tainted 3.10.0 #10 [
> 12.663634] task: c7827d60 ti: c782e000 task.ti: c782e000 [
> 12.669073] PC is at mv643xx_eth_probe+0x98/0x708 ...
>
>
> Regards Jonas
>
> P.S: I'm not on any ML you posted these patches to, so I could not
> reply directly.
>
> [1] https://patchwork.kernel.org/patch/2632571/ etc [2]
> https://patchwork.kernel.org/patch/2811861/
next prev parent reply other threads:[~2013-07-06 21:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-06 19:54 Second ethernet on kirkwood does not work when probed through DT Jonas Gorski
2013-07-06 21:22 ` Sebastian Hesselbarth [this message]
2013-07-06 21:39 ` Jonas Gorski
2013-07-07 10:52 ` Sebastian Hesselbarth
2013-07-07 11:26 ` Jonas Gorski
2013-07-07 11:36 ` Sebastian Hesselbarth
2013-07-07 11:48 ` Jonas Gorski
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=51D88A8E.1060104@gmail.com \
--to=sebastian.hesselbarth@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).