Copy stable/10@r272459 to releng/10.1 as part of
the 10.1-RELEASE process.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

Also use dev2unit() in the pseudo-driver example script.

Because I'm planning on MFC'ing my last change to this file, make sure
we use dev2unit() here as well.

Make the make_pseudo_driver.sh shellscript work again.

It seems this script was broken because of the SYSINIT changes and a
rather awkward variable initialisation. For some reason the
make_device_driver.sh script is also broken, related to BUS_SETUP_INTR.
I have no experience with FreeBSD's interrupt handling, so I hope
someone else is willing to take a look at that shell script.

PR: misc/126435
MFC after: 1 month

Fix path for source file in files.FOO.

- Added ability to provide (optional) path to the kernel sources
- Added check of dirs used by example generator
- Fixed path for ${s}/conf/files.FOO and include it via files
directive from config file
- Changed kernel configuration example with the driver: it is
not produced by copying Generic but by including it
- KDB is added to config (for DDB)
- Added module building instead and fixed kernel building

Reviewed by: julian@

Added copyright templete
Fixed compilation

Reviewed by: julian@

Device counts are gone.

__FUNCTION__ -> __func__

Modernise and tidy up.

- Modify to make the generated device driver code work with current.
- Use M_ZERO instead of another call to bzero().

Inspired by: misc/31905

pseudo-device -> device in kernel config lines. Removed whitespace at EOL.
Reviewed by: joerg, dd

$Id$ -> $FreeBSD$

more $d -> %d fixes

FIxed a bogus comment.

The example drivers should use 'poll' now that it has replaced select.

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.