<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/documentation/kernel-dev, branch yocto-2.3.2</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=yocto-2.3.2</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=yocto-2.3.2'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2017-09-01T23:52:56+00:00</updated>
<entry>
<title>documentation: Preparation for 2.3.2 release</title>
<updated>2017-09-01T23:52:56+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>srifenbark@gmail.com</email>
</author>
<published>2017-08-21T20:32:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=d05391a7d47f034f5e55e0bac370fbadb901c8d2'/>
<id>urn:sha1:d05391a7d47f034f5e55e0bac370fbadb901c8d2</id>
<content type='text'>
poky.ent -&gt; Changed variables
mega-manual.sed -&gt; replaced 2.3.1 with 2.3.2
*.xml files -&gt; Updated manual revision tables for 2.3.2 and
               September 2017

(From yocto-docs rev: ce5bc517148f872e49d617fbfda7ae81c56efa04)

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: Updated "Creating and Preparing a Layer" section</title>
<updated>2017-09-01T23:52:56+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>srifenbark@gmail.com</email>
</author>
<published>2017-08-10T20:36:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=5af18d3753374ae5de917df0b364953b0b413ec0'/>
<id>urn:sha1:5af18d3753374ae5de917df0b364953b0b413ec0</id>
<content type='text'>
This section failed to mention the "yocto-layer create" script,
which is a simple way to create a layer.  I have added this info
into the section by way of a "Tip" box.

(From yocto-docs rev: 0bda177090ef624890e94a13e622e05923185fa9)

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>dev-manual: Updates to "Using .bbappend Files in Your Layer"</title>
<updated>2017-09-01T23:52:56+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>srifenbark@gmail.com</email>
</author>
<published>2017-08-07T22:30:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=d0c89b6d59840f900d1aa9bdde32197eef7cdbb1'/>
<id>urn:sha1:d0c89b6d59840f900d1aa9bdde32197eef7cdbb1</id>
<content type='text'>
I did some rewriting for clarity in the "Using .bbappend Files
in Your Layer" section.  The section needed to be retitled so
focus on the layer aspect of .bbappend files.  Also, while I
was in there, I did more work on the prose in general.

Also had to fix some links in the bsp, kernel, and ref manuals
that linked into the section whose name I changes.

(From yocto-docs rev: 27003c525a05ffa2f810a038c7c8f96bb7535986)

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>documentation: Prepared 2.3.1 release variables and dates</title>
<updated>2017-06-22T08:18:49+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>srifenbark@gmail.com</email>
</author>
<published>2017-06-06T14:07:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=484237aa97fd679ac2be494ee836b2bb4d0555f5'/>
<id>urn:sha1:484237aa97fd679ac2be494ee836b2bb4d0555f5</id>
<content type='text'>
poky.ent - updated variables for 2.3.1
mega-manual.sed - exchanged "2.3.1" for "2.3" for links
&lt;manual&gt;.xml - updated manual revision tables to use
               "June 2017" as the release date for 2.3.1

