linux-kernel - Re: [Intel-gfx] i915 DVI resolution regression (3.13.7+)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAMVG2ssELOqn8BHVwUMu1+X9LKNWQEA2Bpk+n+bVOvxOFGHktg@mail.gmail.com>
Date:	Wed, 9 Apr 2014 10:48:34 +0800
From:	Daniel J Blueman <daniel@...ra.org>
To:	Ville Syrjälä <ville.syrjala@...ux.intel.com>
Cc:	Jani Nikula <jani.nikula@...ux.intel.com>,
	intel-gfx <intel-gfx@...ts.freedesktop.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Daniel Vetter <daniel.vetter@...ll.ch>
Subject: Re: [Intel-gfx] i915 DVI resolution regression (3.13.7+)

Ville et al,

On 8 April 2014 16:02, Daniel Vetter <daniel.vetter@...ll.ch> wrote:
> On Tue, Apr 8, 2014 at 9:32 AM, Daniel J Blueman <daniel@...ra.org> wrote:
>> I am using a dual-link DVI-D to DVI-D cable to this monitor, since I
>> previously couldn't get 2560x1440 via HDMI.
>>
>> If it isn't this commit, then it may be another commit in 3.13.7,
>> albeit it feels less likely.
>
> Before we go on a wild goose chase, can you please confirm your
> suspicion with a revert?

I built stock 3.13.7 to reproduce the issue (Ubuntu mainline config);
I reverted e3ea8fa6beaf55fee64bf816f3b8a80ad733b2c2 and rebuilt, and
don't see the issue. It's probably an idea if you have a panel that
requires dual-link DVI on the automated test matrix if not already.

Anyway, glad to have helped.

Thanks,
  Daniel
-- 
Daniel J Blueman
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/