From: Ann Thornton <Ann.Thornton@freescale.com>
To: Nikolay Dimitrov <picmaster@mail.bg>,
Ann Thornton <ra43240@freescale.com>,
<meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-arm][PATCH v2] imx-base.inc mxs-base.inc: Add imx MACHINEOVERRIDES
Date: Mon, 6 Jul 2015 15:50:38 -0500 [thread overview]
Message-ID: <559AEA1E.8000202@freescale.com> (raw)
In-Reply-To: <559AE65B.6040201@mail.bg>
[-- Attachment #1: Type: text/plain, Size: 772 bytes --]
Hi Nikolay,
QorIQ will be merged into a common layer with i.MX.
See "[meta-freescale] Freescale meta-freescale announcement of new layer"
Ann
On 7/6/2015 3:34 PM, Nikolay Dimitrov wrote:
> Hi Ann,
>
> On 07/06/2015 10:04 PM, Ann Thornton wrote:
>> Soon non-imx machines will be added to the builds. We need to be
>> able to
>> specify imx machines to distinguish between them in recipes. This change
>> allows _imx to be used to limit actions to i.MX machines.
>
> Can you please explain why there's this need for such generalization?
> This "imx" family covers quite a diverse set of SoCs.
>
> Regards,
> Nikolay
--
Ann Thornton
/Microcontrollers Software and Applications
Freescale Semiconductors
email: Ann.Thornton@freescale.com/
[-- Attachment #2: Type: text/html, Size: 1598 bytes --]
next prev parent reply other threads:[~2015-07-06 20:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 19:04 [meta-fsl-arm][PATCH v2] imx-base.inc mxs-base.inc: Add imx MACHINEOVERRIDES Ann Thornton
2015-07-06 20:34 ` Nikolay Dimitrov
2015-07-06 20:50 ` Ann Thornton [this message]
2015-07-07 12:30 ` Daiane Angolini
2015-07-07 15:12 ` Nikolay Dimitrov
2015-07-07 16:33 ` Otavio Salvador
2015-07-08 14:33 ` Ann Thornton
2015-07-08 14:41 ` Otavio Salvador
2015-07-08 15:56 ` Daiane Angolini
2015-07-08 17:00 ` Otavio Salvador
2015-07-08 19:39 ` Daiane Angolini
2015-07-08 17:58 ` Nikolay Dimitrov
-- strict thread matches above, loose matches on Subject: below --
2015-07-08 20:11 Ann Thornton
2015-07-08 20:15 ` Ann Thornton
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=559AEA1E.8000202@freescale.com \
--to=ann.thornton@freescale.com \
--cc=meta-freescale@yoctoproject.org \
--cc=picmaster@mail.bg \
--cc=ra43240@freescale.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.