All of lore.kernel.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: linuxppc-dev Development <linuxppc-dev@ozlabs.org>,
	Sven Luther <sven@genesi-usa.com>
Subject: Re: Discussion on SOC device tree bindings
Date: Mon, 15 Jan 2007 16:42:18 +0100	[thread overview]
Message-ID: <5378f4dcd28423047dc3cfb1404f08e1@kernel.crashing.org> (raw)
In-Reply-To: <20070115110509.GA25974@localhost.localdomain>

> How about always specifying the exact name and only the exact name
> in the device tree, i.e. mpc5200-fec on mpc5200, mpc5200b-fec on
> mpc5200b and so on.

No :-)

> This way the driver can decide whether or not it's
> compatible to a device

It already can.

> and we can be sure not to overlook any
> incompatibilities. We could even decide in later kernel versions that
> two devices are too incompatible and split the driver into two.

You can already; say you have a driver that will only work
on 5200b, is will match on that, and the "plain" 5200 driver
won't get a chance to grab the device.  You have to match
for the most specific first, of course.

> There may be incompatibilities between 5200 and 5200b which we simply 
> did
> not discover yet.

If that is so, than such a 5200b-specific driver can be
created (possibly just as some special cases in the
existing 5200 driver).

Listing something in the "compatible" property doesn't mean
the device is 100% compatible, just that it's mostly compatible.
Earlier entries in there are "more compatible" ;-)


Segher

  parent reply	other threads:[~2007-01-15 15:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <528646bc0701131555n3249b503i3b6e8c37db41dd52@mail.gmail.com>
2007-01-14 22:29 ` Discussion on SOC device tree bindings Grant Likely
2007-01-15 11:05   ` Sascha Hauer
2007-01-15 13:48     ` Grant Likely
2007-01-15 15:42     ` Segher Boessenkool [this message]
2007-01-16  8:25       ` Sascha Hauer
     [not found] ` <45AA098C.70101@246tNt.com>
     [not found]   ` <6189b01379f62aa4516484872f4ef86f@kernel.crashing.org>
     [not found]     ` <1168810790.4803.11.camel@localhost.localdomain>
     [not found]       ` <ccc8fbc935d8f8d3e30870d43959f6c7@kernel.crashing.org>
     [not found]         ` <1168817449.4803.28.camel@localhost.localdomain>
     [not found]           ` <ef64a4198a02929a00c28abb5f0934b5@kernel.crashing.org>
     [not found]             ` <1168818533.4803.37.camel@localhost.localdomain>
     [not found]               ` <a1af25147ea7308c394d243511b96f69@kernel.crashing.org>
     [not found]                 ` <45ABA20E.30008@genesi-usa.com>
2007-01-15 17:06                   ` Grant Likely
2007-01-15 18:31                     ` Segher Boessenkool
2007-01-16  6:25                     ` Benjamin Herrenschmidt
2007-01-16  9:07                       ` Segher Boessenkool
     [not found]                 ` <1168928567.4803.55.camel@localhost.localdomain>
2007-01-17  8:40                   ` Grant Likely
2007-01-19 10:58                     ` Segher Boessenkool
2007-01-19 16:11                       ` Yoder Stuart-B08248
2007-01-19 16:38                         ` Grant Likely
2007-01-19 16:50                         ` Segher Boessenkool

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=5378f4dcd28423047dc3cfb1404f08e1@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=s.hauer@pengutronix.de \
    --cc=sven@genesi-usa.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.