From owner-freebsd-alpha Thu Feb 24 13:12:49 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from anchor-post-30.mail.demon.net (anchor-post-30.mail.demon.net [194.217.242.88]) by hub.freebsd.org (Postfix) with ESMTP id C0A8A37BBA0 for ; Thu, 24 Feb 2000 13:12:28 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-30.mail.demon.net with esmtp (Exim 2.12 #1) id 12O5YW-0007Mz-0U; Thu, 24 Feb 2000 21:12:16 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id VAA57795; Thu, 24 Feb 2000 21:15:27 GMT (envelope-from dfr@nlsystems.com) Date: Thu, 24 Feb 2000 21:15:19 +0000 (GMT) From: Doug Rabson To: Matthew Jacob Cc: Andrew Gallatin , freebsd-alpha@freebsd.org Subject: Re: problems with Qlogic SCSI combo card In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 24 Feb 2000, Matthew Jacob wrote: > > > On Thu, 24 Feb 2000, Andrew Gallatin wrote: > > > > > 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.. > > Uh, I'd have to admit I would have to look at the PCI spec again to know > this... but I can assure you that we'll need quirks no matter what. Hmm. I remember that at one point, I had to cope with the fact that some SRM firmware allocates port ranges outside the 0-65535 range normally used on x86. Is it possible that such port ranges are not supported behind bridges? Neither of my alphas does this now, I must have upgraded the firmware once too often... -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message