README revision 22197 
1Sat Feb  1 23:30:12 PST 1997 <Julian Elischer>
2
3These files are shell scripts.
4
5They will, when run, create an example skeleton driver
6for you. You can use this driver as a starting point for
7writing drivers for your own devices. They have all the hooks needed
8for intiialisation, probing, attaching, as well as DEVFS
9node creation. They also create sample ioctl commands and a sample
10ioctl definition .h file in /sys/sys. In othe rwords they are fully
11functional in a 'skeleton' sort of a way. They support multiple devices
12so that you may have several of your 'foobar' devices probed and atached
13at once.
14
15I expect that these scripts will improve with time.
16
17At present these scripts also link the newly created driver into
18the kernel sources in /sys. Possibly a better way would be
19to make them interactive. (and ask what kernel tree to use as well as
20a name for the driver.).
21
22There are presently two scripts.
23One for making a real device driver for ISA devices, and 
24one for making a device driver for pseudo devices (e.g. /dev/null).
25Hopefully they will be joined by similar scripts for creating
26skeletons for PCI and EISA devices as well.
27
28Give them a single argument: the name of the driver.
29They will use this given name in many places within the driver,
30both in lower and upper case form.  (conforming to normal usage).
31
32The skeleton driver should already link with the kernel 
33and in fact the shell script will compile a kernel with the new 
34drive linked in..  The new kernel should still be 
35runnable and the new driver should be
36fully callable (once you get your device to probe).
37You should simply edit the driver and continue to use
38'make' (as done in the script) until your driver does what you want.
39
40The driver will end up in /sys/i386/isa for the device driver script,
41and in /sys/dev for the pseudo driver script.
42
43
44
45
46