http://bugs.freedesktop.org/show_bug.cgi?id=10892
Summary: Mesa build failure: drm_i915_flip conflict between
intel_buffers.c and DRM
Product: Mesa
Version: CVS
Platform: x86 (IA32)
OS/Version: All
Status: NEW
On 5/8/07, Christoph Brill [EMAIL PROTECTED] wrote:
I reviewed the cleanup done by Olliver McFadden and had the following
questions:
-int r300_get_num_verts(r300ContextPtr rmesa, int num_verts, int prim)
+static int r300NumVerts(r300ContextPtr rmesa, int num_verts, int prim)
Is it
Dave Airlie wrote:
I'll try it out as soon as there is time.
I've just tested glxgears and a few mesa tests on it and it seems to
be working fine
We should probably think about pulling this over into the DRM sooner
rather than later, there are also some changes to the DDX
i830_driver.c
...And the patch.
Thomas Hellström wrote:
Dave Airlie wrote:
I'll try it out as soon as there is time.
I've just tested glxgears and a few mesa tests on it and it seems to
be working fine
We should probably think about pulling this over into the DRM sooner
rather than later, there are
On 5/9/07, Thomas Hellström [EMAIL PROTECTED] wrote:
Dave Airlie wrote:
I'll try it out as soon as there is time.
I've just tested glxgears and a few mesa tests on it and it seems to
be working fine
We should probably think about pulling this over into the DRM sooner
rather than
On Fri, 2007-05-04 at 14:47 -0700, Jesse Barnes wrote:
In playing around yesterday, we found that some drivers will
unnecessarily enable interrupts for vblank events. Since these tend to
happen frequently (60+ Hz), they'll cause your CPU to wake up a lot,
which will waste power if they're
Jerome Glisse wrote:
On 5/8/07, Christoph Brill [EMAIL PROTECTED] wrote:
I reviewed the cleanup done by Olliver McFadden and had the following
questions:
-int r300_get_num_verts(r300ContextPtr rmesa, int num_verts, int prim)
+static int r300NumVerts(r300ContextPtr rmesa, int num_verts, int
Hi,
I added the not implemented yet comment back, although there are other places
that use 65535 so it could be some kind of hardware limit...
The only reason that I went with camel case r300FooBar names is because that's
what 90% of the driver uses; it's easier to change a few r300_foo_bar to
I also think we might need to add _dri_warning/_dri_error because the _mesa
versions output Mesa warning: %s which implies to the user this is a Mesa
problem, not a DRI driver problem.
I could add r300Warning and r300Error, but probably all DRI drivers need warning
and error functions... So maybe
I'd like some input on the VBO stuff in r300. In r300_context.h we have the
following.
/* KW: Disable this code. Driver should hook into vbo module
* directly, see i965 driver for example.
*/
/* #define RADEON_VTXFMT_A */
#ifdef RADEON_VTXFMT_A
#define HW_VBOS
#endif
So the VTXFMT
Here is the patch.
On 5/9/07, Oliver McFadden [EMAIL PROTECTED] wrote:
I'd like some input on the VBO stuff in r300. In r300_context.h we have the
following.
/* KW: Disable this code. Driver should hook into vbo module
* directly, see i965 driver for example.
*/
/* #define RADEON_VTXFMT_A
Oliver McFadden wrote:
I'd like some input on the VBO stuff in r300. In r300_context.h we have the
following.
/* KW: Disable this code. Driver should hook into vbo module
* directly, see i965 driver for example.
*/
/* #define RADEON_VTXFMT_A */
#ifdef RADEON_VTXFMT_A
#define HW_VBOS
On Wed, 2007-05-09 at 12:33 +0200, Michel Dänzer wrote:
On Fri, 2007-05-04 at 14:47 -0700, Jesse Barnes wrote:
In playing around yesterday, we found that some drivers will
unnecessarily enable interrupts for vblank events. Since these tend to
happen frequently (60+ Hz), they'll cause
Oliver McFadden wrote:
I'd like some input on the VBO stuff in r300. In r300_context.h we have the
following.
/* KW: Disable this code. Driver should hook into vbo module
* directly, see i965 driver for example.
*/
/* #define RADEON_VTXFMT_A */
#ifdef RADEON_VTXFMT_A
#define HW_VBOS
Oliver McFadden wrote:
I also think we might need to add _dri_warning/_dri_error because the _mesa
versions output Mesa warning: %s which implies to the user this is a Mesa
problem, not a DRI driver problem.
I could add r300Warning and r300Error, but probably all DRI drivers need
warning
Well both Keith and Jerome are okay with me removing the VTXFMT code, so I'll go
ahead and do that.
I don't think there is any serious risk as I'm only removing code that is
already disabled. :) Brian, let me know if you want to make a branch so I know
when I can push.
On 5/9/07, Brian Paul
If it's just dead code removal, go ahead.
-Brian
Oliver McFadden wrote:
Well both Keith and Jerome are okay with me removing the VTXFMT code, so
I'll go
ahead and do that.
I don't think there is any serious risk as I'm only removing code that is
already disabled. :) Brian, let me know if
Done.
On 5/9/07, Brian Paul [EMAIL PROTECTED] wrote:
If it's just dead code removal, go ahead.
-Brian
Oliver McFadden wrote:
Well both Keith and Jerome are okay with me removing the VTXFMT code, so
I'll go
ahead and do that.
I don't think there is any serious risk as I'm only
http://bugs.freedesktop.org/show_bug.cgi?id=10892
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
Hi list,
I've been browsing through the code to get more in touch with it. On my
way I added few doxygen comments and removed the use of a unnecessary
function. The removal was agreed by Jerome Glisse.
Please check and push these.
Thanks in advance,
Christoph Brill
http://bugs.freedesktop.org/show_bug.cgi?id=10892
--- Comment #2 from [EMAIL PROTECTED] 2007-05-09 12:07 PST ---
Thanks, Michel. Your reply resolved my problem. I'd just like to confirm the
behavior of the DRM and Mesa makefiles now.
For DRM,
$ ./autogen.sh --prefix=/usr
21 matches
Mail list logo
