dd kits.htm

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

<tt>/dev/none</tt>
device driver into the
kernel, the driver writer at EasyDriver Incorporated
tests the driver by using utilities that run on
Digital UNIX.
If the
<tt>/dev/none</tt>
driver does not work with these utilities, then the driver writer at
EasyDriver Incorporated rewrites the driver and goes through the steps for
producing the single binary module and statically and dynamically
configuring the driver into the kernel.
This sequence is repeated until the driver works with the appropriate
utilities.
<a name="ProvContofDistrMed"></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="#TestLoadandStaticDrvProd"><img src="DD%20kits_files/PREV.GIF" alt="[Previous Section]" border="0"></a>
<a href="#DrvKitDevelopPhase"><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.8&nbsp;&nbsp;&nbsp;&nbsp;Providing Driver Product-Related Files and File Fragments to the Kit Developer
</h3>
<p>
<a name="nx_id_547"></a>
The driver writer provides the files and file fragments discussed in
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut17.html#SupplyInfoDrvRelFiles">Section 12.1.3</a>
and listed in
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut17.html#tblItemsNeededbyKit">Table 12-1</a>
to the kit developer.
These files and file fragments become the contents of the device driver kit
and contain information
necessary for system managers (customers) to statically or dynamically
configure the driver product into their kernels.
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut17.html#tblItemsNeededbyKit">Table 12-1</a>
summarizes the files and file fragments the driver writer needs to provide
to the kit developer.
The table has the following columns:
</p><ul>
<p></p><li>
File
<p>
Contains the name of the file or file fragment.
</p><p></p></li><li>
Statically configured drivers (source)
<p>
A ``Yes'' appears in this column if the file or file fragment should be
supplied with statically configured drivers supplied as source.
Otherwise, a ``No'' appears.
</p><p></p></li><li>
Statically configured drivers (binary)
<p>
A ``Yes'' appears in this column if the file or file fragment should be
supplied with statically configured drivers supplied as binary.
Otherwise, a ``No'' appears.
</p><p></p></li><li>
Dynamically configured drivers (binary)
<p>
A ``Yes'' appears in this column if the file or file fragment should be
supplied with dynamically configured drivers supplied as binary.
Otherwise, a ``No'' appears.
</p></li></ul><p>
</p><blockquote><p align="center"><font size="+1"><strong>Note</strong></font></p><p>
The device driver kit delivery process does not currently
support shipping drivers as source and dynamically configuring them at the
customer site.
Therefore, the table omits a column for dynamically configured drivers (source).
</p><p>
The
<tt><var>name</var>.kit </tt>file is needed only if the driver must be available during the initial
installation and boot of Digital UNIX.
In other words, only device drivers that control foreign devices need
this file. 
A foreign device is hardware used during the initial installation and
boot of Digital UNIX.
</p><p>
A subset control program (SCP) is part of the device driver kit.
However, the kit developer supplies the SCP.
See the
<cite>Guide to Preparing Product Kits</cite>
for information on how to write an SCP.
</p><p>
Although
<tt><var>name</var>_data.c </tt>files are still supported, Digital recommends that you not use them in this
and future releases.
</p></blockquote><p>
</p><p>
<a name="tblItemsNeededbyKit"></a>
</p><h3>
Table 12-1: Contents of Device Driver Kit
</h3>
<a name="nx_id_548"></a>
<table border="4" cellpadding="4">
<tbody><tr>
<td align="left" valign="top">
<strong>
File
</strong>
</td>
<td align="left" valign="top">
<strong>
Statically Configured Drivers (Source)
</strong>
</td>
<td align="left" valign="top">
<strong>
Statically Configured Drivers (Binary)
</strong>
</td>
<td align="left" valign="top">
<strong>
Dynamically Configured Drivers (Binary)
</strong>
</td>
</tr>
<tr>
<td align="left" valign="top">
<tt>files</tt>
file fragment
</td>
<td align="left" valign="top">
Yes
</td>
<td align="left" valign="top">
Yes
</td>
<td align="left" valign="top">
No
</td>
</tr>
<tr>
<td align="left" valign="top">
<tt>sysconfigtab</tt>
file fragment
</td>
<td align="left" valign="top">
Yes
</td>
<td align="left" valign="top">
Yes
</td>
<td align="left" valign="top">
Yes
</td>
</tr>
<tr>
<td align="left" valign="top">
Driver headers
(files with
<tt>.h</tt>
extensions)
</td>
<td align="left" valign="top">
Yes
</td>
<td align="left" valign="top">
No*
</td>
<td align="left" valign="top">
No
</td>
</tr>
<tr>
<td align="left" valign="top">
Driver sources
(files with
<tt>.c</tt>
extensions)
</td>
<td align="left" valign="top">
Yes
</td>
<td align="left" valign="top">
No
</td>
<td align="left" valign="top">
No
</td>
</tr>
<tr>
<td align="left" valign="top">
Single binary modules
(files with
<tt>.mod</tt>
extensions)
</td>
<td align="left" valign="top">
Yes
</td>
<td align="left" valign="top">
Yes
</td>
<td align="left" valign="top">
Yes
</td>
</tr>
<tr>
<td align="left" valign="top">
Device method
(files with
<tt>.mth</tt>
extensions)
</td>
<td align="left" valign="top">
No
</td>
<td align="left" valign="top">
No
</td>
<td align="left" valign="top">
Yes
</td>
</tr>
<tr>
<td align="left" valign="top">
<tt><var>name</var>.kit </tt>+
</td>
<td align="left" valign="top">
No
</td>
<td align="left" valign="top">
Yes
</td>
<td align="left" valign="top">
No
</td>
</tr>
<tr>
<td align="left" valign="top">
Subset control program
</td>
<td align="left" valign="top">
Yes
</td>
<td align="left" valign="top">
Yes
</td>
<td align="left" valign="top">
Yes
</td>
</tr>
<!-- </table> -->
<!-- <table> -->
<tr>
<td align="left" valign="top">
* But Yes if needed by data.c
</td>
<td align="left" valign="top">&nbsp;
</td>
<td align="left" valign="top">&nbsp;
</td>
<td align="left" valign="top">&nbsp;
</td>
</tr>
<!-- </table> -->
<!-- <table> -->
<tr>
<td align="left" valign="top">
+ Needed only by drivers that control foreign devices
</td>
<td align="left" valign="top">&nbsp;
</td>
<td align="left" valign="top">&nbsp;
</td>
<td align="left" valign="top">&nbsp;
</td>
</tr>
</tbody></table><p>
<a name="DrvKitDevelopPhase"></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="#ProvContofDistrMed"><img src="DD%20kits_files/PREV.GIF" alt="[Previous Section]" border="0"></a>
<a href="#WritetheSCP"><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><h2>
12.2&nbsp;&nbsp;&nbsp;&nbsp;Device Driver Kit Development Phase
</h2>
<p>
<a name="nx_id_549"></a>
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut17.html#figTasksDrvKitDevelopPhase">Figure 12-4</a>
shows the tasks associated with the device driver kit development phase as
practiced at EasyDriver Incorporated.
As the figure shows,
the kit developer at EasyDriver Incorporated performs the following tasks
during the device driver kit development phase:
</p><ul>
<p></p><li>
Writes the subset control program (SCP)
<p></p></li><li>
Prepares the device driver kit
</li></ul><p>
You can choose to follow this model or devise an alternate one that
matches your device driver kit development environment.
The sections following
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut17.html#figTasksDrvKitDevelopPhase">Figure 12-4</a>
provide an overview of the tasks associated with the device driver
kit development phase.
<a name="figTasksDrvKitDevelopPhase"></a>
</p><h3>Figure 12-4: Tasks for Device Driver Kit Development Phase</h3>
<p><img src="DD%20kits_files/zk-1143U.gif"></p><p>
<a name="WritetheSCP"></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="#DrvKitDevelopPhase"><img src="DD%20kits_files/PREV.GIF" alt="[Previous Section]" border="0"></a>
<a href="#PrepareDistrMed1"><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.2.1&nbsp;&nbsp;&nbsp;&nbsp;Writing the SCP
</h3>
<p>
<a name="nx_id_550"></a>
As part of the kit development phase, the kit developer at
EasyDriver Incorporated writes a subset control program (SCP) similar to the
example provided in
<cite>Guide to Preparing Product Kits</cite>.
Your kit developers can use the example in
<cite>Guide to Preparing Product Kits</cite>
as the basis for writing their
own SCPs.
<a name="PrepareDistrMed1"></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="#WritetheSCP"><img src="DD%20kits_files/PREV.GIF" alt="[Previous Section]" border="0"></a>
<a href="#DrvInstallPhase"><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.2.2&nbsp;&nbsp;&nbsp;&nbsp;Preparing the Device Driver Kit