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 Message-ID: <19970728234428.16657@mi.uni-koeln.de> In-Reply-To: <199707191512.AAA14340@genesis.atrad.adelaide.edu.au>; from Michael Smith on Sun, Jul 20, 1997 at 12:42:09AM %2B0930 References: <QQcywq17534.199707191502@rodan.UU.NET> <199707191512.AAA14340@genesis.atrad.adelaide.edu.au>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970728234428.16657>