From owner-freebsd-hackers Wed Nov 7 6:42:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web.cs.ndsu.nodak.edu (web.cs.ndsu.NoDak.edu [134.129.125.7]) by hub.freebsd.org (Postfix) with ESMTP id BE32337B417 for ; Wed, 7 Nov 2001 06:42:28 -0800 (PST) Received: (from tinguely@localhost) by web.cs.ndsu.nodak.edu (8.11.4/8.11.4) id fA7EfQp95037; Wed, 7 Nov 2001 08:41:26 -0600 (CST) (envelope-from tinguely) Date: Wed, 7 Nov 2001 08:41:26 -0600 (CST) From: mark tinguely Message-Id: <200111071441.fA7EfQp95037@web.cs.ndsu.nodak.edu> To: dragonfire820@mediaone.net, freebsd-hackers@FreeBSD.ORG Subject: Re: PCI Device Drivers In-Reply-To: <008e01c16782$fc4b3080$037d6041@gandalf> 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 put a generic 4.4 PCI device driver skeleton at: http://www.cs.ndsu.nodak.edu/~tinguely/xxx_pci.c it is more that you wanted but less fluff than a complete driver. It is a skeleton C code, not a tutorial on newbus, dma, etc issues. The ioctl() interface depends on how you interface your code with the kernel (network driver is different from a character driver). I think you are implementing a character driver, see the character driver information in /usr/share/examples/drivers/make_device_driver.sh. how to add your driver to the kernel configuration is simular to the changes made in make_device_driver.sh. yes, I know you want a complete make_pci_device_driver.sh file, but I am too lazy. --mark tinguely To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message