From owner-cvs-all  Sun May 13 22: 5:19 2001
Delivered-To: cvs-all@freebsd.org
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id B90A037B423; Sun, 13 May 2001 22:05:14 -0700 (PDT)
	(envelope-from bmah@FreeBSD.org)
Received: (from bmah@localhost)
	by freefall.freebsd.org (8.11.1/8.11.1) id f4E55ED38531;
	Sun, 13 May 2001 22:05:14 -0700 (PDT)
	(envelope-from bmah)
Message-Id: <200105140505.f4E55ED38531@freefall.freebsd.org>
From: "Bruce A. Mah" <bmah@FreeBSD.org>
Date: Sun, 13 May 2001 22:05:14 -0700 (PDT)
To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject: cvs commit: src/release/doc/en_US.ISO_8859-1/hardware/common dev.sgml
X-FreeBSD-CVS-Branch: HEAD
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

bmah        2001/05/13 22:05:14 PDT

  Modified files:
    release/doc/en_US.ISO_8859-1/hardware/common dev.sgml 
  Log:
  General corrections and fixings of the hardware list:
  
  1.  Everywhere I could figure out what driver supported a device or
  class of device, there is now a cross-reference via a &man entity.
  For cases where a driver has no manpage (and hence no &man entity),
  we now at least give the name of the driver.  For the most part,
  this was done by examining driver manpages.
  
  2.  A number of devices which are i386-only are now marked as such,
  determined by noting manpages or kernel source files in
  architecture-specific directories.
  
  3.  Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
  drivers, based on a read of the manpages.
  
  The manpages and source files in question were taken from 4-STABLE,
  (which is what was running on my off-net laptop at the time)
  but at this level of detail, I don't expect there to be any appreciable
  differences between 4-STABLE and 5-CURRENT.
  
  Revision  Changes    Path
  1.6       +194 -86   src/release/doc/en_US.ISO_8859-1/hardware/common/dev.sgml


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message