Re: [Dri-devel] Re: CVS Update: xc (branch: trunk)

2003-10-08 Thread Keith Whitwell
Eric Anholt wrote: On Tue, 2003-10-07 at 10:42, Alex Deucher wrote: I have a question about the license at the top of these new files. what should I put for the copyright? Some of the the code was written by me, but much of it was taken from the sis and mga drivers. Also, what to I put for the

Re: [Dri-devel] dri-cvs & miniglx merge

2003-10-08 Thread Keith Whitwell
Otto Solares wrote: Hi! I am trying to merge the r200 driver from dri-cvs to mesa-miniglx, finally i had most files merged but i am finding heavy X dependencies in header files in dri-cvs (eg radeon.h), it was not supposed dri drivers should be backend agnostic? Is somebody working on resolving th

[Dri-devel] Another cvs policy question

2003-10-08 Thread Felix Kühling
Hi, I have a working copy of the config-0-0-1-branch with the trunk merged in now. According to the CVS policy I would have to commit this to the branch. However, this would be a huge commit due to the intermediate merge from XFree86. cvs diff -uN outputs a 323074-lines patch (11 MB). I believe it

Re: [Dri-devel] Another cvs policy question

2003-10-08 Thread Keith Whitwell
Felix Kühling wrote: Hi, I have a working copy of the config-0-0-1-branch with the trunk merged in now. According to the CVS policy I would have to commit this to the branch. However, this would be a huge commit due to the intermediate merge from XFree86. cvs diff -uN outputs a 323074-lines patch

Re: [Dri-devel] dri-cvs & miniglx merge

2003-10-08 Thread Alan Hourihane
On Wed, Oct 08, 2003 at 12:53:29AM -0600, Otto Solares wrote: > Hi! > > I am trying to merge the r200 driver from dri-cvs to mesa-miniglx, > finally i had most files merged but i am finding heavy X dependencies > in header files in dri-cvs (eg radeon.h), it was not supposed dri > drivers should be

Re: [Dri-devel] Another cvs policy question

2003-10-08 Thread Felix Kühling
On Wed, 08 Oct 2003 10:38:04 +0100 Keith Whitwell <[EMAIL PROTECTED]> wrote: > Felix Kühling wrote: > > Hi, > > > > I have a working copy of the config-0-0-1-branch with the trunk merged > > in now. According to the CVS policy I would have to commit this to the > > branch. However, this would be

Re: [Dri-devel] Another cvs policy question

2003-10-08 Thread Keith Whitwell
Felix Kühling wrote: On Wed, 08 Oct 2003 10:38:04 +0100 Keith Whitwell <[EMAIL PROTECTED]> wrote: Felix Kühling wrote: Hi, I have a working copy of the config-0-0-1-branch with the trunk merged in now. According to the CVS policy I would have to commit this to the branch. However, this would be

Re: [Dri-devel] dri hangs the pc (radeon 7000/VE, SiS645DX AGP)

2003-10-08 Thread Helge Hafting
Michel Dänzer wrote: On Mon, 2003-10-06 at 14:06, Helge Hafting wrote: Unfortunately, xserver-xfree86-dri-trunk from http://people.debian.org/~daenzer/dri-trunk-sid/ hangs my machine rather quickly. X comes up, and can be used in any way for a few seconds. (Rarely enough to log in via xdm) Then

Re: [Dri-devel] radeon & Transition functions

2003-10-08 Thread Jacek Rosik
W liście z pon, 06-10-2003, godz. 15:28, Keith Whitwell pisze: > > I know that vertex are accumulated and then are sent to the hardware. > > Is it possible (hard?) to do something like this in order to render > > into more than buffer. > > > > radeonSetBuffer(GL_FRONT_LEFT) > > radeonSendDataToH

Re: [Dri-devel] radeon & Transition functions

2003-10-08 Thread Keith Whitwell
Jacek Rosik wrote: W liście z pon, 06-10-2003, godz. 15:28, Keith Whitwell pisze: I know that vertex are accumulated and then are sent to the hardware. Is it possible (hard?) to do something like this in order to render into more than buffer. radeonSetBuffer(GL_FRONT_LEFT) radeonSendDataToHardw

[Dri-devel] drm 'lockup' with i845G onboard graphics....

