Alan, Mike Mestnik has kindly volunteered to get the 4.2 DRM modules submitted to the Linux kernel. I'd forgotten about the tar ball you have on your XFree86 page. Do you know if anybody is already working on this--I'm just trying to make sure we don't duplicate effort.
Mike Mestnik wrote: > > I'l get started on making some patch files from > http://www.xfree86.org/~alanh/linux-drm-4.2.0-kernelsource.tar.gz > http://www.kernel.org/pub/linux/kernel/v*/patch-*.gz > > Versions 2.4.17, 2.4.18, 2.4.19-pre7, 2.5.9 > and I'l post them on the web, then maby thay can be tested befour any thing > else. > > I don't at this time have a good web page, just the one on my home connection. > 66.41.82.43:c-66-41-82-43.mn.client2.attbi.com > > This info may be helpfull. > # How do I get my patch into the kernel? > > * (RRR) Depending on your patch there are several ways to get it into the > kernel. The first thing is to determine under which maintainer does your code > fall into (look in the MAINTANERS file). If your patch is only a small bugfix > and you're sure that it is 'obviously correct', then by all means send it to > the appropriate maintainer and post it to the list. If there is urgency to the > bugfix (i.e. a major security hole) you can also send it to Linus directly, but > remember he's likely to ignore random patches unless they are "obviously > correct" to him, have the maintainer's approval, or have been well tested and > meet the first condition. I case you're wondering what constitutes well tested, > here's another important bit: one purpose of the list is to get patches > peer-reviewed and well-tested. Now, if your patch is relatively big, i.e. a > rewrite of a large code section or a new device driver, then to conserve > bandwidth and disk-space just post an announcement to the list with a link to > the patch. Lastly, if you're not too sure about your patch yet, want some > feedback from the maintainer, or wish to avoid open-season flaming on > work-in-progress, then use private email. > * (REG) If there is no specific maintainer for the part of the kernel you > want to patch, then you have three main options: > o send it to [EMAIL PROTECTED] and hope someone picks it > up and feeds it to Linus, or maybe Linus himself will pick it up (don't count > on it) > o send it to linux-kernel and Cc: Linus Torvalds > <[EMAIL PROTECTED]> and hope Linus will apply it. Note that Linus operates > like a black box. Do not expect a response from him. You will need to check > patches he releases to see if he applied your patch. If he doesn't apply your > patch, you will need to resend it (often many times). If after weeks or months > and many patch releases he still hasn't applied it, maybe you should give up. > He probably doesn't like it > o send it to linux-kernel and Cc: Alan Cox <[EMAIL PROTECTED]>. Alan is > better at responding to email, and will queue your patch and resend it to Linus > periodically, so you can forget about it. He also serves as a good taste > tester. If Alan accepts your patch, it's more likely that Linus will too. If he > doesn't like your patch, you will probably get an email saying so. Expect it to > be terse. > > --- Jens Owen <[EMAIL PROTECTED]> wrote: > > Mike, > > > > I haven't personally submitted an update for the drm drivers to Linus, > > but Rik and possibly Jeff have done it. I'll copy them on this e-mail > > to see what they recommend, and whether they have any "gems" of wisdom > > they'd like to share. > > > > Thanks, > > Jens > > > > Mike Mestnik wrote: > > > > > > I can do grunt work, but what is it that you want. diffs, tars, or bins? > > I > > > bet there is a script I can just run and then fix the errors until it works > > > right. no script i can use make, but maby you have a .config you would > > like me > > > to use. > > > > > > just let me know what you need. > > > > > > --- Jens Owen <[EMAIL PROTECTED]> wrote: > > > > I've been seeing some suspicious e-mails regarding DRM version > > > > mismatches, so I spent this morning digging into the r128 DRM versions. > > > > From what I've looked at, it appears backwards compatability from a > > > > kernel perspective is maintained (at least from XFree86 4.1.0 forward) > > > > for the r128 driver. However, the latest Linux kernels have not been > > > > updated with the XFree86 4.2 DRM modules. This results in the DRI being > > > > disabled for users of XFree86 4.2 when they are running the DRM modules > > > > provided with the Linux kernels. > > > > > > > > The Linux kernel DRM modules need to be updated to the latest XFree86 > > > > 4.2 versions. Any Volunteers? > > > > > > > > BTW, does anyone know what the dri-4.0 modules are used for? They are > > > > seriously out of date. > > > > > > > > Here's the version information I dug up this morning for the r128: > > > > > > > > XFree86 Version 4.0.1: > > > > DRM r128 1.0.0 > > > > r128_drv.c, DRI CVS Version 1.6 > > > > r128_drm.h, DRI CVS Version 1.3 > > > > > > > > XFree86 Version 4.1.0: > > > > DRM r128 2.1.6 > > > > r128_drv.c, DRI CVS Version 1.35 > > > > r128_drm.h, DRI CVS Version 1.13 > > > > > > > > XFree86 Version 4.2.0: > > > > DRM r128 2.2.0 > > > > r128_drv.c, DRI CVS Version 1.42 > > > > r128_drm.h, DRI CVS Version 1.13 > > > > > > > > Linux 2.4.17: > > > > drm r128 2.1.6 > > > > r128_drv.c, DRI CVS Version 1.40 > > > > r128_drm.h, DRI CVS Version 1.13 > > > > > > > > Linux 2.4.18: > > > > drm r128 2.1.6 > > > > [same as 2.4.17] > > > > drm-4.0 r128 2.1.2 > > > > r128_drv.c, DRI CVS Version 1.27 > > > > r128_drm.h, DRI CVS Version 1.7 > > > > > > > > Linux 2.4.19-pre7: > > > > [same as 2.4.18] > > > > > > > > Linux 2.5.9: > > > > [same as 2.4.17] > > > > > > > > -- /\ > > > > Jens Owen / \/\ _ > > > > [EMAIL PROTECTED] / \ \ \ Steamboat Springs, Colorado > > > > > > > > _______________________________________________ > > > > Dri-devel mailing list > > > > [EMAIL PROTECTED] > > > > https://lists.sourceforge.net/lists/listinfo/dri-devel > > > > > > __________________________________________________ > > > Do You Yahoo!? > > > Yahoo! Games - play chess, backgammon, pool and more > > > http://games.yahoo.com/ > > > > -- /\ > > Jens Owen / \/\ _ > > [EMAIL PROTECTED] / \ \ \ Steamboat Springs, Colorado > > __________________________________________________ > Do You Yahoo!? > Yahoo! Games - play chess, backgammon, pool and more > http://games.yahoo.com/ -- /\ Jens Owen / \/\ _ [EMAIL PROTECTED] / \ \ \ Steamboat Springs, Colorado _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
