From: "David Baird" <dhbaird@gmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: TLB Miss booting linux kernel on ppc 405
Date: Thu, 21 Feb 2008 11:00:41 -0700 [thread overview]
Message-ID: <440abda90802211000v64e4a952n63f17808d2b46159@mail.gmail.com> (raw)
In-Reply-To: <5ee408090802210950t498b9752meab2b91d2a13191c@mail.gmail.com>
On Thu, Feb 21, 2008 at 10:50 AM, Ricardo Ayres Severo
<severo.ricardo@gmail.com> wrote:
> I rebuilt the design in EDK 9.2i and problem persisted. The only
> difference is the registers are not zeroing anymore. No exception is
> thrown, and the system still hangs at memset_io. I'm running out of
> options.
> It is possible to boot Linux on Virtex-II, isn't?
Yes, it is possible. I have a Virtex-II Pro with Linux running on it
although I didn't configure it myself (it is one of those Black Dog
computers). I work with Virtex-4s right now.
Can you try a reference design for the Virtex-II perhaps?
Can you comment out memset_io and write your own version of it (which
you can insert debug statements into)?
When/where in memset are things breaking? What is the nature of the
breaking? Can you get your serial terminal to print out hex values
(for memory locations, memory values, etc.)?
next prev parent reply other threads:[~2008-02-21 18:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 16:50 TLB Miss booting linux kernel on ppc 405 Ricardo Ayres Severo
2008-02-13 17:17 ` David Baird
2008-02-13 17:38 ` Ricardo Ayres Severo
2008-02-13 17:51 ` David Baird
2008-02-13 18:03 ` Ricardo Ayres Severo
2008-02-13 18:32 ` David Baird
2008-02-13 18:49 ` Ricardo Ayres Severo
2008-02-13 19:02 ` David Baird
2008-02-20 21:24 ` Robert Woodworth
2008-02-20 21:29 ` Ricardo Ayres Severo
2008-02-20 21:47 ` David Baird
2008-02-21 17:50 ` Ricardo Ayres Severo
2008-02-21 18:00 ` David Baird [this message]
2008-02-21 18:04 ` David Baird
2008-02-21 19:12 ` Robert Woodworth
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=440abda90802211000v64e4a952n63f17808d2b46159@mail.gmail.com \
--to=dhbaird@gmail.com \
--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).