From owner-freebsd-hackers Sun Jul 4 3: 6:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 0C96C14CB0 for ; Sun, 4 Jul 1999 03:06:07 -0700 (PDT) (envelope-from dfr@nlsystems.com) 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 LAA19425; Sun, 4 Jul 1999 11:10:23 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sun, 4 Jul 1999 11:05:14 +0100 (BST) From: Doug Rabson To: Warner Losh Cc: hackers@freebsd.org Subject: Re: The busspace modernization initiative. In-Reply-To: <199907032124.PAA33313@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 3 Jul 1999, Warner Losh wrote: > > I'm trying to update the bus-space routines to match more closely the > NetBSD routines. The new-config project has already done this, so > I've been moving their code into a relatively pure -current tree. > > I'm finding that there are many places that assume that > bus_space_handle_t is the same thing as u_int or that > bus_space_handles can be compared with !=. Some of this code I even > wrote :-(. > > These strike me as unwise assumptions. Fortunately, it appears that > there are only 4 files impacted (at least in my config, I've not tried > GENERIC yet): > ../../pci/bt_pci.c > ../../i386/i386/nexus.c > ../../i386/isa/aha_isa.c > ../../pci/es1370.c > It strikes me as unwise to make these assumptions, even if they should > generally prove to be true. > > Comments? I think you are on the right lines here. Where does the resource come from? Are you going to support bus_space_map() and if so, how are you planning to call BUS_ALLOC_RESOURCE? I assume that you will update the alpha version of bus.h too. -- 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-hackers" in the body of the message