On Wed, Jul 03, 2013 at 11:28:36PM +0200, Peter Korsgaard wrote:
"Tom" == Tom Rini trini@ti.com writes:
Tom> - Update Falcon Mode support so that the offsets used in eMMC (or a raw Tom> SD card) would allow for enough room for a device tree to be used Tom> rather than an ATAGS blob as well as environment to be saved in eMMC. Tom> - Add board/ti/am335x/README which covers a few basic items, and Tom> provides an example of Falcon Mode for eMMC, FAT SD card and NAND. Tom> - Round up the size of u-boot.img.raw to match these use-cases, and add Tom> the entries for Falcon Mode to DFU for eMMC, FAT SD cards and NAND Tom> - Correct CONFIG_CMD_SPL_WRITE_SIZE size (eraseblocks are 128KiB)
It looks to me like this should be 4 (or 3) seperate commits then?
I suppose we can go that way, I'll split things up Monday.
Tom> Signed-off-by: Tom Rini trini@ti.com Tom> --- Tom> board/ti/am335x/README | 123 ++++++++++++++++++++++++++++++++++++++++++ Tom> include/configs/am335x_evm.h | 19 ++++--- Tom> 2 files changed, 135 insertions(+), 7 deletions(-) Tom> create mode 100644 board/ti/am335x/README
Tom> diff --git a/board/ti/am335x/README b/board/ti/am335x/README Tom> new file mode 100644 Tom> index 0000000..565f18c Tom> --- /dev/null Tom> +++ b/board/ti/am335x/README Tom> @@ -0,0 +1,123 @@ Tom> +Summary Tom> +======= Tom> + Tom> +This document covers various features of the 'am335x_evm' build, and some of Tom> +the related build targets (am335x_evm_uartN, etc). Tom> + Tom> +Hardware Tom> +======== Tom> + Tom> +The binary produced by this board supports, based on parsing of the EEPROM Tom> +doumentd in TI's reference designs:
documented
Tom> +Note that when we run 'spl export' it will prepare to boot the kernel. Tom> +This includes relocation of the uImage from where we loaded it to the entry Tom> +point defined in the head. As these locations overlap by default, it would
header
Whoops.
Tom> +A further word of warning about using eMMC and partition tables. When Tom> +working with SD cards we can get away with erasing small areas at a time, Tom> +however on eMMC we must keep erases aligned to eraseblocks and thus the Tom> +first erase we issue will erase the partition table.
Really? I thought eMMC behaved just like SD cards?
Yes, really. We know what the erase block size is, and round our commands, probably because we really have to. SD cards take care of things for us, for better or worse.
Tom> +# Ensure are able to talk with this mmc device, erase most previous contents
Ensure we are
Also fixed.