From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Neuer User <auslands-kv@gmx.de>, <yocto@yoctoproject.org>
Subject: Re: Kernel config fragments are not applied
Date: Mon, 28 Apr 2014 09:03:20 -0400 [thread overview]
Message-ID: <535E5198.60709@windriver.com> (raw)
In-Reply-To: <ljl1vt$ink$1@ger.gmane.org>
On 14-04-28 04:03 AM, Neuer User wrote:
> Hello
>
> I am trying to add a custom kernel config to my layer. I followed the
> following guide:
> http://www.yoctoproject.org/docs/1.6/dev-manual/dev-manual.html#creating-config-fragments
>
> I have the following files in my layer:
>
> recipes-kernel/linux/linux-cubox-i_3.0.35.bbappend:
The answer to your question depends on the base linux-cubox-i
recipe.
Config fragment support works for kernels that inherit from linux-yocto,
versus ones that inherit directly from kernel.bbclass. So if you
pop open that base recipe, and look for a reference to linux-yocto.inc,
you'll have the answer.
It is possible to bbappend the linux-yocto support into the kernel
recipe via your layer, and might be worth a try.
The separation between the two classes exists to not break compatibility
with existing kernel recipes, or change long standing oe workflow with
the existing classes.
Cheers,
Bruce
>
> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
>
> inherit kernel
> COMPATIBLE_MACHINE_cubox-i = "(cubox-i)"
>
> SRC_URI += "file://videoin.cfg"
>
>
> recipes-kernel/linux/linux-cubox-i-3.0.35/videoin.cfg:
>
> CONFIG_VIDEOBUF_VMALLOC=y
> CONFIG_VIDEO_TVEEPROM=y
> CONFIG_VIDEO_TUNER=y
> CONFIG_VIDEO_ADV7180=y
> CONFIG_VIDEO_MXC_CAMERA=y
> CONFIG_MXC_TVIN_ADV7180=y
> CONFIG_USB_VIDEO_CLASS=y
> CONFIG_USB_GSPCA=y
> CONFIG_USB_M5602=y
> CONFIG_USB_STV06XX=y
> ...
>
> The layer is included in conf/bblayers.conf. The file videoin.cfg is
> found and "installed" in the correct tmp/work directory. However the
> config is never added to the kernel config file.
>
> What am I doing wrong?
>
> I use Yocto "master-next", cubox-i4pro.
>
> Thanks
>
> Michael
>
next prev parent reply other threads:[~2014-04-28 13:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 8:03 Kernel config fragments are not applied Neuer User
2014-04-28 13:03 ` Bruce Ashfield [this message]
2014-04-28 13:14 ` Neuer User
2014-04-28 13:16 ` Bruce Ashfield
2014-04-28 13:35 ` Neuer User
2014-04-28 13:37 ` Bruce Ashfield
2014-04-28 13:54 ` Neuer User
2014-04-30 18:44 ` Bruce Ashfield
2014-04-30 19:16 ` Neuer User
2014-04-30 19:21 ` Bruce Ashfield
2014-04-30 19:23 ` Neuer User
2014-04-30 21:08 ` Bruce Ashfield
2014-05-01 4:29 ` Bruce Ashfield
2014-05-01 6:32 ` Neuer User
2014-05-01 17:12 ` Bruce Ashfield
2014-05-02 17:24 ` Bruce Ashfield
2014-05-03 8:43 ` Neuer User
2014-04-30 10:24 ` Neuer User
2014-04-30 12:28 ` Bruce Ashfield
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=535E5198.60709@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=auslands-kv@gmx.de \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.