From owner-cvs-share  Sat Feb  1 23:19:33 1997
Return-Path: <owner-cvs-share>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id XAA05546
          for cvs-share-outgoing; Sat, 1 Feb 1997 23:19:33 -0800 (PST)
Received: (from julian@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id XAA05537;
          Sat, 1 Feb 1997 23:19:31 -0800 (PST)
Date: Sat, 1 Feb 1997 23:19:31 -0800 (PST)
From: Julian Elischer <julian>
Message-Id: <199702020719.XAA05537@freefall.freebsd.org>
To: CVS-committers, cvs-all, cvs-share
Subject: cvs commit:  src/share/examples/drivers make_device_driver.sh make_pseudo_driver.sh
Sender: owner-cvs-share@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

julian      97/02/01 23:19:31

  Added:       share/examples/drivers  make_device_driver.sh
                        make_pseudo_driver.sh
  Log:
  These two shell scripts will
  create a skeleton device driver.
  one for a real device and the other for a pseudo device.
  they each take one argument which is the name (prefix) for the driver.
  
  they add the new file to the /sys tree and add appropriate config files
  etc for a build.
  
  hopefully others will build on this so that we get
  1/ these drivers improved and the shell scripts
  improved in how/where that hook the new code in.
  2/ similar tools for providing skeletons for other
  modules (I'm tempted to do a VFS filesystem skeleton :)
  
  please take a look and fix anything that maybe should be added.
  they compile and link fine,
  but I think I wouldn't trust them, as faar as RUNNING yet :)
  (well they really wouldn't do very much being skeletons..
  
  we need to add PCI  and EISA skeletons as well
  followed by a SCSI driver skeleton.