From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ilya Yanok <yanok@emcraft.com>
Date: Tue, 13 Dec 2011 23:13:00 +0400
Subject: [U-Boot] [PATCH V4 2/2] mcx: support for HTKW mcx board
In-Reply-To: <CA+M6bXmG8DGuWz2mLYQXXHDrfc_eP2Vqb+cVj1WNcv9hcXccTg@mail.gmail.com>
References: <1323731713-5460-1-git-send-email-yanok@emcraft.com>	<1323731713-5460-3-git-send-email-yanok@emcraft.com>
	<CA+M6bXmG8DGuWz2mLYQXXHDrfc_eP2Vqb+cVj1WNcv9hcXccTg@mail.gmail.com>
Message-ID: <4EE7A3BC.2040304@emcraft.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

Hi Tom,

On 13.12.2011 22:52, Tom Rini wrote:
>> +#define CONFIG_SYS_TEXT_BASE           0x80008000
> [snip]
>> +#define CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR        0x300 /* address 0x60000 */
>> +#define CONFIG_SYS_MMC_SD_FAT_BOOT_PARTITION   1
>> +#define CONFIG_SPL_FAT_LOAD_PAYLOAD_NAME       "u-boot.img"
> 
> You're able to have CONFIG_SYS_TEXT_BASE that low and not have the
> corruption problem devkit8000 had?

No, I can't see any problems. I have to say I can't do _real_ MMC boot,
as my board lacks the required jumper, so I'm testing it but starting
SPL from NAND, rewriting omap3_boot_device to be MMC with BDI and
running it further. It reads u-boot.img from MMC and starts it without
any problem.

Regards, Ilya.