From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 86539] New: [NVAC] Trying to register nv_backlight after NV96 did it
Date: Fri, 21 Nov 2014 22:19:45 +0000 [thread overview]
Message-ID: <bug-86539-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1181 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=86539
Bug ID: 86539
Summary: [NVAC] Trying to register nv_backlight after NV96 did
it
Product: xorg
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: pierre.morrow-GANU6spQydw@public.gmane.org
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created attachment 109822
--> https://bugs.freedesktop.org/attachment.cgi?id=109822&action=edit
dmesg
Hardware:
* 9600M GT (NV96)
* 9400M (NVAC)
Tested on
http://cgit.freedesktop.org/~darktama/nouveau/commit/?id=1a9d15cb98ec30dfba43bbe65022f22d978ea9fc
Options: nouveau.noaccel=1 (otherwise falling into bug 86537)
When using the NV96 card to drive the display, the NVAC still tries to register
nv_backlight even though it isn't driving a display and the NV96 already
registered it.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2769 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2014-11-21 22:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 22:19 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-86539-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-12-16 22:28 ` [Bug 86539] [NVAC] Trying to register nv_backlight after NV96 did it bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-23 11:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-23 11:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-23 11:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-23 11:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-23 11:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-24 13:32 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-24 15:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-26 11:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-26 11:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-26 20:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-02-29 0:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-02-29 7:39 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-03-02 13:06 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-12 20:56 ` 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-86539-8800@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.