From owner-freebsd-alpha Wed Sep 9 01:46:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA08425 for freebsd-alpha-outgoing; Wed, 9 Sep 1998 01:46:51 -0700 (PDT) (envelope-from owner-freebsd-alpha@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA08415 for ; Wed, 9 Sep 1998 01:46:48 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA17404; Wed, 9 Sep 1998 09:46:44 +0100 (BST) Date: Wed, 9 Sep 1998 09:46:44 +0100 (BST) From: Doug Rabson To: "Justin T. Gibbs" cc: alpha@FreeBSD.ORG Subject: Re: Bt848 driver for Alpha In-Reply-To: <199809082315.RAA07283@narnia.plutotech.com> 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 Tue, 8 Sep 1998, Justin T. Gibbs wrote: > >> Ick. Ick. Ick. Almost all of the CAM code uses the bus space facility > >> to do this. Why re-invent the wheel? > > > > I wasn't re-inventing anything. I just happened to look at a different > > wheel. Constructing a bus space around this is trivial (virtually the > > same as the i386 bus space). > > Well, the NCR driver is an MI driver, so it should use MI interfaces > to get it's work done. My (incorrect??) assumption was that you were > pushing for writeb and friends to become MI interfaces. I used inx/outx and readx/writex to get the port up and running quickly without having to spend huge quantities of effort changing drivers. Of course I will implement the bus_space api when CAM goes in. I will still need to support inx/outx for non-CAM drivers though unless CAM converts all of them to bus_space. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message