Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!news.ececs.uc.edu!news.kei.com!news.mathworks.com!enews.sgi.com!arclight.uoregon.edu!news.sprintlink.net!news-peer.sprintlink.net!howland.erols.net!agate!news.ucsc.edu!ruby.cse.ucsc.edu!not-for-mail From: eric@cse.ucsc.edu (Eric Rosen) Newsgroups: comp.unix.bsd.bsdi.misc Subject: Re: stb 4-com serial card Date: 17 Sep 1996 20:47:05 -0700 Organization: Image Processing & Multimedia Lab (UC Santa Cruz) Lines: 15 Message-ID: <51nrbp$s2f@ruby.cse.ucsc.edu> References: <51i3ra$gtb@nnrp1.news.primenet.com> <51jpil$n15@doctor.nl2k.edmonton.ab.ca> <DxuEu7.C21@wlbr.iipo.gtegsc.com> NNTP-Posting-Host: ruby.cse.ucsc.edu We've been using an STB Systems 4-COM for some time, and our kernel configuration (built from studying the com(4) man page and experimenting) looks similar. --Eric # STB Systems 4-COM # * configured to share single interrupt # * group-id must be non-zero since no interrupt indicator port com4 at isa? port 0x1f8 irq 10 flags 0x01000 com5 at isa? port 0x1e8 flags 0x11000 com6 at isa? port 0x1a8 flags 0x21000 com7 at isa? port 0x2a8 flags 0x31000