linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v2 2/3] mpc82xx: Embedded Planet EP8248E support
Date: Tue, 18 Dec 2007 11:53:48 +1100	[thread overview]
Message-ID: <20071218005348.GC9489@localhost.localdomain> (raw)
In-Reply-To: <47669335.4050405@freescale.com>

On Mon, Dec 17, 2007 at 09:18:13AM -0600, Scott Wood wrote:
> David Gibson wrote:
> > As I think I said about another tree, this mdio-under-bcsr arrangement
> > is pretty strange.  What's going on here.
> 
> As I answered then, it's just the way the hardware is.  I didn't design 
> it. :-P

I obviously missed when you answered this before, I was hoping for
some more detail.

I mean, obviously the MDIO bus is accessed via some of the
board-control registers.  What I'm questioning is whether it makes
sense to have a distinct node to represent the mdio bus, or whether
the phys should just hang straight of the bcsr node.

> >> +	soc@f0000000 {
> >> +		#address-cells = <1>;
> >> +		#size-cells = <1>;
> >> +		device_type = "soc";
> > 
> > Ditch the device_type.
> 
> No, it's used by the bootwrapper.  I'll get rid of it if you want to 
> write a find_node_by_compatible() function. :-)

Well, now that libfdt is merged, there is one :-p.

-- 
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

  reply	other threads:[~2007-12-18  0:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-12 22:54 [PATCH v2 2/3] mpc82xx: Embedded Planet EP8248E support Scott Wood
2007-12-17  3:59 ` David Gibson
2007-12-17 15:18   ` Scott Wood
2007-12-18  0:53     ` David Gibson [this message]
2007-12-18 16:15       ` Scott Wood

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=20071218005348.GC9489@localhost.localdomain \
    --to=david@gibson.dropbear.id.au \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=scottwood@freescale.com \
    /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).