mbox series

[0/4] kernel-yocto: 6.16 fixups and genericarm64

Message ID 20250910050822.3273330-1-bruce.ashfield@gmail.com
Headers show
Series kernel-yocto: 6.16 fixups and genericarm64 | expand

Message

Bruce Ashfield Sept. 10, 2025, 5:08 a.m. UTC
From: Bruce Ashfield <bruce.ashfield@gmail.com>

Richard,

These should cover the first set of warnings / issues that were
seen with the 6.16 reference kernel.

The first fixes vboxguestdrivers in meta-oe

The second is the qemux86 configuration warning fixup

The third is to get genericarm64 building and uses the changes sent by Mikko.

Cheers,

Bruce

Bruce Ashfield (4):
  linux-yocto/6.16: cfg: DRM tweaks for guests
  linux-yocto/6.16: cfg: x86 BIGSMP removal
  yocto-bsp: introduce 6.16 bbappend
  linux-yocto/6.16: genericarm64 config

 .../recipes-kernel/linux/linux-yocto_6.16.bbappend     | 10 ++++++++++
 meta/recipes-kernel/linux/linux-yocto-rt_6.16.bb       |  2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_6.16.bb     |  2 +-
 meta/recipes-kernel/linux/linux-yocto_6.16.bb          |  2 +-
 4 files changed, 13 insertions(+), 3 deletions(-)
 create mode 100644 meta-yocto-bsp/recipes-kernel/linux/linux-yocto_6.16.bbappend

Comments

Richard Purdie Sept. 10, 2025, 11:16 a.m. UTC | #1
On Wed, 2025-09-10 at 01:08 -0400, bruce.ashfield@gmail.com wrote:
> These should cover the first set of warnings / issues that were
> seen with the 6.16 reference kernel.
> 
> The first fixes vboxguestdrivers in meta-oe
> 
> The second is the qemux86 configuration warning fixup
> 
> The third is to get genericarm64 building and uses the changes sent
> by Mikko.

Thanks!

I don't know if I missed a patch or something else went wrong but the
number of warnings went up. The ones I spotted are:

qemuarm:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/16/builds/2386
https://autobuilder.yoctoproject.org/valkyrie/#/builders/40/builds/2343
qemuarmv5:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/80/builds/2207
qemuriscv64:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/45/builds/449
https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/468
qemux86 + poky-tiny:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/50/builds/2384

Also warnings in other layers:
meta-agl-core:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/55/builds/2209
meta-arm:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/75/builds/2245

and meta-virt which I suspect you know about.

The build failures are resolved though, so progress, thanks!

Cheers,

Richard
Bruce Ashfield Sept. 10, 2025, 12:56 p.m. UTC | #2
On Wed, Sep 10, 2025 at 7:16 AM Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:

> On Wed, 2025-09-10 at 01:08 -0400, bruce.ashfield@gmail.com wrote:
> > These should cover the first set of warnings / issues that were
> > seen with the 6.16 reference kernel.
> >
> > The first fixes vboxguestdrivers in meta-oe
> >
> > The second is the qemux86 configuration warning fixup
> >
> > The third is to get genericarm64 building and uses the changes sent
> > by Mikko.
>
> Thanks!
>
> I don't know if I missed a patch or something else went wrong but the
> number of warnings went up. The ones I spotted are:
>
> qemuarm:
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/16/builds/2386
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/40/builds/2343
> qemuarmv5
> <https://autobuilder.yoctoproject.org/valkyrie/#/builders/40/builds/2343qemuarmv5>
> :
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/80/builds/2207
> qemuriscv64
> <https://autobuilder.yoctoproject.org/valkyrie/#/builders/80/builds/2207qemuriscv64>
> :
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/45/builds/449
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/468
> qemux86
> <https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/468qemux86>
> + poky-tiny:
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/50/builds/2384
>
> Also warnings in other layers:
> meta-agl-core:
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/55/builds/2209
> meta-arm
> <https://autobuilder.yoctoproject.org/valkyrie/#/builders/55/builds/2209meta-arm>
> :
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/75/builds/2245
>
> and meta-virt which I suspect you know about.
>

Yup for meta-virt.

Something must be missing, everything is warning free here.

Is your queue on master-next ?

Bruce


