public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/3] imximage: Add MX53 boot image support
Date: Tue, 28 Dec 2010 09:23:08 +0100	[thread overview]
Message-ID: <4D199E6C.7020700@denx.de> (raw)
In-Reply-To: <AANLkTi=eP2+kc+Gfh68kSK_nBUC2UNZk4reQ4s6WuBLw@mail.gmail.com>

On 12/28/2010 09:08 AM, Jason Liu wrote:
>>> +#ifdef CONFIG_MX51
>>
>> NAK. This is wrong: mkimage is a tool running on host and must be
>> possible to include it in a distro. It must be able (as it now does) to
>> produce the correct image at runtime. For this reason there are no
>> #ifdef in the actual code. If a different behavior is required, this
>> must be added extending the syntax of the imximage.cfg file, for example
>> adding a processor type (or a version number, or whatever is needed).
> 
> Sorry, I don't notice that. If that, I have to add extending syntax to
> support mx53 since
> mx53 is different with mx51 for ROM boot structure.
> 
> I would like to add one process type into the imximage.cfg file, what
> do you think of that?
> Any suggestions? Thanks,

You have sure in Freescale a better visibility how to group together
this feature. Is the newer header typical for the MX53 or are there
other processors using the same structure ? John has already pointed out
that the MX28 is very similar, and, after reading the manual, it seems
to me it has the same header as the MX53. Can we distinguish with a
header version ?

As I can see, the actual header is used at least by the MX35, not only
by the MX51. So I would prefer a way to group together processors with
the same header structure else to define a processor type.

Best regards,
Stefano Babic

-- 
=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

  reply	other threads:[~2010-12-28  8:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-22 13:23 [U-Boot] [PATCH 1/3] mxc_gpio: add support for MX53 processor Jason Liu
2010-12-22 13:23 ` [U-Boot] [PATCH 2/3] fsl_pmic: add I2C interface support Jason Liu
2010-12-27 10:43   ` Stefano Babic
2010-12-28  8:00     ` Jason Liu
2010-12-28  8:53     ` Jason Liu
2010-12-22 13:23 ` [U-Boot] [PATCH 3/3] imximage: Add MX53 boot image support Jason Liu
2010-12-27 10:55   ` Stefano Babic
2010-12-28  8:08     ` Jason Liu
2010-12-28  8:23       ` Stefano Babic [this message]
2010-12-28  8:34         ` Jason Liu
2010-12-28  9:21           ` Stefano Babic
2010-12-27 10:26 ` [U-Boot] [PATCH 1/3] mxc_gpio: add support for MX53 processor Stefano Babic
2010-12-28  8:00   ` Jason Liu

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=4D199E6C.7020700@denx.de \
    --to=sbabic@denx.de \
    --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