[U-Boot] [PATCH V2 6/6] arm: mx5: Add support for DENX M53EVK

Stefano Babic
2013-04-25T13:00:13Z

On 25/04/2013 14:48, Stefan Roese wrote:
> On 25.04.2013 14:38, Marek Vasut wrote:
>>>> 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.
>>
>> This would interfere with MBR on SD cards, the offset is there for a reason ;-)
>
> Yes, makes sense. But only for SD cards. On other mediums (e.g. SPI NOR,
> NAND) this padded image would be easier (less error prone) to handle.

If a board can boot only from a single storage, yes. Or at least from
storages with have the same offset. For example, if we have a board with
SPI-NOR and NAND, the offsets are different amd we need two images if we
pad at the beginning. If we want to add such a feature, it should be in
any case disabled to not break most of current boards.

Best regards,
Stefano

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