From: Ilya Yanok <yanok@emcraft.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V4 2/2] mcx: support for HTKW mcx board
Date: Tue, 13 Dec 2011 22:57:32 +0400 [thread overview]
Message-ID: <4EE7A01C.7070508@emcraft.com> (raw)
In-Reply-To: <CA+M6bXmG8DGuWz2mLYQXXHDrfc_eP2Vqb+cVj1WNcv9hcXccTg@mail.gmail.com>
Hi Tom,
On 13.12.2011 22:52, Tom Rini wrote:
> On Mon, Dec 12, 2011 at 4:15 PM, Ilya Yanok <yanok@emcraft.com> wrote:
>> This patch adds support for the HTKW mcx AM3517-based board.
>> Serial, Ethernet, NAND, MMC, RTC, EHCI USB host and both
>> NAND and MMC SPLs are supported.
>>
>> Requires updated mach-types file.
>
> Just define the MACH_ID locally for now so it builds still please.
Ok, will do.
> Also, some problems:
>
>> +#if defined(CONFIG_OMAP_HSMMC) && !defined(CONFIG_SPL_BUILD)
>> +int board_mmc_init(bd_t *bis)
>> +{
>> + omap_mmc_init(0);
>> + return 0;
>> +}
>> +#endif
>
> That should just be return omap_mmc_init(0);
Surely. I've been told about this one already but forgot to fix it. Sorry.
> [snip to config file]
>> +#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?
Hm. What corruption problem?
>> +#define CONFIG_SYS_NAND_U_BOOT_SIZE 0x60000
>
> IIRC you don't need this define since this SPL says you write
> u-boot.img to NAND not u-boot.bin
Right.
Regards, Ilya.
next prev parent reply other threads:[~2011-12-13 18:57 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 23:15 [U-Boot] [PATCH V4 0/2] Support for HTKW mcx board Ilya Yanok
2011-12-12 23:15 ` [U-Boot] [PATCH V4 1/2] ehci-omap: driver for EHCI host on OMAP3 Ilya Yanok
2011-12-19 23:17 ` Ilya Yanok
2011-12-22 6:55 ` Govindraj
2011-12-22 8:14 ` Igor Grinberg
2011-12-22 9:26 ` Govindraj
2011-12-22 9:59 ` Igor Grinberg
2011-12-22 10:49 ` Govindraj
2011-12-22 11:18 ` Igor Grinberg
2011-12-22 11:42 ` Govindraj
2011-12-22 13:24 ` Ilya Yanok
2012-01-15 20:40 ` Remy Bohmer
2012-01-15 22:04 ` Tom Rini
2012-01-16 7:58 ` Govindraj
2012-01-16 9:57 ` Stefano Babic
2012-01-17 6:14 ` Govindraj
2012-01-25 10:32 ` Stefano Babic
2012-01-25 20:49 ` Tom Rini
2012-01-27 9:07 ` Govindraj
2012-01-27 9:12 ` Stefano Babic
2011-12-12 23:15 ` [U-Boot] [PATCH V4 2/2] mcx: support for HTKW mcx board Ilya Yanok
2011-12-13 18:52 ` Tom Rini
2011-12-13 18:57 ` Ilya Yanok [this message]
2011-12-13 19:13 ` Ilya Yanok
2011-12-13 19:30 ` Tom Rini
2011-12-13 19:44 ` Ilya Yanok
2011-12-13 21:47 ` Tom Rini
2011-12-14 0:06 ` Ilya Yanok
2011-12-14 2:48 ` Tom Rini
2011-12-14 16:09 ` Ilya Yanok
2011-12-13 23:54 ` [U-Boot] [PATCH V5 " Ilya Yanok
2011-12-14 16:05 ` [U-Boot] [PATCH V6 " Ilya Yanok
2011-12-19 22:55 ` Ilya Yanok
2011-12-19 22:56 ` Tom Rini
2011-12-19 23:07 ` Ilya Yanok
2011-12-19 23:12 ` Anatolij Gustschin
2011-12-19 23:16 ` Ilya Yanok
2012-02-05 14:57 ` [U-Boot] [PATCH V7] " Stefano Babic
2012-02-06 12:42 ` Igor Grinberg
2012-02-08 9:30 ` [U-Boot] [PATCH V8] " Stefano Babic
2012-02-08 10:07 ` Igor Grinberg
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=4EE7A01C.7070508@emcraft.com \
--to=yanok@emcraft.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