Re: ECP port driver

[Robert Creager <robert@carolinecreager.com>]

Chris,

Well, I was thinking more along the lines of "how far
along are you?".  If you haven't started yet, I'll
continue.  If you're nearly done, I won't continue. 
That sort of thing.  As soon as I have something
working, I'll be happy to show everyone.

I will always support the code I write.

I am using the parport driver.  I am to the point of
implementing the read method on the device.  The 2.4.5
parport driver doesn't implement the read using the
FIFO/FIFO information.  I'm grabbing the 2.4.9 kernel
to see if it might be there, otherwise, I'll spin my
own from the 'broken' paraport block read.

While playing around with another, simpler parallel
port driver, I found that using the insb macro with 16
bytes transfered at a time gets my computer to around
30 second transfer time for 16Mbytes.  Reading 1 byte
at a time using inb read method takes around 90
seconds for 16Mbytes.

The 2.4.5 parport driver only implements DMA on the
write side, not the read side, so that may be more of
an adventure to try to implement.

I am planning on implementing a specific device which
uses the FIFO test mode, which will stream data
without any hardware hooked up, which will provide a
device which behaves the same as the real thing.

You want to see my current code now, let me know and
I'll send it to you.

Later,
Rob

---- Chris Albertson <chrisalbertson90278@yahoo.com>
wrote:
> 
> Thoughts?  Put your code someplace where others can
get
> it and update it often.  I'll take a look at it. 
Maybe
> others will too.  How does your driver work?   Does
it
> user the kernel's "parport" system? 
> 
> Robert Creager wrote:
> > 
> > Hey Chris,
> > 
> > I also am working on a loadable device driver,
> > developing with the 2.4 kernel.  I have a decent
> > skeleton, and am starting on the meat of the
code.  I
> > hope to have a simple reader this week, and then
move
> > on to using DMA.  Rather than duplicate
efforts...  I
> > have no particular preference (as to writing this
or
> > not), as I've other TASS code to write.  Thoughts?
> > 
> > Later,
> > Rob
> > 
> > ---- Chris Albertson
<chrisalbertson90278@yahoo.com>
> > wrote:
> > >
> > > On another front I've got RH7.1 with it's 2.4
Kernel
> > installed.
> > > and I'm working on converting my RAM card
driver.  I
> > intend to
> > > write a loadable kernel level driver for the
Mark
> > IV's ECP port
> > > interface too.  I'll copy the Zip drive driver
or
> > some other
> > > parallel port device's driver.  There are plenty
of
> > examples
> > > in the kernel sources.
> > >
> > > I may send you some code that you could put in
you
> > control
> > > program.  Possibly a new make file with a few
more
> > targets
> > > Like a "make dist" that will build a time
stamped
> > tar file.
> > >
> > > Stupendous Man wrote:
> > > >
> > > >   I've written my own control program for the
Mark
> > IV
> > > > (as you all should know by now, I have a
> > compulsion to
> > > > re-write any and all software I use on a
regular
> > basis).
> > > > This version is written in C and *nix.  It
allows
> > both
> > > > interactive and file-driven input.
> > > >
> > > >   Please read the manual to get an idea for
the
> > way it
> > > > works -- a simple command-line reader.  I
welcome
> > comments
> > > > on improving it.  The program hasn't been
> > field-tested yet,
> > > > but will be soon!
> > > >
> > > >   You can find the manual and full source code
at
> > > >
> > > >         http://spiff.rit.edu/tass/tait/
> > > >
> > > >   Beware -- this is alpha quality.
> > > >
> > > >
> > Michael Richmond
> > >
> > > --
> > >
> > > --
> > >    Chris Albertson
> > >    chrisalbertson90278@yahoo.com
> > >    Redondo Beach, California
> > >    home: 310-376-1029
> > >    cell: 310-990-7550
> > >
> > >
> > >
> 
> -- 
> 
> --
>    Chris Albertson             
>    chrisalbertson90278@yahoo.com
>    Redondo Beach, California
>    home: 310-376-1029
>    cell: 310-990-7550
> 
> 
>