From: Andy Furniss <andyqos@ukfsn.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: Sven Joachim <svenjoac@gmx.de>, Dave Airlie <airlied@redhat.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: Bogus video resolution in Linux 3.5-rc4
Date: Mon, 25 Jun 2012 21:25:02 +0100 [thread overview]
Message-ID: <4FE8C91E.2060406@ukfsn.org> (raw)
In-Reply-To: <s5ha9zr2o1a.wl%tiwai@suse.de>
Takashi Iwai wrote:
>> The xrandr command shows various bogus modes.
>
> Can't these values be displayed on your monitor at all?
> If they can be displayed, they are valid modes, not really bogus.
> After all, they are values that EDID of your montor advertises as
> available ranges.
I have already commented on bogus modes when the patch first went into
dcn, but to repeat -
HDMI TV - lots of new modes but it already advertised all the CVT that
it supports and all the new are bogus.
DVI 120Hz 1920x1080 monitor many bogus modes as it won't display > it's
res and won't scale up some of the new modes.
Even some of the new ones that are not "out of range" will actually end
up setting something different and show some distortion.
Maybe gained a couple.
next prev parent reply other threads:[~2012-06-25 20:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 14:03 Bogus video resolution in Linux 3.5-rc4 Sven Joachim
2012-06-25 15:53 ` Takashi Iwai
2012-06-25 15:57 ` Takashi Iwai
2012-06-25 17:40 ` Sven Joachim
2012-06-25 19:22 ` Adam Jackson
2012-06-25 19:24 ` Takashi Iwai
2012-06-25 19:38 ` Sven Joachim
2012-06-26 7:21 ` Takashi Iwai
2012-06-30 18:46 ` Calvin Owens
2012-06-30 19:24 ` Takashi Iwai
2012-06-30 21:14 ` Sven Joachim
2012-07-02 19:46 ` Adam Jackson
2012-07-03 9:20 ` Takashi Iwai
2012-06-25 20:25 ` Andy Furniss [this message]
2012-06-25 21:03 ` Andy Furniss
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=4FE8C91E.2060406@ukfsn.org \
--to=andyqos@ukfsn.org \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=svenjoac@gmx.de \
--cc=tiwai@suse.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