All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Daniel J Blueman" <daniel@quora.org>,
	"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	intel-gfx@lists.freedesktop.org,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: i915 DVI resolution regression (3.13.7+)
Date: Tue, 08 Apr 2014 10:14:04 +0300	[thread overview]
Message-ID: <878urg9ttv.fsf@intel.com> (raw)
In-Reply-To: <CAMVG2sti6EMQXw5xyNp-wkq0nGz4zVgz1p7AO48Kb1_zYk8K0w@mail.gmail.com>

On Tue, 08 Apr 2014, Daniel J Blueman <daniel@quora.org> wrote:
> Ville et al,
>
> It looks like commit e3ea8fa6beaf55fee64bf816f3b8a80ad733b2c2 (or
> another commit in 3.13.7) broke modes which require DVI-D dual-link,
> eg 2560x1440 with my panel.
>
> I don't see these modelines in 3.13.7 or later (eg 3.14):
>
> [     5.582] (II) intel(0): Modeline "2560x1440"x60.0  312.25  2560
> 2752 3024 3488  1440 1443 1448 1493 -hsync +vsync (89.5 kHz eP)
> [     5.582] (II) intel(0): Modeline "2560x1440"x60.0  312.25  2560
> 2752 3024 3488  1440 1443 1448 1493 -hsync +vsync (89.5 kHz eP)
> [     5.582] (II) intel(0): Modeline "1920x1200"x59.9  193.25  1920
> 2056 2256 2592  1200 1203 1209 1245 -hsync +vsync (74.6 kHz e)
>
> My monitor is a Dell U2713HM; mobo uses an H87 chipset with i5-4670.

By allowing those modes we regressed setups which were not capable of
displaying them. So you've got an HDMI->DVI converter?

https://bugzilla.kernel.org/show_bug.cgi?id=72961


-- 
Jani Nikula, Intel Open Source Technology Center

WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Daniel J Blueman" <daniel@quora.org>,
	"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	intel-gfx@lists.freedesktop.org,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Intel-gfx] i915 DVI resolution regression (3.13.7+)
Date: Tue, 08 Apr 2014 10:14:04 +0300	[thread overview]
Message-ID: <878urg9ttv.fsf@intel.com> (raw)
In-Reply-To: <CAMVG2sti6EMQXw5xyNp-wkq0nGz4zVgz1p7AO48Kb1_zYk8K0w@mail.gmail.com>

On Tue, 08 Apr 2014, Daniel J Blueman <daniel@quora.org> wrote:
> Ville et al,
>
> It looks like commit e3ea8fa6beaf55fee64bf816f3b8a80ad733b2c2 (or
> another commit in 3.13.7) broke modes which require DVI-D dual-link,
> eg 2560x1440 with my panel.
>
> I don't see these modelines in 3.13.7 or later (eg 3.14):
>
> [     5.582] (II) intel(0): Modeline "2560x1440"x60.0  312.25  2560
> 2752 3024 3488  1440 1443 1448 1493 -hsync +vsync (89.5 kHz eP)
> [     5.582] (II) intel(0): Modeline "2560x1440"x60.0  312.25  2560
> 2752 3024 3488  1440 1443 1448 1493 -hsync +vsync (89.5 kHz eP)
> [     5.582] (II) intel(0): Modeline "1920x1200"x59.9  193.25  1920
> 2056 2256 2592  1200 1203 1209 1245 -hsync +vsync (74.6 kHz e)
>
> My monitor is a Dell U2713HM; mobo uses an H87 chipset with i5-4670.

By allowing those modes we regressed setups which were not capable of
displaying them. So you've got an HDMI->DVI converter?

https://bugzilla.kernel.org/show_bug.cgi?id=72961


-- 
Jani Nikula, Intel Open Source Technology Center

  reply	other threads:[~2014-04-08  7:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-08  5:50 i915 DVI resolution regression (3.13.7+) Daniel J Blueman
2014-04-08  5:50 ` Daniel J Blueman
2014-04-08  7:14 ` Jani Nikula [this message]
2014-04-08  7:14   ` [Intel-gfx] " Jani Nikula
2014-04-08  7:32   ` Daniel J Blueman
2014-04-08  7:32     ` [Intel-gfx] " Daniel J Blueman
2014-04-08  8:02     ` Daniel Vetter
2014-04-08  8:02       ` [Intel-gfx] " Daniel Vetter
2014-04-09  2:48       ` Daniel J Blueman
2014-04-09  2:48         ` [Intel-gfx] " Daniel J Blueman
2014-04-09  3:41     ` Dave Airlie
2014-04-09  3:41       ` [Intel-gfx] " Dave Airlie
2014-04-09  6:07       ` Daniel J Blueman
2014-04-09  6:07         ` [Intel-gfx] " Daniel J Blueman
2014-04-09  6:54         ` Dave Airlie
2014-04-09  6:54           ` [Intel-gfx] " Dave Airlie
2014-04-09  7:08           ` Jani Nikula
2014-04-09  7:08             ` [Intel-gfx] " Jani Nikula
2014-04-15  6:27             ` Daniel J Blueman
2014-04-15  6:27               ` [Intel-gfx] " Daniel J Blueman
2014-04-15 10:15               ` Ville Syrjälä
2014-04-15 10:15                 ` [Intel-gfx] " Ville Syrjälä

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=878urg9ttv.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel@quora.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ville.syrjala@linux.intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.