From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] help - loading linux kernel
Date: Thu, 06 Nov 2003 00:37:13 +0100 [thread overview]
Message-ID: <20031105233718.D3253C5F59@atlas.denx.de> (raw)
In-Reply-To: Your message of "Tue, 04 Nov 2003 20:41:45 +0200." <3FA7F2E9.5080302@il.marvell.com>
Dear Ronen,
in message <3FA7F2E9.5080302@il.marvell.com> you wrote:
>
> I have a U-Boot which is working just fine,
> and I'm trying to boot a kernel(ver 2.4) image with it ,
> after I load the uImage to the DRAM by using the tftp as it is described
> in the README file, I'm doing bootm to the uImage location,
> I see that the code is getting to the kernel code , but there it get lost
> after we disable the MMU in head.S.
...in other words, you see no output on the console after passing
control to the Linux kernel.
> Are there any special changes I should make to the Kernel in order for
> it to be able to boot from the U-Boot??
> If so, where can I find a good reference for it??
Well, I think it is especially useful to read
(1) the README file which comes with U-Boot
(2) the FAQ section of the DULG at
http://www.denx.de/twiki/bin/view/DULG/Manual
Pay special attention to question "12.1.3. Linux hangs ..."
at http://www.denx.de/twiki/bin/view/DULG/LinuxHangsAfterUncompressingKernel
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de
egrep patterns are full regular expressions; it uses a fast determi-
nistic algorithm that sometimes needs exponential space.
- unix manuals
prev parent reply other threads:[~2003-11-05 23:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-04 18:41 [U-Boot-Users] help - loading linux kernel Ronen Shitrit
2003-11-05 23:37 ` Wolfgang Denk [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=20031105233718.D3253C5F59@atlas.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.