From owner-freebsd-hackers  Mon Jul 28 14:44:36 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id OAA05279
          for hackers-outgoing; Mon, 28 Jul 1997 14:44:36 -0700 (PDT)
Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA05273
          for <hackers@freebsd.org>; Mon, 28 Jul 1997 14:44:32 -0700 (PDT)
Received: from x14.mi.uni-koeln.de (annexr3-5.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA27499
  (5.67b/IDA-1.5 for <hackers@freebsd.org>); Mon, 28 Jul 1997 23:44:28 +0200
Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.6/8.6.9) id XAA12237; Mon, 28 Jul 1997 23:44:28 +0200 (CEST)
X-Face: "<d]#=8pzx);RzeqSKI86OVa7=!0/(uRa.+B.9Z9\eNUn@UG?!`y7yt2dFNn%k4'.}](uE%
 yCO)$e&Y1%3EO~ifu6Q-#YUM&JZ't,}JkPnAz,8Dj33u%@GBi%[Y#LHz$]h7a<p4)-jKI7~sKjlP-^
 EvA[G;]v&0]W!EL%shs,{7x0|oqN4YVIs5,NI#,V{9"WF):5&RkOhyj*#-IAG}Tnu;YCF,d
Message-Id: <19970728234428.16657@mi.uni-koeln.de>
Date: Mon, 28 Jul 1997 23:44:28 +0200
From: Stefan Esser <se@FreeBSD.ORG>
To: Michael Smith <msmith@atrad.adelaide.edu.au>
Cc: "Mike O'Dell" <mo@uu.net>, hackers@FreeBSD.ORG
Subject: Re: SMBIOS/DMI etc
References: <QQcywq17534.199707191502@rodan.UU.NET> <199707191512.AAA14340@genesis.atrad.adelaide.edu.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.74
In-Reply-To: <199707191512.AAA14340@genesis.atrad.adelaide.edu.au>; from Michael Smith on Sun, Jul 20, 1997 at 12:42:09AM +0930
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Jul 20, Michael Smith <msmith@atrad.adelaide.edu.au> wrote:
> Stefan, do you have any interest in using the PCI BIOS as well
> as/instead of doing things the "hard way" as is done at the moment?

Well, yes and no ...

I have considered adding calls to the PCI BIOS as an
alternate mechanism to directly reading configuration 
space registers. But I have no intention to make the
PCI code depend on PCI BIOS services.

There is one function that might be interesting for SMP 
motherboards that are not compliant to the latest SMP 
spec. and that need some knowledge about the routing of
PCI interrupt pins to the chip-set. 

There is a PCI BIOS function that builds a table which
contains the necessary information (which else has to
be guessed).

But I do not have time to debug the BIOS32 functionality,
right now, and need to know it is operational, before I
try to use it ...

Regards, STefan