From: Martin Ertsaas <martiert@gmail.com>
To: yocto@yoctoproject.org
Subject: Building linux-yocto kernel in own bsp layer
Date: Wed, 31 Jul 2013 09:21:12 +0200 [thread overview]
Message-ID: <51F8BAE8.3090805@gmail.com> (raw)
Hi.
I'm creating my own bsp layer for omap4 chips (Yes, I know of meta-ti,
but I want to learn how to do this myself :)). I'm trying to use the
linux-yocto 3.4 kernel,
and have gotten it to work locally. I then made a
linux-yocto_3.4.bbappend which contains the following:
COMPATIBLE_MACHINE_pandaboard = "pandaboard"
SRCREV_machine_pandaboard ?= "7eb5fbf903d9db90c3cf371b65e1f2a68d5676d7"
THISDIR := "${@os.path.dirname(bb.data.getVar('FILE', d, True))}"
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-3.4"
SRC_URI += "file://defconfig"
do_configure_prepend() {
cp ${WORKDIR}/defconfig ${S}/.config
}
Problem I get is, without this configure_prepend, my defconfig is not
copied into .config the kernel folder. With this however, I get a
complaint from the kernel that the kernel directory is not clean and I
have to run make mrproper.
I would greatly appreciate any pointer/help/explanations as to what I
have done wrong here, and how to fix it. Have been struggling for this
for a while now, and have no idea what I have done wrong.
Best regards
Martin Ertsaas
next reply other threads:[~2013-07-31 7:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 7:21 Martin Ertsaas [this message]
2013-07-31 8:57 ` Building linux-yocto kernel in own bsp layer Andrea Adami
2013-07-31 10:57 ` Martin Ertsaas
2013-07-31 12:42 ` Bruce Ashfield
2013-08-04 21:23 ` martiert
2013-08-05 3:03 ` Bruce Ashfield
2013-08-05 6:25 ` Martin Ertsaas
2013-08-07 16:31 ` martiert
2013-08-07 17:23 ` Bruce Ashfield
2013-08-08 6:04 ` Martin Ertsaas
2013-08-08 12:38 ` Bruce Ashfield
2013-08-11 5:12 ` Bruce Ashfield
2013-08-11 6:30 ` martiert
2013-08-11 6:51 ` martiert
2013-08-11 14:16 ` Bruce Ashfield
2013-07-31 9:11 ` Paul Eggleton
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=51F8BAE8.3090805@gmail.com \
--to=martiert@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.