Drop default y from CONFIG_EFI_GRUB_ARM32_WORKAROUND?

[Jan Kiszka]

On 06.01.26 15:30, Heinrich Schuchardt wrote:
> Am 6. Januar 2026 14:47:30 MEZ schrieb Jan Kiszka <jan.kiszka at siemens.com>:
>> Hi,
>>
>> it seems that some kernel configs can cause problems with the
>> CONFIG_EFI_GRUB_ARM32_WORKAROUND. Namely, 6.1-cip and 5.10-cip with its
>> current defconfigs [1] no longer boot on the BeagleBone Black (other
>> boards still need validation), both with the more recommendable
>> systemd-boot and grub. I do not have the motivation to debug the reason
>> in the kernel / its config, given that everything works fine once the
>> firmware behaves according to the UEFI spec.
>>
>> Meanwhile, grub reached 2.12 now which is far away from the old, broken
>> version of 2019. So, should we rather make this workaround opt-in in 2026?
>>
>> Jan
> 
> Hello Jan,
> 
> Looks ok to me. Will you send a patch?
> 

Can do. Just one follow-up question:

"This workaround currently is also needed on systems with caches that
cannot be managed via CP15."

Do we know them by name? Should we keep the default for those?

Jan

-- 
Siemens AG, Foundational Technologies
Linux Expert Center