From: Scott Wood <scottwood@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v3] powerpc/85xx: Add P2020DS board support
Date: Wed, 22 Apr 2009 12:38:23 -0500 [thread overview]
Message-ID: <49EF560F.90208@freescale.com> (raw)
In-Reply-To: <E25C4315-A3BA-42DF-B2D2-B1CD2D76A03F@kernel.crashing.org>
Kumar Gala wrote:
>
> On Apr 22, 2009, at 12:16 PM, Scott Wood wrote:
>
>> Kumar Gala wrote:
>>> On Apr 22, 2009, at 12:04 PM, Scott Wood wrote:
>>>> Kumar Gala wrote:
>>>>>> If this has an elbc more recent than 1.0 (looks like it), we should
>>>>>> indicate that here.
>>>>> that might be the case, but I leave it to u-boot to do that.
>>>>
>>>> Why? There's no p2020 with an older eLBC, and there's no block
>>>> version register.
>>> But there might be a p2020 w/a newer eLBC version in the future.
>>
>> At which point we can add something to u-boot -- but magic SVR tables
>> seem a step backward from the dts except where needed to avoid the
>> creation of extra dts files.
>
> I don't see the value of complicating u-boot
But complicating u-boot is just what you're suggesting. Put it in the
dts, and u-boot has *zero* code to deal with this unless we find
ourselves wanting to share the dts with another board rev with a newer
chip with a newer elbc.
> to have to parse and
> "fixup" the compatible instead of just having to prepend to it.
> Especially since I don't believe there is anything specific we care
> about in the 1.2 version of elbc at this point.
If the new elbc is compatible with the current one, then you will still
just be prepending. If it is not, then it very likely isn't compatible
with 1.0 either, so you'll have to remove fsl,elbc anyway.
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.
-Scott
next prev parent reply other threads:[~2009-04-22 17:38 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 [this message]
2009-04-22 18:11 ` Kumar Gala
2009-04-22 18:16 ` Scott Wood
2009-04-22 18:23 ` Kumar Gala
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=49EF560F.90208@freescale.com \
--to=scottwood@freescale.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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 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).