similar to: [MESA PATCH] Fix nv40_miptree_layout pitch

Displaying 20 results from an estimated 300 matches similar to: "[MESA PATCH] Fix nv40_miptree_layout pitch"

2010 Jan 18
0
[PATCH] nv04-nv40: Rewrite and unify miptree and transfer code
This patch rewrites all the miptree layout and transfer code in the pre-NV50 Gallium drivers. The code is also unified among them and put in the nv04 directory. The current code is broken in several ways: 1. 3D textures are laid out first by face, then by level, which is incorrect 2. Cube maps should have 128-byte aligned faces 3. Swizzled textures have a strange alignment test that seems
2010 Jan 18
0
[PATCH] nv04-nv40: Rewrite and unify miptree and transfer code (v2)
Changes: - Fixed some nv##_miptree that were not converted to nv04_miptree. - Disable swizzling on non-RGBA 2D textures, since the current 2D code is mostly broken in those cases. A later patch will fix this. Thanks to Andrew Randrianasulu who reported this. This patch rewrites all the miptree layout and transfer code in the pre-NV50 Gallium drivers. The code is also unified among them and
2012 Oct 04
1
[PATCH] gallium/nouveau: use pre-calculated stride for resource_get_handle
Fixes FDO#55294. --- src/gallium/drivers/nv30/nv30_miptree.c | 3 +-- src/gallium/drivers/nv50/nv50_miptree.c | 3 +-- 2 files changed, 2 insertions(+), 4 deletions(-) diff --git a/src/gallium/drivers/nv30/nv30_miptree.c b/src/gallium/drivers/nv30/nv30_miptree.c index 5a9a63b..9700fa8 100644 --- a/src/gallium/drivers/nv30/nv30_miptree.c +++ b/src/gallium/drivers/nv30/nv30_miptree.c @@ -56,8
2009 Dec 31
1
[PATCH] Print NOUVEAU_NO_SWIZZLE and NOUVEAU_NO_TRANSFER messages only once
Currently we are continuously spewing messages messages about these variables since we call debug_get_bool_option everytime we want to check their value This is annoying, slows things down due to terminal rerendering and obscures useful messages. This patch only calls debug_get_bool_option once and caches the result in a static variable. --- src/gallium/drivers/nv04/nv04_transfer.c | 6 ++++--
2009 Feb 16
17
[Bug 20130] New: GT200: nv50 chipset 0xa0 lockup
http://bugs.freedesktop.org/show_bug.cgi?id=20130 Summary: GT200: nv50 chipset 0xa0 lockup Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org
2007 Jun 26
3
[PATCH] Always use mipmaps in cube plugin
Currently, the cube plugin uses mipmapping only when cube is unfolded. When the cube is rotated, mipmaps are not used, which leads to ugly look of textures. The attached patch fixes this. This leads to another kind of artifacts, which are fixable with anisotropic filtering. http://team.pld-linux.org/~wolf/aniso.png The leftmost image is the current state of cube plugin. The center image is with
2009 Sep 17
5
[Bug 24002] New: PFIFO_CACHE_ERROR PGRAPH_ERROR
http://bugs.freedesktop.org/show_bug.cgi?id=24002 Summary: PFIFO_CACHE_ERROR PGRAPH_ERROR Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org
2009 Apr 17
1
NV40 Cubic Texture HW Mip Map Generation
Hello, I have been looking at cubic texture mapping for a bit, and I have found that hw mipmap generation doesn't work at all or the textures are all messed up (normal 2d work fine). This is with linear textures. Also of note is that software mipmap generation works fine. I have done sanity checks for the miptree pitches, offsets, etc and everything seems to match up fine for both the
2008 Mar 31
11
[Bug 15276] New: text rendering, PGRAPH_ERROR/ILLEGAL_MTHD/ PROTECTION_FAULT spam in syslog
http://bugs.freedesktop.org/show_bug.cgi?id=15276 Summary: text rendering, PGRAPH_ERROR/ILLEGAL_MTHD/PROTECTION_FAULT spam in syslog Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component:
2008 Aug 01
1
NV86 (Quadro NVS 140M) errors in dmesg
In case it's any use for debugging, I get these error messages in dmesg on my NV86 (Quadro NVS 140M) card: [ 21.729435] [drm] Initialized drm 1.1.0 20060810 [ 21.749414] nouveau 0000:01:00.0: power state changed by ACPI to D0 [ 21.749425] nouveau 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 21.749432] nouveau 0000:01:00.0: setting latency timer to 64 [ 21.749528]
2006 Dec 04
1
(no subject)
Hi, I've been trying to get the new i915tex DRI module to work with the new DRM memory manager and finally succeeded. Unfortunately it seems to break compiz which errors out complaining that there are no GLXFBConfigs for the default depth. I was able to trace the problem to the following block of code in src/screen.c, starting on line 1897: if (s->fbo) { (*s->getFBConfigAttrib)
2009 Aug 21
21
[Bug 23445] New: NV46: GPU lockup on VT switch
http://bugs.freedesktop.org/show_bug.cgi?id=23445 Summary: NV46: GPU lockup on VT switch Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: critical Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org
2008 Sep 04
1
Tested nouveau on a Quadro NVS 140M
Hi, I've just tried nouveau for the first time and I'd like to thank you all for your hard work. It works well, and I'm especially impressed to see xv running on my card (NV50 generation). Here is a brief report of my test. Details: - Card is Quadro NVS 140M - nouveau-drm and xf86-video-nouveau are from today's git - linux 2.6.26.3 from archlinux - X.Org X Server 1.4.99.906
2007 Jun 05
2
Direct and Indirect: Difference in rendering quality
Hi Why is the quality of scaled textures/objects using --indirect-rendering much worse than direct rendering? Also, vsync does not work with indirect-rendering. I am using an Nvidia Geforce go 7300, with 97.55 drivers. Thanks, Matt
2009 Jan 25
0
Gallium NV40 Textures
On Sun, Jan 25, 2009 at 10:58 AM, Jimmy Rentz <jedynamic at bellsouth.net> wrote: > Hello, > I was playing around with the OpenGlSuperBible samples and > noticed some odd issues around textures. Yes, I know it won't > be perfect right now (and not supported)...I am just curious > if you see the same issues. > Well, I am seeing some
2009 Jul 14
14
[Bug 22763] New: suspend doesn't works
http://bugs.freedesktop.org/show_bug.cgi?id=22763 Summary: suspend doesn't works Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy:
2009 Dec 04
1
[Bug 25440] New: PATCH: fixes conflicting miptree definitions
http://bugs.freedesktop.org/show_bug.cgi?id=25440 Summary: PATCH: fixes conflicting miptree definitions Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau AssignedTo: nouveau at lists.freedesktop.org
2012 Jan 10
5
[PATCH 0/4] nvfx: rework render temps code and fixes
This patch series silences some unknown cap warnings and fixes up coding style (patch 1+4). The most important part of this series are the two patches in the middle. They rework the state_fb code, so that we are able to render to not 64 byte aligned targets, as this is the only real use-case for render temporaries this allows us to drop temp code completely and simplifies a lot
2008 Oct 27
11
[Bug 18250] New: X server crash on NV34
http://bugs.freedesktop.org/show_bug.cgi?id=18250 Summary: X server crash on NV34 Product: xorg Version: 7.3 Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy:
2010 Jan 16
1
[PATCH] drm/nouveau: Acknowledge DMA_VTX_PROTECTION PGRAPH interrupts
Currently Nouveau is unable to dismiss DMA_VTX_PROTECTION errors, which results in an infinite loop in the interrupt handler. These errors are caused both by bugs in the Gallium driver and by user-specified index buffers with out of bounds indices. By mmio-tracing the nVidia drivers, I found out how this is done. On DMA_VTX_PROTECTION, The nVidia driver reads the register 0x402000, always