D Files Related to the Device Driver Kits Delivery Process

Table D-1 summarizes the files and file fragments related to the device driver kits delivery process and provides a summary of how the driver writer populates these files with the necessary information. These files are also needed to statically or dynamically configure device drivers into the kernel prior to kit creation. Chapter 14 describes the actual syntaxes and mechanisms you use to populate these files and file fragments.

Table D-1: Contents of Files Related to Static and Dynamic Configuration

File	Information/Mechanisms
`NAME.list` file	The `NAME.list` 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. This file is not applicable to drivers that are dynamically configured into the kernel.
`BINARY.list`	The `BINARY.list` 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 `BINARY` `Makefile` when the driver writer invokes the `sourceconfig` utility. This file is not supplied on the device driver kit.
`files` file fragment	The `files` 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.
`sysconfigtab` file fragment	The `sysconfigtab` 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.
driver source files, driver header files, and single binary modules	The driver writer supplies the `.c` (optional), `.h` (optional), and `.mod` (for statically or dynamically configured drivers) files associated with the driver product.
Subset control program (SCP)	The kit developer writes an SCP that installs and manages the files and file fragments supplied to customers.