<feed xmlns='http://www.w3.org/2005/Atom'>
<title>android-x86-mesa.git/src/gallium/drivers/nvfx, branch r300</title>
<subtitle>Androïd/x86 port of Mesa drivers
</subtitle>
<id>https://git.hiegel.fr/cgit/android-x86-mesa.git/atom?h=r300</id>
<link rel='self' href='https://git.hiegel.fr/cgit/android-x86-mesa.git/atom?h=r300'/>
<link rel='alternate' type='text/html' href='https://git.hiegel.fr/cgit/android-x86-mesa.git/'/>
<updated>2011-03-11T20:39:31Z</updated>
<entry>
<title>gallium: remove flags from the flush function</title>
<updated>2011-03-11T20:39:31Z</updated>
<author>
<name>Marek Olšák</name>
<email>maraeo@gmail.com</email>
</author>
<published>2011-03-07T23:57:48Z</published>
<link rel='alternate' type='text/html' href='https://git.hiegel.fr/cgit/android-x86-mesa.git/commit/?id=7e02303497237cde958c28608477d0c355a8038b'/>
<id>urn:sha1:7e02303497237cde958c28608477d0c355a8038b</id>
<content type='text'>
The drivers have been changed so that they behave as if all of the flags
were set. This is already implicit in most hardware drivers and required
for multiple contexts.

Some state trackers were also abusing the PIPE_FLUSH_RENDER_CACHE flag
to decide whether flush_frontbuffer should be called.
New flag ST_FLUSH_FRONT has been added to st_api.h as a replacement.
</content>
</entry>
<entry>
<title>gallium: remove the geom_flags param from is_format_supported</title>
<updated>2011-03-11T20:39:30Z</updated>
<author>
<name>Marek Olšák</name>
<email>maraeo@gmail.com</email>
</author>
<published>2011-03-07T23:01:58Z</published>
<link rel='alternate' type='text/html' href='https://git.hiegel.fr/cgit/android-x86-mesa.git/commit/?id=e968975cb57eb854769292f7c6ff773c64a386c3'/>
<id>urn:sha1:e968975cb57eb854769292f7c6ff773c64a386c3</id>
<content type='text'>
</content>
</entry>
<entry>
<title>gallium: kill is_resource_referenced</title>
<updated>2011-03-11T20:39:30Z</updated>
<author>
<name>Marek Olšák</name>
<email>maraeo@gmail.com</email>
</author>
<published>2011-03-07T21:35:49Z</published>
<link rel='alternate' type='text/html' href='https://git.hiegel.fr/cgit/android-x86-mesa.git/commit/?id=25485f4b69447514ab8b595aced90c75606a99bd'/>
<id>urn:sha1:25485f4b69447514ab8b595aced90c75606a99bd</id>
<content type='text'>
Only st/xorg used it and even incorrectly with regards to pipelined transfers.
</content>
</entry>
<entry>
<title>nouveau: common linear buffer manager, ported from nv50/nvc0 drivers</title>
<updated>2011-03-01T04:44:43Z</updated>
<author>
<name>Ben Skeggs</name>
<email>bskeggs@redhat.com</email>
</author>
<published>2011-03-01T01:30:25Z</published>
<link rel='alternate' type='text/html' href='https://git.hiegel.fr/cgit/android-x86-mesa.git/commit/?id=5c1c4f8593073c0bad9bada9234657dda1b25ff0'/>
<id>urn:sha1:5c1c4f8593073c0bad9bada9234657dda1b25ff0</id>
<content type='text'>
nv50_resource is being called nv04_resource now temporarily, to avoid
a naming conflict with nouveau_resource from libdrm.

