Adding a new machine to meta-fsl-arm-extra

Adding a new machine to meta-fsl-arm-extra

[Christian Ege]

Hi,

I am preparing Patches for the UDOO Neo (http://www.udoo.org/udoo-neo/)
i.mx6 SoloX based board to be integrated into meta-fsl-arm-extra. I have
some questions what is the intended work flow for this.

At the moment I have integrated the UDOO Neo board in my fork of
meta-fsl-arm-extra.

https://github.com/graugans/meta-fsl-arm-extra/tree/fido

- Is it okay to provide patches for fido at first or should new boards
be introduced to master only?

- How to deal with the various flavours of the Neo Familiy?
    - BASIC with 512MB RAM, Ethernet
    - EXTENDED 1GB RAM, Wi-Fi/Bluetooth, Motion Sensors
    - FULL 1GB RAM, Wi-Fi/Bluetooth, Motion Sensors, Ethernet

Should I provided 3 machine configs?
  - udooneofull
  - udooneobasic
  - udooneoextended

Are there any suggestions on the naming scheme? As far as I know '-' is
not an good idea as separator.

I Have patches available for the UDOO Quad as-well but no board to test
on. If there is interest I can provide them as-well.


Regards,
Christian

Re: Adding a new machine to meta-fsl-arm-extra

[Otavio Salvador]

Hello Christian,

On Thu, Nov 5, 2015 at 11:02 AM, Christian Ege <k4230r6@gmail.com> wrote:
> I am preparing Patches for the UDOO Neo (http://www.udoo.org/udoo-neo/)
> i.mx6 SoloX based board to be integrated into meta-fsl-arm-extra. I have
> some questions what is the intended work flow for this.
>
> At the moment I have integrated the UDOO Neo board in my fork of
> meta-fsl-arm-extra.
>
> https://github.com/graugans/meta-fsl-arm-extra/tree/fido
>
> - Is it okay to provide patches for fido at first or should new boards
> be introduced to master only?

master only.

> - How to deal with the various flavours of the Neo Familiy?
>     - BASIC with 512MB RAM, Ethernet
>     - EXTENDED 1GB RAM, Wi-Fi/Bluetooth, Motion Sensors
>     - FULL 1GB RAM, Wi-Fi/Bluetooth, Motion Sensors, Ethernet

It depends; ideally UDOO ought to work with SPL and same image should
work fine with all the flavours. Wandboard does it, CuBox does it as
well.

...
> I Have patches available for the UDOO Quad as-well but no board to test
> on. If there is interest I can provide them as-well.
...

I prefer you to not send it than; we should have only maintained boards.

-- 
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

Re: Adding a new machine to meta-fsl-arm-extra

[Christian Ege]

Hello Otavio,

On 05.11.2015 18:19, Otavio Salvador wrote:
> Hello Christian,
> 
> On Thu, Nov 5, 2015 at 11:02 AM, Christian Ege <k4230r6@gmail.com> wrote:
>> I am preparing Patches for the UDOO Neo (http://www.udoo.org/udoo-neo/)
>> i.mx6 SoloX based board to be integrated into meta-fsl-arm-extra. I have
>> some questions what is the intended work flow for this.
>>
>> At the moment I have integrated the UDOO Neo board in my fork of
>> meta-fsl-arm-extra.
>>
>> https://github.com/graugans/meta-fsl-arm-extra/tree/fido
>>
>> - Is it okay to provide patches for fido at first or should new boards
>> be introduced to master only?
> 
> master only.
Makes sense
> 
>> - How to deal with the various flavours of the Neo Familiy?
>>     - BASIC with 512MB RAM, Ethernet
>>     - EXTENDED 1GB RAM, Wi-Fi/Bluetooth, Motion Sensors
>>     - FULL 1GB RAM, Wi-Fi/Bluetooth, Motion Sensors, Ethernet
> 
> It depends; ideally UDOO ought to work with SPL and same image should
> work fine with all the flavours. Wandboard does it, CuBox does it as
> well.
Okay, at the moment SPL is not supported. But this is an good idea.

> ...
>> I Have patches available for the UDOO Quad as-well but no board to test
>> on. If there is interest I can provide them as-well
> ...
> 
> I prefer you to not send it than; we should have only maintained boards.
This is what I've expected.

Regards,
Christian