Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   31559 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

intro(D1)							     intro(D1)

NAME
     intro.D1 - introduction to driver data

SYNOPSIS
     #include <sys/types.h>
     #include <sys/ddi.h>

DESCRIPTION
     This section describes the data definitions a developer needs to include
     in a device driver.  The system finds this information in an
     implementation-specific manner, usually tied to the way system
     configuration is handled.

USAGE
     Each driver is uniquely identified by a prefix string specified in its
     configuration file.  The name of all the driver-supplied routines and
     global variables should begin with this prefix.  This will reduce the
     chance of a symbol collision with another driver.	Any private routines
     defined by a driver that are not entry point routines should be declared
     as static.	 Also, any global variables that are private to the driver
     should be declared as static.

									Page 1

Vote for polarhome