From owner-freebsd-doc Wed Aug 2 17:54:22 1995 Return-Path: doc-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id RAA08644 for doc-outgoing; Wed, 2 Aug 1995 17:54:22 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.11/8.6.6) with SMTP id RAA08338 for ; Wed, 2 Aug 1995 17:53:00 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA24117; Wed, 2 Aug 95 18:44:54 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9508030044.AA24117@cs.weber.edu> Subject: Re: device driver writers guide To: erich@jake.lodgenet.com (Eric L. Hernes) Date: Wed, 2 Aug 95 18:44:53 MDT Cc: doc@freebsd.org In-Reply-To: <199508022232.RAA13169@jake.lodgenet.com> from "Eric L. Hernes" at Aug 2, 95 05:32:15 pm X-Mailer: ELM [version 2.4dev PL52] Sender: doc-owner@freebsd.org Precedence: bulk > Is anyone interested in this type of thing. I know that the > kernel is a very sacred place (unlike linux). But there may > be people who have (possibly proprietary) drivers for other > platforms (SCO comes to mind) that would be interested in > FreeBSD if they could get they're drivers ported. > > I've been toying with the idea of writing this for a while now. > The scope would be more on how to build a driver for FreeBSD, not > unix in general. Meaning BSD specific entry points, config-ing > the kernel, device drivers as lkms, etc. > > I have more or less an outline which I intend to work from. > If there is interest, I'll help round it out for the handbook. > If not, I'll just write it up for my personal notes. I would be *very* interested in one of these existing. One of the issues in BSD is lack of documentation for internal system interfaces. VM would be a good place to start, as would vn_ for kernel level file I/O and bXXX, the block I/O interface. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.