From owner-freebsd-hackers Thu Aug 20 08:12:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25060 for freebsd-hackers-outgoing; Thu, 20 Aug 1998 08:12:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from snitterly.nanoteq.co.za (snitterly.nanoteq.co.za [196.37.90.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA24989 for ; Thu, 20 Aug 1998 08:11:54 -0700 (PDT) (envelope-from edebruin@iname.com) Received: from iname.com (mossie.nanoteq.co.za [196.37.91.6]) by snitterly.nanoteq.co.za (8.8.3/8.8.3) with ESMTP id RAA14653 for ; Thu, 20 Aug 1998 17:15:58 GMT Message-ID: <35DC5860.1B07E107@iname.com> Date: Thu, 20 Aug 1998 17:09:52 +0000 From: eT X-Mailer: Mozilla 4.06 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: attaching devices Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greets, I have a few questions regarding writing a PCI device driver with I/O address access to the PCI chip as opposed to memory mapped access: 1. what does the kernel do/want when it attaches the driver? 2. which pci_* functions are relevant for I/O access to PCI chip? 3. what does pci_attach() do? 4. many of the examples in /usr/src/sys/pci have the xx_softc structure. is this thee structure for accessing and controlling the PCI chip and whatever other chips are on the device? Regards eT -- Etienne de Bruin E-mail: edebruin@iname.com OR edebruin@netscape.net WWW: http://listen.to/eT Forcefully advancing the Kingdom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message