Minimizing X.org 6.8.1 (not KDrive) to meet specs

[Jim Gettys]

Torgeir,

This is not true. On the iPAQ handheld, for example, I turn off any of
these, and certainly if you don't need the functionality, you could
consider turning them off as well.

So, for example, on the iPAQ, I think currently we have the starred
extensions below not built.  This is using the kdrive driver framework.

Last I looked, the size was a bit over 500K bytes on ARM; but since
then, composite, fixes, and damage have gone in (though they turn out
to not be all that large.

The XAA driver framework is considerably larger; kdrive is much
nicer for small embedded systems, but lacks 3D and loadable drivers.
				- Jim


    BIG-REQUESTS
    Composite
    DAMAGE
    DOUBLE-BUFFER *
    DPMS *
    Extended-Visual-Information *
    GLX *
    LBX *
    MIT-SCREEN-SAVER
    MIT-SHM
    MIT-SUNDRY-NONSTANDARD
    RANDR
    RECORD
    RENDER
    SECURITY
    SGI-GLX *
    SHAPE
    SYNC
    TOG-CUP
    X-Resource
    XC-APPGROUP *
    XC-MISC *
    XFIXES
    XFree86-Bigfont *
    XFree86-DGA *
    XFree86-DRI *
    XFree86-Misc *
    XFree86-VidModeExtension *
    XInputExtension *
    XKEYBOARD
    XTEST
    XVideo *

On Thu, 2004-09-23 at 21:36 +0100, Torgeir Veimo wrote:
> On Thu, 2004-09-23 at 16:23 -0400, Sergei Mutovkin wrote:
> > I've just checked xdpyinfo and my "small" X11 has whole load of
> > extensions: 28... Most of which for me mean absolutely nothing... and
> > I have no idea how dependent X on those exensions....
> > 
> > Is there any list with description of know X extensions, so that I can
> > decide what to leave and  what to remove?
> 
> Contrary to extensions in the sense you find them in mozilla firefox,
> jedit etc, X extensions are more in the category of protocol- or
> behaviour extensions of the X11 model and cannot be easily removed from
> the current server implementation without breaking stuff or hampering
> functionality or performance.
>