From: Carsten Emde <C.Emde@osadl.org>
To: Bastien ROUCARIES <roucaries.bastien@gmail.com>
Cc: David Airlie <airlied@linux.ie>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Valdis Kletnieks <Valdis.Kletnieks@vt.edu>,
Thomas Gleixner <tglx@linutronix.de>,
Keith Packard <keithp@keithp.com>,
Paul Menzel <paulepanter@users.sourceforge.net>,
DRI <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [V3 PATCH 1/2] drivers-gpu-drm-allow-to-load-edid-firmware.patch
Date: Thu, 15 Mar 2012 11:45:23 +0100 [thread overview]
Message-ID: <4F61C843.8050307@osadl.org> (raw)
In-Reply-To: <CAE2SPAaz4oa7q4UTZ=iiKGv3v8=6xT_=odgMN-mrH9enRP26qQ@mail.gmail.com>
Bastien,
>> Broken monitors and/or broken graphic boards may send erroneous or no
>> EDID data. This also applies to broken KVM devices that are unable to
>> correctly forward the EDID data of the connected monitor but invent
>> their own fantasy data.
>>
>> This patch allows to specify an EDID data set to be used instead of
>> probing the monitor for it. It contains built-in data sets of frequently
>> used screen resolutions. In addition, a particular EDID data set may be
>> provided in the /lib/firmware directory and loaded via the firmware
>> interface. The name is passed to the kernel as module parameter of the
>> drm_kms_helper module either when loaded
>> options drm_kms_helper edid_firmware=edid/1280x1024.bin
>> or as kernel commandline parameter
>> drm_kms_helper.edid_firmware=edid/1280x1024.bin
>
> Windows allow vendor to override eddid based on 3 bytes manufacturer
> and product code.
This may solve the situation when a particular monitor lies about the
required setting or its EDID data set has an invalid CRC. However, this
does not solve the situation when we do not get any useful EDID
information, because something is totally broken. This also applies to
the KVM situation when the KVM sends EDID data that are totally
unrelated to the monitor at the other side of the KVM.
> Seems a reasonnable approach to follow.
I am not yet convinced.
-Carsten.
next prev parent reply other threads:[~2012-03-15 10:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 9:52 [V3 PATCH 0/2] Provide workarounds to use DRM/KMS with broken graphics hardware Carsten Emde
2012-03-15 9:52 ` [V3 PATCH 1/2] drivers-gpu-drm-allow-to-load-edid-firmware.patch Carsten Emde
2012-03-15 10:30 ` Bastien ROUCARIES
2012-03-15 10:45 ` Carsten Emde [this message]
2012-03-15 15:01 ` el es
2012-03-15 9:52 ` [V3 PATCH 2/2] drivers-gpu-drm-i915-quirk-backlight-inverted.patch Carsten Emde
2012-03-15 10:09 ` Chris Wilson
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=4F61C843.8050307@osadl.org \
--to=c.emde@osadl.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=airlied@linux.ie \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulepanter@users.sourceforge.net \
--cc=roucaries.bastien@gmail.com \
--cc=tglx@linutronix.de \
/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