Re: [poky] [PATCH 1/1] linux-yocto: Use in-tree config for genericarm64

On Mon, Jun 16, 2025 at 8:25 PM Alexander Sowarka <
[email protected]> wrote:

> Understood. I will talk with ARM internally how they would wish to handle
> it.
> I sadly do not think that board manufactures care to enable the
> genericarm64
> machine for their platform. ARM used the upstream kernel config in other
> places
> to create images that boot on most platforms. So I thought it would be
> useful.
> I will advise them to do something in their own layer if desired.
>

I get the push and pull on this! 14 years working at an OSV and working on
the
wrangling of configurations all that time (inside and outside of the
project) and then
continuing to have a different model (and view) from certain h/w companies
about
their reference/demo-ware configurations (I won't name names).

In fact, I maintain multiple parallel configurations with fragments versus
in-tree
deconfigs. I can help with tooling on this front if needed.

There's pros and cons to both.

We just chose to have a predictable base, and one that isn't targeted to
showing
all features, all the time .. just in case. That's what a lot of the
defconfigs do (and
I'm not claiming one way or the other here). But what we do have in that
base is
the foundation for keeping the configuration small/tight (when possible)
and one that
we know enables what we need for the autobuilder testing and then to layer
features
from higher level layers (i.e. meta-virt) or opt-in / dynamic features.

If all the references are using different defconfig bases, then we spend
our time
chasing a moving base and wondering why a runtime error is happening. Plus,
there
could be wildly different behaviour from the various platforms even on the
same
kernel version.  BUT, we do spend our time on the fragments. So time is
spent
no matter what (refer to my pros and cons statement :)

Anyway, you could definitely slap the defconfig on top, or replace in a
layer and
that's my suggestion if the fragments and enabling the h/w features that
are
required for a super wide / broad enablement just aren't working there.

Bruce



>
> Kind regards,
> Alexander Sowarka
>
>
> On Mon, 16 Jun 2025 at 20:49, Bruce Ashfield <[email protected]>
> wrote:
>
>>
>>
>> On Mon, Jun 16, 2025 at 3:05 PM Ross Burton via lists.yoctoproject.org
>> <[email protected]> wrote:
>>
>>> On 16 Jun 2025, at 19:46, Alexander Sowarka via lists.yoctoproject.org
>>> <[email protected]> wrote:
>>> >
>>> > The genericarm64 machine should run on most ARM SystemReady devices.
>>> > The arm64 configuration in the mainline kernel repository works stable
>>> > on a lot more devices then the poky internal one.
>>> > Switch to using the in-tree kernel config to run on more SystemReady
>>> > devices.
>>>
>>> This was almost by design: the initial target platform was the
>>> BeaglePlay, and then the Xilinx KV260.
>>>
>>> As the co-maintainer of this BSP I’d _much_ prefer to see the gaps fixed
>>> instead of upstream defconfig used blindly.  It’s an unusual upstream
>>> release where the defconfig doesn’t result in configuration warnings, and
>>> we have a general ethos that modular configurations are better than a
>>> single monolithic defconfig.
>>>
>>
>> And as one of our reference platforms, that's a hard NO from me (the in
>> tree defconfig).
>>
>> We do our references by the yocto policy, not the kitchen-sink in tree
>> defconfig.
>>
>> If there's issues with the fragments, fix them. Not this. There's
>> absolutely nothing by
>> accident about the way we do it currently.
>>
>> Bruce
>>
>>
>>
>>>
>>> Ross
>>>
>>>
>>> -=-=-=-=-=-=-=-=-=-=-=-
>>> Links: You receive all messages sent to this group.
>>> View/Reply Online (#13651):
>>> https://lists.yoctoproject.org/g/poky/message/13651
>>> Mute This Topic: https://lists.yoctoproject.org/mt/113676396/1050810
>>> Group Owner: [email protected]
>>> Unsubscribe: https://lists.yoctoproject.org/g/poky/unsub [
>>> [email protected]]
>>> -=-=-=-=-=-=-=-=-=-=-=-
>>>
>>>
>>
>> --
>> - Thou shalt not follow the NULL pointer, for chaos and madness await
>> thee at its end
>> - "Use the force Harry" - Gandalf, Star Trek II
>>
>>

-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end
- "Use the force Harry" - Gandalf, Star Trek II