Nice catch Otavio.
Also, a slightly better workflow (as opposed to directly modifying the defconfig
in the metadata) might be:
bitbake virtual/kernel -c cleansstate
bitbake virtual/kernel -c configure (unpack, patch, configure, etc.)
bitbake virtual/kernel -c menuconfig (make your changes to the kernel config
here)
bitbake virtual/kernel (build the kernel)
This allows you to configure the kernel with the correct defconfig, then modify
that using the menuconfig (which takes care of any dependencies). You can hack
away at that until you get it right (just don't bitbake clean it or your changes
will be wiped out).
When you're done reconfiguring:
bitbake virtual/kernel -c devshell -> takes you to the kernel source tree
unset LDFLAGS
make savedefconfig -> creates a reduced form of the defconfig
cp defconfig
fsl-community-bsp/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-wandboard-3.0.35
John
On 10/14/13 2:51 PM, Otavio Salvador wrote:
On Mon, Oct 14, 2013 at 4:26 PM, Joshua Kurland
<[email protected]> wrote:
I have posix mqueue enabled in the defconfig file in
source/meta-fsl-arm/recipes-kernel/linux/linux-imx-3.0.35/mx6q
CONFIG_POSIX_MQUEUE=y
CONFIG_POSIX_MQUEUE_SYSCTL=y
I used menuconfig to set the posix mqflags (bitbake -c menuconfig
linux-imx), the copied the .config from
tmp/work/wandboard_quad-poky-linux-gnueabi/linux-imx/3.0.35-r37.14/git
to the defconfig file mentioned above. I then ran bitbake -c
cleansstate linux-imx followed by bitbake myBuild. After I loaded the
image onto an SD card and booted the board, I used mq_overview to see
if posix message queue had been added properly (mkdir mqueuetest,
mount -t mqueue none mqueuetest). It was not found.
Am I missing a step? My target board is the Wandboard-quad.
Yes; you should change the linux-wandboard recipe, not linux-imx.
_______________________________________________
meta-freescale mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-freescale
