From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 57660] New: nv?? show error nv??_screen_get_param:??? - unknown PIPE_CAP 76
Date: Wed, 28 Nov 2012 20:14:07 +0000 [thread overview]
Message-ID: <bug-57660-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 833 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=57660
Priority: medium
Bug ID: 57660
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Summary: nv?? show error nv??_screen_get_param:??? - unknown
PIPE_CAP 76
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: mustrumr97-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Hardware: All
Status: NEW
Version: git
Component: Drivers/DRI/nouveau
Product: Mesa
Created attachment 70747
--> https://bugs.freedesktop.org/attachment.cgi?id=70747&action=edit
Patch to fix it
Unhandled case PIPE_CAP_CUBE_MAP_ARRAY in nv??_screen.c
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2195 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 reply other threads:[~2012-11-28 20:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 20:14 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-57660-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2012-11-29 15:22 ` [Bug 57660] nv?? show error nv??_screen_get_param:??? - unknown PIPE_CAP 76 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-29 16:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-29 17:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-29 18:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-20 6:39 ` [Bug 57660] [NVA3:NVC0] Turn on support for PIPE_CAP_CUBE_MAP_ARRAY bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-20 15:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-20 15:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-24 4:06 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-07 21:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-07 22:48 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-14 9:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-26 17:17 ` 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-57660-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.