linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: Stuart Yoder <stuyoder@gmail.com>
Cc: devicetree-discuss@lists.ozlabs.org,
	linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [RFC] Clock binding
Date: Fri, 28 Aug 2009 14:09:47 -0600	[thread overview]
Message-ID: <fa686aa40908281309g6eedcdb4neb6a96104807a3f1@mail.gmail.com> (raw)
In-Reply-To: <955e48b80908281105q60c057e8pfc16213f17da9138@mail.gmail.com>

On Fri, Aug 28, 2009 at 12:05 PM, Stuart Yoder<stuyoder@gmail.com> wrote:
>> 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 maintain on=
e
>> on secretlab.
>
> I think broadening it beyond power.org is good. =A0Along those lines I'd =
prefer
> not having this on kernel.org, as device trees are not Linux-centric. =A0=
There
> are other OS vendors I've interacted with that I'd like to see use device=
 trees
> and separating it from Linux may be better IMO.
>
> We could also create a new domain like "devicetree.org" (?)..but it still
> would nee a host.

How about right here:  http://fdt.secretlab.ca/

I've only just created the site.  I'll fill in some documentation and
structure in the next few days.  Feel free to create an account and
start adding stuff.

We'll need to talk about how best to manage bindings and have some
form of review/agreement before a binding is marked as "stable".  And
the site URL could change as well.  But in the meantime we've got a
sandbox to start playing in.

g.

--=20
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

  parent reply	other threads:[~2009-08-28 20:15 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
2009-08-28 20:09                     ` Grant Likely [this message]
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=fa686aa40908281309g6eedcdb4neb6a96104807a3f1@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --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).