From: Jukka Rissanen <jukka.rissanen@linux.intel.com>
To: Diego Sueiro <diego.sueiro@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Custom defconfig is not used
Date: Wed, 30 Oct 2013 09:57:19 +0200 [thread overview]
Message-ID: <5270BBDF.8040905@linux.intel.com> (raw)
In-Reply-To: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
Hi Diego,
On 16.10.2013 00:07, Diego Sueiro wrote:
> Folks,
>
> I created the following bbapend recipe for linux-mainline_3.8.bb
> <http://linux-mainline_3.8.bb> (from meta-beagleboard on dylan branch)
> for beaglebone.
> meta-mine/recipes-kernel/linux/linux-mainline_3.8.bbappend:
>
> FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
> SRC_URI += " file://0019-mine.patch \
> file://defconfig \
> "
>
> But the defconfig and .config files on ${S} and ${WORKDIR} used are from
> meta-beagleboad, not from my bbappend.
I did this like this in
http://git.yoctoproject.org/cgit/cgit.cgi/meta-eca/tree/meta-eca-bsp/recipes-kernel/linux/linux-mainline_3.8.bbappend
FILESEXTRAPATHS_append := ":${THISDIR}/${PN}"
# netfilter stuff is missing from beaglebone kernel
SRC_URI_append_beaglebone += "file://netfilter.cfg"
do_configure_append_beaglebone () {
for i in ${S}/../*.cfg; do
echo "Adding ${i} to ${S}/.config"
cat ${i} >> ${S}/.config
done
yes '' | oe_runmake oldconfig
}
Seems to work just fine for me.
--
Cheers,
Jukka
next prev parent reply other threads:[~2013-10-30 7:57 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 21:07 Custom defconfig is not used Diego Sueiro
2013-10-15 21:29 ` Katu Txakur
2013-10-15 21:49 ` Rudolf Streif
2013-10-15 21:55 ` Andrea Adami
2013-10-16 17:25 ` Diego Sueiro
2013-10-16 18:19 ` Diego Sueiro
2013-10-17 3:56 ` Bruce Ashfield
2013-10-17 10:39 ` Diego Sueiro
2013-10-17 12:50 ` Bruce Ashfield
2013-10-17 13:15 ` Diego Sueiro
2013-10-17 13:19 ` Bruce Ashfield
2013-10-17 13:51 ` Andrea Adami
2013-10-17 15:47 ` Diego Sueiro
2013-10-18 4:48 ` Bruce Ashfield
2013-10-18 9:17 ` Diego Sueiro
2013-10-18 20:17 ` Bruce Ashfield
2013-10-22 16:23 ` Mike Lewis
2013-10-22 22:10 ` Bruce Ashfield
2013-10-24 0:17 ` Bruce Ashfield
2013-10-25 11:43 ` Diego Sueiro
2013-10-25 18:44 ` Bruce Ashfield
2013-10-26 1:19 ` Mike Lewis
2013-10-26 10:57 ` Diego Sueiro
2013-10-26 14:54 ` Bruce Ashfield
2013-10-28 20:58 ` Bruce Ashfield
2013-10-28 21:41 ` Mike Lewis
2013-10-29 10:33 ` Diego Sueiro
2013-10-29 11:00 ` Andrea Adami
2013-10-29 14:55 ` Diego Sueiro
2013-10-29 15:31 ` Diego Sueiro
2013-10-30 13:04 ` Bruce Ashfield
2013-10-30 13:54 ` Bruce Ashfield
2013-10-30 14:08 ` Diego Sueiro
2013-10-30 14:26 ` Bruce Ashfield
2013-11-04 3:14 ` Bruce Ashfield
2013-11-28 15:37 ` Diego Sueiro
2013-11-28 15:49 ` Bruce Ashfield
2013-11-28 16:26 ` Diego Sueiro
2013-11-28 16:28 ` Bruce Ashfield
2013-11-28 16:41 ` Paul Eggleton
2013-11-28 17:26 ` Bruce Ashfield
2013-10-30 7:57 ` Jukka Rissanen [this message]
2013-10-30 12:27 ` 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=5270BBDF.8040905@linux.intel.com \
--to=jukka.rissanen@linux.intel.com \
--cc=diego.sueiro@gmail.com \
--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.