This is a work in progress.  It is not finished.  It is not yet
a usable driver.  It may however move pixels from MK III camera
to disk.  More work need to be done.

To compile edit makefile, remove reference to MLog and shhopt
from the link path.  Nothing calls these as of today.
Next type "make"

To run do this:

Install RT Linux and load both modules using insmod.  Make sure
the test programs that come with RT Linux work.

Now as root type "inmod ts_driver".  This will load the tass
driver with Norman's FSA.  It will be stuck in "idle" until
later.

Next as not root, run t3_server. At the promt type two commands
1) set_ccd0_on
2) begin
this should start the flow of data from CCD #0.  You can turn on
the others but change globals.c first to enable logging nos. 1 amd 2
(I said this this was not finished)

I intend to process a "start-up file" that uses the same commands
as allowed from the keyboard so later you will not need to enter
the set_ccd0-on command.   See proc_ui.c for a list of commands.

Some hinds on debugging RT tasks.  You can not make normal system
calls from an RT task.  You cannot even make calls to libc functions.
The #includes define special versions of everytrhing.  To make
life easyer I put a function in t3_driver called something like
send_message.  Call this with a text string and the text will
appera on the console.

I send these status message back to the server the same way scan lines
are sent but tag them as status messages.  When the server gets a status
message it just echoes it to the screen.  This is the only way I know
to debug an RT Linux task.  Just put send_message calls where needed.

Each time you kill the server (quit command not yet working) do an
rmmod t3_driver too.

Norman,  
Please look at the part of the t3_driver where the interrupt
frequency gets set.  Currently it is 8000Hz.  This may be to fast.
I don't know what constant to use to make it go slower.  change it
to something resonable.

Everyone,
If you make a fix or improvement to the code please make it easy to find.
There could be three of use changing the same line of code.  I am going
to have to collate changes.  I would have liked to have cleaned up the
code, added comments and file headers but i'll do this later.

-- Chris,  2 May 97