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]
Date:	Fri, 8 Jun 2012 15:23:15 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Chris Wilson <chris@...is-wilson.co.uk>
Cc:	Dave Airlie <airlied@...ux.ie>,
	Daniel Vetter <daniel.vetter@...ll.ch>,
	DRI mailing list <dri-devel@...ts.freedesktop.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [git pull] drm intel + exynos fixes

On Fri, Jun 8, 2012 at 3:12 PM, Chris Wilson <chris@...is-wilson.co.uk> wrote:
>
>           So it falls back to
> load-detection, which in your case it cannot do since all the available
> pipes are assigned and so it just reports the VGA connection as unknown.

Btw, it's a singularly stupid decision to say "Ok, I *know* I have a
monitor on output X, and I have no clue what-so-ever what I have on
output Y, and no indication there is anything even there, so let me
just degrade the output on output Y just in case".

Which is basically what you are arguing for. In addition to the
idiotic of argument that "ok, it used to work right, but we broke it
on *purpose*, really".

I'd suggest that if you see no other connectors at all, *then* you
might say "ok, let's assume that we have a VGA monitor behind a broken
KVM switch". At that point, at least that assumption doesn't make
things worse for anything else that you know is there.

And if people have truly undetectable VGA hardware in addition to
another (detectable) output, I would suggest that you tell them to
force it with xrandr. Again, there's no way in hell I will accept the
idiotic argument that my old working single-monitor setup should be
broken because the i915 driver decided that I *might* have a second
monitor on VGA despite everything else saying that is not the case.

                    Linus
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