public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2 6/6] arm: mx5: Add support for DENX M53EVK
Date: Thu, 25 Apr 2013 10:38:35 +0200	[thread overview]
Message-ID: <5178EB8B.7040600@denx.de> (raw)
In-Reply-To: <5178DBD9.1060109@denx.de>

Hi Stefano,

On 25.04.2013 09:31, Stefano Babic wrote:
> On 24/04/2013 12:59, Beno?t Th?baudeau wrote:
> 
>>> Apart of that and not related to this patch, if we in future use SPL
>>> also for booting from SD, we can get a single way to boot from different
>>> storage. TI based SOCs already do this: same SPL, it checks from SD and
>>> NAND.
>>
>> With this also comes the issue of BOOT_FROM in board/denx/m53evk/imximage.cfg.
>> Strictly speaking, in order to be correct, it should be #if-ed depending on some
>> config option: nand or sd.
> 
> Right, this is also correct. Anyway, BOOT_FROM is used to get the offset
> inside the storage, and only to be as much flexible as possible, each
> storage has defined its own offset. However, Freescale uses the same
> offset (0x400) for most storages (NAND, SD..) and another one for NOR or
> OneNAND  (0x1000). Maybe it is easier to have only this two cases.

Yes, I would prefer that.

And being at it, why don't we add the offset to the resulting image as
well? This would make programming the images to the destination (SD,
NAND, MMC etc) easier. We would not have to care for the correct offset
then (which is more error prone). And it is necessary btw, to have this
offset added, when using the FSL kobs-ng tool to program the image to
NAND flash.

Thanks,
Stefan

  reply	other threads:[~2013-04-25  8:38 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-21 15:52 [U-Boot] [PATCH V2 1/6] imx: Align the imximage header and payload to multiples of 4k Marek Vasut
2013-04-21 15:52 ` [U-Boot] [PATCH V2 2/6] nand: Add SPL_NAND support to mxc_nand_spl Marek Vasut
2013-04-22 22:57   ` Scott Wood
2013-04-21 15:52 ` [U-Boot] [PATCH V2 3/6] arm: imx: Pack u-boot.bin into uImage for SPL Marek Vasut
2013-04-21 15:52 ` [U-Boot] [PATCH 4/6] arm: mx5: Add SPL support code to MX5 Marek Vasut
2013-04-21 15:52 ` [U-Boot] [PATCH 5/6] arm: mx5: Add NAND clock handling Marek Vasut
2013-04-21 15:52 ` [U-Boot] [PATCH V2 6/6] arm: mx5: Add support for DENX M53EVK Marek Vasut
2013-04-21 17:16   ` Benoît Thébaudeau
2013-04-21 19:12     ` Marek Vasut
2013-04-21 19:46       ` Benoît Thébaudeau
2013-04-21 20:29         ` Marek Vasut
2013-04-24  7:39           ` Stefano Babic
2013-04-24 10:59             ` Benoît Thébaudeau
2013-04-25  7:31               ` Stefano Babic
2013-04-25  8:38                 ` Stefan Roese [this message]
2013-04-25 12:31                   ` Stefano Babic
2013-04-25 12:38                   ` Marek Vasut
2013-04-25 12:48                     ` Stefan Roese
2013-04-25 12:49                       ` Benoît Thébaudeau
2013-04-25 13:02                         ` Stefano Babic
2013-04-25 13:16                           ` Benoît Thébaudeau
2013-04-25 13:31                             ` Stefano Babic
2013-04-25 13:46                         ` Stefan Roese
2013-04-25 14:12                           ` Marek Vasut
2013-04-25 13:00                       ` Stefano Babic
2013-04-24 18:52             ` Marek Vasut
2013-04-25  7:20               ` Stefano Babic
2013-04-25 13:36                 ` Marek Vasut
2013-04-25 14:45                   ` Stefano Babic
2013-04-25 14:54                     ` Marek Vasut
2013-04-24 19:04   ` Fabio Estevam
2013-04-24 21:32     ` Marek Vasut
2013-04-24 21:44       ` Otavio Salvador
2013-04-25  0:55       ` Fabio Estevam
2013-04-25 20:12         ` Marek Vasut
2013-05-05 15:59 ` [U-Boot] [PATCH V2 1/6] imx: Align the imximage header and payload to multiples of 4k 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=5178EB8B.7040600@denx.de \
    --to=sr@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