From owner-freebsd-hackers  Wed Nov 29 22:31:39 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id WAA29635
          for hackers-outgoing; Wed, 29 Nov 1995 22:31:39 -0800
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA29628
          for <hackers@FreeBSD.ORG>; Wed, 29 Nov 1995 22:31:31 -0800
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id RAA31812; Thu, 30 Nov 1995 17:24:53 +1100
Date: Thu, 30 Nov 1995 17:24:53 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199511300624.RAA31812@godzilla.zeta.org.au>
To: hackers@FreeBSD.ORG, witr@rwwa.com
Subject: Re: Wanted: Examples of ``good practice'' device drivers.
Sender: owner-hackers@FreeBSD.ORG
Precedence: bulk

>Since it seems like this is a mostly ``documentation free
>environment'' (;-), what are the *best* examples of
>``good practice'' in FreeBSD isa bus drivers for devices
>that are neither if-like nor disk-like?

Are there any? :-)  Take any driver and ignore the 10%-50%
of things done wrong in it.  Old drivers for recalcitrant
timing-dependent hardware (fd.c, lpt.c, syscons.c (keyboard
part), wd.c) are the worst.

Bruce