From owner-freebsd-alpha Tue Sep 8 14:07:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13240 for freebsd-alpha-outgoing; Tue, 8 Sep 1998 14:07:56 -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 OAA13209 for ; Tue, 8 Sep 1998 14:07: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 WAA15373; Tue, 8 Sep 1998 22:08:06 +0100 (BST) Date: Tue, 8 Sep 1998 22:08:06 +0100 (BST) From: Doug Rabson To: "Justin T. Gibbs" cc: alpha@FreeBSD.ORG Subject: Re: Bt848 driver for Alpha In-Reply-To: <199809081952.NAA06723@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: > In article you wrote: > > On Mon, 7 Sep 1998, Roger Hardiman wrote: > > > > I would suggest something like the ncr driver: > > > > ... > > vm_offset_t bt848; > > > > #define REGOFF(x) (bt848 + offsetof(struct bt848_reg, x) > > #define READREGB(x) readb(REGOFF(x)) > > #define WRITEREGB(x, v) writeb(REGOFF(x), v) > > 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). -- 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