On 2016-11-14 10:01 AM, Mert Can Ergun wrote:
Hi!
I am currently using a kernel bbappend file to build my kernel and kernel
modules. My bbappend file looks like this:
linux-imx_%.bbappend
SUMMARY = "Patches applied to Freescale kernel"
DESCRIPTION = "blank"
FILESPATH_prepend := "${THISDIR}/patches:"
SRC_URI += " \
file://defconfig-mt \
**patches for kernel modules appear here**
"
do_configure_prepend() {
cp ${WORKDIR}/defconfig-mt ${WORKDIR}/defconfig
}
However, this approach doesn't feel right and I want to seperate kernel
and its modules from each other at build.
If the kernel modules that you are patching and building are in-tree,
there's no problem with the architecture of what you have above. The
build process for in-tree modules is integrated with the main kernel
build.
What I tried to do is remove patches from the bbappend file and keep
defconfig file intact. Create a new bb file and put patches inside there
instead. So new architecture looks like this:
linux-imx_%.bbappend
SUMMARY = "Patches applied to Freescale kernel"
DESCRIPTION = "MT6415CA"
FILESPATH_prepend := "${THISDIR}/patches:"
SRC_URI += " \
file://defconfig-mt \
"
do_configure_prepend() {
cp ${WORKDIR}/defconfig-mt ${WORKDIR}/defconfig
}
mt-module_0.1.bb
SUMMARY = "Patches applied to Freescale kernel"
DESCRIPTION = "blank"
LICENSE = "GPLv2"
inherit module
FILESPATH_prepend := "${THISDIR}/patches:"
SRC_URI += " \
**patches appear here**
"
Now my kernel append module doesn't even apply defconfig changes and new
bb file doesn't do anything either. What's the right way to do this?
If you are patching the kernel source with this recipe, it needs to
match the name of your kernel recipe.
Bruce
-------------------------------
Mert Can Ergun
Yazilim Gelistirme Muhendisi
Mikro-Tasarim Ltd.
ODTU-Teknokent ODTU-MET Alani
A-1 Blok 4. Bolum Ofis 3/A
TR-06530 Ankara
T: +90 312 286 0103
F: +90 312 286 0104
U: www.mikro-tasarim.com.tr
E: mert.er...@mikro-tasarim.com.tr
-------------------------------
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
