All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Ryser <peter.ryser@xilinx.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Source of xparameter_ml300.h
Date: Wed, 28 Sep 2005 02:57:18 -0700	[thread overview]
Message-ID: <433A68FE.8030907@xilinx.com> (raw)
In-Reply-To: <430C7C3A.4000601@ru.mvista.com>

Please have a look at XAPP765 
(http://direct.xilinx.com/bvdocs/appnotes/xapp765.pdf) and the EDK 
documentation to see how this works. The latest MLD to create a BSP for 
a linuxppc-2.4 kernel is linuxppc_mvl31_v1_01_a. linuxppc_mvl31_v1_00_a 
works too but everything else is not up-to-date.

The documentation and tutorials for the ML310 board are also an 
excellent source of information how to get a Linux kernel up and running 
on Virtex-II Pro (see http://www.xilinx.com/ml310).

The reference design for the ML403 is yet another source of information 
(http://www.xilinx.com/ml403). Have a look at the reference design users 
guide.

Using the MLD (tcl script) is much less error-prone than any other 
method that involves changing the files by hand. It's a little bit of a 
learning curve but once mastered it just works.

- Peter



Andrei Konovalov wrote:

> 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
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
>

  parent reply	other threads:[~2005-09-28 10:38 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
2005-08-24 15:12   ` Grant Likely
2005-09-28  9:57   ` Peter Ryser [this message]
     [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=433A68FE.8030907@xilinx.com \
    --to=peter.ryser@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 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.