<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix"><br>
It is true that mx6 can be used today but soon there will be mx7
and mx8 and the list will get longer. Also qoriq and automotive
will be added in which we will want to exclude from i.mx. There
are recipes, images, and packagegroups that currently don't need
to check for the machine that will need to coming up and bbappends
that will be needed to differentiate between machines. imx would
be a convenience that will be useful in the near future. The
alternative is a long list of i.MX machines.<br>
<br>
Ann<br>
<br>
<br>
On 7/7/2015 10:12 AM, Nikolay Dimitrov wrote:<br>
</div>
<blockquote cite="mid:559BEC6C.80407@mail.bg" type="cite">Hi Daiane,
<br>
<br>
On 07/07/2015 03:30 PM, Daiane Angolini wrote:
<br>
<blockquote type="cite">On Mon, Jul 6, 2015 at 5:50 PM, Ann
Thornton <a class="moz-txt-link-rfc2396E" href="mailto:Ann.Thornton@freescale.com"><Ann.Thornton@freescale.com></a> wrote:
<br>
<blockquote type="cite">Hi Nikolay,
<br>
<br>
QorIQ will be merged into a common layer with i.MX.
<br>
See "[meta-freescale] Freescale meta-freescale announcement of
new layer"
<br>
</blockquote>
<br>
Ann, Nikolay,
<br>
<br>
Currently on 1.8 (fido) of meta-fsl-arm we already have 3
different
<br>
product lines from Freescale: i.MX, Layerscape/QoirQ and Vybrid.
And
<br>
currently the OVERRIDE "imx" is not exactly needed (if you think
<br>
everything has been working fine so far).
<br>
<br>
Please see [1], the heads (imx, vybrid and layerscape) are not
from
<br>
the meta-fsl-arm source code, but faked for the picture.
<br>
<br>
Back to 1.6 RN I was able to find vybrid already being
graphically
<br>
represented in a SOC Family tree.
<br>
<br>
So, the argument that imx is needed because of meta-freescale is
not
<br>
right. Having a OVERRIDE for imx and vybrid and layerscape may
make
<br>
sense because of some future differentiation on the BSP
regarding
<br>
product lines.
<br>
<br>
On the other hand, if we have time, we can discuss it a lot. For
<br>
example, if you take the imx6, you see, from BSP point of view,
we
<br>
have more diverging than converging packages. Would it make
sense to
<br>
</blockquote>
<br>
Indeed, I also think that the "imx" family will cover a set of
such
<br>
widely different SoCs, so I was wondering whether there's any
practical
<br>
use case where we can address all these SoCs as "the imx". We
already
<br>
have "imx6*" overrides, which are both specific and works to
separate
<br>
from qoriq.
<br>
<br>
<blockquote type="cite">keep the "imx6" OVERRIDE today?
<br>
<br>
I would like to have the SOC_FAMILY tree reviewed for sure. I
know we
<br>
have a lot of possible enhancement there. But I really don't get
the
<br>
overall picture only with this patch.
<br>
<br>
And, the commit log is wrong. We already have non-imx machines
in meta-fsl-arm.
<br>
<br>
[1]
<a class="moz-txt-link-freetext" href="http://freescale.github.io/doc/release-notes/1.8/index.html#soc-hierarchy">http://freescale.github.io/doc/release-notes/1.8/index.html#soc-hierarchy</a><br>
<br>
Regards,
<br>
Daiane
<br>
<br>
<br>
<blockquote type="cite">
<br>
Ann
<br>
<br>
On 7/6/2015 3:34 PM, Nikolay Dimitrov wrote:
<br>
<br>
Hi Ann,
<br>
<br>
On 07/06/2015 10:04 PM, Ann Thornton wrote:
<br>
<br>
Soon non-imx machines will be added to the builds. We need to
be able to
<br>
specify imx machines to distinguish between them in recipes.
This change
<br>
allows _imx to be used to limit actions to i.MX machines.
<br>
<br>
<br>
Can you please explain why there's this need for such
generalization?
<br>
This "imx" family covers quite a diverse set of SoCs.
<br>
<br>
Regards,
<br>
Nikolay
<br>
<br>
<br>
<br>
--
<br>
Ann Thornton
<br>
<br>
Microcontrollers Software and Applications
<br>
Freescale Semiconductors
<br>
email: <a class="moz-txt-link-abbreviated" href="mailto:Ann.Thornton@freescale.com">Ann.Thornton@freescale.com</a>
<br>
<br>
--
<br>
_______________________________________________
<br>
meta-freescale mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:meta-freescale@yoctoproject.org">meta-freescale@yoctoproject.org</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.yoctoproject.org/listinfo/meta-freescale">https://lists.yoctoproject.org/listinfo/meta-freescale</a>
<br>
<br>
</blockquote>
<br>
<br>
<br>
</blockquote>
<br>
Regards,
<br>
Nikolay
<br>
</blockquote>
<br>
<br>
<div class="moz-signature">-- <br>
Ann Thornton
<br>
<br>
<i>Microcontrollers Software and Applications<br>
Freescale Semiconductors<br>
email: <a class="moz-txt-link-abbreviated" href="mailto:Ann.Thornton@freescale.com">Ann.Thornton@freescale.com</a></i></div>
</body>
</html>