linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Matt Sealey <matt@genesi-usa.com>
Cc: PowerPC dev list <Linuxppc-dev@ozlabs.org>
Subject: Re: Revisited, audio codec device tree entries.
Date: Tue, 20 Nov 2007 12:42:18 +1100	[thread overview]
Message-ID: <20071120014218.GD3126@localhost.localdomain> (raw)
In-Reply-To: <4741C0C4.4070502@genesi-usa.com>

On Mon, Nov 19, 2007 at 04:58:44PM +0000, Matt Sealey wrote:
> Segher Boessenkool wrote:
> >> And I forgot the rant you guys usually get - for god's sake, why isn't
> >> anyone using the "model" property?
> > 
> > Probably because it isn't useful all that often.
> > 
> >> sound@0 {
> >>     \\ this is our magic audio fabric
> >>     device_type = "digispeaker,flinger";
> > 
> > This is wrong in so many ways; see David's mail for a start.
> 
> Why? I'm sorry but I am living in the real world where we have real
> firmwares and real dynamic device trees here. You can't just say
> "this is wrong because it has a device_type".

It's not wrong because it has a device_type, it's wrong because the
device_type value is some random made-up thing that doesn't have an OF
binding behind it.  Nor do you suggest an OF binding.  Nor should
driver selection be based off device_type.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

  reply	other threads:[~2007-11-20  1:42 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-18 18:10 Revisited, audio codec device tree entries Jon Smirl
2007-11-18 20:16 ` Segher Boessenkool
2007-11-18 21:49   ` Jon Smirl
2007-11-18 22:46     ` Matt Sealey
2007-11-18 23:31       ` Matt Sealey
2007-11-18 23:47         ` Jon Smirl
2007-11-19  0:12         ` David Gibson
2007-11-19  0:22           ` Jon Smirl
2007-11-19 12:48           ` Segher Boessenkool
2007-11-20  0:22             ` David Gibson
2007-11-19 16:31           ` Matt Sealey
2007-11-19 17:05             ` Scott Wood
2007-11-19 18:55               ` Grant Likely
2007-11-20  0:33             ` David Gibson
2007-11-19 12:07         ` Segher Boessenkool
2007-11-19 16:58           ` Matt Sealey
2007-11-20  1:42             ` David Gibson [this message]
2007-11-19 14:57       ` Timur Tabi
2007-11-19 15:33         ` Jon Smirl
2007-11-19 15:02 ` Timur Tabi
2007-11-19 15:15   ` Jon Loeliger
2007-11-19 15:33   ` Grant Likely
2007-11-19 16:00     ` Jon Smirl
2007-11-19 16:31       ` Grant Likely
2007-11-19 16:51         ` Jon Smirl
2007-11-19 17:33           ` Grant Likely
2007-11-19 19:20             ` Jon Smirl
2007-11-19 19:28               ` Grant Likely
2007-11-20  0:59                 ` David Gibson
2007-11-26 15:51                   ` Timur Tabi
2007-11-26 16:38                     ` Jon Smirl
2007-11-26 16:40                       ` Timur Tabi
2007-11-19 16:45       ` Timur Tabi
2007-11-19 22:37         ` Jon Smirl
2007-11-19 16:44     ` Timur Tabi
2007-11-19 16:53       ` Grant Likely
2007-11-19 16:55       ` Jon Smirl
2007-11-19 15:37   ` Jon Smirl
2007-11-19 15:42     ` 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=20071120014218.GD3126@localhost.localdomain \
    --to=david@gibson.dropbear.id.au \
    --cc=Linuxppc-dev@ozlabs.org \
    --cc=matt@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 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).