From: Andrei Konovalov <akonovalov@ru.mvista.com>
To: Grant Likely <glikely@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Source of xparameter_ml300.h
Date: Wed, 24 Aug 2005 17:55:06 +0400 [thread overview]
Message-ID: <430C7C3A.4000601@ru.mvista.com> (raw)
In-Reply-To: <20050823170300.GA910@siegfried.thelikelysolution.ca>
Grant Likely wrote:
> Does anyone know the origin of xparameter_ml300.h? The
> Xilinx EDK generates an xparameters.h file for each design, but the
> structure of the file changes between releases.
>
> I want to know if xparameters_ml300.h is the exact output produced by
> EDK or if stuff was changed before it was submitted to the mainline
> tree. (ie. all the stuff under the "linux redefines" comment block)
EDK can also generate the "Linux BSP".
In this case EDK uses the scripts from (depending on your setup)
/opt/xilinx/edk/7.1/sw/ThirdParty/bsp/linux_v2_00_b/data/
In particular, linux_v2_1_0.tcl adds those "linux redefines"
and renames xparameters.h to xparameters_ml300.h.
> Also, where can I get the bitstream/systemace file that matches
> xparameters_ml300.h?
The most reliable way is to generate both (bitstream and
xparameters_ml300.h) by yourself. :)
But if you are speaking about the xparameters_ml300.h in the community
trees (linuxppc-2.4 and the 2.6 one from kernel.org), this file
is for the reference design by Xilinx:
http://www.xilinx.com/ise/embedded/edk6_2docs/ml300_edk3.zip
> I've got a custom ml300 image that I'm regression
> testing against, but I'd like to also test against some form of 'stock'
> image. :)
>
> Thanks,
> g.
Thanks,
Andrei
next prev parent reply other threads:[~2005-08-24 13:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-23 17:03 Source of xparameter_ml300.h Grant Likely
2005-08-24 13:55 ` Andrei Konovalov [this message]
2005-08-24 15:12 ` Grant Likely
2005-09-28 9:57 ` Peter Ryser
[not found] <20050824134404.B1DF668108@ozlabs.org>
2005-08-25 1:20 ` T Ziomek
2005-08-25 6:24 ` Grant Likely
2005-08-25 22:17 ` T Ziomek
2005-08-25 23:02 ` Grant Likely
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=430C7C3A.4000601@ru.mvista.com \
--to=akonovalov@ru.mvista.com \
--cc=glikely@gmail.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 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.