From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?UTF-8?B?QW5kcmVhcyBCaWXDn21hbm4=?= <andreas.devel@googlemail.com>
Date: Fri, 22 May 2015 10:37:34 +0200
Subject: [U-Boot] Ramdisk Error
In-Reply-To: <555DC921.5020307@gmail.com>
References: <CAMvYpdmkPF+gkMvmjUbpgYKqWw--Ms+ZNoeZeZ1MF1P1wWERKQ@mail.gmail.com>
 <555DC921.5020307@gmail.com>
Message-ID: <555EEACE.9070600@gmail.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

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