With our modular architecture, convenient driver framework, and simple testing environment, adding drivers to your QNX-based system has never been easier. And, since our driver framework handles default behaviors common to most devices, you can concentrate on low-level details specific to your device. Test and debug with ease All driver debugging is done with the same source-level tools used for debugging applications. No need for specialized kernel debuggers or kernel developers. Once you've made changes to driver code, you can test and debug by simply recompiling and restarting the driver.
Drivers are a key component of any system - and a common source of system failure.
Drivers can even be added or removed on the fly, without downtime. Each kit provides documentation of the infrastructure for the various driver types, documentation of the API and data structures, and source for one or more sample drivers. A sixth kit, the Audio DDK, will be available in Q2 2001. Writing an input driver means starting with your own input module. Creating a network driver for the QNX realtime platform begins with an understanding of io-net , the network manager.