Re: ECP port driver

[Chris Albertson <chrisalbertson90278@yahoo.com>]

Rob,

Sounds like you should keep working on it.  I am
converting my Buffer Card driver from 2.2 to 2.4
that's enough for now.  And yes "insb" with big
blocks is a win.  I do it in the Buffer Driver
the bottleneck there is now the ISA bus

I would like to see your driver.  I'd like to get
a start on software that would use it.

Robert Creager wrote:
> 
> 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
   Redondo Beach, California
   home: 310-376-1029
   cell: 310-990-7550