<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/meta-yocto-bsp/conf/machine, 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>2024-08-07T14:48:27+00:00</updated>
<entry>
<title>yocto-bsp: set temporary preferred version for genericarm64</title>
<updated>2024-08-07T14:48:27+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@gmail.com</email>
</author>
<published>2024-08-06T18:55:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=1e9f886d76262c74176c8bf8f0691d64b5cc9ceb'/>
<id>urn:sha1:1e9f886d76262c74176c8bf8f0691d64b5cc9ceb</id>
<content type='text'>
We want to introduce the 6.10 linux-yocto recipe, but genericarm64
hasn't been valided for it yet. As such, let's temporarily set the
preferred version to 6.6 so the builds don't break.

(From meta-yocto rev: 6ba3b6f15bf2460432da3a3aee782976e778381c)

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>genericarm64: depend on u-boot in testimage</title>
<updated>2024-05-21T11:09:05+00:00</updated>
<author>
<name>Ross Burton</name>
<email>ross.burton@arm.com</email>
</author>
<published>2024-05-20T15:37:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=98471a91e8d74203e0c22aa933bed97e764bb8e2'/>
<id>urn:sha1:98471a91e8d74203e0c22aa933bed97e764bb8e2</id>
<content type='text'>
genericarm64 supports runqemu, so testimage should work. However, out of
the box it does not:

runqemu - ERROR - BIOS .../tmp/deploy/images/genericarm64/u-boot.bin not found

That is because we make the user explicitly build the qemu-targetting u-boot
to avoid the confusing situation where they have real hardware but the
deploy directory contains a u-boot for qemu.

In automated testing situations, however, we can be a bit more helpful
and make testimage depend on u-boot. This will lead to u-boot binaries
being in deploy, but at this point the user is already running the images
inside a qemu.

Reported-by: James McGregor &lt;James.McGregor2@arm.com&gt;
(From meta-yocto rev: 90b45c62d34396a20078b55d7d36f66b4e2177f7)

Signed-off-by: Ross Burton &lt;ross.burton@arm.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>yocto-bsp/genericarm64: add virtio-gpu</title>
<updated>2024-04-08T22:33:53+00:00</updated>
<author>
<name>Jon Mason</name>
<email>jdmason@kudzu.us</email>
</author>
<published>2024-04-05T15:41:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=1fb353995c7fbfaa9f1614ed52a4a6aa04ccae5a'/>
<id>urn:sha1:1fb353995c7fbfaa9f1614ed52a4a6aa04ccae5a</id>
<content type='text'>
testimage on core-image-sato fails in parselogs and xorg tests.  We can
add the virtio gpu to address these issues (like what is being done in
qemuarm, qemuarm64, and qemuarmv5).

(From meta-yocto rev: ddf075e2abfba6479efc2bc5fe1c41ba6079e355)

Signed-off-by: Jon Mason &lt;jdmason@kudzu.us&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>genericarm64: add qemuboot configuration</title>
<updated>2024-03-23T10:19:00+00:00</updated>
<author>
<name>Ross Burton</name>
<email>ross.burton@arm.com</email>
</author>
<published>2024-03-22T16:50:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=21c9a9f81467a79b6a06b5286e2c7c7bd8bffbab'/>
<id>urn:sha1:21c9a9f81467a79b6a06b5286e2c7c7bd8bffbab</id>
<content type='text'>
A basic SystemReady IR system can be provided by qemu-system-aarch64
and u-boot, so tell u-boot to build the qemu_arm64 machine and configure
qemuboot to start that u-boot and search the virtio-attached wic image
for the EFI boot partition.

Currently this machine support emulated (Cortex-A76) and virtualised (KVM)
execution, and virtio storage/network/console.  Display support will be
added shortly.

Note that this machine still doesn't build U-Boot by default, as a u-boot
binary for qemu in deploy would potentially confuse users who want to
boot on real hardware and think this u-boot is needed.  If you wish to
use genericarm64 with runqemu, you'll need to manually bitbake u-boot.

(From meta-yocto rev: cd40f405844c1ccfabcbe64ad6be5d98d0221f72)

Signed-off-by: Ross Burton &lt;ross.burton@arm.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>genericarm64: clean up kernel modules and firmware</title>
<updated>2024-03-08T08:05:44+00:00</updated>
<author>
<name>Ross Burton</name>
<email>ross.burton@arm.com</email>
</author>
<published>2024-03-07T14:42:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=4b42a93edf3bb661fd7be312b4132292795a7404'/>
<id>urn:sha1:4b42a93edf3bb661fd7be312b4132292795a7404</id>
<content type='text'>
Don't install _all_ of the firmware, as that's huge (almost 1GB). Instead
install a few pieces of firmware for common hardware.

