<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/documentation/dev-manual, branch styhead-5.1.4</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=styhead-5.1.4</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=styhead-5.1.4'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2025-03-13T14:21:44+00:00</updated>
<entry>
<title>Remove all mention of core-image-lsb</title>
<updated>2025-03-13T14:21:44+00:00</updated>
<author>
<name>Ross Burton</name>
<email>ross.burton@arm.com</email>
</author>
<published>2025-03-03T17:20:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=a3f59d7e23af71f57025075c4dd781b4d95ce8d6'/>
<id>urn:sha1:a3f59d7e23af71f57025075c4dd781b4d95ce8d6</id>
<content type='text'>
core-image-lsb was removed in 2019[1], so remove all of the  incredibly
obsolete references in the documentation.

[1] oe-core fb064356af615d67d85b65942103bf943d84d290

(From yocto-docs rev: 9cc8bddc4d3ac0fd2c5dd4ecce582789bb5bd19c)

Signed-off-by: Ross Burton &lt;ross.burton@arm.com&gt;
Reviewed-by: Quentin Schulz &lt;quentin.schulz@cherry.de&gt;
Signed-off-by: Antonin Godard &lt;antonin.godard@bootlin.com&gt;
(cherry picked from commit 062445a49919eff117b5478c1fb18d125c1f895c)
Signed-off-by: Antonin Godard &lt;antonin.godard@bootlin.com&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>vulnerabilities/classes: remove references to cve-check text format</title>
<updated>2025-03-06T21:57:04+00:00</updated>
<author>
<name>Marta Rybczynska</name>
<email>rybczynska@gmail.com</email>
</author>
<published>2025-02-18T15:55:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=b2cf0d5cd0adb73708ce6035ce8611c0bc3860d5'/>
<id>urn:sha1:b2cf0d5cd0adb73708ce6035ce8611c0bc3860d5</id>
<content type='text'>
The text format has been removed, so also remove references and examples
using this format. Replace with examples with the JSON format.

(From yocto-docs rev: 08f4670ef7c7a2071f3634cbf0d9c3d0cd2dde3e)

