From: Darren Hart <dvhart@linux.intel.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: yocto@yoctoproject.org
Subject: Re: How do I patch the kernel before it is built?
Date: Tue, 31 Jan 2012 08:54:41 -0800 [thread overview]
Message-ID: <4F281CD1.70305@linux.intel.com> (raw)
In-Reply-To: <4F281BFB.9010701@windriver.com>
On 01/31/2012 08:51 AM, Bruce Ashfield wrote:
> On 12-01-31 11:45 AM, autif khan wrote:
>> I could not find a way to patch the kernel source before its is built.
>>
>> I promise to update the Yocto wiki's How do I section when I have a
>> working solution for the following :-)
>
> This should be covered in the existing documentation and also the
> more general bitbake/oe-core docs.
>
>>
>> Here is what I am trying to do:
>>
>> 1) Patch the kernel (add VID/PID to hid_ignore_list in
>> drivers/hid/hid-core.c and also to add the VID/PID to .h file)
>> 2) Build the kernel - no change here - standard kernel build
>> 3) Build a kernel module
>>
>> I have a meta layer where I am keeping my changes. I am guessing that I need to:
>>
>> a) write a bbappend file to accomplish #1
>> b) write a recipe to accomplish #3
>>
>> I have written recipes before, but just for libraries and autotools
>> based applications. Not for a kernel module. If there is a recipe out
>> there for some other module, I would be happy to steal from it.
>>
>> Please advise how I can go about patching the kernel and if there is a
>
> It's just like any other package. If your changes are simple, then
> generating patches and putting them on the SRC_URI via a bbappend in
> your layer is all you need. If you have complex changes, there are options
> to manage them via git or via feature descriptions.
>
>> recipe for a kernel module - please point me to it.
>
> Darren validated and updated the kernel module example, so he'd probably
> got this closer at hand than I do.
See the hello-mod example under meta/recipes-kernel/hello-mod
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2012-01-31 16:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 16:45 How do I patch the kernel before it is built? autif khan
2012-01-31 16:51 ` Joshua Lock
2012-01-31 16:51 ` Bruce Ashfield
2012-01-31 16:54 ` Darren Hart [this message]
2012-02-06 19:35 ` autif khan
2012-02-06 19:39 ` Bruce Ashfield
2012-02-06 19:46 ` Bruce Ashfield
2012-02-06 20:18 ` autif khan
2012-02-06 20:24 ` Bruce Ashfield
2012-02-06 21:43 ` autif khan
2012-02-06 21:58 ` Bruce Ashfield
2012-02-06 22:10 ` autif khan
2012-02-07 1:20 ` Bruce Ashfield
2012-02-07 1:28 ` Bruce Ashfield
2012-02-07 19:01 ` autif khan
2012-02-08 15:31 ` autif khan
2012-02-09 14:39 ` Darren Hart
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=4F281CD1.70305@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=bruce.ashfield@windriver.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.