From: Wolfgang Reissnegger <wolfgang.reissnegger@xilinx.com>
To: linuxppc-embedded@ozlabs.org
Subject: [Fwd: Re: [PATCH 3/3] Add support for xupv2p and ml410 boards.]
Date: Wed, 22 Aug 2007 08:12:03 -0700 [thread overview]
Message-ID: <20070822151206.3CB1E29007E@mail42-sin.bigfish.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 0 bytes --]
[-- Attachment #2: Re: [PATCH 3/3] Add support for xupv2p and ml410 boards. --]
[-- Type: message/rfc822, Size: 1308 bytes --]
From: Wolfgang Reissnegger <wolfgang.reissnegger@xilinx.com>
To: Robert Woodworth <rwoodworth@securics.com>
Subject: Re: [PATCH 3/3] Add support for xupv2p and ml410 boards.
Date: Tue, 21 Aug 2007 20:59:05 -0700
Message-ID: <46CBB489.3080700@xilinx.com>
Robert Woodworth wrote:
> Should the xparameters????.h file *really* be included in the tree?
>
> This file is completely board/EDK/ISE/synthesis specific. I'd rather
> it not be included and have people copy theirs from EDK. Or as I have
> done, sym-link it from my EDK project.
>
> Woody.
The purpose of the included xparameter.h files is to provide a
configuration for the default reference designs. They are useful if you
want to compile a kernel without building a system with the EDK first.
As Grant pointed out, for custom designs you'd need to generate your own
xparameter.h file.
Wolfgang
reply other threads:[~2007-08-22 15:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070822151206.3CB1E29007E@mail42-sin.bigfish.com \
--to=wolfgang.reissnegger@xilinx.com \
--cc=linuxppc-embedded@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox