<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [Radeonsi/Hawaii] Rendering errors when running basic opengl 3 demo"
href="https://bugs.freedesktop.org/show_bug.cgi?id=89107#c16">Comment # 16</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [Radeonsi/Hawaii] Rendering errors when running basic opengl 3 demo"
href="https://bugs.freedesktop.org/show_bug.cgi?id=89107">bug 89107</a>
from <span class="vcard"><a class="email" href="mailto:darkdefende@gmail.com" title="Sebastian Parborg <darkdefende@gmail.com>"> <span class="fn">Sebastian Parborg</span></a>
</span></b>
<pre>(In reply to Grigori Goronzy from <a href="show_bug.cgi?id=89107#c15">comment #15</a>)
<span class="quote">> The call to glXChooseFBConfig in MicroGlut doesn't specify any attribute
> list, so a list of all configs is returned by it. Later on, the GLX context
> i just uses the first returned config, which can be pretty much anything.
> When I specify a attribute list to get a suitable FB config, it works fine.
>
> Other drivers might get away with it because they return the FB configs in a
> different order, but obviously you can't count on this.</span >
Ah, that makes sense. It works for me now too :)
Thank you (and everyone else) for your help! I will inform my professor and
hope that he includes the changes so other students doesn't have to run into
the same problems as I did.
I guess this bug can be closed then? As you said, the order of the returned
configs doesn't have to be in any specific order. So I guess the other drivers
just got lucky.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>