Revision as of 16:39, 17 June 2012

By Tim Snape

This article contains a selection of frequently asked questions and is intended to be used by anyone who is writing or planning to write OS/2 device drivers.

Support Categories

Situations when it is (un)necessary to write an OS/2 device driver

Is a driver necessary to use IRQs

Question I have a requirement to intercept hardware interrupts from an adapter. Do I need to write a device driver.

Answer Yes, a device driver is absolutely the only way to interact with hardware generated interrupts.

Is a driver necessary to access I/O ports

Is a driver necessary to access memory on an adapter card

Accessing Video Ram

Application Issues

compiling and building your OS/2 device driver

Initialising the driver for the first time

Start of operations

Using Request Packets

A collection of commonly asked questions about the IOCTL interface

Defining and Using Semaphores

How the stack works

Using DMA

Defining and Using memory

32 Bit issues compiling/linking/running

How time works

Using interrupts

Shutting down OS/2 gracefully

What differences are there between the versions of OS/2

Debugging tips, tricks and treats

A collection of tools & information on tools for device driver authors

General useful information and support

Other sources of information and support

Download

@@ Line 1: / Line 1: @@
+By [[Tim Snape]]
 This article contains a selection of frequently asked questions and is intended to be used by anyone who is writing or planning to write OS/2 device drivers.
@@ Line 7: / Line 9: @@
 ===Is a driver necessary to use IRQs===
+'''Question'''
+I have a requirement to intercept hardware interrupts from an adapter. Do I need to write a device driver.
+'''Answer'''
+Yes, a device driver is absolutely the only way to interact with hardware generated interrupts.
 ===Is a driver necessary to access I/O ports===
 ===Is a driver necessary to access memory on an adapter card===