From: Christian Ege <k4230r6@gmail.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: Adding a new machine to meta-fsl-arm-extra
Date: Thu, 05 Nov 2015 19:23:09 +0100 [thread overview]
Message-ID: <563B9E8D.4010908@gmail.com> (raw)
In-Reply-To: <CAP9ODKqd74Kb2i60sPfgn-69+XtVxiCd=GytKyFecCPJ39UjFw@mail.gmail.com>
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
prev parent reply other threads:[~2015-11-05 18:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 13:02 Adding a new machine to meta-fsl-arm-extra Christian Ege
2015-11-05 17:19 ` Otavio Salvador
2015-11-05 18:23 ` Christian Ege [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=563B9E8D.4010908@gmail.com \
--to=k4230r6@gmail.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio.salvador@ossystems.com.br \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.