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] SPL boot on iMX6
Date: Mon, 26 Aug 2013 09:42:30 +0200	[thread overview]
Message-ID: <521B06E6.5030306@denx.de> (raw)
In-Reply-To: <20130826151743.20e384d4@triceratops>

Hi Tapani,

On 26/08/2013 09:17, Tapani Utriainen wrote:
> 
> Hello all,
> 
> we would like to have some comments how to architecture some patches we would 
> like to submit.

Nice

> 
> Background:
> 
> We have got SPL boot working, circumventing the need to have separate u-boot
> binaries depending on iMX6 CPU type and memory configuration. This allows us
> to have one (say) bootable SD card for all versions of our new SoMs.

Agree on this - we have already discussed in the past about this point,
and the way to get a single image for the different i.MX6 SOCs is to add
SPL support, moving part of the initialization stuff away from the DCD
table managed directly from the bootrom.

> 
> Formatting the patches presents us with some questions:
> 
> 1. Padconfigs. For some reason the existing padconfiguration macros are set
> compile time depending on target cpu variant. Hence the need to add new 
> macros (or smth) so the binary can configure the pads for many cpu variants.
> This would cause duplicate and redundant sets of pad configuration macros 
> for the imx6. Is there any alternative to this, more than rewriting code to 
> comply with cpu specific padconfigs?

Macros wee added exactly in the time they needed, and maybe a global
look was missing.

However, can you provide much more detail about this ? Which macros, in
which files ?

> 
> 2. Is there a minimum set of features that should be supported by new boards?
> (Thinking of features like fdt, fat or network boot).

No, there is not - the board maintainer is responsible to add the
features the board can. You can add support for a restricted number of
feature and later add a patch to full support the board.

> It seems that most imx6 based boards have some standard features enabled by
> default, but some of those we haven't tested on our new board.

You should dropped them, and add them again once they are tested and if
you really want to have them.

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
=====================================================================

  reply	other threads:[~2013-08-26  7:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-26  7:17 [U-Boot] SPL boot on iMX6 Tapani Utriainen
2013-08-26  7:42 ` Stefano Babic [this message]
2013-08-26 11:12   ` Tapani
2013-08-26 13:33     ` Stefano Babic
2013-08-26 14:23       ` Eric Nelson
2013-08-27 12:53         ` Stefano Babic
2013-08-27  4:07       ` Tapani Utriainen
2013-08-27 13:00         ` Stefano Babic
2013-08-27 15:00         ` Eric Nelson
2013-08-26 13:28 ` Fabio Estevam

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=521B06E6.5030306@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