From owner-freebsd-hackers Tue May 8 2:55:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from newgold.net (eat.ManBeef.com [209.42.222.44]) by hub.freebsd.org (Postfix) with SMTP id A127637B423 for ; Tue, 8 May 2001 02:55:10 -0700 (PDT) (envelope-from jmallett@newgold.net) Received: (qmail 7237 invoked by uid 1000); 8 May 2001 09:52:31 -0000 Date: Tue, 8 May 2001 05:52:31 -0400 (EDT) From: Joseph Mallett To: Mike Smith Cc: Subject: Re: syscalls for getting information about system bus? In-Reply-To: <200105080946.f489kei02748@mass.dis.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 Tue, 8 May 2001, Mike Smith wrote: > > I'm sure this probably reeks of cluelessness, but I'm wondering how I can > > find each bus in the system, and if it's PCI/ISA/whatever, so that I could > > say "1 PCI bus, 1 ISA bus in system", etc. without having to probe the > > system directly, since I want to make what I'm working on portable. > > See libdevinfo in -current. There's nothing really portable for this Thanks, looks like a start. > sort of thing, though. Yeah, I figured there wouldn't be, but I figured I'd try asking. I'm trying to implement a '/sbin/hinv' for *BSD, and have been trying to make it as generic as possible, so I don't end up over-relying on certain hardware existing, etc. Thanks /joseph > > -- > ... every activity meets with opposition, everyone who acts has his > rivals and unfortunately opponents also. But not because people want > to be opponents, rather because the tasks and relationships force > people to take different points of view. [Dr. Fritz Todt] > V I C T O R Y N O T V E N G E A N C E > > -- [ Joseph Mallett ] [ xMach Core Team xMach: Proactively Unbloated Microkernel BSD ] [ Proud {Free,Net}BSD User; (Obj)C(++) Programmer ] [ http://xMach.org ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message