Problem building the linux kernel outside source directory for mips
Hi,
I am new to yocto, so I don't know if this is the right list.
I tried to build a kernel for the MTX-1 platform that uses an AU1500 which is a MIPS32 based SoC. After some work I got the standard kernel (3.8.4) used in poky 9 to work.
But I encountered some problems:
In poky-dylan-9.0.0/meta/recipes-kernel/linux/linux-yocto.inc the builddir is set to "${WORKDIR}/linux-${MACHINE}-${LINUX_KERNEL_TYPE}-build", but KERNEL_EXTRA_ARGS does not contain O="${B}". How is the the out of source build of the kernel meant to work?
The task do_kernel_configme trashed my kernel config. This may be because defconfig is copied to ${B}/.config and do_kernel_configme is executed in ${S} and does not find .config.
Is the intended behavior of the out of source build for the kernel documented.
BTW: The kernel works and boots the core-image-minimal with usb USB Storage as rootfs.
Best regards
Michael
Quoted 3 lines · Michael Stickel
Hi,
I am new to yocto, so I don't know if this is the right list.
This will work, we also have the [email protected] kernel mailing list.
Quoted 11 lines
I tried to build a kernel for the MTX-1 platform that uses an AU1500 which is a MIPS32 based SoC.
After some work I got the standard kernel (3.8.4) used in poky 9 to work. But I encountered some problems:In poky-dylan-9.0.0/meta/recipes-kernel/linux/linux-yocto.inc the builddir is set to "${WORKDIR}/linux-${MACHINE}-${LINUX_KERNEL_TYPE}-build", but
KERNEL_EXTRA_ARGSdoes not contain O="${B}". How is the the out of source build of the kernel meant to work?
Can you elaborate on this ? Are you actually seeing a problem, or just wondering about the glue ? If it's the glue, kernel-yocto.bbclass sets:
KBUILD_OUTPUT = "${B}"
For the desired source/binary split.
Quoted 4 lines
The task
do_kernel_configmetrashed my kernel config. This may be because defconfig is copied to ${B}/.config anddo_kernel_configmeis executed in ${S} and does not find .config.
Same question as above. This is basic functionality and kernel_configme is aware of the source/binary split, and has been doing this since yocto 0.9.
Can you define "trashed" ?
Quoted 3 lines
Is the intended behavior of the out of source build for the kernel documented.
Everything should be in the kernel-dev manual and the other yocto project documentation. There's not that much to document, since the functionality has been unchanged for quite some time and works behind the scenes for a linux-yocto* based build.
Cheers,
Bruce
Quoted 10 lines
BTW: The kernel works and boots the core-image-minimal with usb USB Storage as rootfs.
Best regards
Michael
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
Quoted 1 line · Bruce Ashfield
Can you define "trashed" ?
My defconfig is for mips and the .config file was for x86.
But I will dig into the documentation you mentioned first and try to find out what I did wrong and come back later.
Best Regards
Michael
PS: Sorry for the PM, wrong address.
Quoted 4 lines · Michael Stickel
Quoted 1 line · Bruce Ashfield
Can you define "trashed" ?
My defconfig is for mips and the .config file was for x86.
Hmmm. That should definitely not happen, unless the wrong BSP description is being picked up and built. Is this the qemumips BSP, or something custom ?
Quoted 4 lines
But I will dig into the documentation you mentioned first and try to find out what I did wrong and come back later.
Sounds good. I'll wait to hear more.
Cheers,
Bruce
Quoted 8 lines
Best Regards
Michael
PS: Sorry for the PM, wrong address.
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto