dd kits.htm

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

</h3>
<p>
<a name="nx_id_551"></a>
The kit developer prepares the distribution medium,
which in
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut17.html#figHowtoDeliverKit">Figure 12-1</a>
is a CD-ROM.
The
<tt>setld</tt>
utility installs and manages Digital UNIX kernel products (including
device drivers) kits and layered product kits.
See the
<cite>Guide to Preparing Product Kits</cite>
book for a discussion of the media supported by Digital's kitting
architecture.
</p><p>
The distribution medium, referred to as the device driver kit,
consists of a hierarchical group of the files and directories
provided by the device driver writer.
It is the responsibility of the driver writer to work with the kit
developer to determine how the files
and directories are grouped within the hierarchy.
The driver writer for EasyDriver Incorporated works with the kit developer
to create the directory structure
shown in
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut17.html#figDirStructEasyDrv">Figure 12-3</a>.
In addition, the driver writer for EasyDriver Incorporated provides to the kit
developer the files and file fragments 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>,
which become the contents of the device driver kit.
</p><p>
The kit developer performs the appropriate tasks for preparing the
device driver kit to be installed with the
<tt>setld</tt>
utility.
The kit developer should refer to the
<cite>Guide to Preparing Product Kits</cite>,
which contains information about preparing software distribution
kits that are compatible with the
<tt>setld</tt>
utility.
</p><p>
The
<cite>Guide to Preparing Product Kits</cite>
also provides an example SCP written by EasyDriver Incorporated.
</p><p>
If needed, the kit developer should also supply any installation
instructions to accompany the device driver kit.
<a name="DrvInstallPhase"></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="#PrepareDistrMed1"><img src="DD%20kits_files/PREV.GIF" alt="[Previous Section]" border="0"></a>
<a href="#SumrySysMgmtTools"><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.3&nbsp;&nbsp;&nbsp;&nbsp;Device Driver Installation Phase
</h2>
<p>
<a name="nx_id_552"></a>
Digital UNIX provides tools that customers (and
the system manager at EasyDriver Incorporated) use to
automate the installation of
device drivers.
The automated mechanism:
</p><ul>
<p></p><li>
Installs the device driver
<p></p></li><li>
Statically or dynamically configures device drivers into a kernel
<p></p></li><li>
Includes in the driver (at configuration time) site-specific tasks that are 
not currently handled by the
<tt>config</tt>
program
</li></ul><p>
</p><p>
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut17.html#figTasksDrvInstallPhase">Figure 12-5</a>
shows the tasks associated with the device driver kit installation phase as
practiced at EasyDriver Incorporated.
EasyDriver Incorporated expects its customers to follow these same
steps.
However, it is important to test the installation procedure prior to
shipping the product to customers.
You can choose to follow this model or devise an alternate one that
matches your device driver kit installation environment.
As the figure shows, the system manager at EasyDriver Incorporated
performs the following tasks to
install the kits for the
<tt>/dev/none</tt>
and
<tt>/dev/edgd</tt>
device driver products:
</p><ul>
<p></p><li>
Loads the device driver kit onto a system
<p></p></li><li>
Runs the
<tt>setld</tt>
utility
<p></p></li><li>
Chooses from the prompt that the SCP displays to statically or
dynamically configure the driver into the kernel
</li></ul><p>
</p><p>
See the
<cite>Guide to Preparing Product Kits</cite>
for information related to installing device drivers that reside on a
device driver kit.
<a name="figTasksDrvInstallPhase"></a>
</p><h3>Figure 12-5: Tasks for Device Driver Kit Installation Phase</h3>
<p><img src="DD%20kits_files/zk-1144U.gif"></p><p>
<a name="SumrySysMgmtTools"></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="#DrvInstallPhase"><img src="DD%20kits_files/PREV.GIF" alt="[Previous Section]" border="0"></a>
<img src="DD%20kits_files/BLANK.GIF" border="0">
<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.4&nbsp;&nbsp;&nbsp;&nbsp;System Management Tools
</h2>
<p>
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut17.html#tblSumrySysMgmtTools">Table 12-2</a>
summarizes the system management tools related to device driver
configuration.
See
<cite>Reference Pages Section 8 and 1m</cite>
for additional information on these system management tools.
</p><p>
<a name="tblSumrySysMgmtTools"></a>
</p><h3>
Table 12-2: Summary of System Management Tools
</h3>
<a name="nx_id_553"></a>
<table border="4" cellpadding="4">
<tbody><tr>
<td align="left" valign="top">
<strong>
Tool
</strong>
</td>
<td align="left" valign="top">
<strong>
Description
</strong>
</td>
</tr>
<tr>
<td align="left" valign="top">
<tt>doconfig</tt>
</td>
<td align="left" valign="top">
Creates
a new or modifies an existing target configuration file, copies
<tt>.product.list</tt>
to
<tt><var>NAME</var>.list</tt>,
creates
the device special file information for statically configured drivers,
and builds a new
Digital UNIX kernel.
(The
<tt>doconfig</tt>
program calls
<tt>config</tt>,
which actually performs many of the tasks mentioned.)
</td>
</tr>
<tr>
<td align="left" valign="top">
<tt>cfgmgr</tt>
</td>
<td align="left" valign="top">
Works
with
<tt>kloadsrv</tt>,
the kernel load server,
to manage device drivers that are dynamically configured into the
kernel.
</td>
</tr>
<tr>
<td align="left" valign="top">
<tt>device.mth</tt>
</td>
<td align="left" valign="top">
Works
with
driver products to produce the method file (files with
<tt>.mth</tt>
extensions).
</td>
</tr>
<tr>
<td align="left" valign="top">
<tt>kmknod</tt>
</td>
<td align="left" valign="top">
Uses
the information from the driver's
<tt>sysconfigtab</tt>
file fragment and the driver's attribute table to dynamically create
device special files at boot time for statically configured drivers.
</td>
</tr>
<tr>
<td align="left" valign="top">
<tt>kreg</tt>
</td>
<td align="left" valign="top">
Maintains
the
<tt>/sys/conf/.product.list</tt>
system file, which registers device driver products that are statically
configured into the kernel.
</td>
</tr>
<tr>
<td align="left" valign="top">
<tt>sysconfig</tt>
</td>
<td align="left" valign="top">
Configures
a driver or handles a dynamically configured device driver.
The
<tt>sysconfig</tt>
utility provides a user interface to the
<tt>cfgmgr</tt>
framework.
</td>
</tr>
<tr>
<td align="left" valign="top">
<tt>osfboot</tt>
</td>
<td align="left" valign="top">
Boots
a Digital UNIX kernel.
It contains support for boot link kernels that the
<tt>doconfig -b</tt>
command generates.
The tool also supports dynamic booting and linking a kernel that contains
foreign devices.
</td>
</tr>
<tr>
<td align="left" valign="top">
<tt>sysconfigdb</tt>
</td>
<td align="left" valign="top">
Maintains
the
<tt>sysconfigtab</tt>
database.
The driver entries in the
<tt>sysconfigtab</tt>
file fragment are appended to this database when the user
installs a kernel kit. 
</td>
</tr>
</tbody></table><p>
<a name="nx_id_554"></a>
<a name="nx_id_555"></a>
<a name="nx_id_556"></a>
<a name="nx_id_557"></a>
<a name="nx_id_558"></a>
<!--Metrics Tag -->
 <!-- Updated April 22, 2003 --> 
