All of lore.kernel.org
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-BOOT PROBLEM] RAM loading RAMdisk addresses
Date: Mon, 31 Jan 2011 16:24:25 +0100	[thread overview]
Message-ID: <4D46D429.9020207@free.fr> (raw)
In-Reply-To: <F427B25935CD0742BA694C0B6918F5701B705D87C7@FRMRSSXCHMBSE2.dc-m.alcatel-lucent.com>

Le 31/01/2011 14:43, GRACE, ERWAN (ERWAN)** CTR ** a ?crit :
> Hello all,
>
> My name is Erwan Gr?ce, I'm French. Here's my issue : I had loaded the Flash memory of an electronic card with 2 RAMdisk which are supposed to be the same. However, when I checked the messages displayed on a screen at boot time, I observed that there were some differences between the 2 RAMdisk :
>
> Messages displayed for the 1st RAMdisk :
>
> ## Booting image at ffb00000 ...
>     Image Name:   Linux-2.6.10_mvlcge401-8560ads
>     Image Type:   PowerPC Linux Kernel Image (gzip compressed)
>     Data Size:    1662041 Bytes =  1.6 MB
>     Load Address: 00000000
>     Entry Point:  00000000
>     Verifying Checksum ... OK
>     Uncompressing Kernel Image ... OK
> ## Loading RAMDisk Image at fc100000 ...
>     Image Name:   tcifl.ramdisk
>     Image Type:   PowerPC Linux RAMDisk Image (gzip compressed)
>     Data Size:    42466734 Bytes = 40.5 MB
>     Load Address: 00000000
>     Entry Point:  00000000
>     Verifying Checksum ... OK
>     Loading Ramdisk to 15780000, end 17fffdae ... OK
>
> Messages displayed for the 2nd RAMdisk :
>
> ## Booting image at ffb00000 ...
>     Image Name:   Linux-2.6.10_mvlcge401-8560ads
>     Image Type:   PowerPC Linux Kernel Image (gzip compressed)
>     Data Size:    1662041 Bytes =  1.6 MB
>     Load Address: 00000000
>     Entry Point:  00000000
>     Verifying Checksum ... OK
>     Uncompressing Kernel Image ... OK
> ## Loading RAMDisk Image at fc100000 ...
>     Image Name:   tcifl.ramdisk
>     Image Type:   PowerPC Linux RAMDisk Image (gzip compressed)
>     Data Size:    42451540 Bytes = 40.5 MB
>     Load Address: 00000000
>     Entry Point:  00000000
>     Verifying Checksum ... OK
>     Loading Ramdisk to 15783000, end 17fff254 ... OK
>
> As you can notice, the 2 RAMdisk seem to be different but I don't
> know  why. I just observe that they have different size and they are
> not loaded at the same address in RAM memory. I precise that I didn't
> build this RAMdisk. Can someone help me to understand what is the root
> cause of these differences, please ? Thank you very much for your help.

Hi Erwan,

I'm afraid this is absolutely not related to U-Boot. I can just offer 
the remark that iminfo shows your ramdisks differ in their rootfs part.

If you have any additional question, feel free to e-mail me -- in 
private, to avoid noise on the U-Boot list.

> Best regards,
>
> Erwan Gr?ce

Amicalement,
-- 
Albert.

  reply	other threads:[~2011-01-31 15:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-31 13:43 [U-Boot] [U-BOOT PROBLEM] RAM loading RAMdisk addresses GRACE, ERWAN ** CTR **
2011-01-31 15:24 ` Albert ARIBAUD [this message]
2011-01-31 19:21 ` Wolfgang Denk
     [not found]   ` <F427B25935CD0742BA694C0B6918F5701B70632924@FRMRSSXCHMBSE2.dc-m.alcatel-lucent.com>
2011-02-01 10:43     ` 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=4D46D429.9020207@free.fr \
    --to=albert.aribaud@free.fr \
    --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.