Re: [U-Boot] [PATCH v3] common/image.c: align usage of fdt_high with initrd_high

2012-02-12 Thread Stefano Babic
On 09/02/2012 20:43, Simon Glass wrote: >> All the numbers above come from the real case of Freescale i.MX6Q >> Sabrelite board: >> >> 0x2C00 (704 MB) + 0x1000 (physical base) = 0x3C00 > > OK I see, thanks. > Hi guys, thanks everybody for reviewing - I will merge now this patch int

Re: [U-Boot] [PATCH v3] common/image.c: align usage of fdt_high with initrd_high

2012-02-09 Thread Simon Glass
Hi Shawn, On Thu, Feb 9, 2012 at 10:51 AM, Shawn Guo wrote: > Hi Simon, > > Thanks for looking at the patch. > > On 9 February 2012 09:37, Simon Glass wrote: > ... >>>   fdt_high     - if set this restricts the maximum address that the >>>                  flattened device tree will be copied in

Re: [U-Boot] [PATCH v3] common/image.c: align usage of fdt_high with initrd_high

2012-02-09 Thread Shawn Guo
Hi Simon, Thanks for looking at the patch. On 9 February 2012 09:37, Simon Glass wrote: ... >>   fdt_high     - if set this restricts the maximum address that the >>                  flattened device tree will be copied into upon boot. >> +                 For example, if you have a system with

Re: [U-Boot] [PATCH v3] common/image.c: align usage of fdt_high with initrd_high

2012-02-09 Thread Simon Glass
Hi Shawn, On Mon, Jan 9, 2012 at 11:54 PM, Shawn Guo wrote: > The commit message of a28afca (Add uboot "fdt_high" enviroment variable) > states that fdt_high behaves similarly to the existing initrd_high. > But fdt_high actually has an outstanding difference from initrd_high. > The former specifi

Re: [U-Boot] [PATCH v3] common/image.c: align usage of fdt_high with initrd_high

2012-02-09 Thread Simon Glass
Hi Stefan, On Wed, Feb 8, 2012 at 3:39 AM, Stefano Babic wrote: > On 10/01/2012 08:54, Shawn Guo wrote: >> The commit message of a28afca (Add uboot "fdt_high" enviroment variable) >> states that fdt_high behaves similarly to the existing initrd_high. >> But fdt_high actually has an outstanding di

Re: [U-Boot] [PATCH v3] common/image.c: align usage of fdt_high with initrd_high

2012-02-08 Thread Stefano Babic
On 10/01/2012 08:54, Shawn Guo wrote: > The commit message of a28afca (Add uboot "fdt_high" enviroment variable) > states that fdt_high behaves similarly to the existing initrd_high. > But fdt_high actually has an outstanding difference from initrd_high. > The former specifies the start address, wh

Re: [U-Boot] [PATCH v3] common/image.c: align usage of fdt_high with initrd_high

2012-01-16 Thread Shawn Guo
Gentle ping? Regards, Shawn On Tue, Jan 10, 2012 at 03:54:08PM +0800, Shawn Guo wrote: > The commit message of a28afca (Add uboot "fdt_high" enviroment variable) > states that fdt_high behaves similarly to the existing initrd_high. > But fdt_high actually has an outstanding difference from initrd

[U-Boot] [PATCH v3] common/image.c: align usage of fdt_high with initrd_high

2012-01-09 Thread Shawn Guo
The commit message of a28afca (Add uboot "fdt_high" enviroment variable) states that fdt_high behaves similarly to the existing initrd_high. But fdt_high actually has an outstanding difference from initrd_high. The former specifies the start address, while the later specifies the end address. As f