linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Peter Ryser <Peter.Ryser@xilinx.com>
To: Patrick Huesmann <tricknology@gmx.de>
Cc: linuxppc-embedded@lists.linuxppc.org, samlinuxppc@yahoo.com.cn
Subject: Re: How to port ppc-linux to new custom boards? (virtexII)
Date: Tue, 24 Aug 2004 01:31:54 -0700	[thread overview]
Message-ID: <412AFCFA.2040006@xilinx.com> (raw)
In-Reply-To: <18802.1093328823@www32.gmx.net>


>this means that i also have to port u-boot
>
U-Boot supports the ML300 board, again, with MLD technology (i.e. an
automatic way to setup address maps and number of peripherals directly
out of the EDK project). Read the README for the ML300 board in the
u-boot documentation directory for more information.

- Peter


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2004-08-24  8:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-24  6:27 How to port ppc-linux to new custom boards? (virtexII) Patrick Huesmann
2004-08-24  7:25 ` Marc Leeman
2004-08-25  7:34   ` Marius Groeger
2004-08-25  7:57     ` Marc Leeman
2004-08-25 13:52     ` David Ho
2004-08-25 14:30       ` Peter Vandenabeele
2004-08-25 20:08         ` Handling of cascaded interrupt controllers Jeff Domogala
2004-08-26  7:02         ` How to port ppc-linux to new custom boards? (virtexII) Marc Leeman
2004-08-24  8:01 ` Oliver Fuchs
2004-08-24  8:31 ` Peter Ryser [this message]
     [not found] <31481.1093602240@www36.gmx.net>
2004-08-27 11:18 ` Patrick Huesmann
  -- strict thread matches above, loose matches on Subject: below --
2004-08-23 15:17 Patrick Huesmann
2004-08-24  1:30 ` Song Sam
2004-08-24  4:14 ` Peter Ryser
2004-08-24  8:51 ` Peter 'p2' De Schrijver
2004-08-24  9:14   ` Patrick Huesmann
2004-08-24  9:42     ` Peter 'p2' De Schrijver
2004-08-24 10:01     ` Song Sam
2004-08-25  2:00   ` Song Sam

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=412AFCFA.2040006@xilinx.com \
    --to=peter.ryser@xilinx.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=samlinuxppc@yahoo.com.cn \
    --cc=tricknology@gmx.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).