2003-10-08 Thread Daniel Blueman
When I switch from an X session to the (text mode) VGA console, the kernel logs these messages and X gets killed: [drm:i830_wait_ring] *ERROR* space: 131048 wanted 131064 [drm:i830_wait_ring] *ERROR* lockup The mode I'm running in is 1600 x 1200 x 16bpp, and the Intel 845G Extreme Graphics core i

Re: [Dri-devel] dri-cvs & miniglx merge

2003-10-08 Thread Alex Deucher
it's be nice if we could merge radeon and r200 into one driver when we did this as well. Alex --- Alan Hourihane <[EMAIL PROTECTED]> wrote: > On Wed, Oct 08, 2003 at 12:53:29AM -0600, Otto Solares wrote: > > Hi! > > > > I am trying to merge the r200 driver from dri-cvs to mesa-miniglx, > > final

Re: [Dri-devel] dri-cvs & miniglx merge

2003-10-08 Thread Otto Solares
On Wed, Oct 08, 2003 at 09:48:16AM +0100, Keith Whitwell wrote: > Otto Solares wrote: > >Hi! > > > >I am trying to merge the r200 driver from dri-cvs to mesa-miniglx, > >finally i had most files merged but i am finding heavy X dependencies > >in header files in dri-cvs (eg radeon.h), it was not sup

[Dri-devel] Broken Xv in current trunk?

2003-10-08 Thread Stefan Lange
Hello, if I try to use Xv (via mplayer, or with xawtv using the v4l-module) with current cvs (trunk) the X server crashes. I'm using a r200-based card (Radeon 8500). When I check out cvs from just before the mergedfb-merge (i tried 2003-10-07, 4:30:00), I get no problems, so the merge might have

Re: [Dri-devel] Broken Xv in current trunk?

2003-10-08 Thread Roland Scheidegger
Stefan Lange wrote: Hello, if I try to use Xv (via mplayer, or with xawtv using the v4l-module) with current cvs (trunk) the X server crashes. I'm using a r200-based card (Radeon 8500). When I check out cvs from just before the mergedfb-merge (i tried 2003-10-07, 4:30:00), I get no problems, so

Re: [Dri-devel] dri hangs the pc (radeon 7000/VE, SiS645DX AGP)

2003-10-08 Thread Michel Dänzer
On Tue, 2003-10-07 at 11:44, Helge Hafting wrote: > > I did some more experiments with these packages: > xserver-xfree86-dri-trunk xlibmesa-gl1-dri-trunk BTW, there are new versions available, I suppose they don't make a difference? > xdm manages to start, but displays an ugly black & white wind

Re: [Dri-devel] Broken Xv in current trunk?

2003-10-08 Thread Michel Dänzer
On Wed, 2003-10-08 at 22:30, Stefan Lange wrote: > Hello, > if I try to use Xv (via mplayer, or with xawtv using the v4l-module) > with current cvs (trunk) the X server crashes. I'm using a r200-based > card (Radeon 8500). > When I check out cvs from just before the mergedfb-merge (i tried > 200

Re: [Dri-devel] Broken Xv in current trunk?

2003-10-08 Thread Alex Deucher
that's my fault. there's a small bug that I missed that breaks Xv in non-mergedfb mode. I have the fix. it will be committed ASAP. Alex --- Stefan Lange <[EMAIL PROTECTED]> wrote: > Hello, > if I try to use Xv (via mplayer, or with xawtv using the v4l-module) > with current cvs (trunk) the X se

Re: [Dri-devel] Broken Xv in current trunk?

2003-10-08 Thread Linus Torvalds
On Thu, 9 Oct 2003, Michel Dänzer wrote: > > I could, and I just fixed this in CVS. The cause was dereferencing a > pointer which is uninitialized in non-MergedFB mode. It's still broken on i845, though. No crashes, but Xv windows show up as all blue (I assume that's the overlay color), and the

[Dri-devel] [Bug 314] 3D support for Radeon IGP chips

2003-10-08 Thread bugzilla-daemon
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter your comments there. http://bugs.xfree86.org/show_bug.cgi?id=314 --- Additional Comments From [EMAIL PROTECTED] 2003-08-10 21:40 --- I give some more infor

Re: [Dri-devel] Broken Xv in current trunk?

2003-10-08 Thread Alex Deucher
A fix just went into xfree86 CVS earlier today that fixed several things related to Xv on i8xx hardware. that code hasn't been synced with DRI CVS yet. I don't have intel hardware so I can't test. The problem with Xv on radeon was a bug in my mergedfb code, but it's fixed now. Alex --- Linus T