linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Jon Loeliger <jdl@jdl.com>,
	Stefan Roese <sr@denx.de>, Roland Dreier <rdreier@cisco.com>,
	linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH] ppc: Add support for AMCC Taishan 440GX eval board
Date: Wed, 14 Feb 2007 11:11:06 +1100	[thread overview]
Message-ID: <20070214001106.GA11491@localhost.localdomain> (raw)
In-Reply-To: <8DEFFE52-2326-43A9-9719-15E04EF17D3A@kernel.crashing.org>

On Mon, Feb 12, 2007 at 11:28:17PM -0600, Kumar Gala wrote:
> 
> On Feb 12, 2007, at 6:46 PM, David Gibson wrote:
> 
> > On Mon, Feb 12, 2007 at 02:41:36PM -0600, Kumar Gala wrote:
> >>
> >> On Feb 12, 2007, at 2:23 PM, Benjamin Herrenschmidt wrote:
> >>
> >>> On Mon, 2007-02-12 at 14:16 -0600, Jon Loeliger wrote:
> >>>> So, like, the other day Benjamin Herrenschmidt mumbled:
> >>>>>
> >>>>> Note that there are still things that we might want to change. For
> >>>>> example, I think we really should look into adding a macro  
> >>>>> mecanism
> >>>>> and/or an include mecanism to dtc so that we can do things like
> >>>>> #include
> >>>>> <ibm440gp.dtc> to get the base processor/SoC definition and then
> >>>>> "overlay" some properties on top of it (like emac phy mode etc...)
> >>>>
> >>>> What do people prefer here?  Straight CPP pre-run?
> >>>
> >>> CPP pre-run has issue, notably due to the usage of "#" in property
> >>> names.
> >>
> >> You can get around that by invoking cpp with the right flags,  I
> >> looked at doing this a while back and had it working.
> >
> > Umm.. which flags?
> 
> cpp -undef -P -x assembler-with-cpp

What exactly does the -x assembler-with-cpp do?  I can't seem to find
a useful description in the man page or info.

-- 
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-14  0:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-12 10:29 [PATCH] ppc: Add support for AMCC Taishan 440GX eval board Stefan Roese
2007-02-12 12:06 ` Benjamin Herrenschmidt
2007-02-12 12:23   ` Stefan Roese
2007-02-12 18:30   ` Roland Dreier
2007-02-12 18:54     ` Stefan Roese
2007-02-12 19:55     ` Benjamin Herrenschmidt
2007-02-12 20:16       ` Jon Loeliger
2007-02-12 20:23         ` Benjamin Herrenschmidt
2007-02-12 20:41           ` Kumar Gala
2007-02-13  0:46             ` David Gibson
2007-02-13  5:28               ` Kumar Gala
2007-02-14  0:11                 ` David Gibson [this message]
2007-02-14  0:30                   ` Kumar Gala
2007-02-14  1:33                     ` David Gibson
2007-02-12 20:32         ` Scott Wood
2007-02-13  0:43           ` 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=20070214001106.GA11491@localhost.localdomain \
    --to=david@gibson.dropbear.id.au \
    --cc=galak@kernel.crashing.org \
    --cc=jdl@jdl.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=rdreier@cisco.com \
    --cc=sr@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;
as well as URLs for NNTP newsgroup(s).