> The build failures are resolved though, so progress, thanks!
>
> Cheers,
>
> Richard
>
Richard Purdie Sept. 10, 2025, 12:58 p.m. UTC | #3
On Wed, 2025-09-10 at 08:56 -0400, Bruce Ashfield wrote:
> 
> 
> On Wed, Sep 10, 2025 at 7:16 AM Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > On Wed, 2025-09-10 at 01:08 -0400, bruce.ashfield@gmail.com wrote:
> > > These should cover the first set of warnings / issues that were
> > > seen with the 6.16 reference kernel.
> > > 
> > > The first fixes vboxguestdrivers in meta-oe
> > > 
> > > The second is the qemux86 configuration warning fixup
> > > 
> > > The third is to get genericarm64 building and uses the changes
> > > sent
> > > by Mikko.
> > 
> > Thanks!
> > 
> > I don't know if I missed a patch or something else went wrong but
> > the
> > number of warnings went up. The ones I spotted are:
> > 
> > qemuarm:
> > https://autobuilder.yoctoproject.org/valkyrie/#/builders/16/builds/2386
> > https://autobuilder.yoctoproject.org/valkyrie/#/builders/40/builds/2343
> > qemuarmv5:
> > https://autobuilder.yoctoproject.org/valkyrie/#/builders/80/builds/2207
> > qemuriscv64:
> > https://autobuilder.yoctoproject.org/valkyrie/#/builders/45/builds/449
> > https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/468
> > qemux86 + poky-tiny:
> > https://autobuilder.yoctoproject.org/valkyrie/#/builders/50/builds/2384
> > 
> > Also warnings in other layers:
> > meta-agl-core:
> > https://autobuilder.yoctoproject.org/valkyrie/#/builders/55/builds/2209
> > meta-arm:
> > https://autobuilder.yoctoproject.org/valkyrie/#/builders/75/builds/2245
> > 
> > and meta-virt which I suspect you know about.
> > 
> 
> 
> Yup for meta-virt.
> 
> Something must be missing, everything is warning free here.
> 
> Is your queue on master-next ? 

Yes, this was with master-next.

Cheers,

Richard
Mikko Rapeli Sept. 10, 2025, 1:26 p.m. UTC | #4
Hi,

I missed "poky: bump default kernel reference to 6.16" from
emails and can't find from list archives, but it's leaving
"poky-altcfg" distro with 6.12 kernel. Is this the plan?

When building "poky-altcfg" distro, the machines can't override
kernel version. I would like to see genericarm64 systemd
builds, e.g. "poky-altcfg" distro with the new kernel.

Plain old "poky" sysvinit without systemd, udev etc is hard
to support on broad range of HW. Thus I am testing genericarm64
with "poky-altcfg", which can't easily update to 6.16 kernel,
at least without https://lists.yoctoproject.org/g/poky/message/13742

Cheers,

-Mikko
Richard Purdie Sept. 10, 2025, 1:28 p.m. UTC | #5
On Wed, 2025-09-10 at 16:26 +0300, Mikko Rapeli wrote:
> I missed "poky: bump default kernel reference to 6.16" from
> emails and can't find from list archives, but it's leaving
> "poky-altcfg" distro with 6.12 kernel. Is this the plan?
> 
> When building "poky-altcfg" distro, the machines can't override
> kernel version. I would like to see genericarm64 systemd
> builds, e.g. "poky-altcfg" distro with the new kernel.
> 
> Plain old "poky" sysvinit without systemd, udev etc is hard
> to support on broad range of HW. Thus I am testing genericarm64
> with "poky-altcfg", which can't easily update to 6.16 kernel,
> at least without https://lists.yoctoproject.org/g/poky/message/13742

The policy has always been to test one kernel in one configuration and
the other kernel in the other configuration so this is intentional.

Cheers,

Richard
Mikko Rapeli Sept. 10, 2025, 1:40 p.m. UTC | #6
Hi,

On Wed, Sep 10, 2025 at 02:28:55PM +0100, Richard Purdie wrote:
> On Wed, 2025-09-10 at 16:26 +0300, Mikko Rapeli wrote:
> > I missed "poky: bump default kernel reference to 6.16" from
> > emails and can't find from list archives, but it's leaving
> > "poky-altcfg" distro with 6.12 kernel. Is this the plan?
> > 
> > When building "poky-altcfg" distro, the machines can't override
> > kernel version. I would like to see genericarm64 systemd
> > builds, e.g. "poky-altcfg" distro with the new kernel.
> > 
> > Plain old "poky" sysvinit without systemd, udev etc is hard
> > to support on broad range of HW. Thus I am testing genericarm64
> > with "poky-altcfg", which can't easily update to 6.16 kernel,
> > at least without https://lists.yoctoproject.org/g/poky/message/13742
> 
> The policy has always been to test one kernel in one configuration and
> the other kernel in the other configuration so this is intentional.

Is some AB build config testing "poky" distro and the new kernel with systemd?

At least on genericarm64 this is working on the HW I have access to.

If "poky-altcfg" would not override kernel version to 6.12, basically patch
above, then some machines like genericarm64 could update to 6.16 a bit
sooner.

Cheers,

-Mikko