From owner-freebsd-hardware  Tue May 20 19:00:50 1997
Return-Path: <owner-hardware>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id TAA09925
          for hardware-outgoing; Tue, 20 May 1997 19:00:50 -0700 (PDT)
Received: from TRUTH.WOFFORD.EDU (truth.wofford.edu [199.190.174.30])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id TAA09908
          for <HARDWARE@FREEBSD.ORG>; Tue, 20 May 1997 19:00:38 -0700 (PDT)
Date: Tue, 20 May 1997 22:00:35 -0400
From: Dan Welch <WELCHDW@wofford.edu>
To: brett@lariat.ORG
CC: HARDWARE@FREEBSD.ORG, WELCHDW@wofford.edu
Message-Id: <970520220035.22a2107f@wofford.edu>
Subject: Re: isa bus and boca multiport boards
Sender: owner-hardware@FREEBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>>device sio2  at isa? port 0x200 tty flags 0x1105
>>device sio3  at isa? port 0x208 tty flags 0x1105
>>...
>>device sio17 at isa? port 0x278 tty flags 0x1105 irq 12 vector siointr

> Ouch! Don't know what else you have in your system, but you are
> probably stomping on other devices' ports something terrible. There
> are bound to be major conflicts here. You might want to get a book
> on the PC architecture, and survey all of your peripherals' port
> usage, so you can learn to avoid the reserved ports. 

Good point. Before using this range I verified that there are no
conflicts with the ranges listed in the dmesg output for other
devices. I also experimented with addresses in the 0x100 set based
on the same analysis. Nevertheless, there may well be addresses that
other devices use that are not listed by dmesg, so I'll check other
documents as you suggest.

> Also set the flags to 0x1185 for better diagnostics.

Will do. Thanks.