On Fri, Jun 8, 2012 at 3:12 PM, Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> 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
_______________________________________________
dri-devel mailing list
dri-devel@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/dri-devel
