From owner-freebsd-hackers Wed Nov 11 14:24:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10567 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 14:24:56 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10562 for ; Wed, 11 Nov 1998 14:24:54 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from o2.cs.rpi.edu (root@o2.cs.rpi.edu [128.113.96.156]) by cs.rpi.edu (8.9.1/8.9.1) with ESMTP id RAA04716; Wed, 11 Nov 1998 17:24:26 -0500 (EST) Received: from localhost (crossd@localhost) by o2.cs.rpi.edu (8.9.1a/8.9.1) with ESMTP id RAA03311; Wed, 11 Nov 1998 17:24:26 -0500 (EST) X-Authentication-Warning: o2.cs.rpi.edu: crossd owned process doing -bs Date: Wed, 11 Nov 1998 17:24:25 -0500 From: "David E. Cross" To: Phillip Salzman cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel Hacking stuffs (Bidirectional Parallel Port) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11 Nov 1998, Phillip Salzman wrote: > > Have you looked at the Parallel Port Bus info (ie, ppbus)? > > I was going to use this while creating a driver for my parallel > port scanner, but noticed it would require a more advanced knowledge of C > than I had at the time. > > -- > Phillip Salzman I had not looked at it until you mentioned it. It suffers the same problems that the lpt.c driver does. The way these drivers gain their bidirectional ability is by tying the status lines (ACK, BUSY, PE, ERROR, and 1 I forget) to the data lines, allowing 5 bits of data at a time, one of these bits is used as a framing signal (0x1x means high nibble is being transfered, 0x0x is the low nibble). Am I correct in thinking that 'modern' bidirectional ports and printers have 8 lines dedicated to carrying data in both directions? Or is this the only way it has ever been, and ever will be? -- David Cross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message