kernel module development problem with SDK

kernel module development problem with SDK

[György Kövesdi]

Hi,

I have poky at git hash 5686f4e1fe5229705b8c7d35895aa03827796d13 and I 
build for ARMv7.

I wanted to build my kernel module using the SDK generated this way:

     bitbake <my-image> -c populate_sdk

and the recipe kernel-devsrc is added to my sdk.

I found that the recipe meta/recipes-kernel/linux/kernel-devsrc.bb puts 
everything in the kernel source tree, except the following executables:

     scripts/recordmcount
     scripts/basic/fixdep
     scripts/mod/modpost

These would be essential for module development.

In the recipe kernel-devsrc.bb the following line

     oe_runmake -C $kerneldir CC="${KERNEL_CC}" LD="${KERNEL_LD}" clean 
_mrproper_scripts

removes everything, including the executables mentioned above.
IMHO it would be enough to run:

     oe_runmake -C $kerneldir CC="${KERNEL_CC}" LD="${KERNEL_LD}" clean

In this case the module development works properly with the resulting SDK.
Is the 'mrproper' really necessary? IMHO the 'clean' is enough there, 
because 'mrproper' removes too much.

Regards
Gyorgy Kovesdi

Re: kernel module development problem with SDK

[Bruce Ashfield]

On 09/13/2017 09:07 AM, György Kövesdi wrote:
> Hi,
> 
> I have poky at git hash 5686f4e1fe5229705b8c7d35895aa03827796d13 and I 
> build for ARMv7.
> 
> I wanted to build my kernel module using the SDK generated this way:
> 
>      bitbake <my-image> -c populate_sdk
> 
> and the recipe kernel-devsrc is added to my sdk.
> 
> I found that the recipe meta/recipes-kernel/linux/kernel-devsrc.bb puts 
> everything in the kernel source tree, except the following executables:
> 
>      scripts/recordmcount
>      scripts/basic/fixdep
>      scripts/mod/modpost
> 
> These would be essential for module development.
> 
> In the recipe kernel-devsrc.bb the following line
> 
>      oe_runmake -C $kerneldir CC="${KERNEL_CC}" LD="${KERNEL_LD}" clean 
> _mrproper_scripts
> 
> removes everything, including the executables mentioned above.
> IMHO it would be enough to run:
> 
>      oe_runmake -C $kerneldir CC="${KERNEL_CC}" LD="${KERNEL_LD}" clean
> 
> In this case the module development works properly with the resulting SDK.
> Is the 'mrproper' really necessary? IMHO the 'clean' is enough there, 
> because 'mrproper' removes too much.

The executables can't be packaged with the actual kernel source, since
we run into QA errors due to architecture mismatches.

Variants of this issue/concern have been around for several years now,
but since there are workarounds of simply re-creating the scripts
after SDK install, it hasn't been fixed to work out of the box.

So unfortunately, it isn't as simple as just leaving those scripts in
the devsrc package.

A couple of bugs that track work on this are:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=4389
https://bugzilla.yoctoproject.org/show_bug.cgi?id=6630

Bruce

> 
> Regards
> Gyorgy Kovesdi
> 
> 

Re: kernel module development problem with SDK

[György Kövesdi]

Hi,

I put them back and there is no problem if they are stripped. However, 
other versions of Poky may lead to QA error.


On 2017-09-13 15:39, Bruce Ashfield wrote:
> On 09/13/2017 09:07 AM, György Kövesdi wrote:
>> Hi,
>>
>> I have poky at git hash 5686f4e1fe5229705b8c7d35895aa03827796d13 and 
>> I build for ARMv7.
>>
>> I wanted to build my kernel module using the SDK generated this way:
>>
>>      bitbake <my-image> -c populate_sdk
>>
>> and the recipe kernel-devsrc is added to my sdk.
>>
>> I found that the recipe meta/recipes-kernel/linux/kernel-devsrc.bb 
>> puts everything in the kernel source tree, except the following 
>> executables:
>>
>>      scripts/recordmcount
>>      scripts/basic/fixdep
>>      scripts/mod/modpost
>>
>> These would be essential for module development.
>>
>> In the recipe kernel-devsrc.bb the following line
>>
>>      oe_runmake -C $kerneldir CC="${KERNEL_CC}" LD="${KERNEL_LD}" 
>> clean _mrproper_scripts
>>
>> removes everything, including the executables mentioned above.
>> IMHO it would be enough to run:
>>
>>      oe_runmake -C $kerneldir CC="${KERNEL_CC}" LD="${KERNEL_LD}" clean
>>
>> In this case the module development works properly with the resulting 
>> SDK.
>> Is the 'mrproper' really necessary? IMHO the 'clean' is enough there, 
>> because 'mrproper' removes too much.
>
> The executables can't be packaged with the actual kernel source, since
> we run into QA errors due to architecture mismatches.
>
> Variants of this issue/concern have been around for several years now,
> but since there are workarounds of simply re-creating the scripts
> after SDK install, it hasn't been fixed to work out of the box.
>
> So unfortunately, it isn't as simple as just leaving those scripts in
> the devsrc package.
>
> A couple of bugs that track work on this are:
>
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=4389
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=6630
>
> Bruce
>
>>
>> Regards
>> Gyorgy Kovesdi
>>
>>
>
>