From owner-freebsd-arch  Thu Jul 13  4:14:26 2000
Delivered-To: freebsd-arch@freebsd.org
Received: from ywing.creative.net.au (ywing.creative.net.au [203.56.168.34])
	by hub.freebsd.org (Postfix) with ESMTP id 489DD37C3DF
	for <freebsd-arch@FreeBSD.ORG>; Thu, 13 Jul 2000 04:14:17 -0700 (PDT)
	(envelope-from adrian@ywing.creative.net.au)
Received: (from adrian@localhost)
	by ywing.creative.net.au (8.9.3/8.9.3) id NAA16851;
	Thu, 13 Jul 2000 13:20:47 +0200 (CEST)
	(envelope-from adrian)
Date: Thu, 13 Jul 2000 13:20:47 +0200
From: Adrian Chadd <adrian@FreeBSD.ORG>
To: Neil Blakey-Milner <nbm@mithrandr.moria.org>
Cc: Boris Popov <bp@butya.kz>, Andrzej Bialecki <abial@webgiro.com>,
	freebsd-arch@FreeBSD.ORG
Subject: Re: SysctlFS
Message-ID: <20000713132047.B14043@ywing.creative.net.au>
References: <Pine.BSF.4.20.0007121328020.49102-100000@mx.webgiro.com> <Pine.BSF.4.10.10007130754390.15644-100000@lion.butya.kz> <20000713093439.A45743@mithrandr.moria.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <20000713093439.A45743@mithrandr.moria.org>; from nbm@mithrandr.moria.org on Thu, Jul 13, 2000 at 09:34:39AM +0200
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, Jul 13, 2000, Neil Blakey-Milner wrote:
> On Thu 2000-07-13 (08:17), Boris Popov wrote:
> > 	So, internal fs can have structure like that:
> > 
> > 	/bus	- newbus tree
> > 	/sysctl	- sysctl tree
> 
> Once the "dynamic sysctls" hit the tree, I have been running a sysctl
> exportation of newbus information for a few weeks (months, possibly).
> 
> There's also a "sysinfo" console program as a (badly written, since
> sysctl is a pain to manipulate) reference on how to extract information
> from it:
> 
> root0
> nexus0
> pcib0 <Intel 82443LX (440 LX) host to PCI bridge>
> npx0 <math processor>
> pci0 <PCI bus>
> ...
> atapci0 <Intel PIIX4 ATA33 conroller>
> ata0
> ata1
> eisa0: not present
> vga0 <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff
> sc0 <System console>
> atkbdc0 <Keyboard controller (i8042)> at port 0x60,0x64
> ...
> atpic0 <AT interrupt controller> at port 0x20-0x21,0xa0-0xa1 irq 2
> sysresource4 <System Resource> at port 0x4d0-0x4d1,0x8000-0x803f,0x7000-0x700f
> 
> It just grabs the information from the sysctl export:
> 
> hw.devices.fdc0.desc: NEC 72065B or clone
> hw.devices.fdc0.children: fd0,fd1
> hw.devices.fdc0.state: attached
> hw.devices.fdc0.irq: 6
> hw.devices.fdc0.drq: 2
> hw.devices.fdc0.ioport: 0x3f0-0x3f5,0x3f7
> 
> Windows-like Device Manager, anyone?

Uhm, my plan was to write an example newbusfs with my VFS documentation
(no, don't ask me for it, its still in its infancy. :)

I forgot that hw.devices existed now. I was going to do something a little
more like irix/solaris' device tree ..


Adrian

-- 
Adrian Chadd			Build a man a fire, and he's warm for the
<adrian@FreeBSD.org>		rest of the evening. Set a man on fire and
				he's warm for the rest of his life.



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message