From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Alexandre Bounine <Alexandre.Bounine@tundra.com>,
David Gibson <dwg@au1.ibm.com>, Paul Mackerras <paulus@samba.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: Fix problems with Holly's DT representation of ethernet PHYs
Date: Wed, 30 May 2007 08:48:19 -0500 [thread overview]
Message-ID: <1180532899.3360.79.camel@zod.rchland.ibm.com> (raw)
In-Reply-To: <8b93622a41f822c7b8444d42deb9e5ac@kernel.crashing.org>
On Wed, 2007-05-30 at 13:36 +0200, Segher Boessenkool wrote:
> > We're adding these compatible properties to DTS files and the drivers
> > at
> > the same time. Unless (until?) there are firmwares for these boards
> > that start specifying something else in a real device tree, it really
> > doesn't matter much.
>
> Sure. So you have time to work out things now, I
> suggest you take advantage of that :-)
>
> > Not that there's anything wrong with your
> > reasoning. Just seems like we're trying really hard to define
> > something
> > "correctly" when we control what's on both sides :).
>
> Right now, and in your case, you do. OTOH, the
> goal is to have the DTS be a well-established
> stable interface between the firmware/bootloader/
> bootwrapper and the kernel; there is no room for
> either side of that interface playing dirty tricks,
> not on any board ;-)
>
> Also, the DTS files in the kernel source tree should
> server as a best-of-breed example for people doing
> custom device trees for their own boards. We better
> whip them into good shape or we'll all look foolish...
Yeah, I know. Ignore my earlier email. I blame it on lack of sleep.
The only issue we might have in the future is if DT capable firmware for
these boards shows up and does something completely different.
Hopefully that won't happen.
josh
next prev parent reply other threads:[~2007-05-30 13:50 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 6:05 Fix problems with Holly's DT representation of ethernet PHYs 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 [this message]
2007-05-30 15:28 ` Segher Boessenkool
2007-05-31 5:54 ` Zang Roy-r61911
2007-05-30 1:26 ` David Gibson
-- strict thread matches above, loose matches on Subject: below --
2007-05-24 4:16 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
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=1180532899.3360.79.camel@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=Alexandre.Bounine@tundra.com \
--cc=dwg@au1.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=segher@kernel.crashing.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).