From: "David H. Lynch Jr" <dhlii@comcast.net>
To: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: "Now booting the kernel"
Date: Thu, 17 Nov 2005 14:43:33 -0500 [thread overview]
Message-ID: <437CDD65.7020709@comcast.net> (raw)
In-Reply-To: <437C4E07.8020307@comcast.net>
David H. Lynch Jr. wrote:
> I am having similar difficulties on a Xilinx Virtex 4.
>
> I have some advantages over Nitesh in that I have a 32bit port at
> 0x70000000 that I can write values to and see what they are (at least
> until the MMU is enabled)
> and with some additional complexity use as a sort of UART to write
> text.
> Thus far this is what I get:
>
> Starting MonitorX.elf: V3.3.2.0.
> Loading zImage.elf.
Sorry, this is Linux 2.6.14 on a Xilinx-VI
next prev parent reply other threads:[~2005-11-17 19:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-10 8:46 "Now booting the kernel" Nathael PAJANI
2005-11-17 9:31 ` David H. Lynch Jr.
2005-11-17 19:43 ` David H. Lynch Jr [this message]
[not found] <20051111010005.016A868717@ozlabs.org>
2005-11-11 12:51 ` drizzt
-- strict thread matches above, loose matches on Subject: below --
2005-11-10 18:26 Nitesh Guinde
2005-11-10 10:40 Nathael PAJANI
2005-11-10 4:57 Nitesh Guinde
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=437CDD65.7020709@comcast.net \
--to=dhlii@comcast.net \
--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).