The first problem i noticed was xemacs complainig about mouse image maps being to large whenever my mouse got over the toolbar.
Since i don't use the toolbar i just disabled it. But the real problem according to David is:

        The hardware cursor size of the 6554x chipsets is limited to

        32x32 pixels whilst the 65555 can do 64x64. However the code

        in XFree 3.3.2 attempts to be generic and so limits the maximum

        cursor size to 32x32 in all cases. Larger cursor sizes than 

        that cause problems. The solution is to switch between H/W

        and S/W cursor when needed automatically within the server.

        This is done in the latest alpha versions of the XFree C&T 

        driver and so it will be in the next full release of XFree.

        However using the "sw_cursor" option will deal with this 

        problem.

Second problem: though i could run startx, i could not run xdm. The screen started flashing and the system got inoperational.
So i looked at /var/lib/xdm/xdm-errors and found 'xf86MapVidMem: Could not mmap framebuffer (No such device or address)'
Then i looked at the output of the X-Server when started with startx and found:
'(--) SVGA: CHIPS: base address is set at 0xFD000000' The (--) means this line has been autodetected. (**) this line is provided by XF86Config.
The rest was easy i explicitly set the Membase in the device section: MemBase 0xFD000000.

        The problem here is not in the C&T driver, but is common to

        all drivers in XFree when the "-quiet" option is used. In this

        case the PCI probing code doesn't setup some of the address that

        the C&T server relies on to be there (I believe all servers 

        rely on these same values). The MemBase passed in actually 0x0

        which is useless. The fix is to delete the "-quiet" option from

        your scripts. I've fixed this bug in a server that can be found

        on the ftp site,

Third problem when i run smaller resolutions then the mouse pointer and the hotspot get quite far appart (about 5 cm)
Solution: uncomment Option "sw_cursor" in the device section of XF86Config.

        This is a silicon bug in the C&T chipsets and mentioned in the

        README.chips file. The problem is that the H/W cursor doesn't 

        like stretched modes on the screen, it instead tracks an 

        unstretched position. Again the proper solution is to switch

        to a S/W cursor automatically in the server when a stretched

        mode is used, and this is what the latest alphas of XFree do.

        However the older XFree 3.3.2 design can't handle all of the

        cases needed for this in the C&T chipsets (i.e. the user can

        ctrl-alt-+ to another mode!!). The solution is to either use

        a mode on the sc reen that uses the entire screen or again use

        the "sw_cursor" option.

Fourth problem i could only run 640 x 480 with 16bpp and then the display is vertically distorted.
Well, the right dotclocks in the XF86Config and the latest X-Server could fix this. Thanks again to David Bateman, i now
enjoy a very nice 1024x786 mode in 16 bpp.

This is what the device section of my XF86Config looks like:

Section "Device"

Identifier "My Video Card"
BoardName "ct65555"
VideoRam 2048
Option "sw_cursor"
MemBase 0xFD000000

EndSection

Of course you can get my XF86Config. As the C&T driver leaves the panel timings alone when using the LCD, it is fairly safe to share XF86Config files. Be carefull when you attach a monitor though.

If you ever wondered how the timings work for TFT here are the intrinsics :

       The timings for any LCD panel are independent of the mode used on them.

       This is why the C&T chipset have a set of mode timings for the CRT

       and a seperate set for the flat panel. In general the laptop BIOS correctly

       sets up the flat panel timings and the XFree driver leaves them alone.

       Hence the only important number in modeline on LCD panels for the C&T

       chipsets are the dotclock and the mode size. The other number should be

       program as for a CRT mode to allow for the possibilty that you'll use a

       simulscan mode (CRT + LCD)

All the details you will find in the programming manual To get the most out of my X i have a wheelmouse. Once you have tried one, it is hardto get along without one. But there is no need to. The wheelmouse is supported under X. The offical Wheel Mouse Page is hosted by Colas Nahaboo, who is also the author of gwm, the emacs of the windowmanagers.