From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: David Miller <davem@davemloft.net>
Cc: devicetree-discuss@ozlabs.org, linuxppc-dev@ozlabs.org,
sparclinux@vger.kernel.org, paulus@samba.org,
scottwood@freescale.com
Subject: Re: [PATCH 0/3]: Sparc OF I2C support.
Date: Fri, 22 Aug 2008 06:50:48 -0400 [thread overview]
Message-ID: <20080822065048.662e3f8e@zod.rchland.ibm.com> (raw)
In-Reply-To: <20080821.205305.74123372.davem@davemloft.net>
On Thu, 21 Aug 2008 20:53:05 -0700 (PDT)
David Miller <davem@davemloft.net> wrote:
> From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
> Date: Thu, 21 Aug 2008 21:15:37 -0400
>
> > Huge? I'd say mistake, but not necessarily huge. I mean nobody other
> > than you (at least in the context of this conversation) had access to
> > the IEEE1275 proposed binding so it wasn't like there was tons to go on.
>
> I guess all the PowerMAC G5 systems out there and their device trees
> were locked up in a highly secure vault somewhere :-)
Apple has done silly things in their device trees before. I wouldn't
hold them up as an excellent example.
> > Have patience with the embedded people that are both new to
> > OpenFirmware and trying to make stuff work at the same time. I
> > think the devicetree-discuss list will help here as new bindings are
> > proposed. I hope you're subscribed.
>
> Why not ask the people who actually work on the standards? That's who
> I go to when I want to know something about openfirmware issues.
Honestly, I don't know. And from what I can tell, there _aren't_
people who actively work on the standards anymore. Mitch is active
elsewhere and could be a great resource but aside from him I have no
idea who to contact.
josh
next prev parent reply other threads:[~2008-08-22 10:50 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 7:10 [PATCH 0/3]: Sparc OF I2C support David Miller
2008-08-21 16:32 ` Scott Wood
2008-08-21 21:21 ` David Miller
2008-08-21 21:35 ` Scott Wood
2008-08-21 21:45 ` David Miller
2008-08-21 22:05 ` Benjamin Herrenschmidt
2008-08-21 22:27 ` David Miller
2008-08-21 22:38 ` Benjamin Herrenschmidt
2008-08-21 22:05 ` Benjamin Herrenschmidt
2008-08-21 22:28 ` David Miller
2008-08-21 22:39 ` Benjamin Herrenschmidt
2008-08-21 23:14 ` Grant Likely
2008-08-21 23:32 ` David Miller
2008-08-22 1:15 ` Josh Boyer
2008-08-22 3:53 ` David Miller
2008-08-22 4:18 ` Grant Likely
2008-08-22 4:22 ` David Miller
2008-08-22 4:29 ` Mitch Bradley
2008-08-22 4:30 ` Grant Likely
2008-08-22 4:34 ` Grant Likely
2008-08-22 4:37 ` David Miller
2008-08-22 5:19 ` Mitch Bradley
2008-08-22 16:00 ` Yoder Stuart
2008-08-22 16:13 ` Josh Boyer
2008-08-22 10:50 ` Josh Boyer [this message]
2008-08-22 11:06 ` David Miller
2008-08-21 23:45 ` Jon Smirl
2008-08-22 2:33 ` Grant Likely
2008-08-22 2:39 ` Jon Smirl
2008-08-22 15:58 ` Scott Wood
2008-08-22 16:44 ` Grant Likely
2008-08-21 22:01 ` Benjamin Herrenschmidt
2008-08-21 21:53 ` Jon Smirl
2008-08-21 21:58 ` David Miller
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=20080822065048.662e3f8e@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=devicetree-discuss@ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=scottwood@freescale.com \
--cc=sparclinux@vger.kernel.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).