From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] ARM: atmel: sama5d3xek: let emac auto detect phy addr
Date: Fri, 23 Jan 2015 17:19:05 +0800 [thread overview]
Message-ID: <6BAD5335-E077-4EE2-B95B-DFBAB1FE3858@jcrosoft.com> (raw)
In-Reply-To: <20150123080457.GA12209@pengutronix.de>
> On Jan 23, 2015, at 4:04 PM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
>
> On Fri, Jan 23, 2015 at 03:53:48PM +0800, Jean-Christophe PLAGNIOL-VILLARD wrote:
>>
>>> On Jan 23, 2015, at 3:51 PM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
>>>
>>> On Thu, Jan 22, 2015 at 03:26:53PM +0800, Bo Shen wrote:
>>>> On the SAMA5D35 the EMAC phy addr is 1 while not 0. So, let
>>>> the EMAC auto detect phy addr, or else hard code to 0, the
>>>> ethernet can not work on SAMA5D35 board.
>>>>
>>>> Signed-off-by: Bo Shen <voice.shen@atmel.com>
>>>
>>> There ere boards with different phy addresses around, so
>>> the current state does not work on all boards anyway. So the worst
>>> thing that can happen with this and the other patch for the gmac is
>>> that now another set of boards does not work. Let's give it a try.
>>> I'm open to reports when now some board stops working.
>>>
>>> Applied this and the gmac patch.
>>
>> except we can auto detect the board we are running from
>> so it will be better to specify it at Run time
>>
>> as we have issue on auto detect on some of them
>
> Ok, so your suggestion is to detect the board (type, revision?) and
> set phy_addr correctly based on this information, right? Fine with me
> aswell. Is it known which boards have which phy_addr?
yes and I already write the detection code in barebox
Best Regards,
J.
>
> Sascha
>
> --
> Pengutronix e.K. | |
> Industrial Linux Solutions | http://www.pengutronix.de/ |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2015-01-23 9:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 7:26 Bo Shen
2015-01-23 7:51 ` Sascha Hauer
2015-01-23 7:53 ` Jean-Christophe PLAGNIOL-VILLARD
2015-01-23 8:04 ` Sascha Hauer
2015-01-23 9:19 ` Jean-Christophe PLAGNIOL-VILLARD [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=6BAD5335-E077-4EE2-B95B-DFBAB1FE3858@jcrosoft.com \
--to=plagnioj@jcrosoft.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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