From owner-freebsd-hackers Sun Dec 14 18:33:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA08567 for hackers-outgoing; Sun, 14 Dec 1997 18:33:26 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA08515 for ; Sun, 14 Dec 1997 18:33:11 -0800 (PST) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.7/8.8.7) id SAA27957; Sun, 14 Dec 1997 18:30:34 -0800 (PST) Message-ID: <19971214183034.27523@hydrogen.nike.efn.org> Date: Sun, 14 Dec 1997 18:30:34 -0800 From: John-Mark Gurney To: Mike Smith Cc: hackers@freebsd.org Subject: Re: Bus/Processor specific I/O methods - was Re: Beginning SPARC port References: <199712150045.SAA14933@bob.scl.ameslab.gov> <199712150115.LAA00275@word.smith.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <199712150115.LAA00275@word.smith.net.au>; from Mike Smith on Mon, Dec 15, 1997 at 11:45:22AM +1030 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Mike Smith scribbled this message on Dec 15: > > > > FWIW, NetBSD has a couple of nice man pages on their bus stuff. See > > bus_space(9) and bus_dma(9). It looks like a well abstracted interface, > > and works on several architectures. We really should be looking at ways > > to make the BSD's more similar whenever possible. Making the drivers > > more portable would especially be nice.. so I think that this issue > > definately deserves more thought. > > The NetBSD 'bus.h' interface has had a lot of time to stabilise, and > plenty of performance-sensitive pounding. For all its conceptual > difficulty, it *does* appear to be the best way to go. > > (No insult intended, JMG!) actually, after reading the man pages... I found the BEST way to describe bus.h... it's just a subset of what I want to do... bus.h only describes how to interact with mem/io ranges by the cpu... my bus/device code does a lot more than that... it keeps keeps track of ALL bus resources.. my bus/device code is best described as a complete device management system than a bus interface mechanism... I have larger plans for my code than just managing hardware devices... the code will be VERY simply to expand it to support such things as using to keep track of char/block devices, and other things... with a common interface.. it will be VERY easy to create something like the win95's list of system devices that is VERY complete... -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD