From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Javi Roman <javiroman@kernel-labs.org>
Cc: yocto@yoctoproject.org
Subject: Re: Custom kernel in Yocto/dylan branch.
Date: Tue, 11 Jun 2013 11:21:27 -0400 [thread overview]
Message-ID: <51B74077.4050902@windriver.com> (raw)
In-Reply-To: <CACWQdqC6UwX7jYgxp-aRE4pUBz3G=npAAyBRuv3OJQQ_9Y4X_w@mail.gmail.com>
On 13-06-11 10:47 AM, Javi Roman wrote:
> With
>
> SRC_URI_append = "file://defconfig"
>
Which is what I expected. And you say that it isn't being applied
at all ? Is that by inspecting the final contents of .config ?
Or something else ?
Since this is on the dylan branches, I know it has been tested
explicitly there.
I'll switch and do some of my own test builds.
Cheers,
Bruce
>
> Javi Roman
>
>
> On Tue, Jun 11, 2013 at 4:23 PM, Bruce Ashfield
> <bruce.ashfield@windriver.com> wrote:
>> On 13-06-11 10:18 AM, Javi Roman wrote:
>>>
>>> Hi!
>>>
>>>
>>> I few years ago I used to work with OpenEmbedded (the classical
>>> branch). The addition of new kernel recipes was easy for me,
>>> nevertheless I'm unable to do similar things with the current
>>> Yocto-dylan branch.
>>>
>>> The current Yocto-dylan is based on Linux kernel 3.x branches, all the
>>> documentation regarding add custom kernels or new kernel features are
>>> based on those 3.x branches. However, I would like to use a 2.6.32
>>> Linux kernel (it's a constraint for my project).
>>>
>>> I'm using the following kernel recipe in my bsp:
>>>
>>> linux/
>>> linux-yocto-abacus/
>>> defconfig
>>> linux-yocto-abacus_2.6.32.bb
>>>
>>> ##### linux-yocto-abacus_2.6.32.bb ####
>>>
>>> inherit kernel
>>> require recipes-kernel/linux/linux-yocto.inc
>>>
>>> INHIBIT_PACKAGE_DEBUG_SPLIT =3D "1"
>>>
>>> FILESEXTRAPATHS_prepend :=3D "${THISDIR}/${PN}:"
>>> SRC_URI_append =3D "file://defconfig"
>>>
>>> PROVIDES =3D "virtual/kernel"
>>>
>>> SRC_URI =3D
>>> "git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.g=
>>> it;protocol=3Dgit;nocheckout=3D1"
>>>
>>> LINUX_VERSION =3D "2.6.32"
>>> LINUX_VERSION_EXTENSION =3D "-abacus"
>>>
>>> # tag: v3.4 76e10d158efb6d4516018846f60c2ab5501900bc
>>> # tag: v2.6.32 459b3d520991ec1b8e5ba68fbc4b206d602fee6e
>>> SRCREV=3D"459b3d520991ec1b8e5ba68fbc4b206d602fee6e"
>>>
>>> PR =3D "r1"
>>> PV =3D "${LINUX_VERSION}+git${SRCPV}"
>>>
>>> COMPATIBLE_MACHINE =3D "romley"
>>>
>>> ############ end ###################
>>>
>>> When I build the kernel with:
>>>
>>> # bitbake virtual/kernel
>>>
>>> The kernel is downloaded from kernel.org, with the correct git tag
>>> (v2.6.32) and is built with success. Nevertheless, the "defconfig" is
>>> not properly added in the kernel configuration. If I run:
>>>
>>> # bitbake virtual/kernel -c menuconfig
>>>
>>> The ncurses menuconfig is not using the "defconfig" added by me.
>>>
>>> The "defconfig" with all kernel configurations is a deprecated feature?
>>> Which is the correct way to add a new kernel recipe?
>>
>>
>> It definitely should still be working, we have plenty of defconfig
>> users (whether right or wong ;) and it is tested daily.
>>
>> How did you specify your defconfig on the SRC_URI ?
>>
>> Bruce
>>
>>>
>>> Many thanks!
>>> Javi Roman
>>> _______________________________________________
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>>>
>>
next prev parent reply other threads:[~2013-06-11 15:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 14:18 Custom kernel in Yocto/dylan branch Javi Roman
2013-06-11 14:23 ` Bruce Ashfield
2013-06-11 14:47 ` Javi Roman
2013-06-11 15:21 ` Bruce Ashfield [this message]
2013-06-11 15:34 ` Paul Eggleton
2013-06-12 12:37 ` Javi Roman
2013-06-12 12:49 ` 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=51B74077.4050902@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=javiroman@kernel-labs.org \
--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.