From: Robert Woodworth <rwoodworth@securics.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Xilinx Virtex boot
Date: Thu, 30 Aug 2007 08:50:36 -0600 [thread overview]
Message-ID: <1188485436.8717.47.camel@PisteOff> (raw)
In-Reply-To: <fa686aa40708291729j3f63a57dl32e5d4df647326b5@mail.gmail.com>
On Wed, 2007-08-29 at 18:29 -0600, Grant Likely wrote:
> On 8/29/07, Robert Woodworth <rwoodworth@securics.com> wrote:
> > I'm trying to port Linux to a new Virtex Platform. The kernel will not
> > uncompress, I get the following on the console:
> >
> > loaded at: 00400000 004FB19C
> > board data at: 004F9120 004F919C
> > relocated to: 00404054 004040D0
> > zimage at: 00404E50 004F8409
> > avail ram: 004FC000 04000000
> >
> > Linux/PPC load: console=ttyUL root=/dev/xsa2
> > Uncompressing Linux...
> > zlib_inflateInit2 returned 00506530
> > exit
> >
> > Any ideas what causes this error??
> > Is something mis-configured on my EDK project?
> >
>
> Possibly, do you know that EDK has your ram is configured correctly
> (ie. have you run a memory test application)?
>
>
> >
> > I have 64MB DDR on the OPB *not* the PLB.
> > Is that a problem??
>
> It shouldn't be the problem, but why are you doing that?
I did notice in my configuration, that when the memory is on the PLB it
has an interrupt flag and when it's on the OPB it doesn't. What is the
interrupt for? DMA's?
Could Linux be doing a DMA in the uncompression where the lack of an
interrupt causes and error?
prev parent reply other threads:[~2007-08-30 14:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 23:34 Xilinx Virtex boot Robert Woodworth
2007-08-30 0:29 ` Grant Likely
2007-08-30 14:44 ` Robert Woodworth
2007-08-30 15:02 ` Grant Likely
2007-08-30 16:07 ` Xilinx Virtex boot (And MPMC) Stephen Neuendorffer
2007-08-30 14:50 ` Robert Woodworth [this message]
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=1188485436.8717.47.camel@PisteOff \
--to=rwoodworth@securics.com \
--cc=grant.likely@secretlab.ca \
--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).