Date: Tue, 10 Oct 1995 20:09:36 +1000 From: Bruce Evans <bde@zeta.org.au> To: hackers@freebsd.org, msmith@atrad.adelaide.edu.au Subject: Re: non-sio UART driver Message-ID: <199510101009.UAA15689@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
> As I dribbled a little while ago, I need to talk to a multidrop serial bus >using a standard serial port. What's a multidrop serial bus? >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. If you need to do any normal serial i/o to a 16x50 then I suggest adding to sio. >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?) That would work if the new device is probed after sio. >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?) If there are only protocol differences, then use a line discipline. Slip and ppp are good examples. Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199510101009.UAA15689>