Signed-off-by: Marta Rybczynska &lt;marta.rybczynska@ygreky.com&gt;
Signed-off-by: Antonin Godard &lt;antonin.godard@bootlin.com&gt;
(cherry picked from commit a52cd7bcadccc53e982f90d6e170d00798322597)
Signed-off-by: Antonin Godard &lt;antonin.godard@bootlin.com&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>dev-manual/building: document the initramfs-framework recipe</title>
<updated>2025-01-29T14:20:44+00:00</updated>
<author>
<name>Antonin Godard</name>
<email>antonin.godard@bootlin.com</email>
</author>
<published>2025-01-27T09:18:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=2a409637e10bd07d83a29390b2365f9c846bb15d'/>
<id>urn:sha1:2a409637e10bd07d83a29390b2365f9c846bb15d</id>
<content type='text'>
[ YOCTO #14747 ]

Adding a initramfs is a common task, and the way oe-core offers to do so
is by using the initramfs-framework recipe and companion modules. There
was already documentation on adding an initramfs but the documentation
was lacking details on this framework. Add it before the multiconfig
section because it is a bit more important IMO.

Reported-by: Alejandro &lt;alejandro@enedino.org&gt;
Reviewed-by: Quentin Schulz &lt;quentin.schulz@cherry.de&gt;
(From yocto-docs rev: 2df1f56e4863354f05a352d4f61cc797d85100db)

Signed-off-by: Antonin Godard &lt;antonin.godard@bootlin.com&gt;
(cherry picked from commit caedbca4eced4cf5bc74aaae64e4ad2887c2fc65)
Signed-off-by: Antonin Godard &lt;antonin.godard@bootlin.com&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>ref-manual: move runtime-testing section to the test-manual</title>
<updated>2025-01-09T14:02:49+00:00</updated>
<author>
<name>Antonin Godard</name>
<email>antonin.godard@bootlin.com</email>
</author>
<published>2024-12-26T15:20:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=e5b1aa3792e1a162ab584641cbe32d41d1b37c26'/>
<id>urn:sha1:e5b1aa3792e1a162ab584641cbe32d41d1b37c26</id>
<content type='text'>
In the same fashion as the previous commit ("ref-manual/packages: move
ptest section to the test-manual"), move the runtime testing section of
the development tasks manual to the test environment manual.

Add a link to it from the test-manual/intro document.

(From yocto-docs rev: 8ac3e2eb1dd4149b24af03666813dc6d94df466d)

Signed-off-by: Antonin Godard &lt;antonin.godard@bootlin.com&gt;
(cherry picked from commit 6b44257874858db3aa426d3e84a79c41cb4937a3)
Signed-off-by: Antonin Godard &lt;antonin.godard@bootlin.com&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>ref-manual/packages: move ptest section to the test-manual</title>
<updated>2025-01-09T14:02:49+00:00</updated>
<author>
<name>Antonin Godard</name>
<email>antonin.godard@bootlin.com</email>
</author>
<published>2024-12-26T15:20:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=587d779d563f93bdc5d4422923186befe4398520'/>
<id>urn:sha1:587d779d563f93bdc5d4422923186befe4398520</id>
<content type='text'>
[ YOCTO #15106 ]

It makes more sense to document ptests in the test-manual. Since ptests
are still related to packages, keep a link to ptests from packages.rst
to the test-manual.

Reported-by: Yoann Congal &lt;yoann.congal@smile.fr&gt;
(From yocto-docs rev: b79d1c8d501418d20c024c92b0ace755dd6b1c88)

Signed-off-by: Antonin Godard &lt;antonin.godard@bootlin.com&gt;
(cherry picked from commit b389c06b709e4791e1cce5e8a5b58f6b0cd03a14)
Signed-off-by: Antonin Godard &lt;antonin.godard@bootlin.com&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>dev-manual/bmaptool.rst: simplify and fix instructions</title>
<updated>2024-12-26T14:01:37+00:00</updated>
<author>
<name>Michael Opdenacker</name>
<email>michael.opdenacker@rootcommit.com</email>
</author>
<published>2024-12-18T14:47:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=d1b1b3275651f02b55bc0ffc2eeb34438c0c4a42'/>
<id>urn:sha1:d1b1b3275651f02b55bc0ffc2eeb34438c0c4a42</id>
<content type='text'>
- Remove duplicate instructions

- Detail how to run bmaptool directly if you installed it on your host
  instead of building it through the ``bmaptool-native`` recipe,
  as running "oe-run-native bmaptool-native bmaptool ..." won't work
  in this case.

- Use "chmod a+w" instead of "chmod 666", better advice,
  and only run "chmod" in the option that runs "oe-run-native"

(From yocto-docs rev: 8e6b07ffcc3aacee2244e064e09c27418017e414)

Signed-off-by: Michael Opdenacker &lt;michael.opdenacker@rootcommit.com&gt;
Reviewed-by: Antonin Godard &lt;antonin.godard@bootlin.com&gt;
Signed-off-by: Antonin Godard &lt;antonin.godard@bootlin.com&gt;
(cherry picked from commit 4afa71ef6e5bf1db126c80e6d987f588d0b5a086)
Signed-off-by: Antonin Godard &lt;antonin.godard@bootlin.com&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>dev-manual/bmaptool.rst: correct command for bmaptool-native</title>
<updated>2024-12-26T14:01:37+00:00</updated>
<author>
<name>Michael Opdenacker</name>
<email>michael.opdenacker@rootcommit.com</email>
</author>
<published>2024-12-18T14:47:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=4f8eb0e6382b5891385220bdcfe871b288b55936'/>
<id>urn:sha1:4f8eb0e6382b5891385220bdcfe871b288b55936</id>
<content type='text'>
Using only "bitbake bmaptool-native", running "oe-run-native bmaptool-native bmaptool ..."
fails as follows:

Error: Have you run 'bitbake bmaptool-native -caddto_recipe_sysroot'?

Running the "bitbake bmaptool-native -caddto_recipe_sysroot" target
is actually sufficient.

(From yocto-docs rev: 8c08d627127866194aea1ca19b1e4055fe5e7b9f)

Signed-off-by: Michael Opdenacker &lt;michael.opdenacker@rootcommit.com&gt;
Reviewed-by: Antonin Godard &lt;antonin.godard@bootlin.com&gt;
Signed-off-by: Antonin Godard &lt;antonin.godard@bootlin.com&gt;
(cherry picked from commit 72fe904a3bbb5e2c7279ab1f119c2beca200dcf2)
Signed-off-by: Antonin Godard &lt;antonin.godard@bootlin.com&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>dev-manual: fix styling of references to bmaptool</title>
<updated>2024-12-26T14:01:37+00:00</updated>
<author>
<name>Michael Opdenacker</name>
<email>michael.opdenacker@rootcommit.com</email>
</author>
<published>2024-12-18T14:47:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=e1c2e2e3faf68d68db1b3de40c3ed465eb7f867f'/>
<id>urn:sha1:e1c2e2e3faf68d68db1b3de40c3ed465eb7f867f</id>
<content type='text'>
To follow the styling conventions when we are
refering to the name of a tool instead of the command itself
(documentation/standards.md).

This also improves the HTML rendering of the bmaptools subsection.

(From yocto-docs rev: f8bf503b13a53fb0b34c1fdac92d78d66813abfb)

Signed-off-by: Michael Opdenacker &lt;michael.opdenacker@rootcommit.com&gt;
Reviewed-by: Antonin Godard &lt;antonin.godard@bootlin.com&gt;
Signed-off-by: Antonin Godard &lt;antonin.godard@bootlin.com&gt;
(cherry picked from commit c569d840c4b6f43e10629b6f1ff45189211e27a9)
Signed-off-by: Antonin Godard &lt;antonin.godard@bootlin.com&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>Update the documentation for SRCPV</title>
<updated>2024-12-26T14:01:37+00:00</updated>
<author>
<name>Antonin Godard</name>
<email>antonin.godard@bootlin.com</email>
</author>
<published>2024-12-09T16:43:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=e82dc2ad3c04a1499c0ea68295a94920151958f3'/>
<id>urn:sha1:e82dc2ad3c04a1499c0ea68295a94920151958f3</id>
<content type='text'>
The variable SRCPV is deprecated since 4.3. Instead of including SRCPV
in PV, including the sign "+" is enough for bitbake to add the source
control information to PKGV during the packaging phase.

Update the documentation for SRCPV and the places where it was used.
When instructions previously referred to SRCPV, replace by mentioning to
include "+" in the assignment.

In most examples, "+git" is added to PV as it is the most popular SCM.
Simply adding "+" is also possible, although it is better practice to
include the SCM name, so give that example.

Update the gcompat example with l3afpad as it didn't include "+git" in
its PV definition anymore.

(From yocto-docs rev: 3866c09cc0460d25fefc0c831affd89633cf8a7b)

Signed-off-by: Antonin Godard &lt;antonin.godard@bootlin.com&gt;
(cherry picked from commit ee16c96202e5027d1a8d7e89e11c25f127c78326)
Signed-off-by: Antonin Godard &lt;antonin.godard@bootlin.com&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>dev-manual: bblock: use warning block instead of attention</title>
<updated>2024-11-26T13:37:10+00:00</updated>
<author>
<name>Antonin Godard</name>
<email>antonin.godard@bootlin.com</email>
</author>
<published>2024-11-14T15:02:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=4d44b6b9ffd58e630febb86503e6b6e5886a94ca'/>
<id>urn:sha1:4d44b6b9ffd58e630febb86503e6b6e5886a94ca</id>
<content type='text'>
Sphinx recommends using warning and note here:
https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html#directives

Suggested-by: Quentin Schulz &lt;quentin.schulz@cherry.de&gt;
Reviewed-by: Quentin Schulz &lt;quentin.schulz@cherry.de&gt;
(From yocto-docs rev: 8288c8cae7fe7303e89d8ed286de91fc26ce6cc3)

Signed-off-by: Antonin Godard &lt;antonin.godard@bootlin.com&gt;
(cherry picked from commit ed49067f172637d38d470a864feed2a02bd84c66)
Signed-off-by: Antonin Godard &lt;antonin.godard@bootlin.com&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
</feed>
