From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 40747] [NV44] dual-link tmds no longer allowed
Date: Wed, 05 Feb 2014 09:31:40 +0000 [thread overview]
Message-ID: <bug-40747-8800-u73htToKXD@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-40747-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 800 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=40747
--- Comment #20 from Oswald Buddenhagen <ossi-RoXCvvDuEio@public.gmane.org> ---
huh?
i said that it is *easy* to convince the kernel to pick the right mode. it's
picking a wrong one only automatically. there is no hardware limitation at all
here.
X appears more tenacious, apparently because it filters out the good mode
earlier in the process. it's beyond me why it does that - it makes no sense at
all, and the log doesn't indicate anything afaics. this also puts a weird twist
on the meaning of _K_MS ...
also note that i'm a different person than the OP. i just happen to have pretty
much the same configuration (card and monitor) and consequently the same
problem.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1552 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2014-02-05 9:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 20:51 [Bug 40747] New: The new nouveau kernel module fails to use my monitor's native resolution bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-40747-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2011-09-09 20:52 ` [Bug 40747] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-09 20:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-09 22:39 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-10 0:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-10 3:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-10 13:48 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-10 14:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-10 20:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-10 21:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-10 21:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-13 23:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-10-14 14:42 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-10-14 14:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-10-14 14:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-11-03 21:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-19 16:40 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-25 10:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-25 10:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-05 4:18 ` [Bug 40747] [NV44] dual-link tmds no longer allowed bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-05 4:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-05 9:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2014-02-05 19:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-06 14:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-10 0:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 8:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
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=bug-40747-8800-u73htToKXD@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
/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.