[linux-yocto] Linux-yocto-custom and meta-data

[Darren Hart]

On 10/15/2012 04:56 PM, Bruce Ashfield wrote:
> On 12-10-15 7:47 PM, Darren Hart wrote:
>>
>>
>> On 10/15/2012 04:42 PM, Bruce Ashfield wrote:
>>> On 12-10-15 7:26 PM, Darren Hart wrote:
>>>> I've got a customer that insists on using their own kernel version, but
>>>> doesn't want to keep their config in recipe-space. I already have them
>>>> using linux-yocto-custom with a linux 3.5 based git repository. Seems to
>>>> me the best way to address this would be for them to create a meta
>>>> directory in their master branch which contains their BSP definition. Is
>>>> it as simple as the following?
>>>>
>>>>     $ tree meta
>>>>
>>>>     meta/cfg/kernel-cache/bsp/common-pc
>>>>     └── cfg
>>>>         └── kernel-cache
>>>>             └── bsp
>>>>                 └── mybsp
>>>>                     ├── mybsp.cfg
>>>>                     └── mybsp.scc
>>>>
>>>> Where mybsp.scc is:
>>>>
>>>>     define KMACHINE mybsp
>>>>     define KARCH i386
>>>>     kconf hardware mybsp.cfg
>>>>
>>>> This doesn't define any kernel types, would we need to do that, or can
>>>> the tools deal with that?
>>>
>>> The tools want to search by kmachine + ktype. In theory they can just
>>> search on one and get the best match, so taking the default ktype of
>>> standard *should* work (and not specifying it in the .scc, but it
>>> should still be passed to the tools).
>>
>>
>> So if I specify KTYPE=standard and MACHINE=mybsp, then I should be able
>> to get away with:
>>
>>
>>     meta
>>     └── cfg
>>         └── kernel-cache
>>             └── bsp
>>                 └── mybsp
>>                     ├── mybsp.cfg
>>                     └── mybsp-standard.scc
>>
>> Note the mybsp-standard.scc name, and the lack of a
>> ktype/standard/standard.scc.
> 
> Yep. Both are ok, and you don't even need to call it -standard.scc,
> since the file name isn't searched, only the contents for the right
> ktype/kmachine that best matches the machine+ktype passed down from
> the build system.

Ah, so mybsp.scc should contain:

  define KMACHINE mybsp
  define KARCH i386
  define KTYPE standard
  kconf hardware mybsp.cfg

I'm going to try to test this tonight, but I may not be able to get to it.

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel