All of lore.kernel.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	David Gibson <david@gibson.dropbear.id.au>,
	Alexandre Bounine <Alexandre.Bounine@tundra.com>
Subject: Re: TSI ethernet PHY question
Date: Fri, 25 May 2007 16:25:43 +0200	[thread overview]
Message-ID: <a50ad0ac767c59abbf644f7d6bf8ced6@kernel.crashing.org> (raw)
In-Reply-To: <18006.31742.533944.368969@cargo.ozlabs.ibm.com>

>> Only if you think the device tree is a configuration
>> mechanism for the OS.
>
> Well, actually, it's whatever we want it to be...

Oh not this discussion again.

> There is some value in making the device tree abstract and general,
> but not an overwhelming value that trumps all other considerations.

Yes, there can be other considerations; however, not making
a mess out of it all is certainly a very important one in
my book.


Segher

  reply	other threads:[~2007-05-25 14:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-23  7:03 TSI ethernet PHY question Benjamin Herrenschmidt
2007-05-23 13:43 ` Alexandre Bounine
2007-05-23 15:55   ` Segher Boessenkool
2007-05-23 22:52   ` Benjamin Herrenschmidt
2007-05-24 18:53     ` Andy Fleming
2007-05-24 22:51       ` Benjamin Herrenschmidt
2007-05-24 23:54         ` Segher Boessenkool
2007-05-25  0:01           ` Benjamin Herrenschmidt
2007-05-25  0:57             ` Segher Boessenkool
2007-05-25  1:53               ` Benjamin Herrenschmidt
2007-05-25 14:24                 ` Segher Boessenkool
2007-05-25  6:02               ` Paul Mackerras
2007-05-25 14:25                 ` Segher Boessenkool [this message]
2007-05-25  2:00           ` David Gibson
2007-05-25  7:35             ` Zang Roy-r61911
2007-05-25 14:17             ` Segher Boessenkool

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=a50ad0ac767c59abbf644f7d6bf8ced6@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=Alexandre.Bounine@tundra.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.