From: Arnd Bergmann <arnd@arndb.de>
To: Sean MacLennan <smaclennan@pikatech.com>
Cc: linuxppc-dev@ozlabs.org, devicetree-discuss@ozlabs.org
Subject: Re: [PATCH 2/2] port ndfc driver to of platform
Date: Thu, 14 Aug 2008 12:08:56 +0200 [thread overview]
Message-ID: <200808141208.57345.arnd@arndb.de> (raw)
In-Reply-To: <20080813174536.677187f5@lappy.seanm.ca>
On Wednesday 13 August 2008, Sean MacLennan wrote:
> Changes to the warp platform with the ndfc as an of platform device.
> The main changes are:
>
> * moving the NAND information to the DTS
> * removing warp-nand.c
> * moving the NAND fixups to cuboot-warp.c
The device tree stuff looks good, but the significant fixups you still
need to for the old hw do look like an indication that we should really
have a different way of producing almost-identical dts files.
The cleanest solution for now would be to have two dts files for warp,
but I can understand that you don't want to do that.
Did we ever come to a conclusion on how this could be done, e.g. with
preprocessed dts files or simpler dynamic patching of binary device
trees?
Arnd <><
next parent reply other threads:[~2008-08-14 10:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080801233000.3574434f@lappy.seanm.ca>
[not found] ` <20080804132459.3fc12f59@lappy.seanm.ca>
[not found] ` <20080813174536.677187f5@lappy.seanm.ca>
2008-08-14 10:08 ` Arnd Bergmann [this message]
[not found] ` <200808141208.57345.arnd-r2nGTMty4D4@public.gmane.org>
2008-08-14 16:32 ` [PATCH 2/2] port ndfc driver to of platform Jon Loeliger
2008-08-14 23:20 ` Sean MacLennan
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=200808141208.57345.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=devicetree-discuss@ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=smaclennan@pikatech.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