From: Bruce Ashfield <bruce.ashfield@...> updating the 5.15 hardware reference BSPs to match the versions of the oe-core qemu reference platforms. Signed-off-by: Bruce Ashfield <bruce.ashfield@g

From: Bruce Ashfield <bruce.ashfield@...> Updating the hardware reference BSPs to match to core qemu machine versions. Signed-off-by: Bruce Ashfield <bruce.ashfield@...> --- .../linux/linu

On Wed, Jan 25, 2023 at 3:04 PM Bruce Ashfield via lists.yoctoproject.org <bruce.ashfield=gmail.com@...> wrote: I should add that the fixes should be on the meta-virt master-next br

<alexandre.belloni@...> wrote: That's chicken and egg. I won't merge the changes to meta-virt, until oe-core gets the new default kernel. Cheers, Bruce

From: Bruce Ashfield <bruce.ashfield@...> 5.19 has been dropped from oe-core, so we drop our bbappend to match. Signed-off-by: Bruce Ashfield <bruce.ashfield@...> --- .../linux/linux-yocto

From: Bruce Ashfield <bruce.ashfield@...> 5.19 will be removed shortly, bumping the preferred versions for poky/poky-tiny to 6.1. The -alt config remains on 5.15. Signed-off-by: Bruce Ashfield <

From: Bruce Ashfield <bruce.ashfield@...> Richard, These follow the OEcore patches to remove 5.19. This bumps poky and poky-tiny to 6.1 and leaves the alt configuration on 5.15. Bruce The follow

I don't have anything super helpful to add, but when that git command is hung, are you seeing any stalled network connections or processes in D state ? It wasn't clear from your first message. Are all

From: Bruce Ashfield <bruce.ashfield@...> Bumping the reference BSPs to the latest 5.15 in linux-yocto, which picks up the following commits: 509a32764e1a Linux 5.15.78 7038af4ce951 wifi: brcmfm

You can find the details in the yocto manuals, but I'm describing how the standard/tiny/preempt-rt reference kernels have their configurations constructed using the kernel-yocto tooling. For each kern

#yocto

In message: [yocto] Help with setting up a PREEMPT_RT image for BeagleBone Black #yocto on 27/10/2022 mpham20@... wrote: To build a kernel recipe (not just linux-yocto), it must be marked as compa

#yocto

Nope. I got tied up with some other issues, I'll send it tonight when I get a moment! Bruce

emux86-64-c9 login: root root@qemux86-64-c9:~# /usr/lib/docker/cli-plugins/docker-compose version Docker Compose version v2.11.2 Cheers, Bruce

The amount of fetches is certainly impressive, but it is like that for any non-vendored go application, whether we can see it or not. When the recipes are simple, all of the fetching and source struct

FYI: Here's the very lightly tested RFC version of the recipe: https://git.yoctoproject.org/meta-virtualization/commit/?h=master-next&id=fa24cfc08b129de5c7ba36099985359cc0228630 Cheers, Bruce

Yes indeed. This has also passed my other regression testing, but I was traveling today and couldn't send my pull request. I'll send it over the weekend, so hopefully it'll be merged shortly! Bruce

Adding the missing setuptools does get things working. I actually have a prototype recipe for this that I was working on before ELCe, but I didn't get it into meta-virtualization yet, as it had a few

From: Bruce Ashfield <bruce.ashfield@...> Updating linux-yocto/5.10 to the latest korg -stable release that comprises the following commits: 26ae9c361414 Linux 5.10.130 8365b151fd50 dmaengine: t

From: Bruce Ashfield <bruce.ashfield@...> Updating linux-yocto/5.15 to the latest korg -stable release that comprises the following commits: 843dae1756d9 Linux 5.15.54 c0c041a60cac selftests/net

On Thu, Jul 14, 2022 at 3:12 PM Bruce Ashfield via lists.yoctoproject.org <bruce.ashfield=gmail.com@...> wrote: Clearly, I did the opposite of what I claimed, I'm resending to oe-co