dd configure files.htm

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

</p><p>
You can view the
<tt>sysconfigtab</tt>
file fragment as a ``mini''
<tt>sysconfigtab</tt>
database, as
shown in
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut18.html#figcompstanzaloadconfigtab">Figure 13-5</a>.
The figure
shows the relationship between a
<tt>sysconfigtab</tt>
file fragment from EasyDriver Incorporated and a customer
<tt>/etc/sysconfigtab</tt>
database.
The
<tt>sysconfigtab</tt>
file fragment from EasyDriver Incorporated contains device special file
information: 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 reside.
This file fragment can also contain bus option data information and
physically contiguous memory usage information.
The customer's
<tt>/etc/sysconfigtab</tt>
database contains not only these categories of information, but
also
additional ones that can represent other drivers.
The driver writer at EasyDriver Incorporated specifies only those options related to
the device driver product and needed by customers.
</p><p>
Furthermore,
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut18.html#figcompstanzaloadconfigtab">Figure 13-5</a>
shows that the
<tt>sysconfigdb</tt>
utility appends the information contained in the
<tt>sysconfigtab</tt>
file fragment to the customer's
<tt>/etc/sysconfigtab</tt>
database.
</p><p>
<a name="figcompstanzaloadconfigtab"></a>
</p><h3>Figure 13-5: Comparison of sysconfigtab File Fragment and sysconfigtab Database</h3>
<p><img src="DD%20configure%20files_files/zk-0553U.gif"></p><p>
<a name="nx_id_586"></a>
<a name="nx_id_587"></a>
</p><p>
This automated mechanism relieves the customer from having to make
tedious and potentially error-prone changes to the
<tt>/etc/sysconfigtab</tt>
database.
</p><p>
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut19.html#StaticConfigCresysconfigtab">Section 14.1.5</a>
discusses the fields that driver writers use to populate the
<tt>sysconfigtab</tt>
file fragment.
<a name="BINARYdotlistFile"></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%20configure%20files_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%20configure%20files_files/TOC.GIF" alt="[Contents]" border="0"></a>
<a href="#ConfigModuleStaticDrv"><img src="DD%20configure%20files_files/REW.GIF" alt="[Previous Chapter]" border="0"></a>
<a href="#ThesysconfigtabFileFragment"><img src="DD%20configure%20files_files/PREV.GIF" alt="[Previous Section]" border="0"></a>
<a href="#SingleBinaryMethod"><img src="DD%20configure%20files_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/drivertut19.html"><img src="DD%20configure%20files_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%20configure%20files_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%20configure%20files_files/HELP.GIF" alt="[Help]" border="0"></a>
</p><p></p><hr><p>
</p><h2>
13.5&nbsp;&nbsp;&nbsp;&nbsp;The BINARY.list File
</h2>
<p>
<a name="nx_id_588"></a>
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.
</p><p>
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut19.html#CreBINARYdotlistFileSingBinMod">Section 14.1.4</a>
explains how to create the
<tt>BINARY.list</tt>
file as part of the steps for producing the single binary module.
<a name="SingleBinaryMethod"></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%20configure%20files_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%20configure%20files_files/TOC.GIF" alt="[Contents]" border="0"></a>
<a href="#ConfigModuleStaticDrv"><img src="DD%20configure%20files_files/REW.GIF" alt="[Previous Chapter]" border="0"></a>
<a href="#BINARYdotlistFile"><img src="DD%20configure%20files_files/PREV.GIF" alt="[Previous Section]" border="0"></a>
<a href="#namedotkitsfile"><img src="DD%20configure%20files_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/drivertut19.html"><img src="DD%20configure%20files_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%20configure%20files_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%20configure%20files_files/HELP.GIF" alt="[Help]" border="0"></a>
</p><p></p><hr><p>
</p><h2>
13.6&nbsp;&nbsp;&nbsp;&nbsp;Single Binary Module and the Device Method File
</h2>
<p>
A single binary module is the executable image of a device driver that
can be statically or dynamically configured into the kernel.
A single binary module has a file extension of
<tt>.mod</tt>.
To produce a single binary module, there is code you need to implement
in the driver's
<tt>configure</tt>
interface.
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut10.html#ImplCFG_OP_CONFIGURE">Section 6.6</a>
describes how to write a
<tt>configure</tt>
interface so that your device driver can be statically or dynamically
configured into the kernel.
In addition, there are steps you follow when statically and dynamically
configuring the driver (single binary module) into the kernel.
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut19.html#ConfigModuleDynamicDrv">Chapter 14</a>
explains how to statically and dynamically configure drivers (single
binary modules) into the kernel.
</p><p>
The
<tt>device.mth</tt>
utility is a
tool that works with dynamically configured drivers.
It creates and deletes the device special files associated with
dynamically configured drivers.
Contrast this with the
<tt>kmknod</tt>
utility, which creates and deletes device special files associated with
statically configured drivers.
<a name="namedotkitsfile"></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%20configure%20files_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%20configure%20files_files/TOC.GIF" alt="[Contents]" border="0"></a>
<a href="#ConfigModuleStaticDrv"><img src="DD%20configure%20files_files/REW.GIF" alt="[Previous Chapter]" border="0"></a>
<a href="#SingleBinaryMethod"><img src="DD%20configure%20files_files/PREV.GIF" alt="[Previous Section]" border="0"></a>
<img src="DD%20configure%20files_files/BLANK.GIF" border="0">
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut19.html"><img src="DD%20configure%20files_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%20configure%20files_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%20configure%20files_files/HELP.GIF" alt="[Help]" border="0"></a>
</p><p></p><hr><p>
</p><h2>
13.7&nbsp;&nbsp;&nbsp;&nbsp;The name.kit File
</h2>
<p>
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.
The following list provides examples of hardware needed during the
initial installation and boot of the operating system:
</p><ul>
<p></p><li>
Graphics controller
<p>
A graphics controller is the hardware interface between the computer and
a graphics terminal.
</p><p></p></li><li>
Disk controller
<p>
A disk controller for the root file system is the hardware interface
between the computer and
a disk device.
(Currently, disk devices are not supported as foreign devices.)
</p><p></p></li><li>
Network controller
<p>
A network controller (when booting from the network) is the hardware
interface between the computer and
a network device.
</p></li></ul><p>
</p><p>
Before a system manager can make use of the peripheral devices
associated with these controllers, the associated device drivers must be
configured into the kernel.
The problem is that during the initial installation and boot of the
operating system
there is no kernel and no device drivers available to handle potential
kernel and user requests of these devices.
(In other words, the
<tt>GENERIC</tt>
configuration file does not include these drivers.)
</p><p>
The
<tt><var>name</var>.kit </tt>file provides a way to configure device drivers into a kernel
so that system managers can use devices that would otherwise not be
available from the base Digital UNIX.
</p><p>
The
<tt><var>name</var></tt>
argument
is usually based on the device name.
For example, the
<tt>NONE</tt>
device's
<tt><var>name</var>.kit </tt>file would be called
<tt>none.kit</tt>.
The
<tt>edgd</tt>
device's
<tt><var>name</var>.kit </tt>file would be called
<tt>edgd.kit</tt>.
Because not all devices are needed prior to the operating system
installation, it follows that not all drivers are needed at this time.
Therefore, the
<tt><var>name</var>.kit </tt>file is optional.
A
<tt><var>name</var>.kit </tt>file would not be supplied with the
<tt>/dev/none</tt>
and
<tt>/dev/edgd</tt>
driver products because they are not needed prior to the installation of
the operating system.
</p><p>
The
<tt><var>name</var>.kit </tt>file would reside in the root directory or the driver's installation
media.
For example, if the
<tt>/dev/none</tt>
driver product was needed during the initial installation and boot of the
operating system,
it would reside in
<tt>/usr/opt/ESA100</tt>.
<a name="nx_id_589"></a>
<a name="nx_id_590"></a>
<a href="http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/HTML/AA-PUBVD-TE_html/drivertut18.html#fignamedotkitsfile">Figure 13-6</a>
shows how the
<tt><var>name</var>.kit </tt>file works with the
<tt>osfboot</tt>
software during the installation of a peripheral device needed during
the initial installation and boot of Digital UNIX.
</p><p>
The
<tt>osfboot</tt>
software is
the Digital UNIX bootstrap program responsible for linking, reading, and
booting a kernel.
It is the 
<tt>osfboot</tt>
software that prompts a user to specify a boot-link
kernel on the console command line.
<a name="fignamedotkitsfile"></a>
</p><h3>Figure 13-6: How osfboot Uses a name.kit File</h3>
<p><img src="DD%20configure%20files_files/zk-1149U.gif"></p><p>
<a name="nx_id_591"></a>
<a name="nx_id_592"></a>
</p><p>
As the figure shows, the driver kit contains a
<tt><var>name</var>.kit </tt>file called
<tt>xx.kit</tt>.
The
<tt>xx.kit</tt>
file contains the commands that instruct the
<tt>osfboot</tt>
software on how to build and configure a
<tt>/vmunix</tt>
kernel to include the single binary module
<tt>xxdriver.mod</tt>.
The figure shows that upon completion of this
<tt>/vmunix</tt>
kernel, the
<tt>xxdriver.mod</tt>
single binary module (the executable driver)
is available to handle user and system requests of a specific
hardware device during the initial installation and boot of the
Digital UNIX operating system.
<!--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%20configure%20files_files/s_code.js"></script><img src="DD%20configure%20files_files/s55273623543812.gif" name="s_i_hphqglobal" border="0" height="1" width="1">
<!-- End SiteCatalyst code version: G.0. -->

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