Re: [U-Boot] [PATCH] tools: fix FIT image with ramdisk

2013-07-13 Thread Albert ARIBAUD
Hi Tom, I've re-worded this as: common/image.c: Fix regression with ramdisk load/entry points in FIT A FIT image with a ramdisk that sets the entry or load points to 0x0 must be treated as meaning leave in place and NOT relocate to 0x0. This regression was introduced in a51ec63.

Re: [U-Boot] [PATCH] usb: Use well-known descriptor sizes when parsing configuration

2013-07-13 Thread Albert ARIBAUD
Hi Julius, On Fri, 12 Jul 2013 17:30:16 -0700, Julius Werner jwer...@chromium.org wrote: The existing USB configuration parsing code relies on the descriptors' own length values when reading through the configuration blob. Since the size of those descriptors is always well-defined, we should

Re: [U-Boot] [PATCH] arm:exynos:fix: Fix clock calculation for Exynos4210 based targets.

2013-07-13 Thread Minkyu Kang
Dear Tom, Please apply this patch to u-boot directly. I wish that this fix will be merged before release. On 13 July 2013 02:08, Lukasz Majewski l.majew...@samsung.com wrote: Provide proper setting for the APLL fout frequency calculation for Exynos4 based targets (especially Exynos4210 -

Re: [U-Boot] [PATCH] tools: fix FIT image with ramdisk

2013-07-13 Thread Stefano Babic
Am 12/07/2013 23:24, schrieb Tom Rini: On Fri, Jul 12, 2013 at 03:09:23PM +0200, Stefano Babic wrote: Booting a FIT image containing a ramdisk, the ramdisk is loaded at address 0x0 that causes bus errors for architectures that do not have RAM starting at address zero. Signed-off-by:

[U-Boot] [PATCH] ppc: mpc8323erdb: Fix compiler warning

2013-07-13 Thread Marek Vasut
Fix the following warning: mpc8323erdb.c: In function 'mac_read_from_eeprom': mpc8323erdb.c:198:3: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] if (crc32(crc, buf, 24) == *(unsigned int *)buf[24]) { ^ Size remains unchanged after and

Re: [U-Boot] [PATCH v2 0/6] Enhance support for BeagleBone Black

2013-07-13 Thread Stefan Agner
Hi, Am 2013-07-11 15:54, schrieb Justin Waters: Justin Waters (6): am335x_evm: Make NAND support modular am335x_evm: Add command line editing am335x_evm: Rework bootcmd to handle two MMC devs Add additional MLO images to .gitignore am335x_evm: Add support for eMMC environment

Re: [U-Boot] [PATCH] tools: fix FIT image with ramdisk

2013-07-13 Thread Wolfgang Denk
Dear Tom Rini, In message 20130712212416.GV13531@bill-the-cat you wrote: A FIT image with a ramdisk that sets the entry or load points to 0x0 must be treated as meaning leave in place and NOT relocate to 0x0. Why is this the case? 0x0 could be a valid address on some systems. If we need a

Re: [U-Boot] [PATCH] tools: fix FIT image with ramdisk

2013-07-13 Thread Tom Rini
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/13/2013 07:21 AM, Wolfgang Denk wrote: Dear Tom Rini, In message 20130712212416.GV13531@bill-the-cat you wrote: A FIT image with a ramdisk that sets the entry or load points to 0x0 must be treated as meaning leave in place and NOT

Re: [U-Boot] [PATCH] tools: fix FIT image with ramdisk

2013-07-13 Thread Stephen Warren
On 07/13/2013 05:21 AM, Wolfgang Denk wrote: Dear Tom Rini, In message 20130712212416.GV13531@bill-the-cat you wrote: A FIT image with a ramdisk that sets the entry or load points to 0x0 must be treated as meaning leave in place and NOT relocate to 0x0. Why is this the case? 0x0 could

Re: [U-Boot] [PATCH] tools: fix FIT image with ramdisk

2013-07-13 Thread Tom Rini
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/13/2013 10:26 PM, Stephen Warren wrote: On 07/13/2013 05:21 AM, Wolfgang Denk wrote: Dear Tom Rini, In message 20130712212416.GV13531@bill-the-cat you wrote: A FIT image with a ramdisk that sets the entry or load points to 0x0 must be