From owner-freebsd-hackers Tue Oct 10 01:59:37 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA24063 for hackers-outgoing; Tue, 10 Oct 1995 01:59:37 -0700 Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id BAA24045 for ; Tue, 10 Oct 1995 01:59:16 -0700 Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.9/8.6.9) id SAA11459 for hackers@freebsd.org; Tue, 10 Oct 1995 18:58:12 +0930 From: Michael Smith Message-Id: <199510100928.SAA11459@genesis.atrad.adelaide.edu.au> Subject: non-sio UART driver To: hackers@freebsd.org Date: Tue, 10 Oct 1995 18:58:12 +0930 (CST) Content-Type: text Content-Length: 1227 Sender: owner-hackers@freebsd.org Precedence: bulk Hiho serial hackertype people... (that probably means you, Bruce. Sorry 8) As I dribbled a little while ago, I need to talk to a multidrop serial bus using a standard serial port. The nature of the protocol and interface mechanism for the bus tend to indicate to me that I don't want to use the sio driver and hack on that, but perhaps to make a copy and cut it severely down to size. Given this, how should I avoid the MCR_IENABLE conflict that's introduced by sioprobe() forcing the standard four ports' interrupts off? (Perhaps just reenable interrupts on open?) Infact, given that this is really a packet-based network, would I be better of abandoning all of the tty interface gumpf in the sio driver and doing everything via ioctl() calls? (or something equally bogus?) As you can see, I could do with the odd suggestive clue here. -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] My car has "demand start" -Terry Lambert UNIX: live FreeBSD or die! [[