From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Grant Likely" <grant.likely@secretlab.ca>
Cc: devicetree-discuss@ozlabs.org, linuxppc-dev@ozlabs.org,
sparclinux@vger.kernel.org, paulus@samba.org,
Scott Wood <scottwood@freescale.com>,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH 0/3]: Sparc OF I2C support.
Date: Thu, 21 Aug 2008 22:39:40 -0400 [thread overview]
Message-ID: <9e4733910808211939s24f1b2f0tc470aaf3831ebcca@mail.gmail.com> (raw)
In-Reply-To: <fa686aa40808211933o72c2da60v557d5a58f2c9d1a7@mail.gmail.com>
On 8/21/08, Grant Likely <grant.likely@secretlab.ca> wrote:
> On Thu, Aug 21, 2008 at 5:45 PM, Jon Smirl <jonsmirl@gmail.com> wrote:
> > On 8/21/08, Grant Likely <grant.likely@secretlab.ca> wrote:
>
> >> Ugh, more like loads of pain. There are deployed platforms using the
> >> embedded 'invented' bindings. I don't think it is an option to break
> >> compatibility with older trees. If there is some backwards
> >> compatibility code then I'm all for migrating to the same binding as
> >> Sparc and PowerMac
> >
> > Has anything really been deployed? These bindings are only a few months old.
>
>
> It was over a year ago when support for i2c devices in the device tree
> was merged.
I see, the old support needed the drivers to be built-in. The newer
code dynamically loads the correct i2c driver and set its parameters.
Did the old code use anything besides compatible? It would have been
using the older i2c system that probed for the address.
>
> See commit id d13ae8620dfdedfa7e9ab6d1eec294adc0516065.
>
>
> g.
>
> --
> Grant Likely, B.Sc., P.Eng.
> Secret Lab Technologies Ltd.
>
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2008-08-22 2:39 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
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 [this message]
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=9e4733910808211939s24f1b2f0tc470aaf3831ebcca@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=davem@davemloft.net \
--cc=devicetree-discuss@ozlabs.org \
--cc=grant.likely@secretlab.ca \
--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).