linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v3] powerpc/85xx: Add P2020DS board support
Date: Wed, 22 Apr 2009 13:23:32 -0500	[thread overview]
Message-ID: <38B5E2ED-1603-486E-87DB-2F68DFD31DEC@kernel.crashing.org> (raw)
In-Reply-To: <49EF5EFE.2040608@freescale.com>


On Apr 22, 2009, at 1:16 PM, Scott Wood wrote:

> Kumar Gala wrote:
>>> What "we care about" at this point is irrelevant, given the PITA  
>>> it would be to change the device trees (or u-boot) that are  
>>> already in use once we do begin to care.
>> Which is exactly why I didn't put it in the .dts right now.
>
> ???
>
>> Today we know NO code exists that cares about "fsl,elbc-1.2". Once  
>> someone adds such code they can also update the .dts to match it.
>
> DTS files and firmware are *MUCH* harder to update once they're out  
> there than the kernel.  Why such opposition to using an appropriate  
> compatible?

Because I want to avoid make the decision right now.  We are on rev1.x  
silicon and I want to avoid greatly having to spawn a new .dts just  
for "fsl,elbc-1.2.1" that has some errata fix in it.  If dtc was  
smarter and I had less duplication between the 40-50 .dts we have for  
our various parts I wouldn't care that match.

> Is there anything in the p2020ds u-boot patches to set the elbc  
> version, or was that just a brush-off?

I was hoping that Poonam would look at doing that, but there isn't  
anything right now.

I can put out some code for u-boot to address the specific elbc issue  
if that will resolve this.

- k

      reply	other threads:[~2009-04-22 18:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-22  3:31 [PATCH v3] powerpc/85xx: Add P2020DS board support Kumar Gala
2009-04-22  4:54 ` Liu Dave-R63238
2009-04-22 16:44 ` Scott Wood
2009-04-22 16:54   ` Kumar Gala
2009-04-22 17:04     ` Scott Wood
2009-04-22 17:06       ` Kumar Gala
2009-04-22 17:16         ` Scott Wood
2009-04-22 17:25           ` Kumar Gala
2009-04-22 17:38             ` Scott Wood
2009-04-22 18:11               ` Kumar Gala
2009-04-22 18:16                 ` Scott Wood
2009-04-22 18:23                   ` Kumar Gala [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=38B5E2ED-1603-486E-87DB-2F68DFD31DEC@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=scottwood@freescale.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).