From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Marian Balakowicz" <m8@semihalf.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v3 04/13] [POWERPC] Add generic support for simple MPC5200 based boards
Date: Fri, 9 Nov 2007 07:52:11 -0700 [thread overview]
Message-ID: <fa686aa40711090652xa398f89y188f4a6d41ec7e5f@mail.gmail.com> (raw)
In-Reply-To: <4734721A.6030603@semihalf.com>
On 11/9/07, Marian Balakowicz <m8@semihalf.com> wrote:
> I can imagine that we may get into various trouble (or at least the
> situation is less flexible) if we are unable to update .dts file along
> with the kernel image on a deployed board. If so, then in fact there
> is little sens in using "mpc5200-simple-platform" compatible.
>
> But how serious is that, does such situation frequently happen in
> field? If we are able to update kernel image than what prevents .dts
> file update?
Not everything in the device tree is in the .dts file. U-boot or
other firmware can modify the device tree before passing it to the
kernel. It may not always be possible to update the device tree
without also updating the firmware. I already know of changes that
I'd like to make to the lite5200 tree which I know will break u-boot.
That isn't the situation in this particular case, but we must always
keep it in mind.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next prev parent reply other threads:[~2007-11-09 14:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 20:04 [PATCH v3 00/13] [POWERPC] Add TQM5200/CM5200/Motion-PRO board support Marian Balakowicz
2007-11-06 20:04 ` [PATCH v3 01/13] [POWERPC] Add 'model: ...' line to common show_cpuinfo() Marian Balakowicz
2007-11-06 20:05 ` [PATCH v3 02/13] [POWERPC] Add 'fsl, lpb' bus type for MPC5200 LocalPlus Bus Marian Balakowicz
2007-11-06 20:05 ` [PATCH v3 03/13] [POWERPC] Add common mpc52xx_setup_pci() routine Marian Balakowicz
2007-11-06 20:05 ` [PATCH v3 04/13] [POWERPC] Add generic support for simple MPC5200 based boards Marian Balakowicz
2007-11-06 21:04 ` Grant Likely
2007-11-06 22:22 ` Wolfgang Denk
2007-11-06 23:25 ` Grant Likely
2007-11-09 14:43 ` Marian Balakowicz
2007-11-09 14:52 ` Grant Likely [this message]
2007-11-07 2:34 ` Stephen Rothwell
2007-11-09 14:11 ` Marian Balakowicz
2007-11-06 20:05 ` [PATCH v3 05/13] [POWERPC] Export mpc52xx_map_node() routine symbol Marian Balakowicz
2007-11-06 20:05 ` [PATCH v3 06/13] [POWERPC] Use EXPORT_SYMBOL_GPL for 52xx common routines symbol export Marian Balakowicz
2007-11-06 20:05 ` [PATCH v3 07/13] [POWERPC] TQM5200 DTS Marian Balakowicz
2007-11-06 22:36 ` David Gibson
2007-11-09 14:15 ` Marian Balakowicz
2007-11-06 20:05 ` [PATCH v3 08/13] [POWERPC] TQM5200 defconfig Marian Balakowicz
2007-11-06 20:06 ` [PATCH v3 09/13] [POWERPC] CM5200 DTS Marian Balakowicz
2007-11-06 20:06 ` [PATCH v3 10/13] [POWERPC] CM5200 defconfig Marian Balakowicz
2007-11-06 20:06 ` [PATCH v3 11/13] [POWERPC] Motion-PRO: Add LED support Marian Balakowicz
2007-11-06 20:06 ` [PATCH v3 12/13] [POWERPC] Promess Motion-PRO DTS Marian Balakowicz
2007-11-06 22:42 ` David Gibson
2007-11-09 14:22 ` Marian Balakowicz
2007-11-09 17:49 ` Grant Likely
2007-11-06 20:06 ` [PATCH v3 13/13] [POWERPC] Promess Motion-PRO defconfig Marian Balakowicz
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=fa686aa40711090652xa398f89y188f4a6d41ec7e5f@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.org \
--cc=m8@semihalf.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).