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: Wed, 30 Apr 2014 14:44:18 -0400 [thread overview]
Message-ID: <53614482.8010102@windriver.com> (raw)
In-Reply-To: <ljlmib$45t$1@ger.gmane.org>
On 14-04-28 09:54 AM, Neuer User wrote:
> Am 28.04.2014 15:37, schrieb Bruce Ashfield:
>>
>> If you send me pointers to your bblayers and local.conf settings, I'll
>> run a build to see what happens here as well.
>>
>> I'm always interested in tracking these down regardless.
>>
>> Bruce
>>
>
> Testing this should be pretty straightforward, if see that correctly.
>
> Just init the repo with yocto master-next. Then export MACHINE=cubox-i.
>
> My layer has:
>
> recipes-kernel/linux/linux-cubox-i_3.0.35.bbappend:
Can you send me your bblayers out of band ? I'm using meta-fsl-arm
and meta-fsl-arm-extra to get a build going, and running into
expansion errors in the kernel recipes. Rather than hunt around
more than necessary, I'll check against your layers.
Bruce
>
> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
>
> inherit kernel
> COMPATIBLE_MACHINE_cubox-i = "(cubox-i)"
>
> SRC_URI += "file://videoin.cfg"
>
>
> And in recipes-kernel/linux/linux-cubox-i-3.0.35/videoin.cfg:
>
> CONFIG_VIDEO_ADV7180=y
>
> (for a test this should suffice)
>
> Then after a "bitbake linux-cubix-i -c configure" you can grep ADV7180
> in tmp/work/cubox_i-poky-linux-gnueabi/linux-cubox-i/3.0.35-r0/git/.config
>
> Normally it is "=n", now it should be "=y".
>
> Thanks
>
> Michael
>
next prev parent reply other threads:[~2014-04-30 18:44 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
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 [this message]
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=53614482.8010102@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.