*****SPAM***** kdrive documentation?

SPAM: -------------------- Start SpamAssassin results ----------------------
SPAM: This mail is probably spam.  The original message has been altered
SPAM: so you can recognise or block similar unwanted mail in future.
SPAM: See http://spamassassin.org/tag/ for more details.
SPAM: 
SPAM: Content analysis details:   (5.00 hits, 5 required)
SPAM: SPAM_PHRASE_00_01  (0.6 points)  BODY: Spam phrases score is 00 to 01 (low)
SPAM:                    [score: 0]
SPAM: MSG_ID_ADDED_BY_MTA_2 (0.5 points)  'Message-Id' was added by a relay (2)
SPAM: RCVD_IN_MULTIHOP_DSBL (0.8 points)  RBL: Received via a relay in multihop.dsbl.org
SPAM:                    [RBL check: found 16.118.134.159.multihop.dsbl.org]
SPAM: RCVD_IN_RFCI       (2.3 points)  RBL: Received via a relay in ipwhois.rfc-ignorant.org
SPAM:                    [RBL check: found 16.118.134.159.ipwhois.rfc-ignorant.org., type: 127.0.0.6]
SPAM: RCVD_IN_UNCONFIRMED_DSBL (0.8 points)  RBL: Received via a relay in unconfirmed.dsbl.org
SPAM:                    [RBL check: found 16.118.134.159.unconfirmed.dsbl.org]
SPAM: 
SPAM: -------------------- End of SpamAssassin results ---------------------

After a few searches and checking the sources, it seems kdrive is poorly 
documented, at best. The best I found was by Juliusz Chroboczek at his web 
page. And I only found that by going through my past E-Mails from Xpert when 
he gave some great help to someone who was interested in paring X down as far 
as possible.

Now it seems that kdrive support Xfbdev, Xvesa, and several accelerated 
Xservers. Juliusz was able to provide a bit of detail RE: Xfbdev and Xvesa, 
but there doesn't seem to be any doc's RE: any of the accelerated drivers.

Judging from the kdrive directory, there are several accelerated drivers 
supported, but only source code and I can't read source code very well.

It would be nice to have some decent documentation for building kdrive 
Xservers, now that X-Terminal projects are becoming more popular. Older 
hardware with limited drive space and memory can take advantage of such small 
Xservers rather than trying to run a full blown X. I had one such machine:

200Mhz Pentium MMX with 16M. When I had installed a base system with a full 
X, it ran fine, until I tried to run a KDE desktop from my regular box on it. 
It got about half way through the spach-screen for KDE and X crashed. When I 
increased the memory to 32M it ran, but noticably slow. I am guessing that 
kdrive would improve this, and building the system againt uClibc would be 
ever better?

But, I don't want to just bitch about a lack of documentaion, I want to do 
something about it! I've been playing with Linux From Scratch for a while now 
and am getting to enjoy building Linux systems to my whim. I've a few old 
PC's that I use for such experiments and I would like to work on creating 
proper documentation for kdrive. Juliusz gives some guidance for building the 
Xfbdev and Xvesa versions, but I would like to improve on this and add the 
missing information for the other drivers kdrive currently supports.

I know that Keith Packard wrote kdrive, or at least is the lead developer. 
And it seems Juliusz knows a fair bit about it as well. I know that several 
others on this list have been using it recently. If I could ask for any 
helpful info, I'll see how I get on compiling it together into proper 
documentation. It's nice to know how to compile kdrive for Xfbdev, but 
without the background of setting up the frame buffer in the first place, 
it's not much use. I don't know the first thing about setting up the frame 
buffer on a Linux system, therefore compiling the Xfbdev version of kdrive 
doesn't help me much.

Also, what is required to get an X driver to work under kdrive? I've got 
several cards available for testing, but not all of them are listed under the 
kdrive directory. Maybe we can also interest some of the driver maintainers 
to help port the rest of the X drivers to work under kdrive?

Just a few of my ideas.

Cheers,

	John Gay