<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/meta-skeleton, branch nanbield-4.3.2</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=nanbield-4.3.2</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=nanbield-4.3.2'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2023-09-22T06:45:17+00:00</updated>
<entry>
<title>recipes: Drop remaining PR values from recipes</title>
<updated>2023-09-22T06:45:17+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2023-09-20T15:35:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=1b94ea8b2516c929830fea716bb027a9ea1a3a1e'/>
<id>urn:sha1:1b94ea8b2516c929830fea716bb027a9ea1a3a1e</id>
<content type='text'>
We've been removing PR values from recipes at upgrade time for a while. In general
anyone maintaining a binary distro would end up having to curate these themselves
so the values in OE-Core aren't really that useful anymore. In many ways it makes
sense to clear out the remaining ones (which are mostly for 'config' recipes that
are unlikely to increase in PV) and leave a clean slate for anyone implementing
a binary distro config.

References are left in meta-selftest since the tests there do involve them and
their removal upon upgrade.

(From OE-Core rev: d4c346e8ab8f3cae25d1b01c7331ed9f6d4f96ef)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>layer.conf: Update to nanbield release series</title>
<updated>2023-09-10T07:58:53+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2023-09-10T07:58:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=eb7b8476eee1f9916f33a78ef8cb075cd3943a6d'/>
<id>urn:sha1:eb7b8476eee1f9916f33a78ef8cb075cd3943a6d</id>
<content type='text'>
(From OE-Core rev: f212cb12a0db9c9de5afd3cc89b1331d386e55f6)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>recipes/classes/scripts: Drop SRCPV usage in OE-Core</title>
<updated>2023-08-24T15:50:24+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2023-08-11T13:31:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=65318019cd8c6db19ae5d4526a0fa2d8c8ef25fa'/>
<id>urn:sha1:65318019cd8c6db19ae5d4526a0fa2d8c8ef25fa</id>
<content type='text'>
Now that SRCPV isn't needed we can simplify things in a few places...

