[PATCH] Remove xcalibrate and tslib support

[Tiago Vignatti]

Hi Timothy! Sorry to reply this thread so late.

On Thu, Jul 08, 2010 at 08:34:20PM +0200, ext Timothy Meade wrote:
> 
> I would rather move
> forward not backwards and getting XF86 to a usable memory footprint
> and startup time would certainly be moving forward (unacceptible
> startup time being any noticable delay between starting /usr/bin/X and
> completing vt switch). I have a very vague initial proposal for
> replacing kdrive ddx with a more modular and XF86 compatible
> replacement and am also researching optimization options for XF86,
> simplifiying probing and replacing with bus enumeration and maybe
> flattened device trees which Ubuntu/Linaro have shown interest in.

nice!

I kinda started to record some memory usage of Xorg and Xfbdev (with some help
of Ajax and Mikhail). You may find this interesting and would be nice if you
could run mem-usage script on your device to improve this info:

    http://people.freedesktop.org/~vignatti/scrutinizing-x-mem/standalone-usage/
    http://people.freedesktop.org/~vignatti/scrutinizing-x-mem/standalone-usage/xorg_2010-07-14_1.8.0RC1_mydevice.txt
    http://people.freedesktop.org/~vignatti/scrutinizing-x-mem/standalone-usage/xfbdev_2010-03-25_dottedmag.txt


This second link shows a device running with ~ 4.5MB of RSS. This is with Xorg
1.8. On the third link you can see that Mikhail got ~ 3.9MB of RSS using
kdrive Xfbdev. That's not much difference when comparing with Xorg.

Xorg 1.9 will be bringing a bit more expertise regarding memory usage and
we're going to be able to disable other components that for instance I don't
care for my device (such as DBE, Xdmcp, libpciaccess). So, as Ajax stated,
it's very likely that we'll be able to delete kdrive hardware servers if
memory is the only advantage on those (and honestly I get always shocked when
someone comes to this mailing list mentioning that still using kdrive. Move on
:)


Cheers,

             Tiago