From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: David Miller <davem@davemloft.net>
Cc: grant.likely@secretlab.ca, scottwood@freescale.com,
sparclinux@vger.kernel.org, devicetree-discuss@ozlabs.org,
paulus@samba.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 0/3]: Sparc OF I2C support.
Date: Thu, 21 Aug 2008 21:15:37 -0400 [thread overview]
Message-ID: <1219367743.26429.66.camel@jdub.homelinux.org> (raw)
In-Reply-To: <20080821.163216.239892875.davem@davemloft.net>
On Thu, 2008-08-21 at 16:32 -0700, David Miller wrote:
> From: "Grant Likely" <grant.likely@secretlab.ca>
> Date: Thu, 21 Aug 2008 17:14:57 -0600
>
> > On Thu, Aug 21, 2008 at 3:35 PM, Scott Wood <scottwood@freescale.com> wrote:
> > > David Miller wrote:
> > >>>
> > >>> On Thu, Aug 21, 2008 at 12:10:12AM -0700, David Miller wrote:
> > >> If you guys created this format in your compressed openfirmware
> > >> trees, is it possible for you to "fix" it to match what Sparc
> > >> systems following the proper bindings do?
> > >
> > > Possibly, though it'll cause some pain when old trees are used with a kernel
> > > that expects the new binding.
> >
> > 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
>
> You could even put the detection and reg property fixups in the device
> tree expander. This way generic code in drivers/of/of_i2c.c doesn't
> need to know about this huge mistake.
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.
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.
josh
next prev parent reply other threads:[~2008-08-22 1:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080821.001012.265401427.davem@davemloft.net>
[not found] ` <20080821163256.GC15669@ld0162-tx32.am.freescale.net>
[not found] ` <20080821.142134.127315039.davem@davemloft.net>
[not found] ` <48ADDF86.2040200@freescale.com>
2008-08-21 23:14 ` [PATCH 0/3]: Sparc OF I2C support Grant Likely
2008-08-21 23:32 ` David Miller
2008-08-22 1:15 ` Josh Boyer [this message]
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
2008-08-22 15:58 ` Scott Wood
2008-08-22 16:44 ` 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=1219367743.26429.66.camel@jdub.homelinux.org \
--to=jwboyer@linux.vnet.ibm.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