<!-- SiteCatalyst code version: G.0. w/dev site filtering
Copyright 1997-2003 Omniture, Inc. More info available at
http://www.omniture.com --><script language="JavaScript"><!--
/* Specify the Report Suite ID(s) to track here */
var s_account="HPHQGlobal,hphqWWesg,hphqbcs,hphqtru64"
/* Dynamic Report Suite ID Selection Config */
var s_dynamicAccountSelection = true
var s_dynamicAccountList = "hphqwwtrash=dec.com,cpqcorp.net,hpqcorp.net"
/* You may give each page an identifying user friendly name in place of urls. */
var s_pageName="Tru64-" + document.title;
if ( location.pathname.indexOf('/docs' ) != -1 )         { s_pageName = "Tru64-docs-" + document.title; }

/* Regionally assigned variables. */
var s_server=""
var s_channel=""
var s_pageType=""
var s_prop1="Tru64 UNIX"
if ( location.pathname.indexOf('/docs' ) != -1 )         { s_prop1 = "Tru64 documentation"; }
var s_prop2 = "";

   if ( location.search.indexOf('?jumpid=' ) != -1 )
        {
        s_prop2=location.search.substring((location.search.indexOf('?jumpid=' )+8),(location.search.length));
        }
			else
		{ 
		if (location.search.toUpperCase().indexOf('?' ) != -1 )        {
		s_prop2=location.search.toUpperCase().substring((location.search.toUpperCase().indexOf('?' )+1),(location.search.length));
		}
		}
var s_prop6=""
var s_prop7="w1"
var s_prop8="en-us"
var s_prop9="enterprise"
var s_prop10="w1|en-us|enterprise"
var s_prop13="HPHQGlobal,hphqWWesg,hphqbcs,hphqtru64"


/************************ ADDITIONAL FEATURES ************************
     Plugins
*/
/************************** CONFIG SECTION **************************/
/* You may add or alter any code config here.                       */
var s_charSet=""
// Netscape 4.X on Unix uses EUC-JP instead of SHIFT-JIS
if ((navigator.appName.indexOf('Netscape')>=0)&&
    (parseInt(navigator.appVersion)<=4)&&
    (navigator.userAgent.toLowerCase().indexOf('win')<0)&&
    (navigator.userAgent.toLowerCase().indexOf('mac')<0)) {
	s_charSet="EUC-JP"
}
/* E-commerce Config */
var s_eVarCFG=""

/* Link Tracking Config */
var s_trackDownloadLinks=true
var s_trackExternalLinks=true
var s_trackInlineStats=true
var s_linkDownloadFileTypes="exe,zip,wav,mp3,mov,mpg,avi,doc,pdf,xls,cgi,dot,pot,ppt,wmv,cgi,asx,tar,rpm,gz,crypt,sh"
var s_linkInternalFilters="hp,compaq,javascript:"
var s_linkLeaveQueryString=true


/********* INSERT THE DOMAIN AND PATH TO YOUR CODE BELOW ************/
//--></script><script language="JavaScript" src="DD%20kits_files/s_code.js"></script><img src="DD%20kits_files/s58435026158800.gif" name="s_i_hphqglobal" border="0" height="1" width="1">
<!-- End SiteCatalyst code version: G.0. -->

<!--End Tag -->
</p></body></html>