From: greenlean <jmgomez@atc.ugr.es>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Linux 2.6 from git.xilinx and XUPV2P
Date: Wed, 12 Dec 2007 09:05:27 -0800 (PST) [thread overview]
Message-ID: <14299307.post@talk.nabble.com> (raw)
In-Reply-To: <14274035.post@talk.nabble.com>
greenlean wrote:
>
> Thanks both for the response, I've allready visited some of the links.
>
> Yes, you was right it's easear than I think, my problem was the .config
> file. Now, I have generated it from ml300_defconfig and after some changes
> it compiles, but I've two question:
>
> * I've chosen as platform the XUPV2P in Machine Type, instead of ML300,
> so the xparameters file that I'm using is the xparameters_xupv2p.h, but
> the xparameters file generated by the EDK is xparameters_ml300 despite I
> told it to use XUPV2P, so I can't overwrite it...
>
> Should I use the xparameters_ml300 generated by EDK or the
> xparameters_xupv2p included in the git kernel tree?. I can't compile with
> the edk's xparameters_ml300 file because there's some definition that the
> compiler can't find, so I'm using the xparameters_xupv2p.
>
> * Second, if I compile using the xparameters_xupv2p, when I do the dow
> command to download the image to the board, the xmd shell tell me:
>
> XMD% dow zImage.elf
> Failed to download ELF file
>
> ERROR(1053): UNABLE to Read Elf File. The Elf File Maybe Corrupted
> : zImage.elf
> Maybe this error is due to the above asumption??. I'll post this second
> one on xilinx-support maybe it's realted with my system.....
>
>
>
--
View this message in context: http://www.nabble.com/Linux-2.6-from-git.xilinx-and-XUPV2P-tp14274035p14299307.html
Sent from the linuxppc-embedded mailing list archive at Nabble.com.
next prev parent reply other threads:[~2007-12-12 17:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 13:32 Linux 2.6 from git.xilinx and XUPV2P greenlean
2007-12-11 15:34 ` Grant Likely
2007-12-11 17:54 ` Stephen Neuendorffer
2007-12-12 17:05 ` greenlean [this message]
2007-12-12 17:19 ` Stephen Neuendorffer
2007-12-13 9:15 ` greenlean
2007-12-13 11:09 ` greenlean
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=14299307.post@talk.nabble.com \
--to=jmgomez@atc.ugr.es \
--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).