From: Andy Pont <andy.pont@sdcsystems.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] AM335x Ethernet pin mux confusion
Date: Tue, 25 Nov 2014 13:47:29 -0000 [thread overview]
Message-ID: <01aa01d008b6$62032df0$260989d0$@pont@sdcsystems.com> (raw)
In-Reply-To: <54742084.5020308@ti.com>
Hello Mugunthan,
> There is no relation between pinmux and phy attached to the slave.
> Is your cpsw slave structures are populated with proper phy ids?
Thanks for giving me the steer on this. I hadn't updated the slave
structure. Having updated the slave structure it is now correctly detecting
both PHYs and I can communicate with the network. :-)
Now to fix all the issues I am having with the Linux kernel...
Regards,
Andy.
prev parent reply other threads:[~2014-11-25 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 14:27 [U-Boot] AM335x Ethernet pin mux confusion Andy Pont
2014-11-25 6:24 ` Mugunthan V N
2014-11-25 13:47 ` Andy Pont [this message]
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='01aa01d008b6$62032df0$260989d0$@pont@sdcsystems.com' \
--to=andy.pont@sdcsystems.com \
--cc=u-boot@lists.denx.de \
/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