From owner-freebsd-hackers Sat Mar 8 05:50:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA14081 for hackers-outgoing; Sat, 8 Mar 1997 05:50:46 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id FAA14076 for ; Sat, 8 Mar 1997 05:50:40 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA11622; Sat, 8 Mar 1997 08:50:03 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Sat, 8 Mar 1997 08:50 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id IAA07113; Sat, 8 Mar 1997 08:09:34 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id IAA17032; Sat, 8 Mar 1997 08:15:11 -0500 (EST) Date: Sat, 8 Mar 1997 08:15:11 -0500 (EST) From: Thomas David Rivers Message-Id: <199703081315.IAA17032@lakes.water.net> To: ponds!cisco.com!bmcgover, ponds!freebsd.org!hackers, ponds!lambert.org!terry Subject: Re: Cyclom Card Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Brian writes: > I'm not quite sure I understand your reference to top/bottom drivers. I suspect > my driver would conform to this (?), as read/write routines would dump the > info in to and out of the tty buffering scheme (so I can use all the line > disciplines). Then, I'd have an interrupt handler (and a tweak in the write > routine to get things started on the first write) that shuffled data to/from > the tty routines to the card's buffers. IOCTL calls would manipulate the > tty structures on the cards (which are different than the BSD tty structures), > and then send down the appropriate hardware commands to get the card to > implement them. Yes, that's basically the idea. There is a definition of top/bottom drivers in "The Design and Implementat of the 4.3BSD UNIX Operating System" (and probably the 4.4 version, I don't yet own that) - when they discuss disk I/O, etc... - Dave Rivers -