All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Smith <rsmith@imagemap.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Problems loading ramdisk
Date: Mon, 12 Jun 2006 09:01:09 -0400	[thread overview]
Message-ID: <448D6595.9000804@imagemap.com> (raw)
In-Reply-To: <20060611043643.794.qmail@web37104.mail.mud.yahoo.com>

Hello Michael,

See my comments below...

Michael Sprauve wrote:
> Hi,
> So just make sure I understand your response
> 1)The 50180000 address that I pass to the bootloader
> is the location of where I stored my ramdisk image in
> flash
>   
Correct.
> 2)When I create the ramdisk.bin using mkimage, the
> load address I used (using the -a option) is pass to
> the kernel using the ATAG method along the size of the
> ramdisk
>   
I'm not familiar with the load address option since I've never had to 
use it. Perhaps Wolfgang or others will elaborate.
> 3)Because of that, I won't need to use the "initrd"
> parameter in my bootargs
>   
Correct. Though not so sure about the reasoning behind the 
conclusion...see below.
> If I understand all of that is correct, then I must be
> missing something else, since after setting my
> bootargs to "console=ttyS0,115200 root=/dev/ram0
> mem=16M" I still the same error, where it seems the
> kernel can't find the ramdisk location
>   
Try using just "console=ttyS0, 115200" without the root= stuff. It is my 
understanding that when you use bootm addr1 addr2, that u-boot will pass 
whatever information the kernel needs to find its root device 
automatically (ATAGS?).

-Randy Smith
Software Engineer,
ImageMap, Inc.

      reply	other threads:[~2006-06-12 13:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-09 22:15 [U-Boot-Users] Problems loading ramdisk Michael Sprauve
2006-06-09 22:51 ` Wolfgang Denk
2006-06-11  4:36   ` Michael Sprauve
2006-06-12 13:01     ` Randy Smith [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=448D6595.9000804@imagemap.com \
    --to=rsmith@imagemap.com \
    --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.