dd kits.htm

What is this ``device driver stuff anyway? Here s a very short introduction to the concept.

<tt>/usr/opt/ESB100</tt>
directory
<p>
This directory contains the files related to the
<tt>/dev/edgd</tt>
device driver product that EasyDriver Incorporated ships to its customers.
These files include the following product-related file fragments:
<tt>files</tt>
and
<tt>sysconfigtab</tt>.
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut18.html#Thefilesfile">Section 13.3</a>
describes in more detail the
<tt>files</tt>
file fragment.
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut18.html#ThesysconfigtabFileFragment">Section 13.4</a>
describes in more detail the
<tt>sysconfigtab</tt>
file fragment.
This directory also contains the driver header files, which have
<tt>.h</tt>
extensions; the driver source files, which have
<tt>.c</tt>
extensions;
and the single binary modules, which have
<tt>.mod</tt>
extensions.
</p><p></p></li><li>
A
<tt>/subsys</tt>
directory
<p>
This directory contains the single binary modules linked to the method
files, which have
<tt>.mth</tt>
extensions.
This directory typically contains the single binary modules for those
subsystems that need to be configured before single user time.
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut18.html#SingleBinaryMethod">Section 13.6</a>
describes in more detail the method files.
</p><p></p></li><li>
A
<tt>/var/subsys</tt>
directory
<p>
This directory contains files with
<tt>.mod</tt>
(single binary modules)
and
<tt>.mth</tt>
(device method)
extensions.
You can use this directory or the
<tt>/subsys</tt>
directory to contain the files with
<tt>.mod</tt>
and
<tt>.mth</tt>
extensions.
This directory typically contains the single binary modules for those
subsystems that can be configured after single user time.
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut18.html#SingleBinaryMethod">Section 13.6</a>
describes in more detail single binary modules and device method files.
</p><p></p></li><li>
A
<tt>/sys/BINARY</tt>
directory
<p>
This directory contains the single binary modules, which have
<tt>.mod</tt>
extensions.
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut18.html#SingleBinaryMethod">Section 13.6</a>
describes in more detail the
single binary module.
</p></li></ul><p>
<a name="SupplyInfoDrvRelFiles"></a>
</p><p></p><hr><p align="center">
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/Digital_UNIX_Bookshelf.html"><img src="DD%20kits_files/BOOKSHELF.GIF" alt="[Return to Library]" border="0"></a>
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/TOC.html"><img src="DD%20kits_files/TOC.GIF" alt="[Contents]" border="0"></a>
<a href="#DevDriverKitDelivery"><img src="DD%20kits_files/REW.GIF" alt="[Previous Chapter]" border="0"></a>
<a href="#CreateDevDrvDevelopEnv"><img src="DD%20kits_files/PREV.GIF" alt="[Previous Section]" border="0"></a>
<a href="#ProdSingleBinaryModule"><img src="DD%20kits_files/NEXT.GIF" alt="[Next Section]" border="0"></a>
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut18.html"><img src="DD%20kits_files/FF.GIF" alt="[Next Chapter]" border="0"></a>
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/INDEX.html"><img src="DD%20kits_files/INDEX.GIF" alt="[Index]" border="0"></a>
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/HELP.html"><img src="DD%20kits_files/HELP.GIF" alt="[Help]" border="0"></a>
</p><p></p><hr><p>
</p><h3>
12.1.3&nbsp;&nbsp;&nbsp;&nbsp;Creating Driver Product-Related Files and File Fragments
</h3>
<p>
<a name="nx_id_538"></a>
The driver writer creates the
<tt>.c</tt>
and
<tt>.h</tt>
files that contain the source code for the driver product.
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut5.html#SpecNamingScheme">Section 2.1.2.1</a>
provides guidelines for naming the driver product's
<tt>.c</tt>
and
<tt>.h</tt>
files.
The driver writer at EasyDriver Incorporated adheres to the guidelines presented
in
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut5.html#SpecNamingScheme">Section 2.1.2.1</a>
by naming the
<tt>.c</tt>
and
<tt>.h</tt>
files based on the product name.
Thus, the source code for the
<tt>/dev/none</tt>
driver product is in the
<tt>none.c</tt>
and
<tt>nonereg.h</tt>
files.
The source code for the
<tt>/dev/edgd</tt>
driver product is in the
<tt>edgd.c</tt>
and
<tt>edgdreg.h</tt>
files.
</p><p>
Prior to producing the single binary module,
the driver writer at EasyDriver Incorporated supplies information in the following
files:
</p><ul>
<p></p><li>
<tt>files</tt>
file fragment
<p>
The
<tt>files</tt>
file fragment is associated with
drivers delivered in binary form.
Drivers delivered in binary form can be statically or dynamically configured
into the kernel.
You specify a valid syntax for when the driver is to be loaded into the kernel,
the location of the driver source code, and whether the driver sources
are supplied.
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut18.html#Thefilesfile">Section 13.3</a>
describes how the
<tt>config</tt>
program uses the
<tt>files</tt>
file fragment
and
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut19.html#CrefilesFileFragforSingBinMod">Section 14.1.3</a>
describes the syntax for the
<tt>files</tt>
file fragment.
</p><p></p></li><li>
<tt>sysconfigtab</tt>
file fragment
<p>
The
<tt>sysconfigtab</tt>
file fragment is associated with device drivers written to conform to
the single binary module model.
A driver written in this way can be
statically or dynamically configured into the kernel.
You use valid attributes for the driver's major number requirements, the
names and minor numbers of the device special files, and the permissions and
directory name where the device special files are created.
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut18.html#ThesysconfigtabFileFragment">Section 13.4</a>
describes how the
<tt>sysconfigdb</tt>
utility uses a driver's
<tt>sysconfigtab</tt>
file fragment
and
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut19.html#StaticConfigCresysconfigtab">Section 14.1.5</a>
describes the attributes for the
<tt>sysconfigtab</tt>
file fragment.
</p><p></p></li><li>
<tt><var>NAME</var>.list </tt>file
<p>
The
<tt><var>NAME</var>.list </tt>file is associated with drivers that are statically
configured into the kernel.
This file contains such information as where the
files for
the driver product are located.
This file is not supplied on the device driver kit.
However, it is useful for a driver writer to understand the purpose of
this file because you will edit or create such a file as one of the steps
described in
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut19.html#StaticConfigEditNAMElistfile">Section 14.2.1.1</a>
and
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut19.html#StaticConfigbootlinkEditNAMElistfile">Section 14.2.2.1</a>.
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut18.html#TheNAMElistFile">Section 13.2</a>
describes the
<tt><var>NAME</var>.list </tt>file.
</p><p>
The
<tt><var>NAME</var></tt>
variable usually specifies the name of the target configuration file.
For example,
<tt>TIGRIS.list</tt>
would be the name for the file that contains information about
statically
configured device drivers for the customer system described by the
target
configuration file called
<tt>TIGRIS</tt>.
</p><p></p></li><li>
<tt>BINARY.list</tt>
file
<p>
The
<tt>BINARY.list</tt>
file contains such information as where the
files for the driver product are located.
The purpose of the file is to identify the build rules associated with
third-party device drivers built into the
<tt>BINARY</tt>
<tt>Makefile</tt>
when the driver writer invokes the
<tt>sourceconfig</tt>
utility.
This file is not supplied on the device driver kit.
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut18.html#BINARYdotlistFile">Section 13.5</a>
describes the
<tt>BINARY.list</tt>
file.
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut19.html#RunsourceconfigforSingBinMod">Section 14.1.6</a>
explains how to run the
<tt>sourceconfig</tt>
program.
</p></li></ul><p>
</p><p>
The single binary modules are the actual executables associated
with the device driver.
The syntax you specify in the
<tt>files</tt>
file fragment determines whether you want the driver to be statically or
dynamically configured into the kernel.
</p><p>
To produce the method file (files with
<tt>.mth</tt>
extensions) for the driver product, the driver writer at EasyDriver Incorporated
links the driver product to the
<tt>device.mth</tt>
file.
</p><p>
Another file that a driver writer might have to supply is the
<tt><var>name</var>.kit </tt>file.
The
<tt><var>name</var>.kit </tt>file contains the information that certain hardware needs during the initial
installation and boot of Digital UNIX.
This hardware is referred to as a foreign device.
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut18.html#namedotkitsfile">Section 13.7</a>
provides more information on the
<tt><var>name</var>.kit </tt>file.
<a name="nx_id_539"></a>
<a name="nx_id_540"></a>
<a name="nx_id_541"></a>
<a name="nx_id_542"></a>
<a name="ProdSingleBinaryModule"></a>
</p><p></p><hr><p align="center">
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/Digital_UNIX_Bookshelf.html"><img src="DD%20kits_files/BOOKSHELF.GIF" alt="[Return to Library]" border="0"></a>
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/TOC.html"><img src="DD%20kits_files/TOC.GIF" alt="[Contents]" border="0"></a>
<a href="#DevDriverKitDelivery"><img src="DD%20kits_files/REW.GIF" alt="[Previous Chapter]" border="0"></a>
<a href="#SupplyInfoDrvRelFiles"><img src="DD%20kits_files/PREV.GIF" alt="[Previous Section]" border="0"></a>
<a href="#BuildStaticDrvPrior"><img src="DD%20kits_files/NEXT.GIF" alt="[Next Section]" border="0"></a>
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut18.html"><img src="DD%20kits_files/FF.GIF" alt="[Next Chapter]" border="0"></a>
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/INDEX.html"><img src="DD%20kits_files/INDEX.GIF" alt="[Index]" border="0"></a>
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/HELP.html"><img src="DD%20kits_files/HELP.GIF" alt="[Help]" border="0"></a>
</p><p></p><hr><p>
</p><h3>
12.1.4&nbsp;&nbsp;&nbsp;&nbsp;Producing the Single Binary Module
</h3>
<p>
<a name="nx_id_543"></a>
After creating the appropriate files and file fragments, the driver
writer at EasyDriver Incorporated produces the single binary module.
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut19.html#ProduceSingleBinaryModule">Section 14.1</a>
lists the steps for producting the single binary module.
<a name="BuildStaticDrvPrior"></a>
</p><p></p><hr><p align="center">
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/Digital_UNIX_Bookshelf.html"><img src="DD%20kits_files/BOOKSHELF.GIF" alt="[Return to Library]" border="0"></a>
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/TOC.html"><img src="DD%20kits_files/TOC.GIF" alt="[Contents]" border="0"></a>
<a href="#DevDriverKitDelivery"><img src="DD%20kits_files/REW.GIF" alt="[Previous Chapter]" border="0"></a>
<a href="#ProdSingleBinaryModule"><img src="DD%20kits_files/PREV.GIF" alt="[Previous Section]" border="0"></a>
<a href="#BuildLoadDrvPrior"><img src="DD%20kits_files/NEXT.GIF" alt="[Next Section]" border="0"></a>
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut18.html"><img src="DD%20kits_files/FF.GIF" alt="[Next Chapter]" border="0"></a>
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/INDEX.html"><img src="DD%20kits_files/INDEX.GIF" alt="[Index]" border="0"></a>
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/HELP.html"><img src="DD%20kits_files/HELP.GIF" alt="[Help]" border="0"></a>
</p><p></p><hr><p>
</p><h3>
12.1.5&nbsp;&nbsp;&nbsp;&nbsp;Performing Static Configuration of the Driver
</h3>
<p>
<a name="nx_id_544"></a>
After producing the single binary module, the driver writer at EasyDriver Incorporated
statically configures it (the single binary module)
into the kernel.
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut19.html#StaticallyConfigDrvtoProdvmunix">Section 14.2.1</a>
lists the steps for statically configuring a driver (single binary
module) in a
<tt>/vmunix</tt>
kernel.
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut19.html#StaticallyConfigDrvtoProdBootLinkKern">Section 14.2.2</a>
lists the steps for statically configuring a driver (single binary
module) in a boot-link kernel.
<a name="BuildLoadDrvPrior"></a>
</p><p></p><hr><p align="center">
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/Digital_UNIX_Bookshelf.html"><img src="DD%20kits_files/BOOKSHELF.GIF" alt="[Return to Library]" border="0"></a>
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/TOC.html"><img src="DD%20kits_files/TOC.GIF" alt="[Contents]" border="0"></a>
<a href="#DevDriverKitDelivery"><img src="DD%20kits_files/REW.GIF" alt="[Previous Chapter]" border="0"></a>
<a href="#BuildStaticDrvPrior"><img src="DD%20kits_files/PREV.GIF" alt="[Previous Section]" border="0"></a>
<a href="#TestLoadandStaticDrvProd"><img src="DD%20kits_files/NEXT.GIF" alt="[Next Section]" border="0"></a>
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut18.html"><img src="DD%20kits_files/FF.GIF" alt="[Next Chapter]" border="0"></a>
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/INDEX.html"><img src="DD%20kits_files/INDEX.GIF" alt="[Index]" border="0"></a>
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/HELP.html"><img src="DD%20kits_files/HELP.GIF" alt="[Help]" border="0"></a>
</p><p></p><hr><p>
</p><h3>
12.1.6&nbsp;&nbsp;&nbsp;&nbsp;Performing Dynamic Configuration of the Driver
</h3>
<p>
<a name="nx_id_545"></a>
After producing the single binary module, the driver writer at EasyDriver Incorporated
dynamically configures it (the single binary module)
into the kernel.
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut19.html#DynamicallyConfigDrvPriorKitCre">Section 14.3</a>
lists the steps for dynamically configuring a driver (single binary
module).
<a name="TestLoadandStaticDrvProd"></a>
</p><p></p><hr><p align="center">
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/Digital_UNIX_Bookshelf.html"><img src="DD%20kits_files/BOOKSHELF.GIF" alt="[Return to Library]" border="0"></a>
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/TOC.html"><img src="DD%20kits_files/TOC.GIF" alt="[Contents]" border="0"></a>
<a href="#DevDriverKitDelivery"><img src="DD%20kits_files/REW.GIF" alt="[Previous Chapter]" border="0"></a>
<a href="#BuildLoadDrvPrior"><img src="DD%20kits_files/PREV.GIF" alt="[Previous Section]" border="0"></a>
<a href="#ProvContofDistrMed"><img src="DD%20kits_files/NEXT.GIF" alt="[Next Section]" border="0"></a>
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut18.html"><img src="DD%20kits_files/FF.GIF" alt="[Next Chapter]" border="0"></a>
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/INDEX.html"><img src="DD%20kits_files/INDEX.GIF" alt="[Index]" border="0"></a>
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/HELP.html"><img src="DD%20kits_files/HELP.GIF" alt="[Help]" border="0"></a>
</p><p></p><hr><p>
</p><h3>
12.1.7&nbsp;&nbsp;&nbsp;&nbsp;Testing the Device Driver Product
</h3>
<p>
<a name="nx_id_546"></a>
After statically and dynamically configuring the