[meta-freescale] [meta-fsl-arm][PATCH 3/4] linux-fslc-mx6 (3.14-1.0.x): Add recipe

[Otavio Salvador]

On Thu, Jun 18, 2015 at 2:10 PM, Nikolay Dimitrov <picmaster at mail.bg> wrote:
> On 06/18/2015 04:58 PM, Otavio Salvador wrote:
>> linux-fslc_4.0.bb linux-fslc-mx6_3.14-1.0.x.bb
>>
>> or
>>
>> linux-fslc_4.0.bb linux-fslc_3.14-1.0.x-mx6.bb
>
>
> Understood. Then here's my proposal, which I hope aligns with what you
> already outlined:
>
> 1. Drop SOC name from the provider name
> ...in order to have more SOCs benefit from the same efforts. First,
> patches in non-soc-specific common areas can be reused as-is (ext4
> patches anyone :D?), and second, it would be great to have 1 repository
> where all these efforts are concentrated, not separate for each separate
> SoC (also, there are drivers for IP-blocks which are reused 1:1 across
> SoCs).
>
> 2. Make sure the provider name doesn't contain a delimited string of
> "fsl", "imx" or "mx"
> ... to make sure the provider is not confused with the FSL provider, and
> to give due credit to the upstream + community efforts.
>
> 3. Drop the GA release version from the provider name
> ...for several reasons:
> - it will limit the ability to merge patches from different GA releases
> (if/when such need arises)
> - to not confuse it with FSL GA releases
> - sooner or later due to upstream patches merged this code will be
> further and further away from the FSL release point.
>
> So I think that a provider name like...
>
> linux-fslc_3.14.28
> linux-fslc_3.17.4
> linux-fslc_4.0
>
> ...seems practical.
>
> (I can only make the educated guess that "fslc" = "Freescale community", but
> "fsl-community" really seems quite long).

Yes, "fslc" stands for FSL Community.

There are reasons behind the use of another provider, the main ones are:

 - avoid use of version pinning (PREFERRED_VERSION_...);
 - make the SoC it targets explicit;

The 3.14.28-1.0.0-GA has only been tested on the *boards* listed in
the release notes. If you take this and use it in another board, this
is not supported by Freescale.

In case you take the 3.14.28-1.0.0-GA kernel and use it in another
SoC, it is at your risk. Freescale does not test the code changes on
the other SoCs so even if some IP components are shared they were not
tested and even checked when the changes in the drivers and
architecture code were done.

In summary the linux-fslc-mx6 is now a 3.14.44 kernel which merges
3.14.28-1.0.0-GA and should ONLY be used for i.MX6 SoCs. There is no
test or check of this tree for another SoCs.

The shared tree for all SoCs are the ones we maintain based on
mainline (4.0, 4.1...) and this can be expected to work on all SoCs.

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