From: Otavio Salvador <otavio@ossystems.com.br>
To: Nikolay Dimitrov <picmaster@mail.bg>
Cc: meta-freescale Mailing List <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-arm][PATCH 3/4] linux-fslc-mx6 (3.14-1.0.x): Add recipe
Date: Thu, 18 Jun 2015 13:47:56 -0300 [thread overview]
Message-ID: <CAP9ODKqg6Oy1-OdDYMHxt2nw6VjuB-7akq5P9Y1ztFeErEBkXA@mail.gmail.com> (raw)
In-Reply-To: <5582F407.5010803@mail.bg>
On Thu, Jun 18, 2015 at 1:38 PM, Nikolay Dimitrov <picmaster@mail.bg> wrote:
> On 06/18/2015 07:21 PM, Otavio Salvador wrote:
...
>> #2 linux-fslc is a tree to host fslc modified kernels. It has no
>> compromise to be mainline only.
>>
>> #3 allow us to share work among vendors and bring fixes while reusing
>> the work done by FSL BSP team, board vendors and community.
>>
>> #4 has no support; as soon you port it to your board it is
>> non-supported kernel. As soon you move away of their BSP release it
>> is non-supported kernel and plus it does not have patches applied
>> once tagged (nor security or fixes) so any change needs to wait for
>> next GA.
>>
>> To be honest, FSL does not apply fixes until next GA so there is no
>> way to improve their kernel, u-boot, whatever. We try to fill the gap
>> here and avoid work duplication.
>>
>> The amount of duplicated work done by board vendors is insane, I am
>> trying to improve it as much as I can.
>
>
> I see, and fully agree with the explanations. My current understanding
> (could be wrong) is that the current FSL drivers in 3.14.28 are not
> possible to be rebased to newer mainline kernels, is that correct?
Correct; some can be adapted to work on top of mainline kernel however
this is another derivative work.
> That's why I commented about the possible confusion, as for me it's good
> to see in the kernel name whether it has or has not support for the SoC
> bells/whistles (-mainline/-fslc vs -imx).
>
> If my assumption is wrong and these drivers *can* be rebased while
> retaining compatibility with the binary blobs, than probably #2 and #3
> start to look like something that can be merged (what Daiane said also).
Some features can be forward-ported but this is another possible fork
to be started, I won't commit to this myself at this moment.
--
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
next prev parent reply other threads:[~2015-06-18 16:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 18:02 [meta-fsl-arm][PATCH 1/4] core-image-weston: Fail gracefully if using incompatible DISTRO_FEATURES Otavio Salvador
2015-06-17 18:02 ` [meta-fsl-arm][PATCH 2/4] fsl-default-providers.inc: Move content to imx-base.inc and mxs-base.inc Otavio Salvador
2015-06-17 18:33 ` Nikolay Dimitrov
2015-06-17 18:38 ` Otavio Salvador
2015-06-17 19:27 ` Nikolay Dimitrov
2015-06-17 18:02 ` [meta-fsl-arm][PATCH 3/4] linux-fslc-mx6 (3.14-1.0.x): Add recipe Otavio Salvador
2015-06-17 18:28 ` Nikolay Dimitrov
2015-06-17 18:30 ` Otavio Salvador
2015-06-17 18:38 ` Nikolay Dimitrov
2015-06-17 18:39 ` Otavio Salvador
2015-06-17 19:25 ` Nikolay Dimitrov
2015-06-17 19:32 ` Daiane Angolini
2015-06-17 19:45 ` Otavio Salvador
2015-06-18 13:40 ` Daiane Angolini
2015-06-18 13:58 ` Otavio Salvador
2015-06-18 15:32 ` Nikolay Dimitrov
2015-06-18 16:21 ` Otavio Salvador
2015-06-18 16:38 ` Nikolay Dimitrov
2015-06-18 16:47 ` Otavio Salvador [this message]
2015-06-18 16:47 ` Ann Thornton
2015-06-18 17:10 ` Nikolay Dimitrov
2015-06-18 17:40 ` Otavio Salvador
2015-06-17 18:02 ` [meta-fsl-arm][PATCH 4/4] imx-base.inc: Use linux-fslc-mx6 for all i.MX6 by default Otavio Salvador
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=CAP9ODKqg6Oy1-OdDYMHxt2nw6VjuB-7akq5P9Y1ztFeErEBkXA@mail.gmail.com \
--to=otavio@ossystems.com.br \
--cc=meta-freescale@yoctoproject.org \
--cc=picmaster@mail.bg \
/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.