From owner-freebsd-hackers Wed Jul 10 15:42:28 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA23167 for hackers-outgoing; Wed, 10 Jul 1996 15:42:28 -0700 (PDT) Received: from horst.bfd.com (horst.bfd.com [204.160.242.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA23161 for ; Wed, 10 Jul 1996 15:42:26 -0700 (PDT) Received: from harlie (bastion.bfd.com [204.160.242.2]) by horst.bfd.com (8.7.5/8.7.3) with SMTP id PAA19555; Wed, 10 Jul 1996 15:39:25 -0700 (PDT) Date: Wed, 10 Jul 1996 15:39:55 -0700 (PDT) From: "Eric J. Schwertfeger" X-Sender: ejs@harlie To: Terry Lambert cc: jkh@time.cdrom.com, jgreco@brasil.moneng.mei.com, davidg@Root.COM, dawes@rf900.physics.usyd.edu.au, SimsS@Infi.Net, hackers@FreeBSD.ORG Subject: Re: Some recent changes to GENERIC In-Reply-To: <199607102118.OAA27299@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 10 Jul 1996, Terry Lambert wrote: > > Agreed with on machines coming off the shelf that way, but most people I > > know that add an internal modem add it as com3/irq5, since they don't have > > to figure out how to disable a comm port. which isn't 4 port, but it also > > isn't two port. > > Most interrupt capable PC software that supports com3: and com4: do so > by allowing only one of com1:/com3: or com2:/com4: to be open and > running with interrupts enabled simultaneously. While I agree that a lot of people don't bother avoiding interrupt conflict, I have to disagree with the software not allowing for it. I honestly can't remember a single program from 5 years of consulting that allowed for com 3 without letting me specify what IRQ com 3 was on. Even Win3.1 (can't speak for older versions) can be set, just not easily. I've seen a lot more braindead hardware (cheap internal modems) that only allow for IRQ 3/4.