On 2002.05.14 00:42 Jens Owen wrote: > José Fonseca wrote: > >... > > > > Nop, but who will do this? (I can't volunteer as I have no more spare > time > > until June.) > > Mike Mestnik has created this initial patch for testing. I hope Mike > has the time to see this into kernel integration, but we need to make > sure we're giving Mike consistent feedback so he's not doing extranious > work--that's the intent of laying out a plan. > > > I would be nice to know what is the current state of affairs? Is it > like: > > > > - both 2.4.x 2.5.x linux kernel series have the XFree 4.1.0 DRMs > (with > > changes by the linux kernel developers to match the rest of the > kernel). > > Nothing that clean. The r128 driver appears to be something from > slightly after 4.1.0. I haven't looked at any of the others. > > > - the XFree86 4.2.0 tree has DRM source for early 2.4.x series > > - for 2.4.18 changes are required, for which Mike made a patch > > I don't know of any kernel driver interface changes that we need. There > are some patches to drivers in the kernel repository that we need to > propegate back into ours; however, the bulk of the work is getting our > DRM enhancement to the kernel team. >
For example, the virt_to_page change (used in the i8x0 DRM) happened during the 2.4.x kernel series, but it may be others... > > - for 2.5.x likewise, for which Micah patched the radeon kernel > only > > As of 2.5.9 the r128 driver looked identical to the 2.4.17 r128 driver. > If we can keep the source for converged between these two branches, that > would be ideal. > > > And what is necessary to do is: > > > > - adapt the DRI CVS kernel modules to build in at least three kernel > > versions, > > The latest 2.4 and latest 2.5 would be good since we're merging--what > was the third version you had in mind? I was thinking in 2.4.9, 2.4.18, and latest 2.5.x, due to the problem noticed above, at least. The 2.4.9 and the 2.4.18 should cover most of the current distributions. I think that only the most recent distributions use 2.4.18, and I don't think we should force to upgrade to a new one for getting the latest drivers. I've just upgraded my distro to a 2.4.18, so at least for mach64 and the common templates I'll have to doit on my tree. > > > - make a patch against the latest 2.4.x and 2.5.x kernels > > > > Is this picture correct? > > It's a decent start:-) > José Fonseca _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel