devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
To: Greg KH <greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
Cc: ksummit-2013-discuss-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	"devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org"
	<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>
Subject: Re: [Ksummit-2013-discuss] [ATTEND] Handling of devicetree bindings
Date: Mon, 15 Jul 2013 19:50:27 +0100	[thread overview]
Message-ID: <1373914227.2128.24.camel@shinybook.infradead.org> (raw)
In-Reply-To: <20130715165620.GA29040-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 1038 bytes --]

On Mon, 2013-07-15 at 09:56 -0700, Greg KH wrote:
> How about a hint for subsystem maintainers as to what exactly we should
> be looking for with these bindings?  I for one have no idea what is
> "right" vs. "wrong" with them, so a document explaining this would be
> good to have.
> 
> Or if we already have it, a pointer to it perhaps?

The biggest thing is that it should describe the *hardware*, in a
fashion which is completely OS-agnostic.

The same device-tree binding should work for Solaris, *BSD, Windows,
eCos, and everything else.

I've heard tales of people having to keep device-tree files for their
board tightly in sync with the specific *version* of the Linux kernel
that they were shipped with.

That makes me very sad, because it almost certainly means that someone
has done it completely and utterly wrong.

-- 
David Woodhouse                            Open Source Technology Centre
David.Woodhouse-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org                              Intel Corporation




[-- Attachment #1.2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5745 bytes --]

[-- Attachment #2: Type: text/plain, Size: 192 bytes --]

_______________________________________________
devicetree-discuss mailing list
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
https://lists.ozlabs.org/listinfo/devicetree-discuss

  parent reply	other threads:[~2013-07-15 18:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130713192647.GA3798@katana>
     [not found] ` <20130713204927.GA1124@roeck-us.net>
     [not found]   ` <20130713204927.GA1124-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2013-07-13 23:46     ` [Ksummit-2013-discuss] [ATTEND] Handling of devicetree bindings Linus Walleij
     [not found]       ` <CACRpkdaJ5podVCrb7XuhhGF0Oco+eLrFH0EVGZM0MBbGP9m7WQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-07-14 18:13         ` Guenter Roeck
     [not found]           ` <20130714181331.GC26513-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2013-07-15  8:36             ` Linus Walleij
     [not found]               ` <20130715082915.5142547a@lwn.net>
     [not found]                 ` <20130715082915.5142547a-T1hC0tSOHrs@public.gmane.org>
2013-07-15 14:59                   ` Guenter Roeck
2013-07-15 21:07                   ` Linus Walleij
     [not found]                     ` <CACRpkdaEswVPNqwQkMjsNWutCpOQxgMeGwsgemsF4SSZxXMocQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-07-20  5:51                       ` Grant Likely
     [not found]                     ` <20130719154004.GA3081@katana>
2013-07-21  7:42                       ` Guenter Roeck
2013-07-15 16:56         ` Greg KH
     [not found]           ` <20130715165620.GA29040-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2013-07-15 17:06             ` Mark Brown
     [not found]               ` <20130715170600.GW11538-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-07-15 18:41                 ` Greg KH
     [not found]                   ` <20130715184157.GB17220-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2013-07-15 19:58                     ` Mark Brown
2013-07-15 18:50             ` David Woodhouse [this message]
     [not found]               ` <1373914227.2128.24.camel-Fexsq3y4057IgHVZqg5X0TlWvGAXklZc@public.gmane.org>
2013-07-20  5:48                 ` Grant Likely
2013-07-20 16:16                 ` Linus Walleij
2013-07-21  8:05 Chaiken, Alison
     [not found] ` <60BA5429A0E1584BA3633194F6F993B502AF6D65-0dz9ie/QGrnnlEkxMdpx1dQH9K4/4qFeAL8bYrjMMd8@public.gmane.org>
2013-07-21 11:33   ` Linus Walleij
2013-07-21 16:53   ` David Woodhouse
     [not found]     ` <60BA5429A0E1584BA3633194F6F993B502B10DBC@NA-MBX-03.mgc.mentorg.com>
2013-07-22  6:37       ` Chaiken, Alison

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=1373914227.2128.24.camel@shinybook.infradead.org \
    --to=dwmw2-wegcikhe2lqwvfeawa7xhq@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org \
    --cc=ksummit-2013-discuss-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.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).