> -Original Message-
> From: Bruce Ashfield
> Sent: Tuesday, April 23, 2024 7:22 AM
> To: Sourabh Banerjee (QUIC)
> Cc: linux-yocto@lists.yoctoproject.org
> Subject: Re: [linux-yocto] Seeking information on use of linux-yocto-dev
>
>
> On Mon, Apr 22, 2024 at 4:29 PM quic_sbanerje via
> http://lists.yoctoproject.org
> mailto:quicinc@lists.yoctoproject.org> wrote:
> From a previous discussion with Richard, I understand, that the
> linux-yocto-dev
> recipe exists for anyone needing more recent kernels. Bruce is maintaining is
> as a rolling update, and version upgrades are quite frequent.
>
> I am seeking information on following to understand use of linux-yocto-dev
> better:
> 1. When there's a version bump for linux-yocto-dev is there a test suite that
> is
> run?
>
> I have some simple scripts and manual tests that I run against each bump of -
> dev.
>
> In particular core-image-kernel-dev and the tightly coupled tools (lttng,
> systemtap, etc).
>
> A boot of systemd based images tends to shake out most of the major issues, so
> that
> is what I do.
Thank you for pointing to core-image-kernel-dev.
When building this image do you generally use poky-altcfg, as it includes
systemd?
How is the decision made to create a linux-yocto_${version} recipe from
linux-yocto-dev recipe? Is it guided by a set cadence?
>
> 2. Is linux-yocto-dev tested by the autobuilder or a similar CI?
>
> We've had adding it to the autobuilder CI on the wishlist for quite a while. I
> thought
> Ross added something a few months ago, but I can't recall the details. We do
> need
> to decide on exactly what to test, making sure it is lighter than what is run
> against
> the release kernels that I generate.
>
> If it was in CI there might be some breakage due to the bleeding edge nature
> of
> the updates. We just wouldn't want it to block any project milestones if run
> as
> part of CI.
>
Added Ross to get a bit more clarity on autobuilder setup to linux-yocto-dev.
>
> 3. Do BSP layer maintainers generally use linux-yocto-dev to verify the BSP
> layer
> against kernel upstream?
>
> There are some developers that do that, yes. Others use it for the AUTOREV
> and rolling nature of it, etc. Now that even linux-yocto-dev uses versioned
> branches, we could in theory just use linux-yocto for all of those purposes,
> but
> I still strongly prefer that only our supported versions appear in
> linux-yocto.
>
If a BSP maintainer chooses to use linux-yocto-dev and expands the test scope
to frameworks such as Weston, pulseaudio etc., let's say while testing detects
bugs what should be the next step?
I am trying to understand can a BSP maintainer use this as a reference to test
and plan ahead.
> Bruce
>
>
>
>
>
>
>
> --
> - Thou shalt not follow the NULL pointer, for chaos and madness await thee at
> its end
> - "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13858):
https://lists.yoctoproject.org/g/linux-yocto/message/13858
Mute This Topic: https://lists.yoctoproject.org/mt/105677861/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
