Re: XFree86 4.5.0 release schedule
On Mon, Jan 10, 2005 at 11:00:22PM -0500, David Dawes wrote: On Mon, Jan 10, 2005 at 08:43:18AM +, Matthias Scheler wrote: On Sat, Jan 08, 2005 at 07:37:29PM -0500, David Dawes wrote: The schedule for the next XFree86 release -- 4.5.0 is as follows: 26 January 2005feature freeze late February 2005 code freeze early-mid March 2005 release Is a list of changes for this release already available somewhere? Most changes are listed in the changelog file in the source tree. There are some exceptions: for example, the latest Mesa/DRI updates, which should probably be added to the changelog. Sorry, I thought I'd done that. I'll fix it now. Alan. ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: XFree86 4.5.0 release schedule
On Sat, 8 Jan 2005, David Dawes wrote: The schedule for the next XFree86 release -- 4.5.0 is as follows: 26 January 2005feature freeze late February 2005 code freeze early-mid March 2005 release The feature freeze date is the date by which non-bug-fix submissions need to be received in order to be considered for inclusion in the 4.5.0 release. The code freeze date is the point at which only seriaous bug fixes and documentation updates are accepted. Submissions may be made through the XFree86 bugzilla at bugs.xfree86.org or via email to [EMAIL PROTECTED] It is also a good idea to send a note here regarding new submissions or for previous submissions that have not been committed yet. Submissions should be integrated/tested against the most recent XFree86 snapshot or the current CVS trunk, and submitted as patches against such. XFree86 snapshots can be found at http://www.xfree86.org/develsnaps/. The actual code freeze and release dates will be nailed down as they get closer. Should an attempt be made to resurrect DMX before 4.5? Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: XFree86 4.5.0 release schedule
On Tue, Jan 11, 2005 at 08:31:54AM -0700, Marc Aurele La France wrote: On Sat, 8 Jan 2005, David Dawes wrote: The schedule for the next XFree86 release -- 4.5.0 is as follows: 26 January 2005feature freeze late February 2005 code freeze early-mid March 2005 release The feature freeze date is the date by which non-bug-fix submissions need to be received in order to be considered for inclusion in the 4.5.0 release. The code freeze date is the point at which only seriaous bug fixes and documentation updates are accepted. Submissions may be made through the XFree86 bugzilla at bugs.xfree86.org or via email to [EMAIL PROTECTED] It is also a good idea to send a note here regarding new submissions or for previous submissions that have not been committed yet. Submissions should be integrated/tested against the most recent XFree86 snapshot or the current CVS trunk, and submitted as patches against such. XFree86 snapshots can be found at http://www.xfree86.org/develsnaps/. The actual code freeze and release dates will be nailed down as they get closer. Should an attempt be made to resurrect DMX before 4.5? How seriously broken is it? David ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: XFree86 4.5.0 release schedule
On Tue, Jan 11, 2005 at 12:41:15PM -0500, David Dawes wrote: On Tue, Jan 11, 2005 at 08:31:54AM -0700, Marc Aurele La France wrote: On Sat, 8 Jan 2005, David Dawes wrote: The schedule for the next XFree86 release -- 4.5.0 is as follows: 26 January 2005feature freeze late February 2005 code freeze early-mid March 2005 release The feature freeze date is the date by which non-bug-fix submissions need to be received in order to be considered for inclusion in the 4.5.0 release. The code freeze date is the point at which only seriaous bug fixes and documentation updates are accepted. Submissions may be made through the XFree86 bugzilla at bugs.xfree86.org or via email to [EMAIL PROTECTED] It is also a good idea to send a note here regarding new submissions or for previous submissions that have not been committed yet. Submissions should be integrated/tested against the most recent XFree86 snapshot or the current CVS trunk, and submitted as patches against such. XFree86 snapshots can be found at http://www.xfree86.org/develsnaps/. The actual code freeze and release dates will be nailed down as they get closer. Should an attempt be made to resurrect DMX before 4.5? How seriously broken is it? Here's an explanation of the issue with a proposed fix to maintain backward compatibility: http://sourceforge.net/mailarchive/message.php?msg_id=10290987 I've tested my patch to make sure that it works fine on Linux. I don't have an SGI box to verify that it still works fine on their systems. ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: XFree86 4.5.0 release schedule
On Tue, 11 Jan 2005, Kevin E Martin wrote: On Tue, Jan 11, 2005 at 12:41:15PM -0500, David Dawes wrote: On Tue, Jan 11, 2005 at 08:31:54AM -0700, Marc Aurele La France wrote: On Sat, 8 Jan 2005, David Dawes wrote: The schedule for the next XFree86 release -- 4.5.0 is as follows: 26 January 2005feature freeze late February 2005 code freeze early-mid March 2005 release The feature freeze date is the date by which non-bug-fix submissions need to be received in order to be considered for inclusion in the 4.5.0 release. The code freeze date is the point at which only seriaous bug fixes and documentation updates are accepted. Submissions may be made through the XFree86 bugzilla at bugs.xfree86.org or via email to [EMAIL PROTECTED] It is also a good idea to send a note here regarding new submissions or for previous submissions that have not been committed yet. Submissions should be integrated/tested against the most recent XFree86 snapshot or the current CVS trunk, and submitted as patches against such. XFree86 snapshots can be found at http://www.xfree86.org/develsnaps/. The actual code freeze and release dates will be nailed down as they get closer. Should an attempt be made to resurrect DMX before 4.5? How seriously broken is it? Here's an explanation of the issue with a proposed fix to maintain backward compatibility: http://sourceforge.net/mailarchive/message.php?msg_id=10290987 I've tested my patch to make sure that it works fine on Linux. I don't have an SGI box to verify that it still works fine on their systems. Well, if I were you, I'd commit something like that ASAP. I can deal with the build issues, test case or no test case. The point being that no one will fix it if it doesn't build. Longer term though, we need to look at glxProxy being more of an #ifdef'ed derivative of GLX. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: XFree86 4.5.0 release schedule
On Tue, 11 Jan 2005, Marc Aurele La France wrote: On Tue, 11 Jan 2005, Kevin E Martin wrote: On Tue, Jan 11, 2005 at 12:41:15PM -0500, David Dawes wrote: On Tue, Jan 11, 2005 at 08:31:54AM -0700, Marc Aurele La France wrote: On Sat, 8 Jan 2005, David Dawes wrote: The schedule for the next XFree86 release -- 4.5.0 is as follows: 26 January 2005feature freeze late February 2005 code freeze early-mid March 2005 release The feature freeze date is the date by which non-bug-fix submissions need to be received in order to be considered for inclusion in the 4.5.0 release. The code freeze date is the point at which only seriaous bug fixes and documentation updates are accepted. Submissions may be made through the XFree86 bugzilla at bugs.xfree86.org or via email to [EMAIL PROTECTED] It is also a good idea to send a note here regarding new submissions or for previous submissions that have not been committed yet. Submissions should be integrated/tested against the most recent XFree86 snapshot or the current CVS trunk, and submitted as patches against such. XFree86 snapshots can be found at http://www.xfree86.org/develsnaps/. The actual code freeze and release dates will be nailed down as they get closer. Should an attempt be made to resurrect DMX before 4.5? How seriously broken is it? Here's an explanation of the issue with a proposed fix to maintain backward compatibility: http://sourceforge.net/mailarchive/message.php?msg_id=10290987 I've tested my patch to make sure that it works fine on Linux. I don't have an SGI box to verify that it still works fine on their systems. Well, if I were you, I'd commit something like that ASAP. I can deal with the build issues, test case or no test case. The point being that no one will fix it if it doesn't build. Longer term though, we need to look at glxProxy being more of an #ifdef'ed derivative of GLX. Come to think of it, I'll be even blunter. If DMX breaks every time GLX is resync'ed, then there's no point in keeping DMX. This whether we're talking about XFree86's repository, or X.Org's. So, I'd strongly advise you, Kevin, to talk to the GLX people in getting glxProxy done properly. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: XFree86 4.5.0 release schedule
On Tue, Jan 11, 2005 at 02:15:58PM -0700, Marc Aurele La France wrote:
On Tue, 11 Jan 2005, Marc Aurele La France wrote:
On Tue, 11 Jan 2005, Kevin E Martin wrote:
Here's an explanation of the issue with a proposed fix to maintain
backward compatibility:
http://sourceforge.net/mailarchive/message.php?msg_id=10290987
I've tested my patch to make sure that it works fine on Linux. I don't
have an SGI box to verify that it still works fine on their systems.
Well, if I were you, I'd commit something like that ASAP. I can deal with
the build issues, test case or no test case. The point being that no one
will fix it if it doesn't build.
Longer term though, we need to look at glxProxy being more of an #ifdef'ed
derivative of GLX.
Come to think of it, I'll be even blunter. If DMX breaks every time GLX is
resync'ed, then there's no point in keeping DMX.
glxProxy was developed by SGI is almost 100% independent from GLX as
used in the rest of the X server -- the only shared code is from some
header files. One of those headers was changed but not properly
#ifdef'd by SGI to maintain backward compatibility with previous XFree86
releases. The patch that I suggested fixes the backward compatibility
issue. This is all explained in the thread that I referenced in my
previous message.
Unfortunately, I just discovered that there is a much more significant
issue: you've made changes to glxProxy on 4 Aug 2004 that broke the
build. I've attached a patch to make it build again. However, I cannot
verify the correctness of the changes you've made, since glxProxy is not
my code. As I mentioned above, the code was donated by SGI. I would
strongly suggest reverting the changes you've made until you can verify
with SGI that your changes are correct.
If you do revert the changes back to the way they were originally
checked in and then apply the patch from my message to the dri-devel
list (see URL above), then glxProxy should build and work properly, and
it should also be backward compatible with previous XFree86 releases.
Index: programs/Xserver/hw/dmx/dmx_glxvisuals.c
===
RCS file: /home/x-cvs/xc/programs/Xserver/hw/dmx/dmx_glxvisuals.c,v
retrieving revision 1.1
diff -u -r1.1 dmx_glxvisuals.c
--- programs/Xserver/hw/dmx/dmx_glxvisuals.c30 Jun 2004 20:21:38 -
1.1
+++ programs/Xserver/hw/dmx/dmx_glxvisuals.c12 Jan 2005 00:13:53 -
@@ -147,12 +147,14 @@
int value = *p++;
switch (property) {
+#if 0
case GLX_SAMPLES_SGIS:
config-multiSampleSize = value;
break;
case GLX_SAMPLE_BUFFERS_SGIS:
config-nMultiSampleBuffers = value;
break;
+#endif
case GLX_TRANSPARENT_TYPE_EXT:
config-transparentPixel = value;
@@ -177,10 +179,12 @@
config-visualRating = value;
break;
+#if 0
/* visualSelectGroup is an internal used property */
case GLX_VISUAL_SELECT_GROUP_SGIX:
config-visualSelectGroup = value;
break;
+#endif
default :
/* Ignore properties we don't recognize */
@@ -591,9 +595,11 @@
cfg-transparentBlue = fbcfg-transparentBlue;
cfg-transparentAlpha = fbcfg-transparentAlpha;
cfg-transparentIndex = fbcfg-transparentIndex;
+#if 0
cfg-multiSampleSize = fbcfg-multiSampleSize;
cfg-nMultiSampleBuffers = fbcfg-nMultiSampleBuffers;
cfg-visualSelectGroup = fbcfg-visualSelectGroup;
+#endif
}
}
Index: programs/Xserver/hw/dmx/glxProxy/g_renderswap.c
===
RCS file: /home/x-cvs/xc/programs/Xserver/hw/dmx/glxProxy/g_renderswap.c,v
retrieving revision 1.2
diff -u -r1.2 g_renderswap.c
--- programs/Xserver/hw/dmx/glxProxy/g_renderswap.c 4 Aug 2004 16:33:34
- 1.2
+++ programs/Xserver/hw/dmx/glxProxy/g_renderswap.c 12 Jan 2005 00:13:53
-
@@ -63,6 +63,7 @@
void __glXDispSwap_Color3dv(GLbyte *pc)
{
+ __GLX_DECLARE_SWAP_VARIABLES;
__GLX_DECLARE_SWAP_ARRAY_VARIABLES;
#ifdef __GLX_ALIGN64
@@ -76,6 +77,7 @@
void __glXDispSwap_Color3fv(GLbyte *pc)
{
+ __GLX_DECLARE_SWAP_VARIABLES;
__GLX_DECLARE_SWAP_ARRAY_VARIABLES;
__GLX_SWAP_FLOAT_ARRAY(pc + 0, 3);
@@ -83,6 +85,7 @@
void __glXDispSwap_Color3iv(GLbyte *pc)
{
+ __GLX_DECLARE_SWAP_VARIABLES;
__GLX_DECLARE_SWAP_ARRAY_VARIABLES;
__GLX_SWAP_INT_ARRAY(pc + 0, 3);
@@ -90,6 +93,7 @@
void __glXDispSwap_Color3sv(GLbyte *pc)
{
+ __GLX_DECLARE_SWAP_VARIABLES;
__GLX_DECLARE_SWAP_ARRAY_VARIABLES;
__GLX_SWAP_SHORT_ARRAY(pc + 0, 3);
@@ -102,6 +106,7 @@
void __glXDispSwap_Color3uiv(GLbyte *pc)
{
+ __GLX_DECLARE_SWAP_VARIABLES;
__GLX_DECLARE_SWAP_ARRAY_VARIABLES;
4.6 million email addresses - £19.95
UK EMAIL DATABASE just £19.95 inc. pp and contains: 4,600,000 VALIDATED UK email addresses - Verified in August 2004, ensuring a low failure rate and only used privately. TO PURCHASE: Please send a Cheque/PO to: Unbelievable Secrets Unit 716, 78 Marylebone High Street, London W1U 5AP The CD will be sent by first class post and you will also receive FREE bulk email software to send 30,000+ emails per hour. ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
