From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] targets: move target options to their own sub-menu
Date: Sun, 18 Aug 2013 18:41:13 +0200 [thread overview]
Message-ID: <20130818184113.61b46b20@skate> (raw)
In-Reply-To: <20130816175906.GA3422@free.fr>
Dear Yann E. MORIN,
On Fri, 16 Aug 2013 19:59:07 +0200, Yann E. MORIN wrote:
> This is two-sided:
> - either you consider what Buildroot has to offer: one kernel, and
> multiple bootloaders;
> - or you consider what the user may want to install on the targe, at
> most one kernel, and at most one bootloader.
"At most one bootloader" is wrong in many situations. On many ARM
platforms, you have two bootloaders. A small first stage bootloader,
and a full-featured second stage bootloader such as U-Boot or Barebox.
On AT91 platforms, you have AT91Bootstrap + U-Boot or Barebox.
On some i.MX platforms, you have mxs-bootlets + U-Boot or Barebox.
On some OMAP platforms, you have X-Loader + U-Boot.
etc, etc.
So clearly, we should keep "Bootloaders" in the plural form.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-08-18 16:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 20:28 [Buildroot] [PATCH] targets: move target options to their own sub-menu Yann E. MORIN
2013-08-15 23:10 ` Arnout Vandecappelle
2013-08-16 6:30 ` Thomas De Schampheleire
2013-08-16 6:39 ` Yann E. MORIN
2013-08-16 10:24 ` Thomas De Schampheleire
2013-08-16 10:30 ` Thomas De Schampheleire
2013-08-16 17:59 ` Yann E. MORIN
2013-08-16 19:04 ` Thomas De Schampheleire
2013-08-18 16:41 ` Thomas Petazzoni [this message]
2013-08-19 16:33 ` Arnout Vandecappelle
2013-08-18 7:24 ` Thomas De Schampheleire
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=20130818184113.61b46b20@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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