From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Stephen Neuendorffer" <stephen.neuendorffer@xilinx.com>
Cc: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: Xilinx PowerPC
Date: Thu, 21 Feb 2008 12:02:21 -0700 [thread overview]
Message-ID: <fa686aa40802211102i7f636447hfca0f8e1673042a5@mail.gmail.com> (raw)
In-Reply-To: <20080221175025.7817BBD8057@mail91-sin.bigfish.com>
On Thu, Feb 21, 2008 at 10:50 AM, Stephen Neuendorffer
<stephen.neuendorffer@xilinx.com> wrote:
> > Step 2).
> > the code in arch/powerpc/???? is the devicetree equvalent
> to
> > arch/ppc/platforms/4xx/xilinx_ml410.c
> http://git.xilinx.com/linux-2.6-xlnx.git contains a preliminary stab at
> the bootcode for Virtex. I've been using this for a while with
> ARCH=powerpc. There isn't really much need for board specific platform
> code: This should (I think) be handled by the device tree. All of this
> is still pretty preliminary at the moment however. The big problem with
> the boot code in the Xilinx tree is that you need to be able to allocate
> memory in order to parse the device tree in order to figure out how much
> memory you have. I just haven't rewritten the code to use libfdt, which
> can query the device tree without memory allocation yet. Grant has a
> slightly different scheme in his tree, but it works as well. Generally
> I've been more focused on avoiding u-boot, whereas Grant has been using
> u-boot exclusively, I think.
Actually, I'm not using u-boot at all. I've reworked the 'raw' image
target to use libfdt and properly initialize the cache and stuff.
I'll be merging it in the .26 merge window.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2008-02-21 19:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 6:58 Xilinx PowerPC David H. Lynch Jr.
2008-02-21 17:50 ` Stephen Neuendorffer
2008-02-21 19:02 ` Grant Likely [this message]
2008-02-22 17:23 ` Alan Casey
2008-02-22 18:11 ` Stephen Neuendorffer
2008-02-22 18:58 ` Alan Casey
2008-02-22 19:07 ` Stephen Neuendorffer
[not found] ` <47BF43CF.5050102@dlasys.lcl>
2008-02-22 22:05 ` Stephen Neuendorffer
2008-03-02 18:25 ` Michal Simek
2008-03-03 19:53 ` Stephen Neuendorffer
[not found] <480BA36D.1080000@dlasys.net>
[not found] ` <fa686aa40804201314m27caf4fau72956df9dd5d350d@mail.gmail.com>
[not found] ` <480BA821.2030109@dlasys.net>
[not found] ` <fa686aa40804201548o503e9b19p4081cec653a1acd2@mail.gmail.com>
2008-04-20 23:48 ` David H. Lynch Jr.
2008-04-22 22:15 ` Koss, Mike (Mission Systems)
2008-04-23 21:37 ` David H. Lynch Jr.
2008-04-23 0:04 ` Yoshio Kashiwagi
2008-04-23 21:43 ` David H. Lynch Jr.
2008-05-17 15:36 ` David H. Lynch Jr.
2008-05-18 2:13 ` Yoshio Kashiwagi
2008-05-19 3:27 ` David H. Lynch Jr.
2008-05-19 4:09 ` Grant Likely
2008-05-19 4:18 ` Yoshio Kashiwagi
2008-05-19 4:59 ` 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=fa686aa40802211102i7f636447hfca0f8e1673042a5@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-embedded@ozlabs.org \
--cc=stephen.neuendorffer@xilinx.com \
/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).