Re: [PARPORT] IEEE1284


Nicolas Souchu (nsouch@teaser.fr)
Wed, 9 Dec 1998 01:08:17 +0000


On Wed, Dec 09, 1998 at 12:22:38AM +0000, Nicolas Souchu wrote:
>
>Hi guys,
>
>On Tue, Dec 08, 1998 at 07:37:39PM +0000, Tim Waugh wrote:
>>
>>> At least in my application it doesn't make sense
>>> to use ECP when the hardware doesn't directly support it.
>>
>>The only reason it would be necessary is if the peripheral ONLY speak ECP
>>mode, and we don't have the hardware for it.
>
>Then, the peripheral is not IEEE1284 compliant. But,
>
> - peripheral behaviour may be easier to analyze with emulation
> (OfficeJet development is an example)
> - when 2 hosts exchange data, one of them, with full ECP support,
> may want to take advantage of DMA+hardware_handshake
> - just for fun
>
>BTW, Tim, did you think about host<->host operations? The main issue is
>reverting the negociation with only 4 control lines against 5 status lines.
>
>I talk to you about this in order to get FreeBSD<->Linux _compatible_ for
>an ECP/EPP-IP interface. A nice challenge... just with IEEE1284 specifications.
>I'm about to install a Linux box to get the old-style lp/plip Linux stuff
>work with our new ppbus interface.

BTW, you may have a look to the recent web page:

http://www.freebsd.org/~nsouch/ppbus.html

Nicolas.

-- 
nsouch@teaser.fr / nsouch@freebsd.org
FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org

-- To unsubscribe, send mail to: linux-parport-request@torque.net -- -- with the single word "unsubscribe" in the body of the message. --



This archive was generated by hypermail 2.0b3 on Wed 30 Dec 1998 - 10:18:52 EST