From: "Viguera, Javier" <Javier.Viguera@digi.com>
To: 'Otavio Salvador' <otavio@ossystems.com.br>
Cc: 'OE-core' <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] nativesdk-packagegroup-sdk-host: add nativesdk-u-boot-mkimage
Date: Fri, 3 Oct 2014 06:59:20 +0000 [thread overview]
Message-ID: <DA8287CC96892A4EB4FCF4FB3FBDA1AB03DB34@dor-sms-xch01.digi.com> (raw)
In-Reply-To: <CAP9ODKp9EmiTgaLptOQ5qKYjadJ0zBB00_Gjs1whd-i4PB+bJQ@mail.gmail.com>
> -----Original Message-----
> From: otavio.salvador@gmail.com [mailto:otavio.salvador@gmail.com] On
> Ross concern is because we shouldn't force mkimage in every SDK. If
> someone is using barebox, or grub, it shouldn't be added.
Hi Otavio,
I understand what the concern is, what I don't see yet is how to address this *practically*. I put some questions in my previous e-mail, do you have any hints?
I see there is a nativesdk-packagegroup-sdk-host.bbappend in *meta-fsl-arm* that unconditionally adds some tools to the toolchain (elftosb, mxsldr). If my previous patch is not accepted in oe-core, are you willing to accept the same patch in this bbappend in meta-fsl-arm?
--
Javier Viguera
Software Engineer
Digi International® Spain S.A.U.
next prev parent reply other threads:[~2014-10-03 6:59 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
2014-10-02 19:02 ` Otavio Salvador
2014-10-03 6:59 ` Viguera, Javier [this message]
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=DA8287CC96892A4EB4FCF4FB3FBDA1AB03DB34@dor-sms-xch01.digi.com \
--to=javier.viguera@digi.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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.