From: Jani Nikula <jani.nikula@linux.intel.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
ysato@users.sourceforge.jp, dalias@libc.org, arnd@arndb.de
Cc: linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] arch/sh: Drop CONFIG_FIRMWARE_EDID from defconfig files
Date: Wed, 01 Apr 2026 15:45:00 +0300 [thread overview]
Message-ID: <8a7e78415ac5d83ae220125b32fd68a4e629eca4@intel.com> (raw)
In-Reply-To: <808dcd39-ed04-4288-9b21-55b47354de17@suse.de>
On Wed, 01 Apr 2026, Thomas Zimmermann <tzimmermann@suse.de> wrote:
> Am 01.04.26 um 10:46 schrieb John Paul Adrian Glaubitz:
>> My SH7785LCR board does have a DVI output as well as a Silicon Motion SM-501 video
>> chip though, so I think it should be able to perform EDID in general. Or is the
>> protocol actually tied to the x86 architecture? What about monitors on a PowerPC
>> workstation, for example? Does EDID not work there at all?
>
> Yes, your system can fetch the EDID via the Linux driver. But
> FIRMWARE_EDID is a special feature where the EDID gets delivered by the
> boot loader. This has always only been possible on x86 or with EFI.
And then there's the completely separate CONFIG_DRM_LOAD_EDID_FIRMWARE
config to allow loading the EDID through the kernel firmware loader. Not
confusing or misleading at all. ;D
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-04-01 12:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 8:32 [PATCH] arch/sh: Drop CONFIG_FIRMWARE_EDID from defconfig files Thomas Zimmermann
2026-04-01 8:46 ` John Paul Adrian Glaubitz
2026-04-01 8:53 ` Thomas Zimmermann
2026-04-01 12:45 ` Jani Nikula [this message]
2026-04-01 13:24 ` John Paul Adrian Glaubitz
2026-04-01 8:55 ` Geert Uytterhoeven
2026-04-01 9:07 ` Thomas Zimmermann
2026-04-01 13:25 ` John Paul Adrian Glaubitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8a7e78415ac5d83ae220125b32fd68a4e629eca4@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=arnd@arndb.de \
--cc=dalias@libc.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=tzimmermann@suse.de \
--cc=ysato@users.sourceforge.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox