search for: nvfx

...p temp code completely and simplifies a lot of cases. This is only tested on nv49, but there should be nothing different in this area for other nv3x or nv4x gpus. I plan on working on top of that in the following days, so please review and apply as time permits. Thanks, Lucas Lucas Stach (4): nvfx: say no to stream output caps nvfx: rework state_fb code to get rid of render temps nvfx: drop render temporaries code nvfx: random cleanups of the state validation code src/gallium/drivers/nvfx/nvfx_context.h | 2 +- src/gallium/drivers/nvfx/nvfx_fragtex.c | 4 - src/gallium/dr...

Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- Perhaps there was a day when those were different, but that day is not today. src/gallium/drivers/nouveau/nv30/nv30_context.c | 1 - src/gallium/drivers/nouveau/nv30/nv30_context.h | 1 - src/gallium/drivers/nouveau/nv30/nvfx_fragprog.c | 20 ++++++++++---------- src/gallium/drivers/nouveau/nv30/nvfx_vertprog.c | 8 ++++---- 4 files changed, 14 insertions(+), 16 deletions(-) diff --git a/src/gallium/drivers/nouveau/nv30/nv30_context.c b/src/gallium/drivers/nouveau/nv30/nv30_context.c index 2146d27..4f68eee 100644 ---...

Apparently nv3x needs some curde hacks to work properly. This is clearly not the right fix, but it's the behaviour of the old code and fixes regressions seen by users. --- src/gallium/drivers/nvfx/nvfx_state_emit.c | 6 +++++- 1 files changed, 5 insertions(+), 1 deletions(-) diff --git a/src/gallium/drivers/nvfx/nvfx_state_emit.c b/src/gallium/drivers/nvfx/nvfx_state_emit.c index a959015..60ed2d0 100644 --- a/src/gallium/drivers/nvfx/nvfx_state_emit.c +++ b/src/gallium/drivers/nvfx/nvfx_...

fixes these warnings: nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30 nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 55 nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 56 nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 58 nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 59 Bugzilla: https://bugs....

Celestia 1.6.0 again shows corrupted rendering on planets, other parts rendered correctly with the latest git pull on the nvfx-next-5 tree. Yesterday's nvfx-next tree worked perfectly. -- http://www.munted.org.uk One very high maintenance cat living here.

...n flash every frame) behave badly, but in different ways : * etracer is very slow and often crash in ttm code [1] (I think this is an old bug that just resurrected, no idea why) * foobillard is very slow and still flash a bit * strangely, neverball seems to work, I get similar results than with old nvfx-next-6b branch with temporaries reverted. no black flash while playing. * glest segfault [2] I also compared with piglit the old nvfx branch with the new merged one : 114/174 vs 113/174 That looks quite good with 3 new pass, but 4 new fail : * fbo-copypix Returncode was -6 * glean pbo ../../....

