From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Ramdisk Error
Date: Fri, 22 May 2015 10:37:34 +0200 [thread overview]
Message-ID: <555EEACE.9070600@gmail.com> (raw)
In-Reply-To: <555DC921.5020307@gmail.com>
Dear Gaurav Pathak,
On 05/21/2015 02:01 PM, Andreas Bie?mann wrote:
> Dear Gaurav Pathak,
> I'll verify that sama5d3xek is loading ramdisk larger than 4MiB with
> mainline U-Boot and post the results.
The latest mainline does support loading 8MiB ramdisk on a sama5d3xek
(sama5d34):
---8<---
U-Boot> version
U-Boot 2015.07-rc1-00274-g3238639 (May 22 2015 - 00:15:46)
arm-unknown-linux-uclibcgnueabi-gcc (crosstool-NG 1.20.0) 4.7.4
GNU ld (crosstool-NG 1.20.0) 2.22
U-Boot> bootz 0x22000000 0x23000000 0x21000000
Kernel image @ 0x22000000 [ 0x000000 - 0x3315c8 ]
## Loading init Ramdisk from Legacy Image at 23000000 ...
Image Name: Application Ramdisk
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 8047596 Bytes = 7.7 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 21000000
Booting using the fdt blob at 0x21000000
Loading Ramdisk to 3f2db000, end 3fa87bec ... OK
Loading Device Tree to 3f2d0000, end 3f2da78a ... OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
Booting Linux on physical CPU 0x0
Linux version 3.18.14 (andreas at andreas-pc) (gcc version 4.6.2
(OSELAS.Toolchain-2011.11.0) ) #2 Thu May 21 23:51:50 CEST 2015
...
--->8---
Andreas
next prev parent reply other threads:[~2015-05-22 8:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 10:01 [U-Boot] Ramdisk Error Gaurav Pathak
2015-05-21 12:01 ` Andreas Bießmann
2015-05-22 8:37 ` Andreas Bießmann [this message]
2015-05-22 10:12 ` Gaurav Pathak
2015-05-25 13:56 ` Gaurav Pathak
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=555EEACE.9070600@gmail.com \
--to=andreas.devel@googlemail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox