From: zonque@gmail.com (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: Current state of AM33xx patches
Date: Thu, 02 Aug 2012 21:56:57 +0200 [thread overview]
Message-ID: <501ADB89.4030405@gmail.com> (raw)
In-Reply-To: <98DC2F80-9AD6-4A65-8FA8-3B2AABF72692@dominion.thruhere.net>
On 02.08.2012 17:37, Koen Kooi wrote:
> But I still can't get it working:
>
> root at beaglebone:~# dmesg | grep -i cpsw [ 13.504425] net eth0:
> initializing cpsw version 1.12 (0)
>
> root at beaglebone:~# dmesg | grep -i phy [ 0.000000] Booting Linux
> on physical CPU 0 [ 0.228496] nop_usb_xceiv phy.17: transceiver
> type USB2 PHY already exists [ 13.512056] libphy: PHY
> davinci_mdio-0:00 not found [ 13.517168] net eth0: phy
> davinci_mdio-0:00 not found on slave 0 [ 13.523516] libphy: PHY
> davinci_mdio-0:01 not found [ 13.528675] net eth0: phy
> davinci_mdio-0:01 not found on slave 1
>
> root at beaglebone:~# ifconfig -a | grep eth eth0 Link
> encap:Ethernet HWaddr 00:04:9F:01:1B:B8
Ok, I got it up and and running now on my board using the two
davinci_mdio drivers and the hwmod addition I just posted.
With those applied on top of Mugunthan work, I can link my cpsw slave
with the phy id "davinci_mdio.18-:04", but the 18 is just the global
device counter which will change again once I add more devices. That
still needs some cleanup.
Anyway, at least I can boot into my NFS root now :) Koen, can you try
this on your board and see if that works for you as well?
Thanks,
Daniel
next prev parent reply other threads:[~2012-08-02 19:56 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 9:28 Current state of AM33xx patches Daniel Mack
2012-06-11 13:51 ` Jason Kridner
2012-06-11 14:21 ` Hernandez, Carlos
2012-06-18 8:15 ` Hiremath, Vaibhav
2012-06-21 13:50 ` Daniel Mack
2012-06-25 18:17 ` Daniel Mack
2012-06-26 11:42 ` Sekhar Nori
2012-06-27 12:13 ` Hiremath, Vaibhav
2012-06-28 15:09 ` Daniel Mack
2012-06-29 13:54 ` Yegor Yefremov
2012-06-29 17:43 ` Hiremath, Vaibhav
2012-07-02 12:56 ` Yegor Yefremov
2012-06-29 17:33 ` Hiremath, Vaibhav
2012-06-29 18:34 ` Daniel Mack
2012-06-29 18:47 ` Hiremath, Vaibhav
2012-06-30 2:11 ` Paul Walmsley
2012-06-30 9:33 ` Daniel Mack
2012-07-04 10:07 ` Paul Walmsley
2012-07-04 10:50 ` Hiremath, Vaibhav
2012-07-04 11:22 ` Daniel Mack
2012-07-05 17:45 ` N, Mugunthan V
2012-07-23 6:30 ` Daniel Mack
2012-07-23 16:36 ` N, Mugunthan V
2012-07-26 14:52 ` Daniel Mack
2012-07-26 15:00 ` Koen Kooi
2012-07-26 15:58 ` Daniel Mack
2012-07-26 16:09 ` Koen Kooi
2012-07-26 17:46 ` Daniel Mack
2012-07-31 19:29 ` Koen Kooi
2012-08-02 15:30 ` Daniel Mack
2012-08-02 15:37 ` Koen Kooi
2012-08-02 17:19 ` Daniel Mack
2012-08-02 19:56 ` Daniel Mack [this message]
2012-08-02 20:20 ` Koen Kooi
2012-08-03 10:17 ` N, Mugunthan V
2012-08-03 5:25 ` N, Mugunthan V
2012-06-11 14:15 ` Vaibhav Hiremath
2012-06-23 13:03 ` Domenico Andreoli
2012-06-27 12:07 ` Hiremath, Vaibhav
2012-06-27 18:31 ` Paul Walmsley
2012-06-27 19:01 ` Hiremath, Vaibhav
2012-06-27 19:12 ` Paul Walmsley
2012-06-27 19:21 ` Hiremath, Vaibhav
2012-06-27 19:37 ` Paul Walmsley
2012-06-27 20:00 ` Paul Walmsley
2012-06-27 20:56 ` Hiremath, Vaibhav
2012-06-27 21:13 ` Paul Walmsley
2012-06-27 21:44 ` Paul Walmsley
2012-06-29 14:20 ` Mark Jackson
2012-06-29 17:56 ` Hiremath, Vaibhav
2012-07-02 8:04 ` Mark Jackson
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=501ADB89.4030405@gmail.com \
--to=zonque@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).