From owner-freebsd-hackers Sun Dec 14 22:19:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA25151 for hackers-outgoing; Sun, 14 Dec 1997 22:19:04 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from cheops.anu.edu.au (cheops.anu.edu.au [150.203.76.24]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA25116 for ; Sun, 14 Dec 1997 22:18:53 -0800 (PST) (envelope-from avalon@coombs.anu.edu.au) Message-Id: <199712150618.WAA25116@hub.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA230286659; Mon, 15 Dec 1997 17:17:39 +1100 From: Darren Reed Subject: Re: Bus/Processor specific I/O methods - was Re: Beginning SPARC port To: gurney_j@resnet.uoregon.edu Date: Mon, 15 Dec 1997 17:17:38 +1100 (EDT) Cc: mike@smith.net.au, hackers@FreeBSD.ORG In-Reply-To: <19971214183034.27523@hydrogen.nike.efn.org> from "John-Mark Gurney" at Dec 14, 97 06:30:34 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In some mail from John-Mark Gurney, sie said: > > 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... Hmmm, here's a question for you... How long before FreeBSD has an 10-MB kernel at boot-time, just like NT ? (Well, minus whatever bloat there is for the GUI) Darren