[yocto] kernel config and meta-altera
Hi all,
I'm rather new to the Yocto world so please bear with me. I built a Linux
kernel using the Altera "Golden System Reference Design" [1], which is a 1GB
tarball containing all required layers and all source code. Works fine.
Now I'd like to customize the image. Particularly I want to change the kernel
config to include the xHCI driver as a module [2]. I created a layer containing
a bbappend-file and a "config fragment" file. No success. Reading tons of
threads in the mailing list archive I figured that config fragments will not
work, because apparently the meta-altera layer inherits from "kernel" rather
than "linux-yocto".
So I tried the "defconfig" way, which I thought should work always. It turned
out that the defconfig file is correctly picked up and copied to $WORKDIR, but
simply not applied to .config there. After a long time of searching I figured
out that linux-altera.inc [3] apparently overwrites the do_configure task and
ignores any defconfig.
Eventually, the only solution I came up with, was a new task in my bbappend
file:
do_change_config() {
sed -i "s|^.*CONFIG_USB_XHCI_HCD.*$|CONFIG_USB_XHCI_HCD=m\\n#
CONFIG_USB_XHCI_HCD_DEBUGGING is not set|" .config
}
addtask change_config before do_compile after do_configure
This works, but I find it somehow ugly. Can you think of a better way to handle
this? Can I somehow add the "defconfig" or (even better) the "config fragments"
features to the meta-altera layer?
BR, Georg
[1] http://www.rocketboards.org/foswiki/Documentation/GSRD131YoctoUserManual
[2] CONFIG_USB_XHCI_HCD=m
[3]
https://github.com/kraj/meta-altera/blob/master/recipes-kernel/linux/linux-altera.inc
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Devshell configuration
Hi, Is there any way to pre-configure the yocto devshell? I mean settings like the following: * which shell is opened (bash, zsh, etc.), rather than the user's default shell * disable the fakeroot environment (this bothers me most of all) * in terminal mode to not open a screen session (often I already run screen and i don't want a second session inside) * to generally pass arguments to the shell when it is started Ideally I would imagine that I can somewhere configure the exact command that is called when I execute "bitbake xxx -c devshell". If that's not possible, can I at least change some of the points mentioned above? Thanks and best regards, Georg -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Selecting a preferred recipe version for devtools
Hi all, I have two recipes for building Subversion (which I only need as a devtool on the build-machine): $ ls oe-core/meta/recipes-devtools/subversion/*.bb subversion_1.6.15.bb subversion_1.7.8.bb Naturally Yocto uses 1.7.8, which is the newer. However, unfortunately I must use 1.6.15 on my build machine. How can I instruct Yocto to use the older version? I tried to put a variable PREFERRED_VERSION_subversion = "1.6.15" in my local.conf, but it turned out that this only affects the builds for the target-machine (cortexa8hf-vfp-neon-3.8-oe-linux-gnueabi), but not the devtools on the build-machine (x86_64-linux). One apparent solution is to simply remove the subversion_1.7.8.bb file, but I'm wondering if there is a better way, and how I can select a preferred version specifically for devtools. BR, Georg -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Selecting a preferred recipe version for devtools
Khem Raj wrote: >On Wed, Aug 12, 2015 at 6:48 AM, PIEWALD Georg > wrote: >> PREFERRED_VERSION_subversion = "1.6.15" >> >> in my local.conf, but it turned out that this only affects the builds for >> the target-machine (cortexa8hf-vfp-neon-3.8-oe-linux-gnueabi), but not the >> devtools on the build-machine (x86_64-linux). > > you might need to set preferred version for native extension as well. > PREFERRED_VERSION_subversion-native = "1.6.15" That did the trick, thanks a lot! Georg -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Modifying the OE-internal Python code
Hi, I'm trying to do some modifications in the OE-internals (just some personal customizations), in the Python code. In particular, I changed the file oe-core/meta/lib/oe/terminal.py I also compiled it into a terminal.pyc file. However, the modifications don't seem to be picked up by bitbake. Is there something more I have to do? Does the .pyc file have to be installed somewhere? Thanks for any hints, Georg -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Modifying the OE-internal Python code
> Paul Eggleton wrote: > On Tuesday 20 October 2015 21:07:15 PIEWALD Georg wrote: >> I'm trying to do some modifications in the OE-internals (just some personal >> customizations), in the Python code. In particular, I changed the file >> oe-core/meta/lib/oe/terminal.py >> I also compiled it into a terminal.pyc file. However, the modifications >> don't seem to be picked up by bitbake. Is there something more I have to >> do? Does the .pyc file have to be installed somewhere? > > There should be no need to explicitly build the pyc nor do anything special > for any changes to be recognised (assuming you're not using oe-init-build-env- > memres). Something must be going wrong in your setup somewhere. Perhaps an > unusual python path? Thanks for your answer! I looked at it more careful now, and indeed you are right, all changes are recognized implicitly. The problem was in the code that I modified, which was a no-op (and I learned something about Python). BR Georg -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
