From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, U-boot, v2, 3/3] k2hk_evm: add script to automate NAND flash process
Date: Fri, 25 Jul 2014 21:25:56 -0400 [thread overview]
Message-ID: <20140726012556.GY1847@bill-the-cat> (raw)
In-Reply-To: <1404475407-4486-4-git-send-email-ivan.khoronzhuk@ti.com>
On Fri, Jul 04, 2014 at 03:03:27PM +0300, Khoronzhuk, Ivan wrote:
> Add script to automate NAND flash process. As for now the board has
> two burn scripts - burn to boot from SPI NOR flash and burn to boot
> from AEMIF NAND flash, rename burn_uboot script to burn_uboot_spi.
> Also update README to contain NAND burn U-boot process description.
>
> Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
> Acked-by: Murali Karicheri <m-karicheri2@ti.com>
Applied to u-boot-ti/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140725/2d39dd54/attachment.pgp>
prev parent reply other threads:[~2014-07-26 1:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 12:03 [U-Boot] [U-boot] [Patch v2 0/3] Add support for NAND U-boot image upgrade Ivan Khoronzhuk
2014-07-04 12:03 ` [U-Boot] [U-boot] [Patch v2 1/3] mtd: nand: davinci: add opportunity to write keystone U-boot image Ivan Khoronzhuk
2014-07-26 1:25 ` [U-Boot] [U-Boot, U-boot, v2, " Tom Rini
2014-07-04 12:03 ` [U-Boot] [U-boot] [Patch v2 2/3] keystone: add support for NAND gpheader image Ivan Khoronzhuk
2014-07-26 1:25 ` [U-Boot] [U-Boot, U-boot, v2, " Tom Rini
2014-07-04 12:03 ` [U-Boot] [U-boot] [Patch v2 3/3] k2hk_evm: add script to automate NAND flash process Ivan Khoronzhuk
2014-07-07 16:01 ` Murali Karicheri
2014-07-26 1:25 ` Tom Rini [this message]
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=20140726012556.GY1847@bill-the-cat \
--to=trini@ti.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