Hi,
Did you by any chance figure this issue out?
It seems that I am having the same issue.
I can see that MT9P031 gets in .config in build directory that I
modified into defconfig for beagleboard in kernel-mainline's beagleboard
folder.
I would assume that it would have been compiled too when forced to do
so. eg. "normal" build does not seem to work:
bitbake virtual/kernel -c clean
bitbake virtual/kernel
It seems to have similar effect than you have eg. it did not build
anything. configure/compile/deploy did a more things but did not provide
any help either.
So nothing seem to produce mt9p031.ko anywhere nor create package for it.
If there is nothing else then I need to try out completely clean build
and do this mod before doing initial builds. Something weird somewhere
here. Or compile it inside the kernel. Or fallback to cross compiling
the kernel manually.
Thanks,
Vesa J��skel�inen
You can always call this in the kernel source dir:
make ARCH=arm CROSS_COMPILE=.../setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/bin/armv7a-angstrom-linux-gnueabi/arm-angstrom-linux-gnueabi-
modules
You need to update compiler path to reflect where bitbake build
compiler for you.
Hi Marek,
Thanks for the hint for cross-compiling.
I figured out that with command:
bitbake virtual/kernel -c compile_kernelmodules -f
I can build modules but still didn't figure out to package them.
My cycle were: clean, configure, compile, compile_kernelmodules, deploy
and lastly bitbake virtual/kernel and console-image.
At least I have now kernel modules in sysroot...
Smells like there is something wrong in meta-ti's configuration...
Thanks,
Vesa J��skel�inen
You can always call this in the kernel source dir:
make ARCH=arm CROSS_COMPILE=.../setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/bin/armv7a-angstrom-linux-gnueabi/arm-angstrom-linux-gnueabi-
modules
You need to update compiler path to reflect where bitbake build
compiler for you.
Hi Marek,
Thanks for the hint for cross-compiling.
I figured out that with command:
bitbake virtual/kernel -c compile_kernelmodules -f
I can build modules but still didn't figure out to package them.
-c package_write
My cycle were: clean, configure, compile, compile_kernelmodules, deploy
and lastly bitbake virtual/kernel and console-image.
At least I have now kernel modules in sysroot...
Smells like there is something wrong in meta-ti's configuration...
No, everything is working as expected.
Hi Koen,
You can always call this in the kernel source dir:
make ARCH=arm CROSS_COMPILE=.../setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/bin/armv7a-angstrom-linux-gnueabi/arm-angstrom-linux-gnueabi-
modules
You need to update compiler path to reflect where bitbake build
compiler for you.
Hi Marek,
Thanks for the hint for cross-compiling.
I figured out that with command:
bitbake virtual/kernel -c compile_kernelmodules -f
I can build modules but still didn't figure out to package them.
-c package_write
Tried that as "standalone" and that didn't do anything eg. all steps
were already done.
Then tried out:
bitbake virtual/kernel -c clean
bitbake virtual/kernel -c compile -f
bitbake virtual/kernel -c compile_kernelmodules -f
bitbake virtual/kernel -c package_write -f
bitbake virtual/kernel -c delpoy -f
bitbake virtual/kernel
bitbake console-image
and still I do not see the ipk for new kernel module that I added. .ko
is there so it is built but ipk packaging is somehow in weird state.
My cycle were: clean, configure, compile, compile_kernelmodules, deploy
and lastly bitbake virtual/kernel and console-image.
At least I have now kernel modules in sysroot...
Smells like there is something wrong in meta-ti's configuration...
No, everything is working as expected.
I would have expected that following would have been enough:
bitbake virtual/kernel -c clean
bitbake virtual/kernel
(or even without the clean)
So only thing I changed from initial build was the defconfig to include
the MT9P031 as module in building process.
Thanks,
Vesa J��skel�inen
Hi Koen,
You can always call this in the kernel source dir:
make ARCH=arm CROSS_COMPILE=.../setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/bin/armv7a-angstrom-linux-gnueabi/arm-angstrom-linux-gnueabi-
modules
You need to update compiler path to reflect where bitbake build
compiler for you.
Hi Marek,
Thanks for the hint for cross-compiling.
I figured out that with command:
bitbake virtual/kernel -c compile_kernelmodules -f
I can build modules but still didn't figure out to package them.
-c package_write
Tried that as "standalone" and that didn't do anything eg. all steps
were already done.
Then tried out:
bitbake virtual/kernel -c clean
Try using
bitbake virtual/kernel -c cleansstate
then the rest of your steps
Or increase PR as you're supposed to do when making changes that affect output packages. In this specific case: increase MACHINE_KERNEL_PR_append. If you don't, the buildsystem will use a cached version.