Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=8463
--- Additional Comments From [EMAIL PROTECTED] 2006-10-04 11:36 ---
The
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=5714
[EMAIL PROTECTED] changed:
What|Removed |Added
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=918
[EMAIL PROTECTED] changed:
What|Removed |Added
Ben,
I've implemented a version of the drm_mm code that unmaps ptes using
unmap_mapping_range, and remaps IO space using io_remap_pfn_range() for
a single page in nopage. This has the side effect that I need to double
check in nopage() after taking the object mutex that the pte in question
Hi,
I'm using the r300 driver from Mesa 6.5.1 and Xorg 7.1 from Debian unstable
and I'm getting giant 'white boxes' in in an open source game called UFO:AI.
This game is based on a heavily modified Quake 2 engine. I have no idea if
I'm exposing a bug in the game or the r300 driver.
I filed
On 10/5/06, James Spencer [EMAIL PROTECTED] wrote:
Hi,
I'm using the r300 driver from Mesa 6.5.1 and Xorg 7.1 from Debian unstable
and I'm getting giant 'white boxes' in in an open source game called UFO:AI.
This game is based on a heavily modified Quake 2 engine. I have no idea if
I'm
Roland Scheidegger wrote:
Rune Petersen wrote:
I hit a problem constructing this:
- In order to do range mapping in the vertex shader (if I so choose)
I will need a constant (0.5), but how to add it?
I think this might work similar to what is used for position invariant
programs, instead of
Rune Petersen wrote:
Roland Scheidegger wrote:
Rune Petersen wrote:
I hit a problem constructing this:
- In order to do range mapping in the vertex shader (if I so choose)
I will need a constant (0.5), but how to add it?
I think this might work similar to what is used for position invariant
Rune Petersen wrote:
Rune Petersen wrote:
Roland Scheidegger wrote:
Rune Petersen wrote:
I hit a problem constructing this:
- In order to do range mapping in the vertex shader (if I so choose)
I will need a constant (0.5), but how to add it?
I think this might work similar to what is used
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=8489
[EMAIL PROTECTED] changed:
What|Removed |Added
On Thu, 2006-10-05 at 17:52 +0200, Thomas Hellström wrote:
Ben,
I've implemented a version of the drm_mm code that unmaps ptes using
unmap_mapping_range, and remaps IO space using io_remap_pfn_range() for
a single page in nopage. This has the side effect that I need to double
check in
On Thu, 2006-10-05 at 17:52 +0200, Thomas Hellström wrote:
Ben,
I've implemented a version of the drm_mm code that unmaps ptes using
unmap_mapping_range, and remaps IO space using io_remap_pfn_range() for
a single page in nopage. This has the side effect that I need to double
check in
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=8463
--- Additional Comments From [EMAIL PROTECTED] 2006-10-05 18:57 ---
I am
13 matches
Mail list logo