public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@sunsite.dk>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] am335x_evm: Update, document Falcon Mode support
Date: Wed, 03 Jul 2013 23:28:36 +0200	[thread overview]
Message-ID: <87ip0rpc3f.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1372882163-9299-3-git-send-email-trini@ti.com> (Tom Rini's message of "Wed, 3 Jul 2013 16:09:23 -0400")

>>>>> "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?


 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


 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?

 Tom> +# Ensure are able to talk with this mmc device, erase most previous contents

Ensure we are


-- 
Bye, Peter Korsgaard

  reply	other threads:[~2013-07-03 21:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-03 20:09 [U-Boot] [PATCH 0/2] Update Falcon Mode docs Tom Rini
2013-07-03 20:09 ` [U-Boot] [PATCH 1/2] README.falcon: Note how we determine if we can boot the OS or not Tom Rini
2013-07-03 21:19   ` Peter Korsgaard
2013-07-03 20:09 ` [U-Boot] [PATCH 2/2] am335x_evm: Update, document Falcon Mode support Tom Rini
2013-07-03 21:28   ` Peter Korsgaard [this message]
2013-07-03 22:30     ` Tom Rini
2013-07-04  7:39       ` Romain Izard
2013-07-05 12:51         ` Tom Rini

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=87ip0rpc3f.fsf@dell.be.48ers.dk \
    --to=jacmet@sunsite.dk \
    --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