Re: [PATCH 0/3] video/efi: Support FIRMWARE_EDID on non-x86
From: Thomas Zimmermann
Date: Fri Nov 21 2025 - 09:03:21 EST
Hi
Am 20.11.25 um 09:25 schrieb Ard Biesheuvel:
On Thu, 20 Nov 2025 at 09:19, Thomas Zimmermann <tzimmermann@xxxxxxx> wrote:
That sounds great, thanks.
Am 20.11.25 um 08:56 schrieb Thomas Zimmermann:
Hi,If this proposal works for EFI, I could do the changes in graphics
thanks for addressing the remaining EDID support.
First of all, you need to cc dri-devel@xxxxxxxxxxxxxxxxxxxxx on any
further revisions.
Am 19.11.25 um 13:30 schrieb Ard Biesheuvel:
From: Ard Biesheuvel <ardb@xxxxxxxxxx>I don't like how this series complicates everything to make non-x86
Refactor the screen_info handling so non-x86 platforms booting via the
EFI stub also have access to the EDID data exposed by the EFI boot
services.
easier. But the general idea of using efi_screen_info goes into the
right direction. It's just not generic enough.
The sysfb code transfers struct screen_info as device parameter [1].
Drivers later fetch it on probe [2]. The direct ref to the global
edid_info [3] only exists because we have no means of transferring it
as device data.
So instead of using efi_screen_info, let's declare struct
sysfb_display with screen_info and edid_info. The header would be
linux/sysfb.h. We transfer this to all related drivers. The generic
EFI code would set it up like efi_screen_info and the x86 code would
decalre it at [4]; replacing the existing state.
drivers and then resubmit the EDID series with an additional patch for
generic EFI.
Series is out at https://lore.kernel.org/dri-devel/20251121135624.494768-1-tzimmermann@xxxxxxx/ Once/if merged, we can implement EDID support on top of it for all of EFI.
Best regards
Thomas
--
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstr. 146, 90461 Nürnberg, Germany, www.suse.com
GF: Jochen Jaser, Andrew McDonald, Werner Knoblich, (HRB 36809, AG Nürnberg)