All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [NEXT PATCH v1 5/7] SPL: Added MLO for mx35 SOC to SPL Makefile
Date: Mon, 10 Sep 2012 14:27:50 +0200	[thread overview]
Message-ID: <20120910142750.4956ebaf@skate> (raw)
In-Reply-To: <50491C34.1020301@denx.de>

Hello,

Le Thu, 06 Sep 2012 23:57:08 +0200,
stefano babic <sbabic@denx.de> a ?crit :

> > Agreed.  I guess what I'm asking is, in the TI case the ROM reads FAT
> > and must find 'MLO'.  Does mx35 do the same or
> 
> No. And not only the MX35, but also the MX5/MX6.
> 
> > is the post-build step
> > "dd if=MLO of=/dev/... ..." and the filename doesn't matter?
> 
> Exactly. The ROM does not understand a filesystem, and the SPL must be
> stored at a fixed address in the SD card. The filename does not matter,
> and the SPL is not seen as file, but as a raw image.
> 
> >  I'm fine
> > with the change now, just looking for the full details.  Thanks!
> 
> As for Freescale the filename does not matter while for TI does, we can
> use for both MLO ;-)

Then in that case I would precisely *not* use the same filename, in
order to make it clear that Freescale SPL cannot be used in the same
way as the TI SPL. Naming it MLO will certainly confuse users having
previous experience with TI stuff: it will lead them to believe that
creating a FAT filesystem and putting the MLO file in it will be the
necessary steps to get this SPL loaded by the ROM code.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-09-10 12:27 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-06  8:04 [U-Boot] [NEXT PATCH v1 0/7] In this patchset, a new i.MX35 board is added implementing Stefano Babic
2012-09-06  8:04 ` [U-Boot] [NEXT PATCH v1 1/7] ARM: Fix start.S when used with SPL in arm1136 Stefano Babic
2012-09-06  8:04 ` [U-Boot] [NEXT PATCH v1 2/7] NAND: added NAND type to nand_ids Stefano Babic
2012-09-06 23:19   ` Scott Wood
2012-09-07  9:12     ` Stefano Babic
2012-09-07 15:23       ` Stefano Babic
2012-09-07 18:56         ` Scott Wood
2012-09-10 12:09           ` Stefano Babic
2012-09-10 23:18             ` Scott Wood
2012-10-01  7:02               ` Stefano Babic
2012-09-23 19:01             ` Eric Bénard
2012-09-24  8:29               ` Stefano Babic
2012-09-06  8:04 ` [U-Boot] [NEXT PATCH v1 3/7] MX35: add LOW_LEVEL_SRAM_STACK to use SPL_FRAMEWORK Stefano Babic
2012-09-06  8:04 ` [U-Boot] [NEXT PATCH v1 4/7] MX35: Add soc_boot_mode and soc_boot_device to MX35 Stefano Babic
2012-09-23 19:25   ` Eric Bénard
2012-09-24  8:35     ` Stefano Babic
2012-09-06  8:04 ` [U-Boot] [NEXT PATCH v1 5/7] SPL: Added MLO for mx35 SOC to SPL Makefile Stefano Babic
2012-09-06 17:49   ` Tom Rini
2012-09-06 19:59     ` Stefano Babic
2012-09-06 20:48       ` Tom Rini
2012-09-06 21:57         ` stefano babic
2012-09-10 12:27           ` Thomas Petazzoni [this message]
2012-09-10 12:44             ` Stefano Babic
2012-09-10 12:54               ` Tom Rini
2012-09-06  8:04 ` [U-Boot] [NEXT PATCH v1 6/7] ARM: Add MLO target to arm1136 Stefano Babic
2012-09-06  8:05 ` [U-Boot] [NEXT PATCH v1 7/7] MX35: add support for woodburn board 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=20120910142750.4956ebaf@skate \
    --to=thomas.petazzoni@free-electrons.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.