Re: [Dri-devel] Merging radeon mergedfb patch before 4.4.0
On Fri, Oct 03, 2003 at 12:35:42PM -0400, David Dawes wrote: On Fri, Oct 03, 2003 at 07:31:49AM -0700, Alex Deucher wrote: his thoughts. Will there be another xfree86-DRI merge before the release? will Felix' config code make it in? There won't be any further wholesale DRI-XFree86 merge. !? Instead, new features and bug fixes should be separated out and submitted to XFree86 for consideration for the upcoming release before the deadline(s). New stuff should be discussed in advance on the broader XFree86 development list so that there are no surprises, and it'd be helpful all around if you guys maintained some sort of changelog. !! Well, if that's the way XFree86-DRI relationship is going then I have a better suggestion: why doesn't XFree86 (or any XFree86's fork or any linux distribution for that matter) come to our tree and make all the little nice tidy patches they want? After all we are the upstream maintainers of DRI and not the opposite! Jose Fonseca PS: Speaking for myself, as a DRI developer, and nobody else. --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Merging radeon mergedfb patch before 4.4.0
On Fri, Oct 03, 2003 at 06:13:37PM +0100, José Fonseca wrote: On Fri, Oct 03, 2003 at 12:35:42PM -0400, David Dawes wrote: On Fri, Oct 03, 2003 at 07:31:49AM -0700, Alex Deucher wrote: his thoughts. Will there be another xfree86-DRI merge before the release? will Felix' config code make it in? There won't be any further wholesale DRI-XFree86 merge. !? Instead, new features and bug fixes should be separated out and submitted to XFree86 for consideration for the upcoming release before the deadline(s). New stuff should be discussed in advance on the broader XFree86 development list so that there are no surprises, and it'd be helpful all around if you guys maintained some sort of changelog. !! Well, if that's the way XFree86-DRI relationship is going then I have a better suggestion: why doesn't XFree86 (or any XFree86's fork or any linux distribution for that matter) come to our tree and make all the little nice tidy patches they want? After all we are the upstream maintainers of DRI and not the opposite! I don't see anything new or unusual about what I said. A similar thing happened with the 4.3 release -- there was no wholesale merge of the then DRI trunk into XFree86 at the point of the feature freeze. The only difference I can see is that I was more involved in DRI stuff at the time and so did a lot of the work to make sure that patches for bug fixes originating here made it into XFree86. That included creating a for XFree86 release branch in the DRI repository, separating out the relevant patches, and even going through the DRI commit logs to create useful changelog entries when bringing them into XFree86. Just in case it wasn't clear, I did all of this as a DRI developer, not as an XFree86 developer. My personal priorities now lie in other areas, so someone else, preferably someone who keeps up with DRI development more closely than I do these days, will have to do all of this. That is, if the DRI developers collectively want anything that hasn't already been merged to appear in the XFree86 4.4 release. If they don't, then there's no problem, right? David -- David Dawes Founder/committer/developer The XFree86 Project www.XFree86.org/~dawes --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Merging radeon mergedfb patch before 4.4.0
On Sun, Oct 05, 2003 at 11:05:21AM -0400, David Dawes wrote: I don't see anything new or unusual about what I said. A similar thing happened with the 4.3 release -- there was no wholesale merge of the then DRI trunk into XFree86 at the point of the feature freeze. The only difference I can see is that I was more involved in DRI stuff at the time and so did a lot of the work to make sure that patches for bug fixes originating here made it into XFree86. That included creating a for XFree86 release branch in the DRI repository, separating out the relevant patches, and even going through the DRI commit logs to create useful changelog entries when bringing them into XFree86. Just in case it wasn't clear, I did all of this as a DRI developer, not as an XFree86 developer. My personal priorities now lie in other areas, so someone else, preferably someone who keeps up with DRI development more closely than I do these days, will have to do all of this. That is, if the DRI developers collectively want anything that hasn't already been merged to appear in the XFree86 4.4 release. If they don't, then there's no problem, right? Probably I made a bad interpertation, but from your words it seemed that there would be no wholesale merge of the DRI trunk into XFree86 *ever*, neither by you or anyone else. But I now understand it's a personal shift of priorities rather than a seperation of the DRI-XFree86 projects. Sorry for jumping on the gun. Jose Fonseca --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Merging radeon mergedfb patch before 4.4.0
With my latest patch the just about all the outstanding bugs have been fixed. the only thing remaining is that pagflipping doesn't always work in some mergedfb configurations. I'm working on that one, but then again, pageflipping doesn't work for everyone anyway. The driver currently supports all major features you'd want in a dualheaded setup: 3D on both heads, Xv overlay moves from one crtc to the other depending on where the output is, and it provides a pseudo-xinerama extension for window placement and such. What are your thoughts on merging the radeon mergedfb patch into CVS? I agree that it would probably be a better idea to separate out the device independant code, but I'm not sure I'll have time to do that and test it before the 4.4 feature freeze (oct 15th). Also merging the driver now, as is, doesn't mean it can't be converted to the device independant code later on. I've emailed Kevin E. Martin as well to get his thoughts. Will there be another xfree86-DRI merge before the release? will Felix' config code make it in? Thanks, Alex __ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Merging radeon mergedfb patch before 4.4.0
On Fri, 2003-10-03 at 16:31, Alex Deucher wrote: What are your thoughts on merging the radeon mergedfb patch into CVS? I agree that it would probably be a better idea to separate out the device independant code, but I'm not sure I'll have time to do that and test it before the 4.4 feature freeze (oct 15th). Also merging the driver now, as is, doesn't mean it can't be converted to the device independant code later on. I agree, but this is Kevin's call. -- Earthling Michel Dnzer \ Debian (powerpc), XFree86 and DRI developer Software libre enthusiast \ http://svcs.affero.net/rm.php?r=daenzer --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Merging radeon mergedfb patch before 4.4.0
On Fri, Oct 03, 2003 at 07:31:49AM -0700, Alex Deucher wrote: his thoughts. Will there be another xfree86-DRI merge before the release? will Felix' config code make it in? There won't be any further wholesale DRI-XFree86 merge. Instead, new features and bug fixes should be separated out and submitted to XFree86 for consideration for the upcoming release before the deadline(s). New stuff should be discussed in advance on the broader XFree86 development list so that there are no surprises, and it'd be helpful all around if you guys maintained some sort of changelog. David -- David Dawes Founder/committer/developer The XFree86 Project www.XFree86.org/~dawes --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel