From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 75602] Unigine Heaven/Vally: Multi monitor rendering does not work
Date: Sat, 01 Mar 2014 06:20:54 +0000 [thread overview]
Message-ID: <bug-75602-502-rCPLftL3rS@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-75602-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 643 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=75602
--- Comment #9 from Michel Dänzer <michel@daenzer.net> ---
(In reply to comment #8)
> I only reported this because the proprietary works in this case.
Presumably fglrx supports higher OpenGL versions and GL_ARB_geometry_shader4 in
compatibility contexts.
> There is no reason why Mesa should fall back to the compatibility profile
> when more than one context is used I guess?
Mesa doesn't (couldn't) 'fall back' to the compatibility context. It means the
app didn't ask for a core context.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1561 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-03-01 6:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 9:29 [Bug 75602] New: Unigine Heaven/Vally: Multi monitor rendering does not work bugzilla-daemon
2014-02-28 14:22 ` [Bug 75602] " bugzilla-daemon
2014-02-28 14:24 ` bugzilla-daemon
2014-02-28 14:24 ` bugzilla-daemon
2014-02-28 14:24 ` bugzilla-daemon
2014-02-28 14:25 ` bugzilla-daemon
2014-02-28 14:33 ` bugzilla-daemon
2014-03-01 2:19 ` bugzilla-daemon
2014-03-01 2:32 ` bugzilla-daemon
2014-03-01 6:20 ` bugzilla-daemon [this message]
2015-10-07 21:02 ` [Bug 75602] Unigine Heaven/Valley: " bugzilla-daemon
2019-09-18 19:15 ` bugzilla-daemon
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-75602-502-rCPLftL3rS@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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.