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 14:34:24 +0000	[thread overview]
Message-ID: <DA8287CC96892A4EB4FCF4FB3FBDA1AB03D9B8@dor-sms-xch01.digi.com> (raw)
In-Reply-To: <CAJTo0Lazv8xfBPA51UF_NDz0MJm7tCgjEP9Ya404x0V54q7dAA@mail.gmail.com>

> -----Original Message-----
> From: Burton, Ross [mailto:ross.burton@intel.com]
> 
> On 2 October 2014 09:06, Javier Viguera <javier.viguera@digi.com>
> wrote:
> > Add the 'mkimage' host tool to the toolchains generated with 'bitbake
> > meta-toolchain' or with 'bitbake -c populate_sdk <image>'.
> 
> But not all BSPs uses u-boot.  Having the bootloader tooling makes
> sense, but it needs to be the right tooling.


Hi Ross,

I was not targeting any specific BSP. I was just using a generic toolchain created with poky. My steps:

1. Clone Poky (or oe-core)
2. Created a generic project and configure for 'qemuarm' (MACHINE=qemuarm changed in local.conf)
3. bitbake meta-toolchain

With this toolchain you can build zImage kernel images but not uImage. Sure the uImage is to be used with u-boot, but I see the value of having a generic ARM toolchain and that still allows me to create uImage files. The mkimage binary adds about 80 KB in a 273 MB toolchain (doesn't seem too much).

-- jviguera




  reply	other threads:[~2014-10-02 14:41 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 [this message]
2014-10-02 14:40     ` Burton, Ross
2014-10-02 16:51       ` Viguera, Javier
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=DA8287CC96892A4EB4FCF4FB3FBDA1AB03D9B8@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.