From: Mirco Fuchs <mircofuchs@web.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: Problem with bootm command
Date: Tue, 26 Jul 2005 11:28:31 +0200 [thread overview]
Message-ID: <4221395@web.de> (raw)
I have one more question about using the bootm command.
I searched the do_bootm_linux() function to find out what u-boot is doing when booting linux using the bootm command, because the kernel patch i found in the mailing list (which makes the kernel able to copy an initrd directly from flash to ram) has to be used with kernel version 2.4.18, but i have 2.6.12.
It seems as if u-boot checks for an enviroment string called "initrd_high" and if it exists, u-boot does not copy the initrd to ram -> the kernel will fail to load the ramdisk. But there is no such string in my enviroment, so shouldn't the bootm command copy initrd to it's designated sdram location? It seems as it does not because the start address of the initrd, which u-boot delivers to the linux kernel is located in flash (one can read it in the kernel booting sequence; the error is that the initrd extends physical memory, but it's quite clear why this error occures).
Is it possible to force u-boot to copy the image to ram? Of course i could use the cp.b command before using bootm (i tested this and it works fine), but thats not what i want to do.
Regards
Mirco
_________________________________________________________________________
Mit der Gruppen-SMS von WEB.DE FreeMail k?nnen Sie eine SMS an alle
Freunde gleichzeitig schicken: http://freemail.web.de/features/?mc=021179
next reply other threads:[~2005-07-26 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-26 9:28 Mirco Fuchs [this message]
2005-07-26 11:09 ` [U-Boot-Users] Re: Problem with bootm command Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2005-07-26 11:37 Mirco Fuchs
2005-07-26 12:42 ` Wolfgang Denk
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=4221395@web.de \
--to=mircofuchs@web.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.