From: Mark Hatle <mark.hatle@windriver.com>
To: Juro Bystricky <juro.bystricky@intel.com>,
<openembedded-core@lists.openembedded.org>,
<jurobystricky@hotmail.com>
Cc: richard.purdie@intel.com
Subject: Re: [PATCH 0/2] Support for VirtualBox guest additions
Date: Tue, 4 Aug 2015 11:20:01 -0500 [thread overview]
Message-ID: <55C0E631.7070703@windriver.com> (raw)
In-Reply-To: <1438634128-4347-1-git-send-email-juro.bystricky@intel.com>
On 8/3/15 3:35 PM, Juro Bystricky wrote:
> In order to support VirtualBox guest additions, kernel headers need to be present
> in the VM. I am aware we already have two packages/recipes that are somewhat similar
> (kernel-devsrc.bb, linux-libc-headers), but none of them is suitable for this purpose.
> Besides the kernel headers, some additional files (scripts, Makefiles, .config, etc)
> are also required.
linux-libc-headers is only for building applications. kernel-devsrc is for
building modules on the target.
What do these specific modules need that are not present in kernel-devsrc? (I
really don't want 'yet another' confusing package added to the system.)
> The new recipe "kernel-headers.bb" can in principle be used by other images as well.
> It is not limited to the Build Appliance and hence is not a part of the Build Appliance
> recipe.
I think kernel-headers is a bad name for a package. It could be confusing.
--Mark
> Juro Bystricky (2):
> kernel-headers: linux kernel headers
> build-appliance-image: support for VirtualBox guest addtions
>
> .../README_vbox_guest_additions.txt | 78 ++++++++++++++++++++++
> .../images/build-appliance-image_12.0.1.bb | 4 +-
> meta/recipes-kernel/linux/kernel-headers.bb | 66 ++++++++++++++++++
> 3 files changed, 147 insertions(+), 1 deletion(-)
> create mode 100644 meta/recipes-core/images/build-appliance-image/README_vbox_guest_additions.txt
> create mode 100644 meta/recipes-kernel/linux/kernel-headers.bb
>
next prev parent reply other threads:[~2015-08-04 16:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 20:35 [PATCH 0/2] Support for VirtualBox guest additions Juro Bystricky
2015-08-03 20:35 ` [PATCH 1/2] kernel-headers: linux kernel headers Juro Bystricky
2015-08-04 4:37 ` Christopher Larson
2015-08-04 16:06 ` Bystricky, Juro
2015-08-05 2:20 ` Bruce Ashfield
2015-08-26 17:55 ` Josh Cartwright
2015-08-26 17:57 ` Bruce Ashfield
2015-08-26 18:11 ` Josh Cartwright
2015-08-03 20:35 ` [PATCH 2/2] build-appliance-image: support for VirtualBox guest addtions Juro Bystricky
2015-08-04 4:37 ` Christopher Larson
2015-08-04 16:08 ` Bystricky, Juro
2015-08-04 16:20 ` Mark Hatle [this message]
2015-08-04 17:25 ` [PATCH 0/2] Support for VirtualBox guest additions Bystricky, Juro
2015-08-04 17:32 ` Mark Hatle
2015-08-04 19:10 ` Bystricky, Juro
2015-08-04 19:22 ` Mark Hatle
2015-08-04 21:27 ` Bystricky, Juro
2015-08-04 21:31 ` Otavio Salvador
2015-08-05 2:24 ` Bruce Ashfield
2015-08-05 2:24 ` Bruce Ashfield
2015-08-05 2:43 ` Bruce Ashfield
2015-08-05 2:48 ` Bruce Ashfield
2015-08-05 22:02 ` Bystricky, Juro
2015-08-06 2:09 ` Bruce Ashfield
2015-08-06 2:20 ` Khem Raj
2015-08-07 22:13 ` Bystricky, Juro
2015-08-08 1:09 ` Bruce Ashfield
2015-08-08 17:36 ` Bystricky, Juro
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=55C0E631.7070703@windriver.com \
--to=mark.hatle@windriver.com \
--cc=juro.bystricky@intel.com \
--cc=jurobystricky@hotmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox