From: Mitch Bradley <wmb-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
To: Johns Daniel <johns.daniel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org
Subject: Re: I2C not working upon 2.6.24 to 2.6.28 kernel upgrade
Date: Thu, 12 Mar 2009 12:18:45 -1000 [thread overview]
Message-ID: <49B98A45.8020304@firmworks.com> (raw)
In-Reply-To: <ba5d9360903121438p57e068b6n46e58868b814539c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
>
> Binding on device_type or name is strongly discouraged, so the above
> > snippit isn't a good idea.
>
>
> Would you please explain why? I just want to weigh the risk of
> changing the DTB vs. the risk of using a device_type binding.
>
This has been discussed to death, but ...
The proper meaning of "device_type" is to tell Open Firmware that the
device node contains a specific set of methods that implements a
specific API that the firmware can for internal purposes like, for
example, a console.
People have tried to co-opt it for other uses, but doing so just makes
its meaning ambiguous, thus making it difficult to use for any purpose.
The "compatible" property is specifically intended for driver selection.
next prev parent reply other threads:[~2009-03-12 22:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 17:37 I2C not working upon 2.6.24 to 2.6.28 kernel upgrade Johns Daniel
[not found] ` <ba5d9360903121037m6d5be5e9m4b164d56bd6b5f3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-03-12 18:08 ` Grant Likely
[not found] ` <fa686aa40903121108p50338218w18714686d1f8bdbf-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-03-12 21:38 ` Johns Daniel
[not found] ` <ba5d9360903121438p57e068b6n46e58868b814539c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-03-12 22:18 ` Mitch Bradley [this message]
2009-03-17 18:36 ` Scott Wood
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=49B98A45.8020304@firmworks.com \
--to=wmb-d5eqfidgl7eakbo8gow8eq@public.gmane.org \
--cc=devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
--cc=johns.daniel-Re5JQEeQqe8AvxtiuMwx3w@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 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.