From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] RFC: generic property fixup mechanism for LIBFDT
Date: Thu, 23 Aug 2007 13:28:26 -0400 [thread overview]
Message-ID: <46CDC3BA.8020103@smiths-aerospace.com> (raw)
In-Reply-To: <20070823114842.08b9ae7e.kim.phillips@freescale.com>
Kim Phillips wrote:
> On Thu, 23 Aug 2007 01:30:29 +0200
> Wolfgang Denk <wd@denx.de> wrote:
>
>> In message <20070822160915.5cf9e116.kim.phillips@freescale.com> you wrote:
>>> Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com> wrote:
>>>
>>>> IMO your proposal is not acceptable. Follow Grant's advice and the
>>>> current cpu/mpc83xx/cpu.c methodology.
>>> ? Bartlomiej's first patch followed the 83xx 'methodology', which Grant
>>> commented on, which is what Bartlomiej tried to fix here. Maybe I
>>> missed something, but anyway, now that the window has closed, we can
>>> arrange to fix libfdt support for all powerpc boards for the next
>>> release.
>> We still accept patches that fix bugs and solve urgent problems, and
>> if I understand correctly, Bartek's patch attempts to fix a real
>> problem.
>
> maybe I misunderstood then. I just don't want to see code being
> duplicated among two subplatforms (83xx and 52xx) without some stuff
> being refactored into common powerpc areas.
>
> Kim
I didn't jump into this one because it really is Grant's call, but my
understanding is this is new 5xxx functionality which would imply it
goes into the next window. *Good* functionality, but new.
The refactoring should be an effort across 5xxx and 8[356]xx (and
possibly 4xx, 82xx, 8xx) platforms and I would love to see it adopted in
the next window.
gvb
next prev parent reply other threads:[~2007-08-23 17:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 18:24 [U-Boot-Users] [PATCH] fdt, mpc5xxx: Adapt MPC5xxx to use libfdt in ft_cpu_setup() Bartlomiej Sieka
2007-08-03 9:07 ` [U-Boot-Users] [PATCH CORRECTION] " Bartlomiej Sieka
2007-08-03 14:25 ` Grant Likely
2007-08-22 11:54 ` [U-Boot-Users] [PATCH] RFC: generic property fixup mechanism for LIBFDT Bartlomiej Sieka
2007-08-22 13:18 ` Jerry Van Baren
2007-08-22 21:09 ` Kim Phillips
2007-08-22 23:16 ` Jerry Van Baren
2007-08-23 16:24 ` Kim Phillips
2007-08-23 17:01 ` Jerry Van Baren
2007-08-29 18:01 ` Grant Likely
2007-08-30 2:40 ` Jerry Van Baren
2007-08-30 11:51 ` Jerry Van Baren
2007-08-30 12:49 ` Bartlomiej Sieka
2007-08-22 23:30 ` Wolfgang Denk
2007-08-23 16:48 ` Kim Phillips
2007-08-23 17:28 ` Jerry Van Baren [this message]
2007-08-23 19:25 ` Wolfgang Denk
2007-08-29 10:59 ` [U-Boot-Users] [PATCH CORRECTION] fdt, mpc5xxx: Adapt MPC5xxx to use libfdt in ft_cpu_setup() Wolfgang Denk
2007-08-29 18:23 ` Grant Likely
2007-08-04 21:21 ` [U-Boot-Users] [PATCH] " Jerry Van Baren
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=46CDC3BA.8020103@smiths-aerospace.com \
--to=gerald.vanbaren@smiths-aerospace.com \
--cc=u-boot@lists.denx.de \
/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