From owner-freebsd-alpha Thu Feb 24 10:27:44 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 60D0337BCEF for ; Thu, 24 Feb 2000 10:27:40 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id NAA09412; Thu, 24 Feb 2000 13:27:39 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id NAA49387; Thu, 24 Feb 2000 13:27:08 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 24 Feb 2000 13:27:08 -0500 (EST) To: mjacob@feral.com Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: problems with Qlogic SCSI combo card In-Reply-To: References: <14517.28475.49296.652665@grasshopper.cs.duke.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14517.30581.883054.17781@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob writes: > > > > Matthew Jacob writes: > > > > > > Is there any reason why we shouldn't allow only memory mapping > > > if I/O mapping is broken? > > > > > > > That's a great idea -- how do we tell? > > Ah! do I detect a pink of irony? :-) No.. I was serious, but in a hurry. I was wondering how one tells if a ppb doesn't deal with i/o space access behind it. Is there a standard value you get back when you read the i/o base & i/o limit registers in config space, or is there some other way to tell, or do we need a quirk for 21050s, etc.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message