From: "H. Peter Anvin" <hpa@zytor.com>
To: Daniel Drake <dsd@gentoo.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jan Beulich <jbeulich@novell.com>,
linux-kernel@vger.kernel.org, zwane@infradead.org,
Andi Kleen <ak@suse.de>, "Antonino A. Daplas" <adaplas@pol.net>
Subject: Re: [PATCH] retrieve VBE EDID/DDC info independent of used video mode
Date: Tue, 10 Jul 2007 10:23:45 -0700 [thread overview]
Message-ID: <4693C0A1.8010901@zytor.com> (raw)
In-Reply-To: <4693BF02.2050705@gentoo.org>
Daniel Drake wrote:
> H. Peter Anvin wrote:
>> User error.
>> Please replace user and press any key.
>>
>> # CONFIG_FIRMWARE_EDID is not set
>>
>> The user has *explicitly* disabled acquisition of EDID from the
>> firmware, so of course it doesn't probe for it.
>
> I'm not versed with all this EDID and resolution stuff, but shouldn't
> the resolution be detected correctly under all configurations?
Not if you actively disable detection!
Why would you want to be able to disable detection? Well, your BIOS
might be buggy.
> The original problem is that as of 2.6.20.11, the resolution is
> misdetected - it is wrong by 6 pixels. The same configuration with
> 2.6.20.10 works fine.
That is because 2.6.20.11 incorrectly disabled EDID detection when a
non-VESA mode was chosen as the initial mode. This is a bug.
> With the 2.6.20.10/2.6.20.11 configuration, the user did have
> CONFIG_FIRMWARE_EDID set. I'm not sure why he changed this for the -mm
> testing, but then again I don't understand why it should matter.
You're complaining that we didn't query EDID when you *explicitly* asked
us not to. This is not a bug!
-hpa
next prev parent reply other threads:[~2007-07-10 17:31 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 15:57 [PATCH] retrieve VBE EDID/DDC info independent of used video mode Jan Beulich
2007-06-30 22:25 ` Daniel Drake
2007-06-30 22:42 ` Andrew Morton
2007-07-08 13:27 ` Daniel Drake
2007-07-08 18:14 ` Andrew Morton
2007-07-08 18:33 ` H. Peter Anvin
2007-07-09 22:53 ` Daniel Drake
2007-07-09 22:59 ` H. Peter Anvin
2007-07-10 17:16 ` Daniel Drake
2007-07-10 17:23 ` H. Peter Anvin [this message]
2007-07-10 18:07 ` Daniel Drake
2007-07-10 18:15 ` H. Peter Anvin
2007-07-31 23:58 ` Daniel Drake
2007-08-01 0:21 ` Zwane Mwaikambo
2007-08-01 1:17 ` Daniel Drake
2007-08-01 1:53 ` H. Peter Anvin
2007-08-01 1:54 ` Antonino A. Daplas
2007-08-01 2:08 ` Gabriel C
2007-08-02 3:09 ` Antonino A. Daplas
2007-08-02 3:50 ` H. Peter Anvin
2007-08-02 10:16 ` Antonino A. Daplas
2007-08-02 13:23 ` H. Peter Anvin
2007-08-03 2:33 ` Daniel Drake
2007-08-03 3:33 ` Antonino A. Daplas
2007-08-01 1:04 ` Antonino A. Daplas
2007-07-08 19:48 ` Andi Kleen
2007-07-09 1:10 ` Daniel Drake
2007-07-09 0:48 ` H. Peter Anvin
2007-07-02 20:13 ` Chuck Ebbert
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=4693C0A1.8010901@zytor.com \
--to=hpa@zytor.com \
--cc=adaplas@pol.net \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=dsd@gentoo.org \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@infradead.org \
/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