From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 50375] [NV1A] KMS/fbcon accel failing after scrolling/tty switch
Date: Wed, 28 Aug 2013 17:31:09 +0000 [thread overview]
Message-ID: <bug-50375-8800-6nVuFpvAlS@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-50375-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 741 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=50375
--- Comment #5 from Bruno <bonbons67-H4aWS73dXupiYsDpGMXq6A@public.gmane.org> ---
(In reply to comment #4)
> Created attachment 84758 [details] [review]
> patch to treat nv1a as pre-nv17
>
> Generationally, NV1A is pre-NV17. However in a bunch of places in the
> nouveau code, this wasn't recognized. I believe this patch should help, at
> least with something. Mind trying it out? Should apply on top of a git-ish
> kernel (but probably doesn't really matter).
This patch gets the signal to the monitor.
Tested-by: Bruno Prémont <bonbons-ud5FBsm0p/xEiooADzr8i9i2O/JbrIOy@public.gmane.org>
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1932 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:[~2013-08-28 17:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-26 16:55 [Bug 50375] New: NV11: KMS/fbcon accel failing after scrolling/tty switch bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-50375-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-08-27 20:09 ` [Bug 50375] [NV11] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-27 20:11 ` [Bug 50375] [NV1A] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-27 20:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-28 3:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-28 17:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2013-08-28 17:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-05 1:40 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-05 1:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-14 14:48 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-21 22:48 ` 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-50375-8800-6nVuFpvAlS@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