<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/documentation/kernel-dev/kernel-dev-common.xml, branch yocto-2.2.2</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=yocto-2.2.2</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=yocto-2.2.2'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2016-06-06T21:53:35+00:00</updated>
<entry>
<title>kernel-dev: Fix the locations of .config and source directory</title>
<updated>2016-06-06T21:53:35+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>srifenbark@gmail.com</email>
</author>
<published>2016-06-06T20:25:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=9c75c64cb99a3d5103b7bb4e2a700e5bb5af516b'/>
<id>urn:sha1:9c75c64cb99a3d5103b7bb4e2a700e5bb5af516b</id>
<content type='text'>
The locations of the kernel .config file and source direcotry
moved a couple releases ago.  Updated the documentation
accordingly.

Also added a note explaining how to check the expansion of
variables, which servs a couple of purposes:

 * For curious readers, shows them how to understand where
   these variables come from and how they are used.

 * For suspicious readers, shows them how they can verify that
   the variables in the documentation are actually correct.

Author: Tom Zanussi &lt;tom.zanussi@linux.intel.com&gt;
(From yocto-docs rev: a4f92870e70cb625f2987a59aff3f460457b4889)

Signed-off-by: Scott Rifenbark &lt;srifenbark@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>kernel-dev: Applied review comments to "Adding Recipe-Space Kernel Features"</title>
<updated>2016-04-06T22:11:58+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>srifenbark@gmail.com</email>
</author>
<published>2016-04-04T20:51:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=ee42a9b73e13b9b4356a0c50c67876b94f72a33b'/>
<id>urn:sha1:ee42a9b73e13b9b4356a0c50c67876b94f72a33b</id>
<content type='text'>
Fixes [YOCTO #4047]

I went through and fixed a few areas where reviewers said there
was "quirky" phrasing.  They might have been right in a few
places.

(From yocto-docs rev: 66fb97838f338ed3f787ec18f62702ef726ceffc)

Signed-off-by: Scott Rifenbark &lt;srifenbark@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>kernel-dev: Added new "Adding Recipe-Space Kernel Features" section.</title>
<updated>2016-04-06T22:11:57+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>srifenbark@gmail.com</email>
</author>
<published>2016-03-31T21:42:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=23dbf81eddb3c539875b29885ff52e2f116887ef'/>
<id>urn:sha1:23dbf81eddb3c539875b29885ff52e2f116887ef</id>
<content type='text'>
Fixes [YOCTO #4047]

I added a new section describing how to add kernel features
from within a kernel recipe through the KERNEL_FEATURES
variable and the SRC_URI statement.

(From yocto-docs rev: d30925c65e3f49b2ba481f1e7f9cac98fe86f6af)

Signed-off-by: Scott Rifenbark &lt;srifenbark@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>kernel-dev: Changed a link from an example to in-text.</title>
<updated>2016-03-23T21:56:09+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>srifenbark@gmail.com</email>
</author>
<published>2016-03-18T00:07:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=0654224f739a371f1de9411d5978582a44f3ff18'/>
<id>urn:sha1:0654224f739a371f1de9411d5978582a44f3ff18</id>
<content type='text'>
Better placement of this link.  It did not need to be in the
&lt;literallayout&gt; example.

(From yocto-docs rev: 53c33ea4cc929e016812f0d3aac0d302758dc0f8)

Signed-off-by: Scott Rifenbark &lt;srifenbark@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>kernel-dev: Added cross-reference to .config information</title>
<updated>2015-10-29T22:05:36+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>srifenbark@gmail.com</email>
</author>
<published>2015-10-27T15:54:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=a79e303c918883ef5fd2415de392a1cc3c35edd6'/>
<id>urn:sha1:a79e303c918883ef5fd2415de392a1cc3c35edd6</id>
<content type='text'>
Fixes [YOCTO #7474]

There was not a strong tie between .config file discussions
for the kernel between corresponding menuconfig sections in
the kernel-dev and dev-manual manuals.  I added a cross-
reference link in the kernel-dev manual to help tie this
information together.

(From yocto-docs rev: bbeb7b0f48be6c2bdb6c6031ce0476d6d2081f94)

Signed-off-by: Scott Rifenbark &lt;srifenbark@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>kernel-dev: Added 'make defconfig' details for own source work</title>
<updated>2015-07-28T17:02:32+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>scott.m.rifenbark@intel.com</email>
</author>
<published>2015-06-17T12:53:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=c3ac09f06e7af1bdaedc4bf6daf1c4019a1979e6'/>
<id>urn:sha1:c3ac09f06e7af1bdaedc4bf6daf1c4019a1979e6</id>
<content type='text'>
I added some detail about what really happens when you use the
'make defconfig' command when working with your own sources.

Fixes [YOCTO #6611]

(From yocto-docs rev: 653c7726e024dcaa908127f0df1d1856f26f4ff0)

Signed-off-by: Scott Rifenbark &lt;scott.m.rifenbark@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>kernel-dev: Added kernel-devsrc information for building on target</title>
<updated>2015-07-28T17:02:31+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>scott.m.rifenbark@intel.com</email>
</author>
<published>2015-06-01T14:31:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=926d70f9b90e6624578655a0af35db36203b8bdb'/>
<id>urn:sha1:926d70f9b90e6624578655a0af35db36203b8bdb</id>
<content type='text'>
I added a clarifying paragraph at the start of the section that talks
about building on the target hardware.  Included kernel-devsrc and
rationale for why a user would even do this (it is not normal).

(From yocto-docs rev: 5c42f981e9e54ae286b5ea5faf4dd29486c6350c)

Signed-off-by: Scott Rifenbark &lt;scott.m.rifenbark@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>kernel-dev: Added new requirement for working with yocto-linux-custom.bb</title>
<updated>2015-07-28T17:02:30+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>scott.m.rifenbark@intel.com</email>
</author>
<published>2015-05-26T20:17:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=5644756bc7abe3e4bc82ba28af1bce58bfd2f2ad'/>
<id>urn:sha1:5644756bc7abe3e4bc82ba28af1bce58bfd2f2ad</id>
<content type='text'>
Fixes [YOCTO #6611]

Added a new step to the "Working With Your Own Sources" section
so that the user is aware of needing to provide a defconfig file
or configuration fragments to the SRC_URI variable when working
with the yocto-linux-custom.bb recipe.

(From yocto-docs rev: dd25274979f689ae9135158279080add19a98393)

Signed-off-by: Scott Rifenbark &lt;scott.m.rifenbark@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>kernel-dev: Added new "in-tree" defconfig file section.</title>
<updated>2015-07-28T17:02:30+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>scott.m.rifenbark@intel.com</email>
</author>
<published>2015-05-18T22:31:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=f9df1a4473f116b0f16359be432497d3c8f7160e'/>
<id>urn:sha1:f9df1a4473f116b0f16359be432497d3c8f7160e</id>
<content type='text'>
I added the new section "Using an "In-Tree" defconfig File"
section.  This section addresses the ability to not use the
default location for defconfig files, which is usually in the
metadata layer.  The section describes how to use the
KBUILD_DEFCONFIG variable.

Fixes [YOCTO #7474]

(From yocto-docs rev: d68f7b47d974d94177b344247056778742f57786)

Signed-off-by: Scott Rifenbark &lt;scott.m.rifenbark@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>kernel-dev: Added detail to start of generating config file</title>
<updated>2015-07-28T17:02:30+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>scott.m.rifenbark@intel.com</email>
</author>
<published>2015-05-18T19:56:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=7b1697bd1583a28d49c1364de079a0f441671d41'/>
<id>urn:sha1:7b1697bd1583a28d49c1364de079a0f441671d41</id>
<content type='text'>
Fixes [YOCTO #7474]

The "Generating Configuration Files" section has a procedure that
starts with a step to complete a build at least through the
kernel configuration task.  This is needed but we could use a
bit of explanation here.  I added some rationale behind why you
should do this.

(From yocto-docs rev: 63df3474f4ed211dd6b7d1cf4f4e90bbc92c2595)

Signed-off-by: Scott Rifenbark &lt;scott.m.rifenbark@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
