On Wednesday 11 December 2002 07:51 pm, you wrote: > XFree86 4.3 is going to go with a Mesa 4.0.x-based DRI because of time > constraints and stability concerns. I know that this complicates things > a little, but I don't see a practical alternative. > > I've created a branch called "mesa-4-0-4-branch" in the DRI CVS, branching > from the trunk tag (trunk-20021125) that Brian put in before merging > Mesa 5.0 into the trunk. If any fixes since then that are independent > of Mesa 5.0 could be committed to that branch, that should ensure that > they get picked up for XFree86 4.3. I'm planning to resync the XFree86 > trunk with that branch sometime this weekend.
With X 4.3.0 approaching, what are the chances that the gatos code can be synced back into X before DRI syncs up from X so that the DRI branch can have videoin support (for radeon)? I know there are differences in the memory allocation requirements that need to be solved, but it would really be nice to have at least the basic videoin supported in the DRI tree. I at least (and presume there are others) track the DRI code, and would like to not have to use an entirely different X server build just to get videoin. X 4.3.0 seems like as good a time as any to get both sets of functionality finally in the same place at the same time... If this is an unreasonable goal, would someone care to comment as to when this might or why this won't occur? Nick ------------------------------------------------------- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