Also use the same list of packages to populate the initramfs, so there's
no need to manually sync the package lists (as initramfs doesn't install
the MACHINE_EXTRA_RRECOMMENDS automatically).

(From meta-yocto rev: a5aa914990f36cc5175577983dd1ad1aa0bb81f2)

Signed-off-by: Ross Burton &lt;ross.burton@arm.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>Add genericarm64 MACHINE</title>
<updated>2024-03-05T12:26:21+00:00</updated>
<author>
<name>Ross Burton</name>
<email>ross.burton@arm.com</email>
</author>
<published>2024-02-28T11:44:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=2f4f72fff2b642beff179530a74403fa2c608b64'/>
<id>urn:sha1:2f4f72fff2b642beff179530a74403fa2c608b64</id>
<content type='text'>
This is a new 64-bit "generic" Arm machine, that expects the hardware to
be SystemReady IR compatible.

(From meta-yocto rev: 68de209f58917d8e7108caacfefc55bbe0e0c5a2)

Signed-off-by: Ross Burton &lt;ross.burton@arm.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>yocto-bsp: Bump the default kernel to v6.6</title>
<updated>2024-01-22T13:45:33+00:00</updated>
<author>
<name>Kevin Hao</name>
<email>kexin.hao@windriver.com</email>
</author>
<published>2024-01-20T13:42:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=640927625e490e0ae974ddd26252b1e354b4bf3c'/>
<id>urn:sha1:640927625e490e0ae974ddd26252b1e354b4bf3c</id>
<content type='text'>
Create the bbappend for v6.6 and bump the default kernel to v6.6 for
all the machines.

In the v6.6 kernel the dtb files for beaglebone have been moved to a
vendor specific directory, so we also need to adjust the corresponding
variables for its DTB generation.

(From meta-yocto rev: 58ac51b7a44fbb165311c7226ae8b15cd004114d)

Signed-off-by: Kevin Hao &lt;kexin.hao@windriver.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>beaglebone-yocto: Remove the obsolete variables for uImage</title>
<updated>2024-01-02T22:50:10+00:00</updated>
<author>
<name>Kevin Hao</name>
<email>kexin.hao@windriver.com</email>
</author>
<published>2024-01-02T11:57:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=5d7a4304d91800ee1cb8d4618ce1867c0a47abd5'/>
<id>urn:sha1:5d7a4304d91800ee1cb8d4618ce1867c0a47abd5</id>
<content type='text'>
Now we only support the zImage kernel type for this machine, so remove
the obsolete variables for uImage kernel type.

[YOCTO #15232]

Reported-by: Robert Berger &lt;pokylinux@reliableembeddedsystems.com&gt;
(From meta-yocto rev: a8a5abe05ec4e96287acc994883f4b977290cde1)

Signed-off-by: Kevin Hao &lt;kexin.hao@windriver.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>beaglebone-yocto: Remove the redundant kernel-devicetree</title>
<updated>2024-01-02T22:50:10+00:00</updated>
<author>
<name>Kevin Hao</name>
<email>kexin.hao@windriver.com</email>
</author>
<published>2024-01-02T11:57:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=97306ebc00ef3dd7eacab817659d980c29da96ea'/>
<id>urn:sha1:97306ebc00ef3dd7eacab817659d980c29da96ea</id>
<content type='text'>
The kernel-devicetree is set in both MACHINE_ESSENTIAL_EXTRA_RDEPENDS
and MACHINE_EXTRA_RRECOMMENDS. Since it is an essential package for
boot, drop the one in MACHINE_EXTRA_RRECOMMENDS.

[YOCTO #15229]

(From meta-yocto rev: 5935d4fd751153f0f1c930924a5e2771f6dd5e72)

Signed-off-by: Kevin Hao &lt;kexin.hao@windriver.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>genericx86: remove redundant assignments</title>
<updated>2023-12-06T22:56:03+00:00</updated>
<author>
<name>Ross Burton</name>
<email>ross.burton@arm.com</email>
</author>
<published>2023-11-28T11:43:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=7d06e4e30b39a901a3d0b263d5de43f954c3270b'/>
<id>urn:sha1:7d06e4e30b39a901a3d0b263d5de43f954c3270b</id>
<content type='text'>
GLIBC_ADDONS was removed from the glibc recipe in 2018 (oe-core 9dc9983).

matchbox-panel-2 uses the ACPI battery by default if the machine has the
'acpi' feature, which genericx86 has.

(From meta-yocto rev: 0e50dbf558fda7595f5cb13667cbe0a01481a9f5)

Signed-off-by: Ross Burton &lt;ross.burton@arm.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
