Modules & releases needed for X11R7.7 katamari

Jeremy Huddleston jeremyhu at
Fri Mar 9 15:15:32 PST 2012

On Mar 8, 2012, at 11:12 PM, Alan Coopersmith <alan.coopersmith at> wrote:

> For this year's katamari, I've only kicked out a couple modules - the
> two input drivers (acecad & aiptek) which were declared dead during
> the last year.
> So far I've not added any new ones - the most likely candidate I see
> for adding is xf86-video-nouveau.   Given nvidia's statement about
> ending support for xf86-video-nv, is it time to replace -nv with
> -nouveau?   (I'm sure we've discussed this before and I'm just doing
> too many things at once to remember right now.)

It is way past time that we include nouveau.  Additionally considering that xorg-server-1.12 prefers nouveau if present, we really should roll it into the katamari:

commit d0c6732a99c9a7e40752b9ba7898a01c325103fa
Author: Anssi Hannula <anssi.hannula at>
Date:   Wed Apr 20 14:34:52 2011 +0300

    xfree86: add nouveau as the first automatic driver for NVIDIA hardware
    Add nouveau as the first driver on linux for NVIDIA hardware when
    driver autoconfiguration is done, as it is more capable than nv.
    nv is also kept in the list as it is more widely supported and because
    some old cards are not supported by nouveau.
    Signed-off-by: Anssi Hannula <anssi.hannula at>
    Reviewed-by: Daniel Stone <daniel at>
    Reviewed-by: Cyril Brulebois <kibi at>
    Reviewed-by: Jeremy Huddleston <jeremyhu at>
    Signed-off-by: Keith Packard <keithp at>

> xf86-video-modesetting seems like a candidate for next year, but it
> seemed too soon for inclusion this year.

I'd like to consider xf86-video-nested next year as well.

> Any other modules people want to nominate to add or remove for the
> X11R7.7 katamari?
> Remember - being in or out doesn't change the usability or support status
> of a module, just which end up in the /releases/7.7 directory for people
> trying to bootstrap from a known-working-together baseline.
> There's still a bunch of modules needing release, marked with a * below.
> In deciding what to * as needing release, I figured that these things
> needed releases:
> - drivers with commits mentioning new ABI support
> - modules with fixes for bugs reported by users
> - modules with the DocBook/XML cross-linking support changes
> and that modules that just had configure clean ups or other minor things
> didn't need to be called out here as blocking the katamari.   (Doesn't mean
> people can't release them if wanted, and I can also provide the output of my
> script that lists all the commits in each module since it was last tagged if
> anyone else  wants to go through some.)
> I'm finishing off the libs still, and will do the proto modules soon, but the
> drivers I'm mainly leaving for the driver maintainers to do.
> I'm not planning on doing a mass font release just to get the new cross-compiling support into their configure scripts, but if someone who would
> use that wants to do it, I won't object.
> BTW, I've been using Gaetan's new version of that automates
> even more of the steps, so you just need to commit the version bump to
> the and then run the script to tag, make dist, upload, etc.
> and can recommend it to others releasing modules.   I haven't tried the
> multi-module release mode yet, but someone wanting to release a batch of
> fonts or unloved video drivers for archaic hardware may want to try that out.
> -- 
> 	-Alan Coopersmith-              alan.coopersmith at
> 	 Oracle Solaris Engineering -
> <7.7-katamari.txt>_______________________________________________
> xorg-devel at X.Org development
> Archives:
> Info:

More information about the xorg-devel mailing list