similar to: NV40 Cubic Texture HW Mip Map Generation

This patch fixes two issues in nv40_miptree_layout. First, pt->width0 is used, which is the size of the whole texture, while width, which is the size of the mipmap level, should be used. Second, the current code does not 64-byte align the pitch of swizzled textures. However, on my NV40 this causes a pgraph error regarding the pitch register (and sometimes a system lockup too), which is fixed

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

I wrote a tool for automatically finding out the texture layout for Gallium drivers. You can find it attached to http://sourceforge.net/mailarchive/forum.php?thread_name=ff13bc9a1001081140y18450c3ejdfac25c9260fd367%40mail.gmail.com&forum_name=mesa3d-dev . Here are the findings from running it. The result is that our miptree layout code is partially broken, and overly complex. In particular:

http://bugs.freedesktop.org/show_bug.cgi?id=24668 Summary: KMS does not work with nva8 Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy:

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)

http://bugs.freedesktop.org/show_bug.cgi?id=15861 Summary: Account Request For Nouveau DDX Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy:

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

Hello, I have been working on a kernel and a user layer for the nv40 mpeg2 video decoding hardware: * The decode hw accepts commands written to a fifo along with a set of registers for firing (put) and queries (get). * The fifo can be mapped in vram or agp (though, agp isn't working right now). * The fifo does not support dma jumps and such like the 3d fifo. Well, I have some questions about

family having (several?) different video decode engine. The only work I know about is an initial support for mpeg2 decode engine on nv40 : http://cgit.freedesktop.org/nouveau/linux-2.6/commit/?h=3Dnvfx-vpe&id=3D538= d6ef8aac1cd861f6336e24e79a315fe58aba0 And afaik, the other engines are mostly unknown (no RE and no code). Some of these details could be wrong, in that case hopefully someone can

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

Make sure to normalize the z coordinates as well as the x/y ones when there are mipmaps present. Fixes 3d mipmap generation, which now uses the blit path. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> Cc: "10.2" <mesa-stable at lists.freedesktop.org> --- Did a full piglit run on nva8 and nve7 without regressions. The cubemap array mipmap generation test still fails,

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

--- Hi, this is still WIP, but already passes piglit's s3tc-teximage, s3tc-texsubimage and fbo-generatemipmap-formats(s3tc tests) and even Wolfenstein:Enemy-Territory works on my nv25. It's based on Ben's newlib branch. I have few issues though: 1) So far it needs libtxc_dxtn, but I might expose the s3tc extensions even without encoder using driconf option - Is that desirable? 2)

Hello, I have a dual-GPU card GeForce 7950 GX2 (PCI ID 10de:0294). Unfortunately, I cannot make a dump using renouveau, because the program crashes. The backtrace looks like this: Program received signal SIGSEGV, Segmentation fault. 0x00000000004153af in read_fb_ramin (instanceMem=4, offset=2) at objects.c:4089 4089 return fb[((fb_size - (ramin_block*512*1024) + ramin_inst)/4) +

The headers hadn't been regenerated in a long time, and there were a few minor divergences. Among other things, rnndb has changed naming to G80/etc, for now I've not tackled switching that over and manually replaced the nvidia codenames back to the chip ids. However no other modifications of the headergen'd headers was done. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu>

So I have been going on over the documentation trying to figure out the exact layout of Pitch Linear Textures and find some missing values. First Question: What's the correct layout of pitch linear textures in memory? Is padding of the pitch added at start or at the end? Do they have some kind of header? Currently I see them as a normal texture matrix with just pitch at the end of each row

The headers hadn't been regenerated in a long time and had seen a number of manual modifications. A few changes: - remove nvc0_2d entirely, use the nv50 header which has the nvc0 values too - remove 3ddefs, it's identical to the nv50 file - move macros out into a separate file Also the upstream rnndb changed the overall chip naming convention; this was fixed up manually in the

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

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

These are copied directly from the mesa repository. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- src/hwdefs/gm107_texture.xml.h | 365 +++++++++++++++++ src/hwdefs/nvc0_3d.xml.h | 867 +++++++++++++++++++++++++---------------- 2 files changed, 892 insertions(+), 340 deletions(-) create mode 100644 src/hwdefs/gm107_texture.xml.h diff --git