...and nv40 Gallium drivers are very similar, and contain about 5000 lines of essentially duplicate code. I prepared a patchset (which can be found at http://repo.or.cz/w/mesa/mesa-lb.git/shortlog/refs/heads/unification+fixes) which gradually unifies the drivers, one file per the commit. A new "nvfx" directory is created, and unified files are put there one by one. After all patches are applied, the nv30 and nv40 directories are removed and the only the new nvfx directory remains. The first patches unify the engine naming (s/curie/eng3d/g; s/rankine/eng3d), and switch nv40 to use the NV3...

https://bugs.freedesktop.org/show_bug.cgi?id=56757 Priority: medium Bug ID: 56757 Assignee: nouveau at lists.freedesktop.org Summary: [regression][bisected][screenshots] nvfx -> nv30 driver rework causes regression in UrbanTerror4.2 (beta5) Severity: normal Classification: Unclassified OS: Linux (All) Reporter: ronald645 at gmail.com Hardware: x86-64 (AMD64) Status:...

...are tightly tied together, and create context is handled similarly, but it shouldn't hurt ? Additionally r300g and llvmpipe added util_format_s3tc_init to their create_screen functions, and util/u_format_s3tc.c apparently contains all the functions that a gallium driver uses. So I suppose that nvfx and nv50 should do the same ? If that's correct, the patch below might not be completely wrong. On Mon, May 3, 2010 at 12:44 AM, Xavier Chantry <chantry.xavier at gmail.com> wrote: > flightgear now dies with : > Mesa warning: external dxt library not available: texstore_rgba_dxt3...

A reworked version of 3 out of 4 patches mentioned earlier. [1/4]: Fixes nearly all piglit vertprog testcases, due to now being able to pass the results on to the fragment shader. V2: rename samplers to texcoords. [2/4]: Fixes shader compiler assertion errors, as some source registers do not exist for certain operations. Fixes several piglit tests when mesa is compiled with --enable-debug [3/4]:

Hello, I have my work on the nv vpe video decoder in a functional state. In case you didn't know this decoder accelerates mpeg2 video at the idct/mc level. I have verified that it works on nv40 hardware. I believe it works on nv30 hardware (and maybe some earlier hardware), but I cannot verify since I have none. I will reply with patches against the kernel, drm, ddx and mesa for

...blending/render targets on nv40 3. NV30 has fixed function registers, which NV40 lacks The vertex shader instruction format also differs, but this does not affect renouveau.xml. This is in preparation for unifying the Gallium drivers. Unification is carried out by creating a new artificial "NVFXTCL" object. This results in most of the old NV34TCL_ and NV40TCL_ definitions being replaced by NVFXTCL_. A sed script is provided to fix the Gallium driver and DDX. This provides the following advantages: 1. Registers are defined only once in renouveau.xml 2. grep NV34TCL_ yields all usages...

...functions. Loosely based on Luca Barbieri's commit 52e9b990a192a9329006d5f7dd2ac222effea5a5. Looking at llvm and r300 code and trying to guess, I came up with the following patch that allows flightgear to start again. But I don't really understand that stuff so it could be wrong. nvfx is probably affected as well. diff --git a/src/gallium/drivers/nouveau/nouveau_screen.c b/src/gallium/drivers/nouveau/nouveau_screen.c index 233a91a..a91b00b 100644 --- a/src/gallium/drivers/nouveau/nouveau_screen.c +++ b/src/gallium/drivers/nouveau/nouveau_screen.c @@ -5,6 +5,7 @@ #include &quo...

...memory. Was easy to discover for me due since I'm using dual head with kwin opengl rendering. glxdemo produce the same corruption if enlarged enougth. Thought I was not really able to test if the same kind of problem appends with expending the height. Note that this is a regression in nv30 from nvfx. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

...../../../../src/mesa/drivers/dri/common/xmlconfig.o ../../../../src/gallium/state_trackers/dri/drm/libdridrm.a ../../../../src/gallium/winsys/nouveau/drm/libnouveaudrm.a ../../../../src/gallium/drivers/trace/libtrace.a ../../../../src/gallium/drivers/rbug/librbug.a ../../../../src/gallium/drivers/nvfx/libnvfx.a ../../../../src/gallium/drivers/nv50/libnv50.a ../../../../src/gallium/drivers/nvc0/libnvc0.a ../../../../src/gallium/drivers/nouveau/libnouveau.a \ -Wl,--start-group ../../../../src/mesa/libmesagallium.a ../../../../src/gallium/auxiliary/libgallium.a -Wl,--end-group \...

https://bugs.freedesktop.org/show_bug.cgi?id=32097 Summary: Segfault when starting X with latest nouveau Product: xorg Version: 7.5 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

For all these patches I'd say: testers are welcome. The first three patches seem good enough to push as we speak IMHO (so if you agree, go ahead!), whereas for the fourth I don't know if this is the desired way to fix. The result of these four patches is that NV34 gives a nearly-correct desktop experience, where only some fading animations appear broken. It's quite useable now! [1/4]:

https://bugs.freedesktop.org/show_bug.cgi?id=49731 Bug #: 49731 Summary: wine 1.5.2 and 3Dmark2001se on nv43 hits assertion in simplify_cmp: Assertion `inst->dst.index < 4096' failed Classification: Unclassified Product: Mesa Version: git Platform: x86 (IA32) OS/Version: Linux

https://bugs.freedesktop.org/show_bug.cgi?id=27603 Summary: [nouveau] Celestia 1.6.0 crashes with nv04_surface_copy_swizzle assertion Product: Mesa Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component:

...nd at bertrand-desktop ~]$ fgfs --fog-disable --timeofday=noon --fg-scenery=/home/bertrand/FlightGear/Scenery/e000n40/ --aircraft=c172p --airport=lfmd --nav1=1fgfs --fog-disable --timeofday=noon --fg-scenery=/home/bertrand/FlightGear/Scenery/e000n40/ --aircraft=c172p --airport=lfmd --nav1=109.95:45 nvfx_screen_get_param:94 - Warning: unknown PIPE_CAP 29 FGMultiplayMgr - No receiver port, Multiplayermode disabled Nasal runtime error: props.setAttribute() with invalid attribute at /usr/share/FlightGear/Nasal/props.nas, line 25 called from: /usr/share/FlightGear/Nasal/gui.nas, line 137 KI266 dme...