From: Fabio Estevam <fabioestevam@yahoo.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2 1/9] mkimage: Add Freescale imx Boot Image support (imximage)
Date: Wed, 13 Jan 2010 09:08:59 -0800 (PST) [thread overview]
Message-ID: <4828.39397.qm@web51002.mail.re2.yahoo.com> (raw)
In-Reply-To: <1263376259-29764-2-git-send-email-sbabic@denx.de>
Hi Stefano,
--- On Wed, 1/13/10, Stefano Babic <sbabic@denx.de> wrote:
> From: Stefano Babic <sbabic@denx.de>
> Subject: [U-Boot] [PATCH V2 1/9] mkimage: Add Freescale imx Boot Image support (imximage)
> To: u-boot at lists.denx.de
> Date: Wednesday, January 13, 2010, 7:50 AM
> This patch adds support for
> "imximage" (MX Boot Image)
> to the mkimage utility. The imximage is used on the
> Freescales's
> MX.51 processors.
I like the way you handle the internal boot on the MX51. Very smart approach ;-)
MX25 and MX35 can also benefit from the imximage utility that you proposed, so please change the description to make it more generic, such as:
"The imximage can be used on MX25, MX35 and MX51 processors for handling internal boot mode."
....
> +---------------------------------------------
> +Imximage Boot Image generation using mkimage
> +---------------------------------------------
> +
> +This document describes how to set up a U-Boot image
> +that can be booted by the Freescale i.MX51 processor.
You could write: "... that can be booted by Freescale MX25, MX35 and MX51 processors via internal boot mode"
...
> +#define MAX_HW_CFG_SIZE 60??? /* Max number
> of registers imx.51 can set */
MX25, MX35, MX51 can set
...
> +??? /* Init Freescale imx.51 Boot image
> generation/list support */
MX25, MX35 and MX51 Boot image ...
Regards,
Fabio Estevam
next prev parent reply other threads:[~2010-01-13 17:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 9:50 [U-Boot] MX51 Support V2 Stefano Babic
2010-01-13 9:50 ` [U-Boot] [PATCH V2 1/9] mkimage: Add Freescale imx Boot Image support (imximage) Stefano Babic
2010-01-13 9:50 ` [U-Boot] [PATCH V2 2/9] MX51: Add initial support for the Freescale MX51 Stefano Babic
2010-01-13 9:50 ` [U-Boot] [PATCH V2 3/9] MX51: Add register definitions Stefano Babic
2010-01-13 9:50 ` [U-Boot] [PATCH V2 4/9] MX51: Add pin and multiplexer definitions Stefano Babic
2010-01-13 9:50 ` [U-Boot] [PATCH V2 5/9] serial_mxc: add support for MX51 processor Stefano Babic
2010-01-13 9:50 ` [U-Boot] [PATCH V2 6/9] fec_mxc: " Stefano Babic
2010-01-13 9:50 ` [U-Boot] [PATCH V2 7/9] fsl_esdhc: add support for mx51 processor Stefano Babic
2010-01-13 9:50 ` [U-Boot] [PATCH V2 8/9] mmc: check correctness of the voltage mask in ocr Stefano Babic
2010-01-13 9:50 ` [U-Boot] [PATCH V2 9/9] Add initial support for Freescale mx51evk board Stefano Babic
2010-01-19 8:26 ` [U-Boot] [PATCH V2 7/9] fsl_esdhc: add support for mx51 processor Andy Fleming
2010-01-20 9:33 ` Stefano Babic
2010-01-13 17:08 ` Fabio Estevam [this message]
2010-01-14 8:51 ` [U-Boot] [PATCH V2 1/9] mkimage: Add Freescale imx Boot Image support (imximage) Stefano Babic
2010-01-15 0:56 ` Fabio Estevam
2010-01-15 8:40 ` stefano at babic.homelinux.org
2010-01-15 12:19 ` Fabio Estevam
2010-01-15 15:01 ` Stefano Babic
2010-01-15 15:39 ` Wolfgang Denk
2010-01-18 6:27 ` Stefano Babic
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=4828.39397.qm@web51002.mail.re2.yahoo.com \
--to=fabioestevam@yahoo.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