From: Geoff Levand <geoffrey.levand@am.sony.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Linux PPC Dev ML <linuxppc-dev@ozlabs.org>,
Jon Loeliger <jdl@jdl.com>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: macros and dtc
Date: Mon, 19 Feb 2007 07:51:00 -0800 [thread overview]
Message-ID: <45D9C764.1050400@am.sony.com> (raw)
In-Reply-To: <729E7ED6-D601-4D4C-B110-F951409BAE2B@kernel.crashing.org>
Kumar Gala wrote:
> After spending some time this weekend cleaning up dts files I figured
> it would be nice if we can some to consensus on how we are going to
> do macro support. There is clearly a lot of duplication between
> dts's and it only gets worse when you add in slight variations for
> revs of boards.
>
> I wasn't sure if we are thinking of using some style of preprocessor
> (cpp, m4, etc..) or trying to add something into dtc itself.
>
> However, I think it would be good for us to get some traction towards
> a solution for in kernel dts files.
Based on the previous discussions, there were some concerns with using CPP
on the dts. m4 is a nice preprocessor and I think that it sould be the
choice.
It would be good to have the kernel config available when running the
preprosessor, so that would mean running it from the makefile, not the
wrapper script. It also seems then that having a different file extension
so the processing would fall naturally into a makefile target.
$(obj)/xyz.dts: xyz.dts.m4
$(call cmd,m4)
-Geoff
next prev parent reply other threads:[~2007-02-19 15:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-18 16:58 macros and dtc Kumar Gala
2007-02-19 15:51 ` Geoff Levand [this message]
2007-02-19 18:07 ` Dan Malek
2007-02-19 18:57 ` Yoder Stuart-B08248
2007-02-19 20:16 ` Dan Malek
2007-02-19 21:06 ` Yoder Stuart-B08248
2007-02-20 13:15 ` Segher Boessenkool
2007-02-19 19:28 ` Kumar Gala
2007-02-19 20:04 ` Benjamin Herrenschmidt
2007-02-19 23:29 ` David Gibson
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=45D9C764.1050400@am.sony.com \
--to=geoffrey.levand@am.sony.com \
--cc=david@gibson.dropbear.id.au \
--cc=galak@kernel.crashing.org \
--cc=jdl@jdl.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.