Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Interest in upgrading syslinux to 5.x?
Date: Mon, 25 Mar 2013 07:38:18 +0100	[thread overview]
Message-ID: <514FF0DA.4030105@mind.be> (raw)
In-Reply-To: <EBADBC9F10F448F49B067CB7A90C908C@beraninstruments.com.local>

On 20/03/13 13:29, Will Moore wrote:
> It might help to see what Arnout is up to with his grub2 patch which is also
> looking at providing a bootloader with host and target tools.  See
> http://patchwork.ozlabs.org/patch/191813/

  That patch has been sitting in the freezer :-)

  As you can see from the corresponding mail thread, there is no 
convergence about what to call the two variants of a bootloader. It's a 
bit like gcc: the normal variant builds an installer running on the host, 
but it includes binary code for the target; the other variant is 
completely running on the target.

  Note that for u-boot, the chosen solution is to create a completely 
separate package uboot-tools for the target. But it's a bit a special 
case, because mkimage is not an installer.


  Regards,
  Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2013-03-25  6:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-19 20:43 [Buildroot] Interest in upgrading syslinux to 5.x? Daniel Price
2013-03-19 21:22 ` Daniel Price
2013-03-20  8:50 ` Will Moore
2013-03-20  9:25   ` Daniel Price
2013-03-20  9:50     ` Will Moore
2013-03-20 12:29       ` Will Moore
2013-03-25  6:38         ` Arnout Vandecappelle [this message]
2013-03-25 18:10           ` Daniel Price

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=514FF0DA.4030105@mind.be \
    --to=arnout@mind.be \
    --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