(From yocto-docs rev: 01d60d08a0c7371b8f7476f45fca89226caec680)

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: Provided better wording for recipe-space metadata section</title>
<updated>2017-03-31T11:14:18+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>srifenbark@gmail.com</email>
</author>
<published>2017-03-27T20:05:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=d7c537694614576b7967d3e73e9a404c92084fcc'/>
<id>urn:sha1:d7c537694614576b7967d3e73e9a404c92084fcc</id>
<content type='text'>
Fixes [YOCTO #10946]

Based on feedback, I made some minor rewrites to a sentence describing
when you need to use a different form to get BitBake to pick up
hierarchical data as kernel data.

(From yocto-docs rev: 65fcd23826e9a69152933f84cb3f8bac650cd4e5)

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>bsp-guide, kernel-dev: Updates to how kernel metadata is found</title>
<updated>2017-03-31T11:14:17+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>srifenbark@gmail.com</email>
</author>
<published>2017-03-27T16:17:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=ed0d609c7c40ad638f634a5e1822ab3bcc4e6681'/>
<id>urn:sha1:ed0d609c7c40ad638f634a5e1822ab3bcc4e6681</id>
<content type='text'>
Fixes [YOCTO #10946]

There was insufficient information in the combination of the
BSP Guide and the Kernel Development Manual on just how to locate
and use kernel metadata.

 * bsp-guide - Removed the detailed append file example for the
   kernel recipe.  This is moved now to the chapter in the kernel
   manual that describes append files.

 * kernel-dev - Placed the example from the BSP Guide into the
   section that describes kernel append files.  Cleaned up some
   terminology issues throughout chapter 3.  Added information
   about how BitBake picks up kernel metadata when the metadata
   is in a hierarchical directory and not just a simple *.scc
   file.

(From yocto-docs rev: 1048acb7127e77ca9c1f524a208fe25344fcb57c)

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: Reorganized Kernel Metadata Location and Syntax sections</title>
<updated>2017-03-24T23:44:03+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>srifenbark@gmail.com</email>
</author>
<published>2017-03-21T19:52:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=d9f293892174ffb8a7c3e3dc23e58f4ba1b09ee4'/>
<id>urn:sha1:d9f293892174ffb8a7c3e3dc23e58f4ba1b09ee4</id>
<content type='text'>
It seems that the two sections "Kernel Metadata Location" and
"Kernel Metadata Syntax" were flipped regarding their order of
apperance in the kernel-dev manual.  I belive that syntax should
be first and then followed by a discussion on the location.  I
have swapped these section's ordering in the manual.

(From yocto-docs rev: 167b088f459c7128bdc1abddd0b948be8f3bf5fe)

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: Corrected linking format for two variables.</title>
<updated>2017-03-24T23:44:03+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>srifenbark@gmail.com</email>
</author>
<published>2017-03-21T19:41:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=3f06074a0d7d576399ba65364ca71378602c8138'/>
<id>urn:sha1:3f06074a0d7d576399ba65364ca71378602c8138</id>
<content type='text'>
Convention is to avoid using hyperlinks for variables that appear
in &lt;literallayout&gt;/&lt;/literallalyout&gt; coded blocks.  I removed the
links for the KERNEL_FEATURES and LINUX_KERNEL_TYPE variables,
which appeared in a literal block and put the links into the
context of the description.

(From yocto-docs rev: 3384f67e4b9f15e8f96297ceb2aafc63a5994d22)

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>documentation: Added support for "pyro" name and May release date.</title>
<updated>2017-03-24T23:44:03+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>srifenbark@gmail.com</email>
</author>
<published>2017-03-21T17:19:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=b3e2ecaae2dda85b56e1e1017ba12c191a0dd7ea'/>
<id>urn:sha1:b3e2ecaae2dda85b56e1e1017ba12c191a0dd7ea</id>
<content type='text'>
poky.ent - changed the "tbd" and "TBD" strings to "pyro" and
           "Pyro", respectively.

Manual Head Files - Updated the manual history table with the
           May release month.

(From yocto-docs rev: 076226d2986d0cf69685121e4342f50c1603fc7b)

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>documentation: Updated "latest manual" note on title page</title>
<updated>2017-02-19T14:59:51+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>srifenbark@gmail.com</email>
</author>
<published>2017-02-03T18:52:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=77afd14e817677810868de82b77a4682052b6f95'/>
<id>urn:sha1:77afd14e817677810868de82b77a4682052b6f95</id>
<content type='text'>
Fixes [YOCTO #10076]

The note on the title page for each manual was brief regarding
where to find the latest version of the manual.  I updated the
note to have more detailed information on finding current,
alternate, and latest versions of the manual based on YP
releases.

(From yocto-docs rev: 0ec81465296a7a78309d3039af4d00caa52d2285)

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