linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "M. Warner Losh" <imp@bsdimp.com>
To: stuyoder@gmail.com
Cc: linuxppc-dev@ozlabs.org, devicetree-discuss@lists.ozlabs.org
Subject: Re: [RFC] Clock binding
Date: Fri, 28 Aug 2009 12:23:20 -0600 (MDT)	[thread overview]
Message-ID: <20090828.122320.2072670641.imp@bsdimp.com> (raw)
In-Reply-To: <955e48b80908281105q60c057e8pfc16213f17da9138@mail.gmail.com>

In message: <955e48b80908281105q60c057e8pfc16213f17da9138@mail.gmail.co=
m>
            Stuart Yoder <stuyoder@gmail.com> writes:
: > Lets *not* do it on power.org. =A0I'd like to see the bindings used=
 by
: > more than just powerpc people, and power.org might become a bit of =
a
: > mental barrier for non-powerpc folks. =A0kernel.org would be a good=

: > host. =A0So would ozlabs or infradead. =A0Or I'd be happy to mainta=
in one
: > on secretlab.
: =

: I think broadening it beyond power.org is good.  Along those lines I'=
d prefer
: not having this on kernel.org, as device trees are not Linux-centric.=
  There
: are other OS vendors I've interacted with that I'd like to see use de=
vice trees
: and separating it from Linux may be better IMO.

I know of at least one other free OS that will be migrating to device
trees for enumeration of devices in the embedded space...

Warner

  reply	other threads:[~2009-08-28 18:34 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-18  4:21 [RFC] Clock binding Benjamin Herrenschmidt
2009-08-18  7:45 ` [RFC/PATCH] Clock binding prototype implementation Benjamin Herrenschmidt
2009-08-27  4:09 ` [RFC] Clock binding Benjamin Herrenschmidt
2009-08-27  5:20   ` Grant Likely
2009-08-27 21:11   ` Mitch Bradley
2009-08-27 22:18     ` Benjamin Herrenschmidt
2009-08-27 22:28       ` Mitch Bradley
2009-08-27 22:45       ` Mitch Bradley
2009-08-28  0:51         ` Benjamin Herrenschmidt
2009-08-28  2:36           ` Mitch Bradley
2009-08-28  2:43             ` Benjamin Herrenschmidt
2009-08-28  2:53               ` Michael Ellerman
2009-08-28 10:58               ` Josh Boyer
2009-08-28 11:23                 ` David Gibson
2009-08-28 22:28                   ` Benjamin Herrenschmidt
2009-08-28 12:16               ` Stuart Yoder
2009-08-28 16:06                 ` Grant Likely
2009-08-28 18:05                   ` Stuart Yoder
2009-08-28 18:23                     ` M. Warner Losh [this message]
2009-08-28 20:09                     ` Grant Likely
2009-08-31 17:49                       ` Stuart Yoder
2009-08-28 18:12                   ` Mitch Bradley
2009-08-28 18:24                   ` Rafal Jaworowski
2009-08-28 22:33                     ` Benjamin Herrenschmidt
2009-08-28 16:37 ` Grant Likely

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=20090828.122320.2072670641.imp@bsdimp.com \
    --to=imp@bsdimp.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=stuyoder@gmail.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).