From owner-freebsd-hackers Tue May 22 17:34:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web13405.mail.yahoo.com (web13405.mail.yahoo.com [216.136.175.63]) by hub.freebsd.org (Postfix) with SMTP id 2906F37B43C for ; Tue, 22 May 2001 17:34:14 -0700 (PDT) (envelope-from sandejain@rocketmail.com) Message-ID: <20010523003414.51600.qmail@web13405.mail.yahoo.com> Received: from [207.17.136.129] by web13405.mail.yahoo.com; Tue, 22 May 2001 17:34:14 PDT Date: Tue, 22 May 2001 17:34:14 -0700 (PDT) From: SJ Subject: Device driver questions To: freebsd-questions@freebsd.org Cc: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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 Hi all, I am new to writing device drivers...so please excuse my ignorance. I have a couple of questions regarding that: 1. "ioconf.c" contains struct config_resource and config_device definitions for declarations in "config" file. But I noticed that for some devices e.g. device atadisk device atapicd ... the corresponding lines in ioconf.c are missing?? 2. Whats the use of device_ops structure and what does "ops" stand for? 3. File naming question: whats the reasoning behind having "bus.h" and "bus_private.h"....whats the significance of "private" here. 4. concept behind having devclasses...I know that devclasses for a particular bus holds devices and device drivers for that bus. But then whats the need for defining a devclass for each driver we write ? 5. Any poniters to literature which explains the design philosophy and code specific help for device drivers in freebsd - I am referring to files kern/subr_bus.c, bus.h, bus_private.h, isa/* etc. thanks for your help, SJ __________________________________________________ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message