linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Joachim Meyer" <Jogi95@web.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Linux for ml310
Date: Wed, 9 Jan 2008 11:07:31 -0700	[thread overview]
Message-ID: <fa686aa40801091007h4bc65804h9a7b562a49478deb@mail.gmail.com> (raw)
In-Reply-To: <524275432@web.de>

On 1/9/08, Joachim Meyer <Jogi95@web.de> wrote:
> Hi again
>
> In which xparams* files should i look for the right definition?
> In the xparameters.h from the BSP I can't find it, it looks like this:
> -------------------------------------------------------------------
> /*
>  * include/asm-ppc/xparameters.h
>  *
>  * This file includes the correct xparameters.h for the CONFIG'ed board
>  *
>  * Author: MontaVista Software, Inc.
>  *         source@mvista.com
>  *
>  * 2004 (c) MontaVista Software, Inc.  This file is licensed under the terms
>  * of the GNU General Public License version 2.  This program is licensed
>  * "as is" without any warranty of any kind, whether express or implied.
>  */
>
> #include <linux/config.h>
>
> #if defined(CONFIG_XILINX_ML300)
> #include <platforms/4xx/xparameters/xparameters_ml300.h>

<--- Add fixups here.

> #endif
> #if defined(CONFIG_XILINX_ML40x)
> #include <platforms/4xx/xparameters/xparameters_ml40x.h>
> #endif

The fixups should look like this:

#define XPAR_UARTNS550_0_CLOCK_FREQ_HZ \
                XPAR_<real-name-from-xparams-ml300>_FREQ_HZ
#define XPAR_INTC_0_UARTNS550_0_VEC_ID \
                XPAR_<real-name-from-xparams-ml300>_VEC_ID
#define XPAR_UARTNS550_0_BASEADDR \
                XPAR_<real-name-from-xparams-ml300>_BASEADDR

Note: when you generate the EDK bsp, *make sure* you generated it for
the "linux 2.6" target; not "standalone".  If you don't then
xparams_ml300 will be missing stuff.

  reply	other threads:[~2008-01-09 18:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-09 17:29 Linux for ml310 Joachim Meyer
2008-01-09 18:07 ` Grant Likely [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-01-11 11:40 Enno Lübbers
2008-01-10 15:44 Joachim Meyer
2008-01-10 15:48 ` Grant Likely
2008-01-10 10:13 Joachim Meyer
2008-01-10 14:54 ` Grant Likely
2008-01-09 19:00 Joachim Meyer
2008-01-09 19:16 ` Grant Likely
     [not found] <524178230@web.de>
2008-01-09 16:48 ` Grant Likely
2008-01-09 15:19 Joachim Meyer
2008-01-09 15:24 ` Grant Likely
2008-01-07 20:41 Joachim Meyer
2008-01-07 21:02 ` Grant Likely
2008-01-09 21:29 ` Joachim Meyer
2008-01-09 22:10   ` Grant Likely
2008-01-14 18:42     ` greenlean
2008-01-14 18:47       ` Stephen Neuendorffer

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=fa686aa40801091007h4bc65804h9a7b562a49478deb@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=Jogi95@web.de \
    --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;
as well as URLs for NNTP newsgroup(s).