search for: z24s8

...uch better-prepared to tackle the issue this time around. To recap, nv30 (and nv40) hw can't handle certain color/depth format combinations. Specifically, a 16-bit color format must be paired with a 16-bit depth format, and a 32-bit color format must be paired with a 32-bit depth format (well, Z24S8). This HW also can't handle different per-attachment sizes, and also the "linearity" of all the attachments must be the same. (Whether a surface is linear or not is _generally_ dictated by its w/h, but not always -- POT textures can sometimes end up allocated linearly by e.g. the ddx,...

...time around. >> >> To recap, nv30 (and nv40) hw can't handle certain color/depth format >> combinations. Specifically, a 16-bit color format must be paired with >> a 16-bit depth format, and a 32-bit color format must be paired with a >> 32-bit depth format (well, Z24S8). This HW also can't handle different >> per-attachment sizes, and also the "linearity" of all the attachments >> must be the same. (Whether a surface is linear or not is _generally_ >> dictated by its w/h, but not always -- POT textures can sometimes end >> up...

...gt;> To recap, nv30 (and nv40) hw can't handle certain color/depth format >>>> combinations. Specifically, a 16-bit color format must be paired with >>>> a 16-bit depth format, and a 32-bit color format must be paired with a >>>> 32-bit depth format (well, Z24S8). This HW also can't handle different >>>> per-attachment sizes, and also the "linearity" of all the attachments >>>> must be the same. (Whether a surface is linear or not is _generally_ >>>> dictated by its w/h, but not always -- POT textures can s...

...and nv40) hw can't handle certain color/depth format >>>>>> combinations. Specifically, a 16-bit color format must be paired with >>>>>> a 16-bit depth format, and a 32-bit color format must be paired with a >>>>>> 32-bit depth format (well, Z24S8). This HW also can't handle different >>>>>> per-attachment sizes, and also the "linearity" of all the attachments >>>>>> must be the same. (Whether a surface is linear or not is _generally_ >>>>>> dictated by its w/h, but not alwa...

https://bugs.freedesktop.org/show_bug.cgi?id=92306 Bug ID: 92306 Summary: GL Excess demo renders incorrectly on nv43 Product: Mesa Version: git Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau

...on.c +++ b/src/nv_accel_common.c @@ -71,7 +71,7 @@ nouveau_allocate_surface(ScrnInfoPtr scrn, int width, int height, int bpp, tile_mode = 0x00; if (usage_hint & NOUVEAU_CREATE_PIXMAP_ZETA) - tile_flags = 0x1100; /* S8Z24 */ + tile_flags = (bpp == 16) ? 0x0100 : 0x1100; /* Z16 : Z24S8 */ else tile_flags = 0xfe00; @@ -90,7 +90,7 @@ nouveau_allocate_surface(ScrnInfoPtr scrn, int width, int height, int bpp, tile_mode = 0; if (usage_hint & NOUVEAU_CREATE_PIXMAP_ZETA) - tile_flags = 0x22800; + tile_flags = (bpp == 16) ? 0x26c00 : 0x22800; else if (...

...the > issue this time around. > > To recap, nv30 (and nv40) hw can't handle certain color/depth format > combinations. Specifically, a 16-bit color format must be paired with > a 16-bit depth format, and a 32-bit color format must be paired with a > 32-bit depth format (well, Z24S8). This HW also can't handle different > per-attachment sizes, and also the "linearity" of all the attachments > must be the same. (Whether a surface is linear or not is _generally_ > dictated by its w/h, but not always -- POT textures can sometimes end > up allocated linea...

...t;> >>> To recap, nv30 (and nv40) hw can't handle certain color/depth format >>> combinations. Specifically, a 16-bit color format must be paired with >>> a 16-bit depth format, and a 32-bit color format must be paired with a >>> 32-bit depth format (well, Z24S8). This HW also can't handle different >>> per-attachment sizes, and also the "linearity" of all the attachments >>> must be the same. (Whether a surface is linear or not is _generally_ >>> dictated by its w/h, but not always -- POT textures can sometimes end...

...ecap, nv30 (and nv40) hw can't handle certain color/depth format >>>>> combinations. Specifically, a 16-bit color format must be paired with >>>>> a 16-bit depth format, and a 32-bit color format must be paired with a >>>>> 32-bit depth format (well, Z24S8). This HW also can't handle different >>>>> per-attachment sizes, and also the "linearity" of all the attachments >>>>> must be the same. (Whether a surface is linear or not is _generally_ >>>>> dictated by its w/h, but not always -- POT te...

https://bugs.freedesktop.org/show_bug.cgi?id=75776 Priority: medium Bug ID: 75776 Assignee: nouveau at lists.freedesktop.org Summary: Hearthstone displays corrupted buffers on NVA5 Severity: normal Classification: Unclassified OS: All Reporter: lubosz at gmail.com Hardware: Other Status: NEW

From: Ben Skeggs <bskeggs at redhat.com> Signed-off-by: Ben Skeggs <bskeggs at redhat.com> --- src/gallium/drivers/nouveau/nv50/g80_defs.xml.h | 279 ++++++++++++++++++++++++ 1 file changed, 279 insertions(+) create mode 100644 src/gallium/drivers/nouveau/nv50/g80_defs.xml.h diff --git a/src/gallium/drivers/nouveau/nv50/g80_defs.xml.h