From owner-freebsd-hackers Tue Oct 10 21:40:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106]) by hub.freebsd.org (Postfix) with ESMTP id D8BE337B503 for ; Tue, 10 Oct 2000 21:40:35 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9B4gUh04451; Tue, 10 Oct 2000 21:42:36 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010110442.e9B4gUh04451@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: cmoran@emergent.com.au Cc: freebsd-hackers@freebsd.org Subject: Re: Writing Drivers In-reply-to: Your message of "Mon, 09 Oct 2000 20:25:39 +1100." <000001c031d2$e43ed4b0$0a00a8c0@gt3> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Oct 2000 21:42:30 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is probably a dumb question, but here goes. > > I want to write a driver for some custom hardware we use here. I've done > this Windows NT and (earlier) MS-DOS, so the concept doesn't scare me. > > What I need is a starting point. Besides trawling through the code, are > there any standard references or texts I could check out? Not really. The code is your best reference, although you should be sure to ask around here for help/advice, since there are plenty of people that can help you. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message