From owner-freebsd-hackers Mon Jun 24 13:00:54 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA26120 for hackers-outgoing; Mon, 24 Jun 1996 13:00:54 -0700 (PDT) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA26115 for ; Mon, 24 Jun 1996 13:00:49 -0700 (PDT) Received: by Sisyphos id AA11705 (5.67b/IDA-1.5 for hackers@freebsd.org); Mon, 24 Jun 1996 21:52:55 +0200 Message-Id: <199606241952.AA11705@Sisyphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Mon, 24 Jun 1996 21:52:54 +0200 In-Reply-To: A JOSEPH KOSHY "Q: Getting PCI information" (Jun 24, 14:24) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: A JOSEPH KOSHY Subject: Re: Q: Getting PCI information Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Jun 24, 14:24, A JOSEPH KOSHY wrote: } Subject: Q: Getting PCI information } } Is there any way from user-land to get the current PCI configuration } on a machine? There are several possible approaches: 1) Read the PCI configuration space registers using port accesses 2) Read the PCI configuration space registers by calling PCI BIOS functions 3) Have the PCI probe code keep all information from the boot phase in a kernel table I'm strongly in favour of 3), since the other methods can't be guaranteed to be non-disruptive. Reading a port or memory mappings base address is no problem, but reading the size of such a map is done by changing the devices current configuration may cause a operation to fail! What information do you want to obtain ? Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se