From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] powerpc/83xx: Revive Marvell PHY option on MPC8313E-RDB rev. C boards
Date: Fri, 13 Feb 2009 04:18:01 +0300 [thread overview]
Message-ID: <20090213011801.GA28509@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <F0245D03-4191-4482-B007-603C3DAC8A1A@kernel.crashing.org>
On Thu, Feb 12, 2009 at 05:51:57PM -0600, Kumar Gala wrote:
> On Feb 11, 2009, at 11:40 PM, Li Yang-R58472 wrote:
>>>> Li, thanks for heads-up!
>>>>
>>>> One thing though: documentation says that Marvell PHY
>>> address is 0x3,
>>>> while old device tree and this patch:
>>>>
>>>>
>>> http://www.bitshrine.org/gpp/linux-fsl-2.6.23-MPC8313ERDB-add-
>>> default-
>>>> dts.patch
>>>>
>>>> says "0x1"... I don't have any rev. C boards, so it would
>>> be great if
>>>> somebody could confirm that 0x1 is the actual address.
>>
>> The correct address is 0x3. The previous patch in revB BSP used a
>> guess
>> value before the revC documentation is available. The latest BSP has
>> been updated to use the correct address.
>
> Anton, will you spin a new patch with this change?
Since the correct address is 0x3, that means that the old device
tree never worked on rev. C boards, thus there is no regression.
And furthermore, it appears that U-Boot doesn't support Marvell
PHY option either.
So, I don't think that adding the new device tree makes any sense
now.
I think the better option would be to implement Marvell PHY support
in U-Boot, and at the same time teach U-Boot to fixup 8313rdb's
device tree depending on the environment variable (something like
setenv marvell_phy_option yes/no), i.e. like I did for
MPC8315E-RDB's ULPI/TSEC1 options:
http://lists.denx.de/pipermail/u-boot/2008-July/036553.html
Makes sense? If not, I'll readily respin this patch with the PHY
address change.
Thanks,
--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
next prev parent reply other threads:[~2009-02-13 1:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 20:10 [PATCH 2/2] powerpc/83xx: Fix TSEC0 workability on MPC8313E-RDB boards Anton Vorontsov
2009-02-06 16:39 ` Kumar Gala
2009-02-09 7:47 ` Li Yang
2009-02-09 15:32 ` Kumar Gala
2009-02-10 15:10 ` [PATCH] powerpc/83xx: Revive Marvell PHY option on MPC8313E-RDB rev. C boards Anton Vorontsov
2009-02-10 15:30 ` Kumar Gala
2009-02-12 2:36 ` Li Yang-R58472
2009-02-12 5:25 ` Kumar Gala
2009-02-12 5:24 ` Kumar Gala
2009-02-12 5:40 ` Li Yang-R58472
2009-02-12 23:51 ` Kumar Gala
2009-02-13 1:18 ` Anton Vorontsov [this message]
2009-02-13 2:24 ` [PATCH] powerpc/83xx: Revive Marvell PHY option onMPC8313E-RDB " Li Yang-R58472
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=20090213011801.GA28509@oksana.dev.rtsoft.ru \
--to=avorontsov@ru.mvista.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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).