mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Lucas Stach <l.stach@pengutronix.de>
To: Holger Schurig <holgerschurig@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: Suggestions for new i.MX6 board
Date: Wed, 02 Apr 2014 17:19:40 +0200	[thread overview]
Message-ID: <1396451980.19064.11.camel@weser.hi.pengutronix.de> (raw)
In-Reply-To: <CAOpc7mEKy0sKGdKbSqvCJjQRcz_wBQY_tVYWZ3-TH_V4XqAQ1A@mail.gmail.com>

Hi Holger,

Am Mittwoch, den 02.04.2014, 17:05 +0200 schrieb Holger Schurig:
> Hi list,
> 
> I'm going to implement barebox to an i.MX6Q based board we've
> developed in the company I work for.
> 
> Now the very first question is: to CONFIG_IMX_MULTI_BOARDS or not to
> CONFIG_IMX_MULTI_BOARDS??
> 
If you are adding a new board please go for multi board support.

> For example, I see in "make xconfig" that some boards are made in a
> multi-board way, e.g. they are active when CONFIG_IMX_MULTI_BOARDS is
> set (e.g. Sabrelite). However, there is one that is only visible
> without that config,. the Armadillo2. Obviously I could do it this are
> that way, so which should I use?   Personally I don't think that it
> makes sense to compile a barebox binary that runs on different boards,
> I don't even know how the boot loader would discriminate if it runs on
> board A or board B ...
> 
There are some boards that don't use the multi-image support as nobody
had time to convert them them over to the new method. But we would
definitely like to get rid of them, not add to that list...

In barebox the multi board support doesn't work like a multiarch kernel.
You don't build a single image for all boards, but rather build a basic
barebox binary and then link it together with the board specific parts
to form multiple board dependent images. You still have to chose which
image is the right one for your board.

The upside of this mechanism is that you can easily have a single
barebox config and built images for different configurations of the same
board (like different memory configurations, or in case of the MX6
different version of the SoC).

> 
> Or, I could phrase that question differently: from all the existing
> i.MX6 boards, which one is the one with the least bitrot, i.e. which
> one should I take as a template?
> 
Pretty much all of the multi-image enabled boards have seen some love
recently. A relatively simple example with different configs for the
same board can be found within the boundarydevices nitrogen6x support.

Regards,
Lucas
-- 
Pengutronix e.K.                           | Lucas Stach                 |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-5076 |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2014-04-02 15:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-02 15:05 Holger Schurig
2014-04-02 15:19 ` Lucas Stach [this message]

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=1396451980.19064.11.camel@weser.hi.pengutronix.de \
    --to=l.stach@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=holgerschurig@gmail.com \
    /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