http://bugs.freedesktop.org/show_bug.cgi?id=25193
--- Comment #1 from Alex Deucher 2009-11-19 22:02:08 PST ---
Sounds like you are building against an old version of libdrm_radeon. To
update build libdrm configured with --enable-radeon-experimental-api
--
Configure bugmail: http://bugs.f
http://bugs.freedesktop.org/show_bug.cgi?id=25109
--- Comment #3 from Tom 2009-11-19 21:24:36 PST ---
I tried to run git bisect to find the cause of this bug, but I couldn't find
the exact commit because some of the commits caused Wine to crash. However, I
still think I have some useful inf
http://bugs.freedesktop.org/show_bug.cgi?id=25193
Summary: Git 3f2c77659ca552c43f544228f3a5a5fe6365513a breaks here
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
http://bugs.freedesktop.org/show_bug.cgi?id=25177
--- Comment #5 from Maciej Cencora 2009-11-19 13:18:55
PST ---
(In reply to comment #4)
> That was from yesterday's merges around 2009-11-18 23:55
>
I'll try reproducing this bug on my machine.
--
Configure bugmail: http://bugs.freedesk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tormod Volden wrote:
> From: Tormod Volden
>
> ---
>
> For automated bug triaging hackery purposes, it can be nice to have
> these chipset labels, reported in glxinfo, more consistent.
>
> I wonder if also the "E7221G (i915)" string can be further
> On Tue, 2009-11-10 at 14:30 -0800, Andrew Morton wrote:
> > On Wed, 4 Nov 2009 20:03:19 +0100
> > Jerome Glisse wrote:
> >
> > > Just do nothings crct_set_base i call with no FB.
> > >
> >
> > hmpf. It's obvious that you spent hours carefully describing this
> > patch for us.
> >
>
> Sor
http://bugs.freedesktop.org/show_bug.cgi?id=25177
--- Comment #4 from Shawn Starr 2009-11-19 12:30:57
PST ---
That was from yesterday's merges around 2009-11-18 23:55
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: --
Martin Michlmayr wrote:
> drm/ttm fails to build on MIPS because "struct page" is not known:
> | In file included from drivers/gpu/drm/ttm/ttm_memory.c:28:
> | include/drm/ttm/ttm_memory.h:154: warning: 'struct page' declared inside
> parameter list
> | include/drm/ttm/ttm_memory.h:154: warning: i
Sorry, I think I posted this (and the previous patch) to the wrong
mailing list. This should have gone to Mesa3d-dev@ I guess. Or even
intel-...@.
Tormod
--
Let Crystal Reports handle the reporting - Free Crystal Reports
http://bugs.freedesktop.org/show_bug.cgi?id=25114
Alex Deucher changed:
What|Removed |Added
Component|DRM/Radeon |Drivers/DRI/R600
Product|DRI
From: Tormod Volden
---
For automated bug triaging hackery purposes, it can be nice to have
these chipset labels, reported in glxinfo, more consistent.
I wonder if also the "E7221G (i915)" string can be further harmonized
with the other labels, but I have no idea what that chip is.
Tormod
sr
>From fa621056b43d24ca97b61863c8566ac12696ce25 Mon Sep 17 00:00:00 2001
From: Jesse Barnes
Date: Thu, 19 Nov 2009 10:25:46 -0800
Subject: [PATCH 2/2] drm: use page flip event to signal flip completion
We don't actually know which frame number the flip will complete on, so
userspace needs a specif
>From 3dea813806ecc117fadd2751580018040afefd0b Mon Sep 17 00:00:00 2001
From: Jesse Barnes
Date: Wed, 18 Nov 2009 04:31:47 +
Subject: [PATCH 1/2] drm/i915: add GETPARAM request for page flipping
Add a GETPARAM request for checking if page flipping is supported.
Useful for the 2D driver to ena
Dave, here's an updated version that fixes the checkpatch warnings, removes a
stray line (the forced alignment hack) and fixes pre-965 support. I have
some related followup patches, but I think this one is ready.
Thanks,
Jesse
--
From 2bec6039e7e6180a981971665be712f5a5b9b0e0 Mon Sep 17 00:00:00
From: Tormod Volden
---
src/mesa/drivers/dri/radeon/radeon_bo_legacy.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/src/mesa/drivers/dri/radeon/radeon_bo_legacy.c
b/src/mesa/drivers/dri/radeon/radeon_bo_legacy.c
index ce60a2f..90b69f9 100644
--- a/src/mesa/drivers/d
* Thomas Hellstrom [2009-11-19 14:49]:
> Sorry for not reviewing this earlier, but what about including the
> include file that defines
> struct page instead of a separate declaration?
Sure, I can send such a patch.
--
Martin Michlmayr
http://www.cyrius.com/
drm/ttm fails to build on MIPS because "struct page" is not known:
| In file included from drivers/gpu/drm/ttm/ttm_memory.c:28:
| include/drm/ttm/ttm_memory.h:154: warning: 'struct page' declared inside
parameter list
| include/drm/ttm/ttm_memory.h:154: warning: its scope is only this definition
On Tue, 2009-11-17 at 11:33 -0500, Kristian Høgsberg wrote:
> 2009/11/6 Kristian Høgsberg :
> > Hi,
> >
> > This has come up a few time and it's something I think makes a lot of
> > sense. Since all driver development (afaik) now happens in linux
> > kernel tree, it makes sense to drop the driver
http://bugs.freedesktop.org/show_bug.cgi?id=25179
--- Comment #1 from Alex Deucher 2009-11-19 07:29:54 PST ---
(In reply to comment #0)
> After the great work of Maciej doom3 now starts fine. However after about 1
> minute of play the game trigger this:
>
> *
drm/ttm fails to build on MIPS because "struct page" is not known:
| In file included from drivers/gpu/drm/ttm/ttm_memory.c:28:
| include/drm/ttm/ttm_memory.h:154: warning: 'struct page' declared inside
parameter list
| include/drm/ttm/ttm_memory.h:154: warning: its scope is only this definition
Martin,
Sorry for not reviewing this earlier, but what about including the
include file that defines
struct page instead of a separate declaration?
/Thomas
Martin Michlmayr wrote:
> drm/ttm fails to build on MIPS because "struct page" is not known:
> | In file included from drivers/gpu/drm/tt
Hi Jerome,
Actually, I haven't done any benchmark yet.
The memory management itself is complicated and powerful, and the fence
object "allocate/free" is trivial to some extent in contrast with the memory
management. So maintain a pool in the driver is useless, meanwhile the
kernel slab act the
http://bugs.freedesktop.org/show_bug.cgi?id=23710
Fabio changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
http://bugs.freedesktop.org/show_bug.cgi?id=25179
Summary: File radeon_dma.c function radeonReleaseDmaRegions line
348 - Leaking dma buffer object!
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
http://bugs.freedesktop.org/show_bug.cgi?id=22742
Fabio changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
On Thu, 2009-11-19 at 16:29 +0800, Donnie Fang wrote:
> Hi all,
> after reviewed the radeon fence scheme, there are lots of chances
> that it needs create a new fence object, and also there are lots of
> chances need to destroy these fence objects.
> In my opinion, is it possible to mainta
http://bugs.freedesktop.org/show_bug.cgi?id=25177
Maciej Cencora changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #3 from Maciej
http://bugs.freedesktop.org/show_bug.cgi?id=21501
Maciej Cencora changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #4 from Maciej
Hi all,
after reviewed the radeon fence scheme, there are lots of chances that
it needs create a new fence object, and also there are lots of chances need
to destroy these fence objects.
In my opinion, is it possible to maintain a list for recording some
freed fence object for later usage
brucech...@via.com.tw wrote:
> Hello Sirs:
> Thank you very much for your help on adding VX800 PCIIDS. I would also
> like to share the DRM patch I have for VIA Chrome9 graph as below. The
> 32bit/64bit issue is solved with comp_ioctl which is used by most of the
> GFX chipset. This patch ha
30 matches
Mail list logo