From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 60680] [NV96] HDMI is connected and has mode, TV says "no signal"
Date: Sun, 26 Jan 2014 11:27:04 +0000 [thread overview]
Message-ID: <bug-60680-8800-4qrCM5TrQL@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-60680-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1035 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=60680
--- Comment #24 from Pekka Paalanen <ppaalanen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
Tried the complete kernel from nouveau/drm-nouveau-next
(v3.13-rc8-665-g1139ffb) which contains the commit
commit f87cd8b695d372087685976460fac1ec6ba2fca9
Author: Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
Date: Sun Jan 19 04:18:15 2014 -0500
drm/nouveau/devinit: lock/unlock crtc regs for all devices, not just
pre-nv50
Also make nv_lockvgac work for nv50+ devices. This should fix
IO_CONDITION and related VBIOS opcodes that read/write the crtc regs.
See https://bugs.freedesktop.org/show_bug.cgi?id=60680
Signed-off-by: Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
Signed-off-by: Ben Skeggs <bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
which apparently is supposed to fix the issue.
This kernel works, and the issue is fixed.
Thank you!
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2143 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
prev parent reply other threads:[~2014-01-26 11:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 18:20 [Bug 60680] New: HDMI is connected and has mode, TV says "no signal" bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-60680-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-02-11 18:23 ` [Bug 60680] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-11 18:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-11 18:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-12 8:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-13 20:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-03-27 13:06 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-20 23:12 ` [Bug 60680] [NV96] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-21 5:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-24 8:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-06 12:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-06 14:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-22 9:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-22 19:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-28 6:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-10 10:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-15 17:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-15 17:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-15 22:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-17 6:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-18 8:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-19 15:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-21 18:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-23 6:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-26 11:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
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-60680-8800-4qrCM5TrQL@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox