[Openembedded-architecture] RFC: Non-Linux BSPs and/or non-standard architectures

[Paul Barker]

On Thu, May 11, 2017 at 10:18 PM, Denys Dmytriyenko <denis at denix.org> wrote:
> All,
>
> Somewhat related to the other Yocto Project Compliance 2.0 discussion, I
> have a question about supporting non-Linux BSPs or BSPs with both Linux and
> non-Linux targets. I've noticed there's some support for "baremetal" builds.
> What about non-standard architectures? Will that affect Compliance factors in
> any way?
>
> Just to provide some specific examples - I'm trying to determine feasibility
> and validity of adding meta-ti support for RTOS OS on TI existing platforms,
> as well as adding C6x-architecture DSP-based platforms to meta-ti that can
> only do RTOS. Unfortunately, support for C6x architecture is not proper, as
> from OE perspective it's not a new architecture, but instead just a hacked up
> ARM one, that uses own toolchain, kernel and so on. Yes, it's not clean, but
> it is what it is at this point... I don't expect these new platforms to affect
> regular Linux builds or conflict with other BSPs. But still, wanted to run it
> by the community for any comments. Thanks.
>

As someone who's worked with Keystone II processors and released two
entirely separate BSPs for a single board (OpenEmbedded-based for ARM,
custom for C6x), it'd be great to combine all of this into one
OpenEmbedded BSP! I can also see a benefit for mixed IoT deployments
(for example, deployments with Linux for the IoT gateway/router and
microcontrollers running an RTOS for the individual devices).

If you need any help making this happen then let me know.

Thanks,

-- 
Paul Barker
Co-Founder & Principal Engineer
Togán Labs Ltd