Re: [Dri-devel] Status of XFree86 4.4.0 integration?
On Mon, Mar 01, 2004 at 07:43:51PM -0700, [EMAIL PROTECTED] wrote: >> On Mon, Mar 01, 2004 at 06:44:38PM +, Alan Cox wrote: >>>On Llu, 2004-03-01 at 14:34, Adam K Kirchhoff wrote: The client libraries are still distributed under the old license, so there is no problem linking GPLed libraries or apps to the 4.4 libraries. Which means there is no longer a reason for those distributions not to include 4.4 any more. >>> >>>There are several reasons, including for example the X Vnc servers >>> which also use GPL code in the server >> >> The GLX licence is problematic for this also, given that it is used in >> the server. Both the freedesktop.org and x.org trees also >> included this problematic GLX code last I checked. I think it >> would be good all around if each of these projects, including the >> DRI project, made a clear licensing policy statement. As everyone >> should know by now, you can't be a little bit GPL-incompatible. >> Either you are or you aren't. >> > >It's certainly a can of worms. I'm not particularly interested in the >subtle differences between licenses, but I can say that the GLX-licenced >code doesn't have much to do with the DRI project in particular - I >believe it came directly from SGI and their license has been maintained >since then. All the changes from this project (to my knowledge) have >been intended to fall under a license comparable to the older, previous, >uncontentious XFree86 one. If there are issues with the continued use of >the GLX code, the first step would be to approach SGI and request a change >of license. I've no idea if this would be succesful or not. I've also no >idea if it is necessary or not. I'll leave this up to others with more >interest in licenses than I have. > >There was an independently-developed GLX implementation (Utah-GLX). If >worst came to worst, that could be revived. I'm not at all convinced this >is the case or will become the case. > >I'd like someone to convince me there was a problem before any actual >steps are taken. It matters mostly if GPL-compatibility of the X server code is a concern. Given how the strict interpretation of the GPL works, you only need one piece of non-compatible code in a program for the whole to be non-compatible. Also with the strict interpretation, no GPL'd application could link with a libGL that included GPL-incompatible code. I happen to disagree with the ideas behind the GPL's definition of derivative works, but that's neither here nor there. I would expect all of this to be a non-issue for the DRI Project, particularly given that binary-only drivers or driver components from vendors present exactly the same issues when it comes to the X server and GL apps. Obviously GPL-compatibility of the X server code is also a non-issue as far as I am concerned. I'm just pointing out that if the new XFree86 licence is considered problematic because it makes the X server GPL-incompatible, then SGI's GLX licence is also problematic for the same reason. I'm personally more concerned that SGI's GLX licence doesn't meet the FSF's Free Software definition, but that is something that I intend to follow up elsewhere. If all of this licence stuff makes you feel nauseous, then I know how you feel... David --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Status of XFree86 4.4.0 integration?
> On Mon, Mar 01, 2004 at 06:44:38PM +, Alan Cox wrote: >>On Llu, 2004-03-01 at 14:34, Adam K Kirchhoff wrote: >>> The client libraries are still distributed under the old license, so >>> there is no problem linking GPLed libraries or apps to the 4.4 >>> libraries. Which means there is no longer a reason for those >>> distributions not to include 4.4 any more. >> >>There are several reasons, including for example the X Vnc servers >> which also use GPL code in the server > > The GLX licence is problematic for this also, given that it is used in > the server. Both the freedesktop.org and x.org trees also > included this problematic GLX code last I checked. I think it > would be good all around if each of these projects, including the > DRI project, made a clear licensing policy statement. As everyone > should know by now, you can't be a little bit GPL-incompatible. > Either you are or you aren't. > It's certainly a can of worms. I'm not particularly interested in the subtle differences between licenses, but I can say that the GLX-licenced code doesn't have much to do with the DRI project in particular - I believe it came directly from SGI and their license has been maintained since then. All the changes from this project (to my knowledge) have been intended to fall under a license comparable to the older, previous, uncontentious XFree86 one. If there are issues with the continued use of the GLX code, the first step would be to approach SGI and request a change of license. I've no idea if this would be succesful or not. I've also no idea if it is necessary or not. I'll leave this up to others with more interest in licenses than I have. There was an independently-developed GLX implementation (Utah-GLX). If worst came to worst, that could be revived. I'm not at all convinced this is the case or will become the case. I'd like someone to convince me there was a problem before any actual steps are taken. Keith --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Status of XFree86 4.4.0 integration?
On Mon, Mar 01, 2004 at 06:44:38PM +, Alan Cox wrote: >On Llu, 2004-03-01 at 14:34, Adam K Kirchhoff wrote: >> The client libraries are still distributed under the old license, so there >> is no problem linking GPLed libraries or apps to the 4.4 libraries. Which >> means there is no longer a reason for those distributions not to include >> 4.4 any more. > >There are several reasons, including for example the X Vnc servers which >also use GPL code in the server The GLX licence is problematic for this also, given that it is used in the server. Both the freedesktop.org and x.org trees also included this problematic GLX code last I checked. I think it would be good all around if each of these projects, including the DRI project, made a clear licensing policy statement. As everyone should know by now, you can't be a little bit GPL-incompatible. Either you are or you aren't. David --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] [Bug 314] 3D support for Radeon IGP chips
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] 2004-03-01 18:02 --- (In reply to comment #265) > Sorry if this is an incorrect place to ask. > since 4.4.0 is released, did 3D IGP patch for Xfree86 make it into the release > or not ? > The release notes explicitely state that Radeon IGP is only supported in 2D. > > if it didn't make it, can somebody provide us with the correct patch for the > released version ? IGP support did not make it into 4.4. IGP support is available in the DRI tree. see this page for access to the source from cvs and binary snapshots: http://dri.sourceforge.net/cgi-bin/moin.cgi/Download > > Thanks -- Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] [Bug 314] 3D support for Radeon IGP chips
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] 2004-03-01 17:35 --- Sorry if this is an incorrect place to ask. since 4.4.0 is released, did 3D IGP patch for Xfree86 make it into the release or not ? The release notes explicitely state that Radeon IGP is only supported in 2D. if it didn't make it, can somebody provide us with the correct patch for the released version ? Thanks -- Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Status of XFree86 4.4.0 integration?
On Mon, Mar 01, 2004 at 10:26:58PM +0100, Felix Kühling wrote: > On Mon, 1 Mar 2004 19:29:45 + > Alan Hourihane <[EMAIL PROTECTED]> wrote: > > > On Mon, Mar 01, 2004 at 01:19:39PM -0500, David Dawes wrote: > > > On Mon, Mar 01, 2004 at 02:15:13PM +, Alan Hourihane wrote: > > > >On Mon, Mar 01, 2004 at 02:37:37PM +0100, Dieter Nützel wrote: > > > >> Someone preparing a merge? > > > > > > > >Possibly, > > > > > > > >for the binary packages we need to include the LICENSE documents. > > > > > > Including the LICENSE documents is, strictly speaking, required by > > > many of the other licenses too. Even the old style MIT licence > > > that you use for your trident driver says: > > > > > >"... and that both that copyright notice and this permission notice > > >appear in supporting documentation." > > > > Right, and so we need to fix these things up. > > > > Felix, > > > > Can you add the LICENSE file to the binary packages ? > > Sure. I assume you mean programs/Xserver/hw/xfree86/doc/LICENSE? Yup. Thanks. Alan. --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id56&alloc_id438&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Status of XFree86 4.4.0 integration?
On Mon, 1 Mar 2004 19:29:45 + Alan Hourihane <[EMAIL PROTECTED]> wrote: > On Mon, Mar 01, 2004 at 01:19:39PM -0500, David Dawes wrote: > > On Mon, Mar 01, 2004 at 02:15:13PM +, Alan Hourihane wrote: > > >On Mon, Mar 01, 2004 at 02:37:37PM +0100, Dieter Nützel wrote: > > >> Someone preparing a merge? > > > > > >Possibly, > > > > > >for the binary packages we need to include the LICENSE documents. > > > > Including the LICENSE documents is, strictly speaking, required by > > many of the other licenses too. Even the old style MIT licence > > that you use for your trident driver says: > > > >"... and that both that copyright notice and this permission notice > >appear in supporting documentation." > > Right, and so we need to fix these things up. > > Felix, > > Can you add the LICENSE file to the binary packages ? Sure. I assume you mean programs/Xserver/hw/xfree86/doc/LICENSE? > > Alan. > Felix --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id56&alloc_id438&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Status of XFree86 4.4.0 integration?
On Mon, Mar 01, 2004 at 01:19:39PM -0500, David Dawes wrote: > On Mon, Mar 01, 2004 at 02:15:13PM +, Alan Hourihane wrote: > >On Mon, Mar 01, 2004 at 02:37:37PM +0100, Dieter Nützel wrote: > >> Someone preparing a merge? > > > >Possibly, > > > >for the binary packages we need to include the LICENSE documents. > > Including the LICENSE documents is, strictly speaking, required by > many of the other licenses too. Even the old style MIT licence > that you use for your trident driver says: > >"... and that both that copyright notice and this permission notice >appear in supporting documentation." Right, and so we need to fix these things up. Felix, Can you add the LICENSE file to the binary packages ? Alan. --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id56&alloc_id438&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Weekly IRC meeting reminder
This is just a friendly reminder that the weekly dri-devel IRC meeting will be starting in the #dri-devel channel on irc.freenode.net at 2100 UTC (or 4:00PM EST or 1:00PM PST, if you prefer). Time zone conversion available at: http://www.timezoneconverter.com/cgi-bin/tzc.tzc Logs of previous IRC meetings are available at: http://dri.sourceforge.net/IRC-logs/ --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Status of XFree86 4.4.0 integration?
On Llu, 2004-03-01 at 16:28, Michel DÃnzer wrote: > For my part, I'd certainly prefer staying clear of the silly new > license. In the long run, I'd vote for moving the DRI X server code to a > freedesktop.org X server tree and the libGL code to Mesa or its own > xlibs module. I'd definitely like to see this, and perhaps closer CVS integration so that DRI work can be done as a branch on the x.org tree not in a seperate tree. Assuming all the relevant powers that be can make it happen anyway Alan --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id56&alloc_id438&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Status of XFree86 4.4.0 integration?
On Llu, 2004-03-01 at 14:34, Adam K Kirchhoff wrote: > The client libraries are still distributed under the old license, so there > is no problem linking GPLed libraries or apps to the 4.4 libraries. Which > means there is no longer a reason for those distributions not to include > 4.4 any more. There are several reasons, including for example the X Vnc servers which also use GPL code in the server > > > Or the old license with 4.4 RC2 fork that is somewhere on freedesktop? > > And, as I understand it, is so significantly different from the XFree86 > codebase to make a merge rather, shall we say, pointless? If someone plans to merge with 4.4 can you please tag the codebase just before so that everyone else can fork it too 8) --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Status of XFree86 4.4.0 integration?
On Mon, Mar 01, 2004 at 02:15:13PM +, Alan Hourihane wrote: >On Mon, Mar 01, 2004 at 02:37:37PM +0100, Dieter Nützel wrote: >> Someone preparing a merge? > >Possibly, > >for the binary packages we need to include the LICENSE documents. Including the LICENSE documents is, strictly speaking, required by many of the other licenses too. Even the old style MIT licence that you use for your trident driver says: "... and that both that copyright notice and this permission notice appear in supporting documentation." David --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id56&alloc_id438&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] BillardGL problems
MickaÃl Cornet wrote: Le samedi 28 FÃvrier 2004 14:16, Michel DÃnzer a Ãcrit : The ball shadows are white, and I get lots of Mesa implementation error: User called no-op dispatch function (not part of Mesa subset?) Please report to the Mesa bug database at www.mesa3d.org Is this a BillardGL bug? If not, how can I track it down? I've got same problems with my savage TwisterK. It would be informative to put a breakpoint in the generic_noop() function (from Mesa/src/main/state.c) and get a stack trace from gdb. -Brian --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id56&alloc_id438&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Status of XFree86 4.4.0 integration?
On Mon, Mar 01, 2004 at 09:34:57AM -0500, Adam K Kirchhoff wrote: > >On Mon, 1 Mar 2004, Alan Swanson wrote: > >> On Mon, 2004-03-01 at 13:37, Dieter Nützel wrote: >> > Someone preparing a merge? >> >> To which release? >> >> The official 4.4 release that Red Hat, SUSE, Debian, Mandrake, Gentoo >> and most other distributions are not touching with a barge pole? > >The client libraries are still distributed under the old license, so there >is no problem linking GPLed libraries or apps to the 4.4 libraries. Which >means there is no longer a reason for those distributions not to include >4.4 any more. If GPL compatibility is a concern for the DRI project, you will need to take a careful look at the SGI "Free Software B" licence that applies to the GLX code. It is not GPL compatible. The FSF doesn't even consider it Free Software (in spite of its name). Personally I think that the GLX licence not qualifying as Free Software (as defined by the FSF) is a serious problem, and one that needs to be addressed. If my recollection is correct, and Brian can probably correct me if I'm wrong, the GLX licence was understood at the time it was hammered out to be compatible with the Open Source Definition. However, I don't see any specific mention of it at www.opensource.org. David --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id56&alloc_id438&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] build errors
Em Seg 01 Mar 2004 14:09, Alex Deucher escreveu: > I just checked out a fresh copy of mesa and the dri and I can't get it > to build: > > ../lib/GL/mesa/x86/3dnow_xform4.o > ../../../../../lib/GL/mesa/x86/sse.o > ../../../../../lib/GL/mesa/x86/sse_normal.o > ../../../../../lib/GL/mesa/x86/sse_xform1.o > ../../../../../lib/GL/mesa/x86/sse_xform2.o > ../../../../../lib/GL/mesa/x86/sse_xform3.o > ../../../../../lib/GL/mesa/x86/sse_xform4.oar: > ../../../../../lib/GL/mesa/tnl/t_save_playback.o: No such file or > directory > make[5]: *** [libOSMesa.a] Error 1 > make[5]: Leaving directory > `/home/alex/cvs/DRI/xc/xc/lib/GL/mesa/drivers/osmesa' > make[4]: *** [all] Error 2 > make[4]: Leaving directory `/home/alex/cvs/DRI/xc/xc/lib/GL' > make[3]: *** [all] Error 2 > make[3]: Leaving directory `/home/alex/cvs/DRI/xc/xc/lib' > make[2]: *** [all] Error 2 > make[2]: Leaving directory `/home/alex/cvs/DRI/xc/xc' > make[1]: *** [World] Error 2 > make[1]: Leaving directory `/home/alex/cvs/DRI/xc/xc' > make: *** [World] Error 2 > > Any ideas? > > Alex A little strange... Just finished a fresh (complete) install, but ONLY for the savage driver; seem to have worked well: make[4]: Leaving directory `/usr/src/test/xc/xc/programs/xdriinfo' make[3]: Leaving directory `/usr/src/test/xc/xc/programs' make[2]: Leaving directory `/usr/src/test/xc/xc' make[1]: Leaving directory `/usr/src/test/xc/xc' Mon Mar 1 14:47:58 BRT 2004 Full build of XFree86 version 4.3.99.12 (10 September 2003) complete. Best regards, Paulo --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] MGA updates for driinterface banch
Roland Scheidegger wrote: The reason I didn't commit the changes was I didn't want to commit untested changes, but I forgot to test it (don't have the radeon handy all the times). I can commit it (respectively an updated version) if you want, but AFAIK nobody has tested the driinterface branch with this patch. Though you'd need to update the Imakefile.inc. I've tested it briefly with my radeon over the weekend (only to make sure 3d acceleration still works), and commited now. Roland --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Status of XFree86 4.4.0 integration?
On Mon, 2004-03-01 at 17:28, Michel DÃnzer wrote: > > For my part, I'd certainly prefer staying clear of the silly new > license. In the long run, I'd vote for moving the DRI X server code to a > freedesktop.org X server tree and the libGL code to Mesa or its own > xlibs module. I should probably clarify that I would have voted for that even without the license change. -- Earthling Michel DÃnzer | Debian (powerpc), X and DRI developer Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] build errors
I just checked out a fresh copy of mesa and the dri and I can't get it to build: ../lib/GL/mesa/x86/3dnow_xform4.o ../../../../../lib/GL/mesa/x86/sse.o ../../../../../lib/GL/mesa/x86/sse_normal.o ../../../../../lib/GL/mesa/x86/sse_xform1.o ../../../../../lib/GL/mesa/x86/sse_xform2.o ../../../../../lib/GL/mesa/x86/sse_xform3.o ../../../../../lib/GL/mesa/x86/sse_xform4.oar: ../../../../../lib/GL/mesa/tnl/t_save_playback.o: No such file or directory make[5]: *** [libOSMesa.a] Error 1 make[5]: Leaving directory `/home/alex/cvs/DRI/xc/xc/lib/GL/mesa/drivers/osmesa' make[4]: *** [all] Error 2 make[4]: Leaving directory `/home/alex/cvs/DRI/xc/xc/lib/GL' make[3]: *** [all] Error 2 make[3]: Leaving directory `/home/alex/cvs/DRI/xc/xc/lib' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/alex/cvs/DRI/xc/xc' make[1]: *** [World] Error 2 make[1]: Leaving directory `/home/alex/cvs/DRI/xc/xc' make: *** [World] Error 2 Any ideas? Alex __ Do you Yahoo!? Get better spam protection with Yahoo! Mail. http://antispam.yahoo.com/tools --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] freedesktop CVS
Hello, I'm not able to checkout the DRI CVS from freedesktop.org, since I seem to have been dropped from the dri group -- same problem that others had recently. I sent an email to Eric but apparently he's away for some time. Does anyone else on the list have the ability to modify groups on freedesktop.org? Thanks, Leif -- Leif Delgass http://www.retinalburn.net --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Status of XFree86 4.4.0 integration?
On Mon, 2004-03-01 at 15:27, Alan Swanson wrote: > On Mon, 2004-03-01 at 13:37, Dieter NÃtzel wrote: > > Someone preparing a merge? > > To which release? > > The official 4.4 release that Red Hat, SUSE, Debian, Mandrake, Gentoo > and most other distributions are not touching with a barge pole? > > Or the old license with 4.4 RC2 fork that is somewhere on freedesktop? For my part, I'd certainly prefer staying clear of the silly new license. In the long run, I'd vote for moving the DRI X server code to a freedesktop.org X server tree and the libGL code to Mesa or its own xlibs module. -- Earthling Michel DÃnzer | Debian (powerpc), X and DRI developer Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Status of XFree86 4.4.0 integration?
On Mon, 2004-03-01 at 14:34, Adam K Kirchhoff wrote: > On Mon, 1 Mar 2004, Alan Swanson wrote: > > The official 4.4 release that Red Hat, SUSE, Debian, Mandrake, Gentoo > > and most other distributions are not touching with a barge pole? > > The client libraries are still distributed under the old license, so there > is no problem linking GPLed libraries or apps to the 4.4 libraries. Which > means there is no longer a reason for those distributions not to include > 4.4 any more. Unless there has been a new development, they're still not touching it. The DRI list has been free of any flame bait regarding X licensing, but I'm concerned with what happened and what multitude of projects/forks the DRI may have to support. > > Or the old license with 4.4 RC2 fork that is somewhere on freedesktop? > > And, as I understand it, is so significantly different from the XFree86 > codebase to make a merge rather, shall we say, pointless? I wasn't referring to the X Server project. -- Alan. "One must never be purposelessnessnesslessness." signature.asc Description: This is a digitally signed message part
[Dri-devel] [patch] Testing a theory about Savage lockups
Hi savage users, those of you who experience more or less reproducible lockups, could you try the attached patch with the latest Mesa trunk? There were substantial changes in the hardware state management over the weekend. Therefore comparisons of the latest patched Mesa trunk with an older unpatched Mesa trunk are basically useless. Please proceed as follows: - "cvs update" your mesa sources - "make" and "make install" DRI - try to reproduce a lockup - patch your mesa sources with the attached patch - "make" and "make install" DRI - try to reproduce the same lockup Please let me know if the patch makes any difference. Best regards, Felix Index: src/mesa/drivers/dri/savage/savagestate.c === RCS file: /cvs/mesa/Mesa/src/mesa/drivers/dri/savage/savagestate.c,v retrieving revision 1.3 diff -u -r1.3 savagestate.c --- a/src/mesa/drivers/dri/savage/savagestate.c 29 Feb 2004 20:42:22 - 1.3 +++ b/src/mesa/drivers/dri/savage/savagestate.c 1 Mar 2004 14:53:07 - @@ -1507,7 +1507,9 @@ WRITE_CMD (pBCIBase, WAIT_3D_IDLE, GLuint); savageDMACommit (imesa, pBCIBase); } -if (imesa->lostContext) +/* Try to always emit all registers. May prevent lockups on certain + * hardware. */ +if (1 || imesa->lostContext) savageEmitContiguousRegs (imesa, 0x1e, 0x39); else savageEmitChangedRegs (imesa, 0x1e, 0x39);
Re: [Dri-devel] Status of XFree86 4.4.0 integration?
On Mon, 1 Mar 2004, Alan Swanson wrote: > On Mon, 2004-03-01 at 13:37, Dieter Nützel wrote: > > Someone preparing a merge? > > To which release? > > The official 4.4 release that Red Hat, SUSE, Debian, Mandrake, Gentoo > and most other distributions are not touching with a barge pole? The client libraries are still distributed under the old license, so there is no problem linking GPLed libraries or apps to the 4.4 libraries. Which means there is no longer a reason for those distributions not to include 4.4 any more. > Or the old license with 4.4 RC2 fork that is somewhere on freedesktop? And, as I understand it, is so significantly different from the XFree86 codebase to make a merge rather, shall we say, pointless? Adam --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id56&alloc_id438&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Status of XFree86 4.4.0 integration?
On Mon, 2004-03-01 at 13:37, Dieter Nützel wrote: > Someone preparing a merge? To which release? The official 4.4 release that Red Hat, SUSE, Debian, Mandrake, Gentoo and most other distributions are not touching with a barge pole? Or the old license with 4.4 RC2 fork that is somewhere on freedesktop? -- Alan. "One must never be purposelessnessnesslessness." signature.asc Description: This is a digitally signed message part
Re: [Dri-devel] Status of XFree86 4.4.0 integration?
On Mon, Mar 01, 2004 at 02:37:37PM +0100, Dieter Nützel wrote: > Someone preparing a merge? Possibly, for the binary packages we need to include the LICENSE documents. Alan. --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id56&alloc_id438&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] BillardGL problems
Le lundi 1 Mars 2004 14:22, Michel DÃnzer a ÃcritÂ: > On Sun, 2004-02-29 at 04:47, SÃrgio Monteiro Basto wrote: > > On Sat, 2004-02-28 at 17:22, MickaÃl Cornet wrote: > > > Le samedi 28 FÃvrier 2004 14:16, Michel DÃnzer a Ãcrit : > > > > The ball shadows are white, and I get lots of > > > > > > > > Mesa implementation error: User called no-op dispatch function (not > > > > part of Mesa subset?) > > > > Please report to the Mesa bug database at www.mesa3d.org > > > > > > > > Is this a BillardGL bug? If not, how can I track it down? > > > > > > I've got same problems with my savage TwisterK. > > > > well I had the same problem but I install glut and glut-devel, from > > freshrpm.net and works for me. > > What version of glut is that exactly? I see the same problem with glut > from current Mesa CVS. I use current Mesa CVS and current DRI. $ glxinfo name of display: :0.0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.2 server glx extensions: GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_SGI_make_current_read, GLX_SGIS_multisample client glx vendor string: SGI client glx version string: 1.2 client glx extensions: GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context GLX extensions: GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context OpenGL vendor string: S3 Graphics Inc. OpenGL renderer string: Mesa DRI SAVAGE Linux_1.1.18 OpenGL version string: 1.2 Mesa 6.1 OpenGL extensions: GL_ARB_multitexture, GL_ARB_texture_env_add, GL_ARB_transpose_matrix, GL_ARB_window_pos, GL_EXT_abgr, GL_EXT_bgra, GL_EXT_clip_volume_hint, GL_EXT_compiled_vertex_array, GL_EXT_copy_texture, GL_EXT_draw_range_elements, GL_EXT_packed_pixels, GL_EXT_polygon_offset, GL_EXT_rescale_normal, GL_EXT_separate_specular_color, GL_EXT_subtexture, GL_EXT_texture, GL_EXT_texture3D, GL_EXT_texture_edge_clamp, GL_EXT_texture_env_add, GL_EXT_texture_lod_bias, GL_EXT_texture_object, GL_EXT_vertex_array, GL_APPLE_packed_pixels, GL_IBM_rasterpos_clip, GL_MESA_window_pos, GL_NV_light_max_exponent, GL_NV_texgen_reflection, GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod glu version: 1.3 glu extensions: GLU_EXT_nurbs_tessellator, GLU_EXT_object_space_tess --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id56&alloc_id438&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Status of XFree86 4.4.0 integration?
Someone preparing a merge? Thanks, Dieter --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] BillardGL problems
On Sun, 2004-02-29 at 04:47, SÃrgio Monteiro Basto wrote: > On Sat, 2004-02-28 at 17:22, MickaÃl Cornet wrote: > > Le samedi 28 FÃvrier 2004 14:16, Michel DÃnzer a Ãcrit : > > > The ball shadows are white, and I get lots of > > > > > > Mesa implementation error: User called no-op dispatch function (not part > > > of Mesa subset?) > > > Please report to the Mesa bug database at www.mesa3d.org > > > > > > Is this a BillardGL bug? If not, how can I track it down? > > I've got same problems with my savage TwisterK. > > well I had the same problem but I install glut and glut-devel, from > freshrpm.net and works for me. What version of glut is that exactly? I see the same problem with glut from current Mesa CVS. -- Earthling Michel DÃnzer | Debian (powerpc), X and DRI developer Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
