All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Viguera, Javier" <Javier.Viguera@digi.com>
To: "'Burton, Ross'" <ross.burton@intel.com>
Cc: 'OE-core' <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] nativesdk-packagegroup-sdk-host: add nativesdk-u-boot-mkimage
Date: Thu, 2 Oct 2014 16:51:01 +0000	[thread overview]
Message-ID: <DA8287CC96892A4EB4FCF4FB3FBDA1AB03DAAE@dor-sms-xch01.digi.com> (raw)
In-Reply-To: <CAJTo0LYOkeLawn2TW=8+E=GwsBLEoYJdTM8LQ6LZfu3RpcAzLg@mail.gmail.com>



> -----Original Message-----
> From: Burton, Ross [mailto:ross.burton@intel.com]
> 
> If we're adding u-boot to the SDK then we should add every bootloader.
> But why install grub for a PPC SDK?  This is why I suggested adding
> the right bootloader for each machine.

Hi Ross,

Not sure if I follow you. Are you suggesting adding this in a bbappend inside a BSP layer instead of oe-core?

Or something like the following would be suitable for oe-core?:

RDEPENDS_${PN}_append_arm = " nativesdk-u-boot-mkimage"

This seems strange to me as I don't know if all ARM machines use u-boot as bootloader. How do I restrict this per-machine?

Notice that strictly speaking this is not "adding u-boot to the SDK". It's a host tool that allows to create kernel images suitable for u-boot. But not only that, it also allows for example to create FIT (Flattened Image Tree) images. I seem to remember there was a patch lately to add support for FIT images to oe-core.

-- jviguera

  reply	other threads:[~2014-10-02 16:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-02  8:06 [PATCH] nativesdk-packagegroup-sdk-host: add nativesdk-u-boot-mkimage Javier Viguera
2014-10-02 10:49 ` Burton, Ross
2014-10-02 14:34   ` Viguera, Javier
2014-10-02 14:40     ` Burton, Ross
2014-10-02 16:51       ` Viguera, Javier [this message]
2014-10-02 19:02         ` Otavio Salvador
2014-10-03  6:59           ` Viguera, Javier
2014-10-03 12:20             ` Otavio Salvador

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=DA8287CC96892A4EB4FCF4FB3FBDA1AB03DAAE@dor-sms-xch01.digi.com \
    --to=javier.viguera@digi.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.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 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.