[meta-freescale] [fsl-community-bsp-platform][PATCH] Adding new i.MX53 TURING machine definitions

Otavio Salvador otavio.salvador at ossystems.com.br
Thu Dec 3 11:43:47 PST 2015


On Thu, Dec 3, 2015 at 5:35 PM, Mauricio Cirelli
<mauricio.cirelli at quantatec.com.br> wrote:
> I did not notice that.
>
> We were working on fido branch instead of master, because we heard that kernel 2.6.35 would not build on newer Yocto versions than Fido (as it seems to be true, but I am afraid that even Fido does not fully support i.MX5).

Fido does however we don't accept new machines for old releases. So
you must base patches on master.

This is documented:
http://freescale.github.io/doc/release-notes/2.0/index.html#main-branch-names

> I have read that patch you point out and it seems that any i.MX5 dependancy for 2.6.35 drivers have been removed from the i.MX5 recipes. Despite of upgrading for kernel 4.1, it seems that several GPU drivers would need to be ported to the newer kernel, is that correct? This seems to be a lot a work (not sure if that is even possible as several of these drivers are not open-source). From this point of view, it seems that i.MX5 is essentially dead in newer Yocto versions. Is it correct?

Well it depends on the peripherals you use. We have customers using
mainline and keeping it alive.

> If that is the case, which is the latest Yocto version that fully supports i.MX5? I could use that as the base version for our board and create a custom layer for that if patches targeting this old release are not acceptable anymore. We can work with newer versions when we release our i.MX6 boards.

Fido.

> What should be the best way to go?

As I said, use master for upstream work. Fido is dead for development purposes.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750


More information about the meta-freescale mailing list