With this patch textures work again. Thanks!
On Wed, 05 Nov 2003 16:07:01 +0100
Michel Dänzer <[EMAIL PROTECTED]> wrote:
> On Wed, 2003-11-05 at 14:39, Felix Kühling wrote:
> > After a cvs update with the new radeon memory layout I get this on all
> > applications that use textures. The applicat
On Thu, 2003-11-06 at 00:36, Felix KÃhling wrote:
> I just ran into another related problem. The xscreensaver demo cage (for
> example) terminated with:
>
> drmCommandWrite: -22
> drmRadeonCmdBuffer: -22 (exiting)
>
> before rendering the first frame. The kernel log shows:
>
> [drm:radeon_check_
I just ran into another related problem. The xscreensaver demo cage (for
example) terminated with:
drmCommandWrite: -22
drmRadeonCmdBuffer: -22 (exiting)
before rendering the first frame. The kernel log shows:
[drm:radeon_check_and_fixup_packets] *ERROR* Invalid R100 texture offset
[drm:radeon_e
On Wed, 2003-11-05 at 14:39, Felix KÃhling wrote:
> After a cvs update with the new radeon memory layout I get this on all
> applications that use textures. The application reports:
>
> DRM_RADEON_TEXTURE: return = -22
>offset=0x00c0
>image width=64 height=64
> blit width=1024 heig
After a cvs update with the new radeon memory layout I get this on all
applications that use textures. The application reports:
DRM_RADEON_TEXTURE: return = -22
offset=0x00c0
image width=64 height=64
blit width=1024 height=8 data=0x814b400
In the kernel log I see:
[drm:radeon_cp_di
