[meta-freescale] [meta-fsl-ppc][PATCH][v2] linux: add support for kernel fragmentation

Otavio Salvador otavio at ossystems.com.br
Fri Oct 3 07:01:44 PDT 2014


On Thu, Oct 2, 2014 at 1:48 AM, Bob Cochran <yocto at mindchasers.com> wrote:
> On 09/30/2014 04:42 AM, b40527 at freescale.com wrote:
>>
>> From: Zongchun Yu <Zongchun.Yu at freescale.com>
>>
>> Using the metadata which is stored in recipe-space, and adding the .scc
>> files on the SRC_URI. BitBake can parses them and fetches any files
>> referenced in the .scc files by the include, patch, or kconf
>> commands. these commands can achieve kernel fragmentation configuration,
>> appliying patch and so on.
>
>
>
> I think you mean to say 'add support for kernel configuration fragments',
> not 'kernel fragmentation'.  However, perhaps stating that you are adding
> support for scc description files would be more appropriate.
>
> I'm wondering why you are adding this abstraction to the base configuration.
> Is this the start of further customization following the linux-yocto model
> as described in the Yocto Project Linux Kernel Development Manual?  My
> impression of scc files is that they are useful for describing various
> features and BSPs.  They only seem to make sense if multiple scc files exist
> and can be chosen for various reasons.
>
> This single, particular scc file just describes the base kernel, so I'm
> wondering why it's being added now & if multiple scc files are going to
> follow for linux-qoriq.  If not, I think it just adds unneeded abstraction /
> complexity.

Agreed.  I think this is the direction to go in long term but I would
also expect a more complete set of scc files so it could be indeed
flexible.

> And will the use of scc files also be adopted in meta-fsl-arm / linux-imx?

I hope we do it in future. I didn't yet looked at it and I am not
aware of someone working on it yet.

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


More information about the meta-freescale mailing list