http://bugs.freedesktop.org/show_bug.cgi?id=13362
[EMAIL PROTECTED] changed:
What|Removed |Added
Summary|Error with i915tex in file |Error with i915tex in file
http://bugs.freedesktop.org/show_bug.cgi?id=13362
[EMAIL PROTECTED] changed:
What|Removed |Added
Summary|Error with i915tex in file |Error with i915tex in file
http://bugs.freedesktop.org/show_bug.cgi?id=13362
Summary: Error with i915tex in file dri_bufmgr.c
Product: Mesa
Version: unspecified
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priorit
Hi Kristian,
Got a question on cliprect this might be dumb but what happen if hw is limited
on numbers of cliprect it can handle ? Does the X server also provide some kind
of informations like buffer draw order (in which case cliprect are only usefull
to save cpy memory) ?
I haven't looked yet in
http://bugs.freedesktop.org/show_bug.cgi?id=13358
Summary: Radeon X800XL 256 (R430) can only run the first started
opengl program after X is loaded
Product: Mesa
Version: CVS
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Keith Whitwell wrote:
> Dave Airlie wrote:
>>> I'm trying to figure out how context switches acutally work... the DRI
>>> lock is overloaded as context switcher, and there is code in the
>>> kernel to call out to a chipset specific context switch routine when
>>> the DRI lock is taken... but only f
Dave Airlie wrote:
>> I'm trying to figure out how context switches acutally work... the DRI
>> lock is overloaded as context switcher, and there is code in the
>> kernel to call out to a chipset specific context switch routine when
>> the DRI lock is taken... but only ffb uses it... So I'm guessin
Dave Airlie wrote:
>> I'm trying to figure out how context switches acutally work... the DRI
>> lock is overloaded as context switcher, and there is code in the
>> kernel to call out to a chipset specific context switch routine when
>> the DRI lock is taken... but only ffb uses it... So I'm guessin
>
> I'm trying to figure out how context switches acutally work... the DRI
> lock is overloaded as context switcher, and there is code in the
> kernel to call out to a chipset specific context switch routine when
> the DRI lock is taken... but only ffb uses it... So I'm guessing the
> way context