From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Scott Wood" <scottwood@freescale.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: use of fsl, in lite5200b.dts in git current
Date: Thu, 8 Nov 2007 17:17:51 -0500 [thread overview]
Message-ID: <9e4733910711081417h7a571398md59a8987f15423a6@mail.gmail.com> (raw)
In-Reply-To: <473387AF.6030105@freescale.com>
On 11/8/07, Scott Wood <scottwood@freescale.com> wrote:
> Jon Smirl wrote:
> > On 11/8/07, Scott Wood <scottwood@freescale.com> wrote:
> >>> As far as I know the only dts using vendor prefixes in the compatible
> >>> attributes is 5200lite one for the gpt entries. Everything else will
> >>> need to be changed.
> >> Look a little harder. Many of the Freescale boards/devices do it right
> >> -- and yes, we need to fix the ones that don't.
> >
> > I see that there are quite a few with the ibm prefix. But by
> > eyeballing grep output it looks like several hundred attributes need
> > to be fixed. Code referencing these will need to be fixed too.
>
> Several hundred? I don't think there are several hundred unique
> property names or compatible entries in arch/powerpc/boot/dts *total*,
There are 601 'compatible' attributes in the directory.
> much less that need fixing. The main ones in fsl-land that I can think
> of are gianfar, i2c, talitos, QE, USB, tsi108, watchdog, SPI, and IPIC.
>
> CPM1 and CPM2 devices, PCI, 85xx memory/cache controllers, and 85xx
> global utilities have the prefix.
>
> For the most part, we've been adding prefixes whenever we have any other
> reason to touch the binding.
>
> > If lite5200 hadn't mixed half prefixed and half not prefixed I never
> > would have started looking at this.
> >
> > Let's make up our minds in the lite5200 dts so that I can sync up my
> > development hardware.
>
> Patches are welcome. :-)
>
> -Scott
>
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2007-11-08 22:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 21:55 use of fsl, in lite5200b.dts in git current Jon Smirl
2007-11-07 22:17 ` Matt Sealey
2007-11-07 22:18 ` Jon Smirl
2007-11-08 20:40 ` Jon Smirl
2007-11-08 20:47 ` Scott Wood
2007-11-08 20:51 ` Jon Smirl
2007-11-08 20:56 ` Scott Wood
2007-11-08 21:53 ` Jon Smirl
2007-11-08 22:03 ` Scott Wood
2007-11-08 22:17 ` Jon Smirl [this message]
2007-11-08 22:30 ` Scott Wood
2007-11-08 20:50 ` Grant Likely
2007-11-07 22:21 ` Jon Smirl
2007-11-08 0:30 ` Matt Sealey
2007-11-08 2:15 ` Jon Smirl
2007-11-08 16:28 ` Scott Wood
2007-11-08 17:04 ` Jon Smirl
2007-11-08 19:48 ` Matt Sealey
2007-11-08 19:57 ` Jon Loeliger
2007-11-10 14:09 ` Matt Sealey
2007-11-08 20:39 ` Jon Smirl
2007-11-08 3:14 ` 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=9e4733910711081417h7a571398md59a8987f15423a6@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=scottwood@freescale.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).