Hi all,
I've gotten all the patches that have gone into 2.6 into the DRM
module except one,
there is a patch in 2.6 to add sysfs support to the DRM, it is at
http://dri.freedesktop.org/~airlied/drm-2.6.diff
It is a bit intrusive and I can't see an easy way to wrap it ...
How have we
It is a bit intrusive and I can't see an easy way to wrap it ...
How have we dealt with these sorta major ones before? and at what point
should we just branch the DRM so 2.4 and 2.6 are separate tracks? (I might
start another e-mail in a minute...)
Okay I talked with Michael Danzer on IRC
Am Donnerstag, 8. April 2004 15:13 schrieb Dave Airlie:
It is a bit intrusive and I can't see an easy way to wrap it ...
How have we dealt with these sorta major ones before? and at what point
should we just branch the DRM so 2.4 and 2.6 are separate tracks? (I
might start another e-mail
On Thu, 2004-04-08 at 16:32, Dieter Ntzel wrote:
Am Donnerstag, 8. April 2004 15:13 schrieb Dave Airlie:
our DRM is now synced with changes in 2.6 that we don't have, now to try
and get a patch or maybe a bk repo going the other way...
Thanks for working on this Dave.
Apr 7 17:39:53
Jacek Rosik wrote:
Hi,
For some time i haven't been paying much attention to dri development.
I'm need to do some work now but I'm little lost. From my little
investigation I presume that situation looks more less like this.
* 3d driver development was moved to mesa tree, bu it needs dri tree in
Second:
What about this ksymoops?
I could catch it for the first time when the system hangs after running UT2003
only some FEW seconds.
hmm .. might be a pre-emption issue in the drivers somewhere, try it with
pre-empt turned of .. or maybe just UP and see if it still happens..
Dave.
Am Donnerstag, 8. April 2004 17:14 schrieb Michel Dnzer:
On Thu, 2004-04-08 at 16:32, Dieter Ntzel wrote:
Am Donnerstag, 8. April 2004 15:13 schrieb Dave Airlie:
our DRM is now synced with changes in 2.6 that we don't have, now to
try and get a patch or maybe a bk repo going the other
Am Donnerstag, 8. April 2004 17:26 schrieb Dave Airlie:
Second:
What about this ksymoops?
I could catch it for the first time when the system hangs after running
UT2003 only some FEW seconds.
hmm .. might be a pre-emption issue in the drivers somewhere, try it with
pre-empt turned of ..
I updated to the latest cvs as of this morning. glxgears works fine, and flx info says
sirect rendering is enabled. I don't have any problems with scrambled windows.
However, the last two times I've built from cvs tuxracer has been crashing (it worked
with earlier cvs). Here is the diagnostic
dri-trunk/xc diff -ur xc/programs/Xserver/GL/glx/single2.c
xc/programs/Xserver/GL/glx/single2.c.orig
--- xc/programs/Xserver/GL/glx/single2.c2004-03-04 23:01:25.0
+0100
+++ xc/programs/Xserver/GL/glx/single2.c.orig 2004-04-08 18:19:38.936761159
+0200
@@ -344,7 +344,7 @@
On Thu, Apr 08, 2004 at 06:22:15PM +0200, Dieter Nützel wrote:
dri-trunk/xc diff -ur xc/programs/Xserver/GL/glx/single2.c
xc/programs/Xserver/GL/glx/single2.c.orig
--- xc/programs/Xserver/GL/glx/single2.c2004-03-04 23:01:25.0
+0100
+++
There are problems building the savage driver on systems that pass
5 args into remap_page_range().
Looking at that function, isn't it best to follow suit with how the
i810 and i830 do this ?
Alan.
---
This SF.Net email is sponsored by: IBM
Am Donnerstag, 8. April 2004 19:54 schrieb Alan Hourihane:
On Thu, Apr 08, 2004 at 05:48:52PM +0200, Dieter Nützel wrote:
Am Donnerstag, 8. April 2004 17:14 schrieb Michel Dänzer:
On Thu, 2004-04-08 at 16:32, Dieter Nützel wrote:
Am Donnerstag, 8. April 2004 15:13 schrieb Dave Airlie:
On Thu, 8 Apr 2004 19:28:29 +0100
Alan Hourihane [EMAIL PROTECTED] wrote:
There are problems building the savage driver on systems that pass
5 args into remap_page_range().
Looking at that function, isn't it best to follow suit with how the
i810 and i830 do this ?
This is the reason why I
After the Mesa CVS rearrangement the libOSMesa libary in Mesa CVS and in the
DRI CVS tree differs. But we only have the osmesa.h version in Mesa CVS.
Where can I find the right one for /usr/X11R6/lib/libOSMesa.so.4.0?
I get errors with /opt/Mesa/include/GL/osmesa.h
and
BTW, I'm going to start working on the DRM driver soon. I'm not sure
where to make my changes, in the xc module or in the new drm module. Has
the transition been formally completed? I havn't heard anything definite
yet. But apperently some people are already committing stuff in the new
On Fri, Apr 09, 2004 at 12:38:07AM +0100, Dave Airlie wrote:
BTW, I'm going to start working on the DRM driver soon. I'm not sure
where to make my changes, in the xc module or in the new drm module. Has
the transition been formally completed? I havn't heard anything definite
yet. But
17 matches
Mail list logo