(From OE-Core rev: 843f82a246a535c353e08072f252d1dc78217872)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>useradd-example: package typo correction</title>
<updated>2023-06-13T21:12:36+00:00</updated>
<author>
<name>Fabien Mahot</name>
<email>fabien.mahot@smile.fr</email>
</author>
<published>2023-06-13T15:33:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=34d73073a88c111a580e00e7fecf0f3d328c643f'/>
<id>urn:sha1:34d73073a88c111a580e00e7fecf0f3d328c643f</id>
<content type='text'>
Fixes [YOCTO #15143]

(From OE-Core rev: 9adffbb9b5fcd67d9c4e98d97bc459cbcc1b9c05)

Signed-off-by: Fabien Mahot &lt;fabien.mahot@smile.fr&gt;
Reviewed-by: Yoann Congal &lt;yoann.congal@smile.fr&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>baremetal-helloworld: Move from skeleton to recipes-extended matching what rust-hello-world is doing</title>
<updated>2023-01-12T23:08:58+00:00</updated>
<author>
<name>Alejandro Hernandez Samaniego</name>
<email>alejandro@enedino.org</email>
</author>
<published>2023-01-12T04:34:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=6bcbbd9ee3d2001cc26a4493aeb0d9cdd1b5239d'/>
<id>urn:sha1:6bcbbd9ee3d2001cc26a4493aeb0d9cdd1b5239d</id>
<content type='text'>
(From OE-Core rev: 13916de0145f83bb28323f0a6bde5c3d503c1319)

Signed-off-by: Alejandro Enedino Hernandez Samaniego &lt;alejandro@enedino.org&gt;
Signed-off-by: Alexandre Belloni &lt;alexandre.belloni@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>baremetal-helloworld: Enable x86 and x86-64 ports</title>
<updated>2023-01-12T23:08:58+00:00</updated>
<author>
<name>Alejandro Hernandez Samaniego</name>
<email>alejandro@enedino.org</email>
</author>
<published>2023-01-08T19:15:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=1149b4fbb6002aa5a4cfe90bd404834721593968'/>
<id>urn:sha1:1149b4fbb6002aa5a4cfe90bd404834721593968</id>
<content type='text'>
- The qemux86 port for helloworld-baremetal builds in the standard way, however,
  it uses NASM syntax for the startup code, hence we include a dependency to
  nasm-native, QEMU forces us to use an ELF file rather than a bin file to boot
  from this architecture using the -kernel parameter.

- QEMU refuses to boot using the -kernel parameter for files containing an ELF64
  header [1], instead, it requires a multiboot2 compatible image.

  We could create an image that contains a multiboot2 header by piggybacking
  into grub2-native, specifically grub-mkrescue, but it requires some extra
  runtime dependencies (xorriso which is currently part of meta-oe), and assumes
  a grub installation exists on the host.

  Due to host contamination and dependency complications, we dont rely on grub2,
  but rather do this process manually instead, the x86-64 port contains a stage1
  bootloader, stage2 bootloader and a 64 bit baremetal app (multiboot2
  compatible), booting into real (16 bit), protected (32 bit) and long (64 bit)
  modes, eventually running the helloworld-baremetal app. This is the reason why
  we need the code changes to use a separate Makefile, and create an image
  specifically for qemux86-64.

$ runqemu nographic
Booting from ROM..
Hello OpenEmbedded on x86!

$ runqemu nographic
Starting Stage 1 Bootloader
Loading Stage 2 Bootloader
Stage 2 Loaded.
Jumping to Stage2 Bootloader
In Stage 2
Done

Hello OpenEmbedded on x86-64!

[1] https://gitlab.com/qemu-project/qemu/-/blob/v7.2.0/hw/i386/multiboot.c#L199

(From OE-Core rev: 1dffd81b2991f90ab95cb36d8ff7626efd21434f)

Signed-off-by: Alejandro Enedino Hernandez Samaniego &lt;alejandro@enedino.org&gt;
Signed-off-by: Alexandre Belloni &lt;alexandre.belloni@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>layer.conf: Update to use mickledore as the layer series name</title>
<updated>2023-01-03T15:47:29+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2023-01-03T12:31:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=db47e8aa9e60adfec3f4201e66039bc513ab7cb2'/>
<id>urn:sha1:db47e8aa9e60adfec3f4201e66039bc513ab7cb2</id>
<content type='text'>
OE-Core has changes which do need careful evaluation for compatibilty,
such as the addpylib directive. Move the core later names to mickledore
so layers can mark their compatibility as such.

Also increase the version number for core. If we do make further changes
that need layer changes, we'll update the version again so layers can mark
compatibility within the series.

(From OE-Core rev: 57239d66b933c4313cf331d35d13ec2d0661c38f)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>useradd-example: do not use unsupported clear text password</title>
<updated>2022-09-29T20:15:50+00:00</updated>
<author>
<name>Chen Qi</name>
<email>Qi.Chen@windriver.com</email>
</author>
<published>2022-09-28T08:44:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=d96f13c40343b99818dfc692e87351865d9c85ba'/>
<id>urn:sha1:d96f13c40343b99818dfc692e87351865d9c85ba</id>
<content type='text'>
The clear text password support has been dropped. So let's just
use a normal ecrypted one. The password remains to be 'user3'.

(From OE-Core rev: cd8232f9c58980d95180ad320b7b0bb0fcfd9ff5)

Signed-off-by: Chen Qi &lt;Qi.Chen@windriver.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>skeleton/service: Ensure debug path handling works as intended</title>
<updated>2022-08-17T18:57:32+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2022-08-16T09:30:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=d63de87dd63b37d56e967db1d0703fdef291f181'/>
<id>urn:sha1:d63de87dd63b37d56e967db1d0703fdef291f181</id>
<content type='text'>
DEBUG_PREFIX_MAP uses ${S} but that wasn't set correctly for this
recipe meaning cwd during the build (WORKDIR) was encoded into the
binary leading to buildpath warnings in debug symbols. Set S correctly
to avoid this issue.

(From OE-Core rev: 299abc1d69db13924f02d922139051126f19b306)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>meta-skeleton/hello-mod: Switch to SPDX-License-Identifier</title>
<updated>2022-08-12T10:46:26+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2022-08-11T14:13:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=b5200793c26661797fe8845958d257c9297c6256'/>
<id>urn:sha1:b5200793c26661797fe8845958d257c9297c6256</id>
<content type='text'>
(From OE-Core rev: bb43462b0fcd510582c4c6f1081bb2f3f0c63843)

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