On Fri, 2008-06-06 at 15:39 +0200, Thomas Hellström wrote:
Hi!
A small suggestion to the core GEM interface:
Could you add a driver-private uint64_t member when a gem object is created?
The primary purpose of this member would be to allow the implementation
to choose the
initial
We're getting close to ready to mark GEM on Intel as done. We've got
one failing testcase that we isolated this week with interrupt handling,
and we've got a fix in testing that appears to be doing the job.
Tomorrow I'm planning on merging the GEM code to master of all 3
repositories. At that
Eric Anholt wrote:
On Fri, 2008-06-06 at 15:39 +0200, Thomas Hellström wrote:
Hi!
A small suggestion to the core GEM interface:
Could you add a driver-private uint64_t member when a gem object is created?
The primary purpose of this member would be to allow the implementation
to
Quoting Eric Anholt:
We're getting close to ready to mark GEM on Intel as done. We've got
one failing testcase that we isolated this week with interrupt handling,
and we've got a fix in testing that appears to be doing the job.
Tomorrow I'm planning on merging the GEM code to master of all 3
Quoting He, Shuang:
You may need to build mesa with --enable-ttm-api, and update drm
kernel modules as well whose source is under drm/linux-core,
Thanks for your hint, I had that symbol already enabled. Once I enabled
ttm-api in Mesa I get the following (of course after recompiling xserver
Eric Anholt wrote:
We're getting close to ready to mark GEM on Intel as done. We've got
one failing testcase that we isolated this week with interrupt handling,
and we've got a fix in testing that appears to be doing the job.
Tomorrow I'm planning on merging the GEM code to master of all 3
Eric Anholt wrote:
We're getting close to ready to mark GEM on Intel as done. We've got
one failing testcase that we isolated this week with interrupt handling,
and we've got a fix in testing that appears to be doing the job.
Tomorrow I'm planning on merging the GEM code to master of all 3
Eric Anholt wrote:
Please clarify which commits of which branches were used in the test,
along with which kernel version.
I can't really analyze your results, which differ significantly from
ours, without that.
Sure.
I'm using the drm-gem branches of mesa, drm and xf86-video-intel. On
2008/6/12 Daniel Stone [EMAIL PROTECTED]:
On Thu, Jun 12, 2008 at 10:49:57AM +0300, Timo Jyrinki wrote:
Speaking of which, if you have any ideas how to better interlink and combine:
- http://dri.freedesktop.org/
- http://xorg.freedesktop.org/
- http://mesa3d.org/
...
I don't understand why
On Thu, Jun 12, 2008 at 5:28 PM, Timo Jyrinki [EMAIL PROTECTED] wrote:
2008/6/12 Daniel Stone [EMAIL PROTECTED]:
On Thu, Jun 12, 2008 at 10:49:57AM +0300, Timo Jyrinki wrote:
Speaking of which, if you have any ideas how to better interlink and
combine:
- http://dri.freedesktop.org/
-
Keith Whitwell wrote:
The DRI list has in effect become the list for development of the drm
kernel module, libdrm, and the various memory manager implementations.
While Mesa is an important client of these, it is far from being the
only client.
Interesting. Who else is a client of drm?
On Thu, Jun 12, 2008 at 12:56 PM, Tomas Carnecky [EMAIL PROTECTED] wrote:
Keith Whitwell wrote:
The DRI list has in effect become the list for development of the drm
kernel module, libdrm, and the various memory manager implementations.
While Mesa is an important client of these, it is far
He, Shuang wrote:
Johannes Engel ??:
Quoting Eric Anholt:
We're getting close to ready to mark GEM on Intel as done. We've got
one failing testcase that we isolated this week with interrupt handling,
and we've got a fix in testing that appears to be doing the job.
Tomorrow I'm planning
On Thu, Jun 12, 2008 at 10:14 AM, Keith Packard [EMAIL PROTECTED] wrote:
On Thu, 2008-06-12 at 09:03 +0200, Thomas Hellström wrote:
Yes, unless it's to enforce a local permission model, like the old DRM
shmem maps did.
Abusing GEM objects to hold state which never touches the graphics card
http://bugs.freedesktop.org/show_bug.cgi?id=7155
mitch074 [EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
On Thu, 2008-06-12 at 16:06 +0100, Johannes Engel wrote:
Quoting He, Shuang:
You may need to build mesa with --enable-ttm-api, and update drm
kernel modules as well whose source is under drm/linux-core,
Thanks for your hint, I had that symbol already enabled. Once I enabled
ttm-api in
http://bugs.freedesktop.org/show_bug.cgi?id=16321
Summary: [GEM] Updated DRM has issues with wait_irq ioctl
Product: Mesa
Version: CVS
Platform: Other
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority:
http://bugs.freedesktop.org/show_bug.cgi?id=16321
Eric Anholt [EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
--
Keith Packard wrote:
On Thu, 2008-06-12 at 16:06 +0100, Johannes Engel wrote:
Quoting He, Shuang:
You may need to build mesa with --enable-ttm-api, and update drm
kernel modules as well whose source is under drm/linux-core,
Thanks for your hint, I had that symbol already
On Thu, 2008-06-12 at 17:17 +0200, Thomas Hellström wrote:
Eric Anholt wrote:
We're getting close to ready to mark GEM on Intel as done. We've got
one failing testcase that we isolated this week with interrupt handling,
and we've got a fix in testing that appears to be doing the job.
http://bugs.freedesktop.org/show_bug.cgi?id=16323
Summary: [classic 945]Mesa demo ipers draw nothing
Product: Mesa
Version: unspecified
Platform: Other
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority:
http://bugs.freedesktop.org/show_bug.cgi?id=16323
--- Comment #1 from Colin.Joe [EMAIL PROTECTED] 2008-06-12 20:04:12 PST ---
Created an attachment (id=17085)
-- (http://bugs.freedesktop.org/attachment.cgi?id=17085)
Xorg.0.log
--
Configure bugmail:
http://bugs.freedesktop.org/show_bug.cgi?id=16325
Summary: [945 classic]demo case 'terrain' font wrong
Product: Mesa
Version: unspecified
Platform: Other
OS/Version: Linux (All)
Status: NEW
Severity: normal
http://bugs.freedesktop.org/show_bug.cgi?id=16325
--- Comment #1 from Colin.Joe [EMAIL PROTECTED] 2008-06-12 20:30:55 PST ---
Created an attachment (id=17086)
-- (http://bugs.freedesktop.org/attachment.cgi?id=17086)
Xorg.0.log
--
Configure bugmail:
http://bugs.freedesktop.org/show_bug.cgi?id=16325
--- Comment #2 from Colin.Joe [EMAIL PROTECTED] 2008-06-12 20:32:27 PST ---
Created an attachment (id=17087)
-- (http://bugs.freedesktop.org/attachment.cgi?id=17087)
wrong font photo
--
Configure bugmail:
*GEARS* (Should be GPU bound)
i915tex (TTM):1035fps @ 70% CPU
GEM, no buffer reuse: 863fps @ 95% CPU
GEM, buffer reuse: 1000fps @ 80% CPU
Unichrome CX700 1009fps @ 70% CPU
So just to try and do some testing off my own, I can't get TTM code from
However so far I can't get glxgears on TTM to not flicker as do all my
other apps. Am I missing something?
Granted my gears numbers are better with TTM, but the flicker does leave
me to think something broke.
Ah keithp pointed out single buffered rendering due to visual failure.
It
27 matches
Mail list logo