Signed-off-by: Ben Skeggs &lt;bskeggs@redhat.com&gt;
</content>
</entry>
<entry>
<title>gallium: notify drivers about possible changes in user buffer contents</title>
<updated>2011-02-14T20:50:08Z</updated>
<author>
<name>Marek Olšák</name>
<email>maraeo@gmail.com</email>
</author>
<published>2011-02-09T00:10:11Z</published>
<link rel='alternate' type='text/html' href='https://git.hiegel.fr/cgit/android-x86-mesa.git/commit/?id=588fa884d212eba5ffbc69fda75db37d7c77214c'/>
<id>urn:sha1:588fa884d212eba5ffbc69fda75db37d7c77214c</id>
<content type='text'>
Also implement the redefine_user_buffer hook in the drivers.
</content>
</entry>
<entry>
<title>nouveau: fix build against out of tree libdrm</title>
<updated>2011-01-17T05:42:34Z</updated>
<author>
<name>Dave Airlie</name>
<email>airlied@redhat.com</email>
</author>
<published>2011-01-17T05:41:49Z</published>
<link rel='alternate' type='text/html' href='https://git.hiegel.fr/cgit/android-x86-mesa.git/commit/?id=2bf52e7c28e6d48374c3c4314e06e3600d7f668a'/>
<id>urn:sha1:2bf52e7c28e6d48374c3c4314e06e3600d7f668a</id>
<content type='text'>
For doing builds against a separated libdrm these cflags are needed.

Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>nvfx,nv50: pipe_reference the constant buffers</title>
<updated>2011-01-08T14:40:14Z</updated>
<author>
<name>Christoph Bumiller</name>
<email>e0425955@student.tuwien.ac.at</email>
</author>
<published>2011-01-08T14:40:14Z</published>
<link rel='alternate' type='text/html' href='https://git.hiegel.fr/cgit/android-x86-mesa.git/commit/?id=90e29afcb62411b69d57dac76fe89c69c9936ed6'/>
<id>urn:sha1:90e29afcb62411b69d57dac76fe89c69c9936ed6</id>
<content type='text'>
</content>
</entry>
<entry>
<title>gallium: drivers should reference vertex buffers</title>
<updated>2011-01-06T15:16:29Z</updated>
<author>
<name>Marek Olšák</name>
<email>maraeo@gmail.com</email>
</author>
<published>2010-12-26T17:43:39Z</published>
<link rel='alternate' type='text/html' href='https://git.hiegel.fr/cgit/android-x86-mesa.git/commit/?id=3c9aa3a7b12cfe178c14fea93cfb64a32db0b8ad'/>
<id>urn:sha1:3c9aa3a7b12cfe178c14fea93cfb64a32db0b8ad</id>
<content type='text'>
So that a state tracker can unreference them after set_vertex_buffers.
</content>
</entry>
<entry>
<title>nvfx: Remove unused variable.</title>
<updated>2010-12-26T03:09:54Z</updated>
<author>
<name>Vinson Lee</name>
<email>vlee@vmware.com</email>
</author>
<published>2010-12-26T03:09:54Z</published>
<link rel='alternate' type='text/html' href='https://git.hiegel.fr/cgit/android-x86-mesa.git/commit/?id=8ca0aca8dd4075e7d8c692617584a940ebad2d42'/>
<id>urn:sha1:8ca0aca8dd4075e7d8c692617584a940ebad2d42</id>
<content type='text'>
Fixes this GCC warning.
nvfx_vbo.c: In function 'nvfx_idxbuf_emit':
nvfx_vbo.c:410: warning: unused variable 'eng3d'
</content>
</entry>
<entry>
<title>nvfx: restore BEGIN_RING usage</title>
<updated>2010-12-25T19:37:39Z</updated>
<author>
<name>Xavier Chantry</name>
<email>chantry.xavier@gmail.com</email>
</author>
<published>2010-12-25T15:39:01Z</published>
<link rel='alternate' type='text/html' href='https://git.hiegel.fr/cgit/android-x86-mesa.git/commit/?id=5f0f9f0486e9cf43939dfbd1051298f05da1eec4'/>
<id>urn:sha1:5f0f9f0486e9cf43939dfbd1051298f05da1eec4</id>
<content type='text'>
Michel Hermier reported libdrm segfault (and kernel crash) on nv40 using
gallium :
http://www.mail-archive.com/nouveau@lists.freedesktop.org/msg06563.html

It turns out these were caused by some missing WAIT_RING (or wrong
computation of the WAIT_RING sizes). Unlike all other libdrm_nouveau users,
nvfx gallium tried to use a mininum calls of WAIT_RING, one WAIT_RING could
apply to many methods for different code paths and spread across several
functions. This made it too tricky to find out what the missing or wrong
WAIT_RING was.

By restoring BEGIN_RING, we force one WAIT_RING per method, and it's much
easier to check if the free size required in the pushbuffer is correct.  As
curro said, "let's keep it simple for the maintainers until the big
bottlenecks are gone"

Benchmarked on nv35 with openarena, nexuiz and ut2004 and no performance
regression.

The core of this patch was made with Coccinelle, with minor manual fixes
made on top.

Tested-by: Michel Hermier &lt;hermier@frugalware.org&gt;
Signed-off-by: Francisco Jerez &lt;currojerez@riseup.net&gt;
</content>
</entry>
</feed>
