linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "John Rigby" <jcrigby@gmail.com>
To: "Grant Likely" <grant.likely@secretlab.ca>
Cc: Linuxppc-embedded <Linuxppc-embedded@ozlabs.org>
Subject: Re: [PATCH] Add USB support to mpc8349-mitx board port
Date: Mon, 9 Jul 2007 17:35:58 -0600	[thread overview]
Message-ID: <4b73d43f0707091635o3ff98713raae9bd914007d9f3@mail.gmail.com> (raw)
In-Reply-To: <fa686aa40707091003n45870ccdn8c9a3629cf19cf77@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 920 bytes --]

I'm just saying that an argument can be made that having all the OF to
non-OF
glue in one place is better than having dual bindings in every driver.

If you count ugliness in terms of file count the fsl_soc.c solution
gets a score of 1 and the dual binding solution gets an score of N.
Where N is the number of drivers.

John

On 7/9/07, Grant Likely <grant.likely@secretlab.ca> wrote:
>
> On 7/8/07, John Rigby <jcrigby@gmail.com> wrote:
> > I see your point, I agree the two layers of glue is bad.  But this means
> > the double code is spread across many drivers instead of being in one
> > place (fsl_soc.c).
>
> ???  I don't understand what you mean.  Are you saying that it's
> better to have all the OF bindings in one place (fsl_soc.c) instead of
> with each individual driver?
>
> Cheers,
> g.
>
>
> --
> Grant Likely, B.Sc., P.Eng.
> Secret Lab Technologies Ltd.
> grant.likely@secretlab.ca
> (403) 399-0195
>

[-- Attachment #2: Type: text/html, Size: 1388 bytes --]

      reply	other threads:[~2007-07-09 23:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-06 22:29 [PATCH] Add USB support to mpc8349-mitx board port Grant Likely
2007-07-06 23:48 ` Arnd Bergmann
2007-07-07  5:46   ` Grant Likely
2007-07-08  0:34     ` John Rigby
2007-07-08  0:48       ` Grant Likely
2007-07-09  3:55         ` John Rigby
2007-07-09 17:03           ` Grant Likely
2007-07-09 23:35             ` John Rigby [this message]

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=4b73d43f0707091635o3ff98713raae9bd914007d9f3@mail.gmail.com \
    --to=jcrigby@gmail.com \
    --cc=Linuxppc-embedded@ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    /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).