The Instant Device Activation User's Guide will help you set up a “minidriver” to start devices quickly when the system boots. The following table may help you find information quickly in this guide:
|For information on:||Go to:|
|An overview of Instant Device Activation||Using Minidrivers for Instant Device Activation|
|How to write instant device activation code||Writing a Minidriver|
|An example of the code for a minidriver||Sample Minidriver|
|API and datatypes||API and Datatypes|
|Sample drivers for writing code for different platforms||Sample Drivers for Instant Device Activation|
|Hardware interaction within the minidriver||Hardware Interaction within the Minidriver|
Throughout this manual, we use certain typographical conventions to distinguish technical terms. In general, the conventions we use conform to those found in IEEE POSIX publications. The following table summarizes our conventions:
|Code examples||if( stream == NULL )|
|File and pathnames||/dev/null|
|Keyboard input||something you type|
|Programming data types||unsigned short|
|Programming literals||0xFF, "message string"|
We use an arrow (→) in directions for accessing menu items, like this:
You'll find the Other... menu item under.
We use notes, cautions, and warnings to highlight important messages:
|Notes point out something important or useful.|
|Cautions tell you about commands or procedures that may have unwanted or undesirable side effects.|
|Warnings tell you about commands or procedures that could be dangerous to your files, your hardware, or even yourself.|
In our documentation, we use a forward slash (/) as a delimiter in all pathnames, including those pointing to Windows files.
We also generally follow POSIX/UNIX filesystem conventions.
To obtain technical support for any QNX product, visit the Support area on our website (www.qnx.com). You'll find a wide range of support options, including community forums.
Copyright 2006–2018, QNX Software Systems Limited, a subsidiary of BlackBerry Limited. All rights reserved.