All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Eric Bénard" <eric@eukrea.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-arm][PATCH 2/2] nativesdk-packagegroup-sdk-host: Fix inclusion of elftosb and mxsldr
Date: Fri, 18 Jan 2013 14:25:11 +0100	[thread overview]
Message-ID: <20130118142511.016b6c5f@e6520eb> (raw)
In-Reply-To: <CAP9ODKqoVTUm6Hx4eKMU_2z5tqJKQG-wPgGmyQNAFvaOK9dxRQ@mail.gmail.com>

Hi,

please keep the ML in copy.

Le Fri, 18 Jan 2013 09:12:08 -0200,
Otavio Salvador <otavio@ossystems.com.br> a écrit :

> On Thu, Jan 17, 2013 at 8:36 AM, Eric Bénard <eric@eukrea.com> wrote:
> > Le Thu, 17 Jan 2013 08:29:04 -0200,
> > Otavio Salvador <otavio@ossystems.com.br> a écrit :
> >> On Wed, Jan 16, 2013 at 10:54 AM, Eric Bénard <eric@eukrea.com> wrote:
> >> > Le Wed, 16 Jan 2013 10:02:29 -0200,
> >> > Otavio Salvador <otavio@ossystems.com.br> a écrit :
> >> >> > Shouldn't we limit this to the machines which need these tools ?
> >> >>
> >> >> How do you think we can manage this?
> >> >>
> >> > maybe using mxs override in the bbappend ?
> >>
> >> Or maybe armv5? since this is useful for toolchains for all mxs SoCs?
> >>
> > no, i.MX25 is armv5 and doesn't use these tools.
> > And other BSP can provide support for armv5 machines which also don't
> > need these tools.
> 
> So in this case use 'mxs' would do it. The problem with this is the
> package group is a native so it is suppose to be regarding host but we
> seems to be changing it content of the host depending on the target.
> 
What is the problem ?
The SDK are already typed with parameters of the target (headers of the
target's kernel, compiler's target arch, dev libraries included in sync
with the content of target's image, etc ...).

Eric


  parent reply	other threads:[~2013-01-18 13:25 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-15 11:11 [meta-fsl-arm][PATCH 1/2] mxsldr: Update to newer snapshot Otavio Salvador
2013-01-15 11:11 ` [meta-fsl-arm][PATCH 2/2] nativesdk-packagegroup-sdk-host: Fix inclusion of elftosb and mxsldr Otavio Salvador
2013-01-15 11:58   ` Daiane Angolini
2013-01-15 11:58     ` Daiane Angolini
2013-01-15 12:16       ` Otavio Salvador
     [not found]   ` <20130116124552.34be3eec@e6520eb>
2013-01-16 12:02     ` Otavio Salvador
     [not found]       ` <20130116135445.67810ada@e6520eb>
2013-01-17 10:29         ` Otavio Salvador
2013-01-17 10:36           ` Eric Bénard
     [not found]             ` <CAP9ODKqoVTUm6Hx4eKMU_2z5tqJKQG-wPgGmyQNAFvaOK9dxRQ@mail.gmail.com>
2013-01-18 13:25               ` Eric Bénard [this message]
2013-01-18 13:53                 ` Otavio Salvador
2013-01-15 11:56 ` [meta-fsl-arm][PATCH 1/2] mxsldr: Update to newer snapshot Daiane Angolini
2013-01-15 11:57   ` Fabio Estevam
2013-01-15 12:15   ` Otavio Salvador
2013-01-15 13:01   ` Eric Bénard
2013-01-15 15:04     ` Daiane Angolini
2013-01-15 13:00 ` Eric Bénard
2013-01-15 13:15   ` Fabio Estevam
2013-01-15 13:22     ` Eric Bénard
2013-01-15 13:51       ` Otavio Salvador
2013-01-15 13:50     ` Otavio Salvador
2013-01-15 13:23   ` Otavio Salvador
2013-01-15 13:27     ` Eric Bénard
2013-01-15 13:53       ` 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=20130118142511.016b6c5f@e6520eb \
    --to=eric@eukrea.com \
    --cc=meta-freescale@yoctoproject.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.