From: David Gibson <dwg@au1.ibm.com>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Alexandre Bounine <Alexandre.Bounine@tundra.com>
Subject: Re: Fix problems with Holly's DT representation of ethernet PHYs
Date: Fri, 25 May 2007 12:04:57 +1000 [thread overview]
Message-ID: <20070525020457.GB13575@localhost.localdomain> (raw)
In-Reply-To: <1180014348.3360.17.camel@zod.rchland.ibm.com>
On Thu, May 24, 2007 at 08:45:48AM -0500, Josh Boyer wrote:
> On Thu, 2007-05-24 at 14:16 +1000, David Gibson wrote:
> > This patch fixes some problems with the way the Ethernet PHYs are
> > represented in the device tree for the Holly board. This means
> > changes to the dts itself, and to the code with instantiates the
> > tsi108 ethernet platform devices based on the device tree.
> >
> > - First, and most importantly, the PHYs are given with an
> > identical 'reg' property. This reg currently encodes the accessible
> > register used to initiate mdio interaction with the PHYs, rather than
> > a meaningful address on the parent bus (mdio in this case), which is
> > incorrect. Instead we give the address of these registers as 'reg' in
> > the mdio node itself, and encode the ID of each phy in their 'reg'
> > propertys. The PHY's unit name addresses are updated to match.
>
> You'll need to fixup the mpc7448hpc2 board's DTS with the same change
> then, as it shares the same bridge and ethernet code.
Ah, yes. Done.
> > - Second, the PHYs give only "bcm54xx" as a compatible
> > property. This is unfortunate, because there are many bcm54xx PHY
> > models, and they have differences which can matter. We add a more
> > precise compatible string, giving the precise PHY model (bcm5461A in
> > this case).
>
> This part is fine with me.
>
> josh
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
>
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2007-05-25 2:48 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 4:16 Fix problems with Holly's DT representation of ethernet PHYs David Gibson
2007-05-24 4:22 ` Kumar Gala
2007-05-24 5:59 ` David Gibson
2007-05-24 9:13 ` Segher Boessenkool
2007-05-24 13:44 ` Josh Boyer
2007-05-25 4:23 ` David Gibson
2007-05-25 4:37 ` David Gibson
2007-05-25 4:38 ` David Gibson
2007-05-25 14:03 ` Josh Boyer
2007-05-27 23:36 ` David Gibson
2007-05-25 14:11 ` Segher Boessenkool
2007-05-27 23:30 ` David Gibson
2007-05-28 1:38 ` Benjamin Herrenschmidt
2007-05-28 11:07 ` Segher Boessenkool
2007-05-28 11:15 ` Benjamin Herrenschmidt
2007-05-28 11:06 ` Segher Boessenkool
2007-05-29 4:47 ` David Gibson
2007-05-24 9:11 ` Segher Boessenkool
2007-05-24 13:45 ` Josh Boyer
2007-05-25 2:04 ` David Gibson [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-05-29 6:05 David Gibson
2007-05-29 6:43 ` Segher Boessenkool
2007-05-29 14:19 ` Josh Boyer
2007-05-29 14:49 ` Segher Boessenkool
2007-05-29 19:29 ` Josh Boyer
2007-05-30 11:17 ` Benjamin Herrenschmidt
2007-05-30 11:32 ` David Gibson
2007-05-30 11:36 ` Segher Boessenkool
2007-05-30 13:48 ` Josh Boyer
2007-05-30 15:28 ` Segher Boessenkool
2007-05-31 5:54 ` Zang Roy-r61911
2007-05-30 1:26 ` David Gibson
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=20070525020457.GB13575@localhost.localdomain \
--to=dwg@au1.ibm.com \
--cc=Alexandre.Bounine@tundra.com \
--cc=jwboyer@linux.vnet.ibm.com \
--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).