From owner-freebsd-hackers Sat Aug 25 7:26:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from slc.robotech.net (www.cyber-wire.com [209.119.76.3]) by hub.freebsd.org (Postfix) with ESMTP id 813FE37B408 for ; Sat, 25 Aug 2001 07:26:07 -0700 (PDT) (envelope-from johnson@faradayco.com) Received: from faradayco.com [216.4.209.14] by slc.robotech.net with ESMTP (SMTPD32-5.05) id A4E56A680098; Sat, 25 Aug 2001 08:23:33 -0600 Message-ID: <3B87B6C3.E5DDBB12@faradayco.com> Date: Sat, 25 Aug 2001 08:31:31 -0600 From: djohnson X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: PCI Enumeration Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I am working on an embedded FreeBSD (4.2) device with proprietary PCI devices on the bus.. I don't have a FreeBSD background and am having trouble finding the right underlying code to hook into, for what we need to do. Basically two things need to happen: 1) Need to be able to enumerate the PCI bus and printf as much information about bus devices as possible (sort of like what pcisupport.c does). Preferrably this would do the enumeration without going to BIOS for it, but BIOS calls may be acceptable. So, which of the several (sort of undocumented) underlying pci code modules are preferred, for: (a) getting the raw data, and (b) for converting it to human form? 2) I also need to be able to perform basic write-read tests on devices on the bus, both in memory space and I/O space. Upsetting the hardware during these tests is acceptable. Any pointers would be appreciated. Doryn Johnson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message