All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linux PPC Dev ML <linuxppc-dev@ozlabs.org>, Jon Loeliger <jdl@jdl.com>
Subject: Re: macros and dtc
Date: Tue, 20 Feb 2007 10:29:07 +1100	[thread overview]
Message-ID: <20070219232907.GA17818@localhost.localdomain> (raw)
In-Reply-To: <1171915484.18571.55.camel@localhost.localdomain>

On Tue, Feb 20, 2007 at 07:04:44AM +1100, Benjamin Herrenschmidt wrote:
> 
> > I could envision using something like cpp with #include
> > to get some standard SOC block properties, but macros
> > that try to account for board variations could be quite
> > complex.
> 
> For things like SoC, what I'd like is a way via #include or macros,
> whatever, to layout in a part of the tree a standard block, and then, be
> able to "overlay" on top of it.

Yes, certainly macros on their own wouldn't be very useful for SoCs or
standard boards.  But macros plus overlays should be quite useful.

> I can see other uses for macros for things like making easier to build
> interrupt-map properties for example, especially since most embedded
> boards use standard swizzling

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

      reply	other threads:[~2007-02-19 23:29 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
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 [this message]

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=20070219232907.GA17818@localhost.localdomain \
    --to=david@gibson.dropbear.id.au \
    --cc=benh@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.