[meta-freescale] [PATCH] mx6q-ba16: Add initial board support

Justin Waters justin.waters at timesys.com
Thu Aug 27 09:32:33 PDT 2015

Hi Otavio,

On Thu, Aug 27, 2015 at 11:37 AM, Otavio Salvador <
otavio.salvador at ossystems.com.br> wrote:

> Hello Justin,
> On Thu, Aug 27, 2015 at 11:45 AM, Justin Waters
> <justin.waters at timesys.com> wrote:
> > We have been working with a vanilla (4.0+) kernel on some related
> platforms,
> > and are considering moving the BA16 platform to this as well. Is there an
> > effort to move some of the mainline work, such as etna-viv and related
> > packages, into the meta-freescale layer? Would it be acceptable to push a
> > 4.0 kernel even if those packages are not supported?
> We have intending to do this for quite some time but we are lacking
> the resources to do so.

I do have some patches against meta-fsl-arm-extra to add support for
etna-viv. I can clean those up a bit and send them out, although they need
a lot of work to play nicely with the proprietary packages.

> However I want to know what level of compromise Timesys will have in
> maintaining the board and any proposed new components as we have been
> having a hard time to get the Vybrid boards updated[3][4][5] (both
> maintained by Timesys) since long time ago even though
> Toradex[6][7][8] has did all the hard work of updating it for 4.0
> kernel. I do hope to get this solved and discussed this with Andy at
> FTF but no move has been done so far.
Andy had mentioned that conversation. We are currently working on a plan
for Vybrid. Once the higher-ups come to an agreement, we'll get that
implemented and moving forward. I'll keep you posted on any updates. Is
there anything in particular that is blocking development on your side? If
so, I can prioritize that internally.

> So all Timesys help and contributions are welcome but we do need to
> have a high level of commitment from you guys if more high impact
> changes are going to be proposed.

Understood. I'm working with Advantech to get those details ironed out, but
I needed to make sure this approach was viable. It sounds like it is.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-freescale/attachments/20150827/3a3bfeca/attachment.html>

More information about the meta-freescale mailing list