From: Neuer User <auslands-kv@gmx.de>
To: yocto@yoctoproject.org
Subject: Re: Kernel config fragments are not applied
Date: Sat, 03 May 2014 10:43:39 +0200 [thread overview]
Message-ID: <lk2a7r$kan$1@ger.gmane.org> (raw)
In-Reply-To: <5363D4E2.2080006@windriver.com>
That's great! And just one line to add. Perfect solution!
Thanks a lot!
Michael
Am 02.05.2014 19:24, schrieb Bruce Ashfield:
> On 14-05-01 01:12 PM, Bruce Ashfield wrote:
>> On 14-05-01 02:32 AM, Neuer User wrote:
>>> Hi Bruce
>>>
>>> Here is the error messega, I get after a "bitbake linux-cubox-i -c
>>> cleansstate; bitbake linux-cubox-i" using the recipe you posted:
>>
>> Aha. This is what I was seeing as well, and there's some issues and
>> assumptions
>> that are built into those kernel recipes that are causing the yocto
>> tools to attempt a patch (which is already on the branch) and hence
>> the failure (the recipes should really be tweaked .. but I digress).
>>
>> I'm prepping a small patch that will have this particular recipe and
>> use case working out of the box.
>
> ... and I managed to get this working without a patch. You just
> need the following as your bbappend:
>
> ----------------
> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
>
> inherit kernel
> require recipes-kernel/linux/linux-yocto.inc
>
> COMPATIBLE_MACHINE_cubox-i = "(cubox-i)"
>
> SRC_URI += "file://videoin.cfg"
>
> SRCREV_machine = "${SRCREV}"
> ----------------
>
> The key is the addition of SRCREV_machine. It deals with the issue
> that I mentioned with the kernel recipes. They have a series of patches
> that are already on the branch being built. But yet the SRCREV backs
> the branch off and allows the patches to apply (something I wouldn't
> do .. but that's not the point).
>
> The linux-yocto validation can do a similar back off, but it currently
> triggers on SRCREV_machine, which wasn't set .. this is already fixed
> in my current series that will go out for Yocto 1.7.
>
> After this:
>
> ]> pwd
> /home/bruce/poky/build/tmp/work/cubox_i-poky-linux-gnueabi/linux-cubox-i/3.0.35-r0
>
> yow-bashfiel-d3 [/home/bruc.../3.0.35-r0]> grep CONFIG_VIDEO_ADV7180
> linux-cubox_i-standard-build/.config
> CONFIG_VIDEO_ADV7180=y
>
> Note, the fragment you were working with needs this:
>
>> cat videoin.cfg
> CONFIG_VIDEO_CAPTURE_DRIVERS=y
> CONFIG_VIDEO_ADV7180=y
>
> Or you'll be missing a dependency and have the config dropped from
> the final .config.
>
> Bruce
>
next prev parent reply other threads:[~2014-05-03 8: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
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 [this message]
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='lk2a7r$kan$1@ger.gmane.org' \
--to=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.