Hello people,

I guess, this stuff is well known to the experts and community, but not
entirely to me, considering YOCTO setup. So I apologize for repeating the
topic.

So I took Sumo branch, advanced my BeagleBone Black bare-bone image, and
recompiled the whole Beaglebone Black for the core-image-minimal .

After doing that, and fixing some miss-configuration of some layers, I got
very interesting results.

The zImage (compressed kernel) is only 1MB of size:
1240848 Jul 10 15:16 zImage--4.17.2-r0-beaglebone-20180710124751.bin

To explore that, I issued the following command:
bitbake virtual/kernel -c devshell

and (obvious to me) found the following:

root@localhost:~/projects/beaglebone-black/yocto-rocko/poky/build/tmp/work-shared/beaglebone/kernel-build-artifacts#
ls -al
total 448
drwxr-xr-x 4 1377009974 1377000513   4096 Jul 10 13:16 .
drwxr-xr-x 4 1377009974 1377000513   4096 Jul 10 13:16 ..
drwxr-xr-x 3 1377009974 1377000513   4096 Jul 10 13:16 arch
-rw-r--r-- 1 1377009974 1377000513  30043 Jul 10 13:16 .config
drwxr-xr-x 4 1377009974 1377000513   4096 Jul 10 13:16 include
-rw-r--r-- 1 1377009974 1377000513     15 Jul 10 13:16 kernel-abiversion
-rw-r--r-- 1 1377009974 1377000513      0 Jul 10 13:16 Module.symvers
-rw-r--r-- 1 1377009974 1377000513 404070 Jul 10 13:16
System.map-4.17.2-jumpnow

As we  see, no any modules (Module.symvers size is 0) encountered, and tiny
default .config (30043 Jul 10 13:16 .config).

Now, for the very first time using YOCTO build system, I have to have
modules.tgz included into the build.

What should I do to:
[1] swap default tiny defconfig with my defconfig (which is 6x of the
default size with 2000+ kernel modules defined in it)?
[2] How to include module definition in the final build using bitbake, or
.../meta/recipes-core/images/core-image-minimal.bb (any premeditated
examples)?

Thank you,
Zoran
-- 
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to