OS2DD304 - Pointer Device Drivers: Difference between revisions

From OS2World.Com Wiki
Jump to navigation Jump to search
No edit summary
Jugbogdan (talk | contribs)
mNo edit summary
 
Line 1: Line 1:
This workshop enables programmers to write pointer device drivers to enable pointing devices, such as mice, trackballs, touch screens, light pens, tracking pens, and Braille pads, to be used with OS/2 2.x by OS/2, DOS, and Windows (TM) applications. This class describes how to communicate with other device drivers and the kernel using the DevHlp interface. Installation and debug techniques are also covered. The OS/2 Device Driver Kit (DDK) is used extensively to build and test the pointer device driver.
This workshop enables programmers to write pointer device drivers to enable pointing devices, such as mice, trackballs, touch screens, light pens, tracking pens, and Braille pads, to be used with OS/2 2.x by OS/2, DOS, and Windows™ applications. This class describes how to communicate with other device drivers and the kernel using the DevHlp interface. Installation and debug techniques are also covered. The OS/2 Device Driver Kit (DDK) is used extensively to build and test the pointer device driver.
   
   
The target audience is IBM or IHV programmers who code device drivers for pointer devices such as mice, pens, etc.
The target audience is IBM or IHV programmers who code device drivers for pointer devices such as mice, pens, etc.
Line 10: Line 10:
** Elements: physical, virtual
** Elements: physical, virtual
** Device-dependent code versus device-independent code
** Device-dependent code versus device-independent code
** Swappable / resident
** Swappable/resident
** Physical versus logical
** Physical versus logical
** FG / BG / detached request processing
** FG / BG / detached request processing
Line 26: Line 26:
==Prerequisites==
==Prerequisites==
* Programming expertise in C and Macro Assembler
* Programming expertise in C and Macro Assembler
* Have written device drivers / utilities for OEM hardware (DOS device drivers, ROM BIOS, test utilities)
* Have written device drivers/utilities for OEM hardware (DOS device drivers, ROM BIOS, test utilities)
* Have purchased development software (OS/2 2.1, OS/2 DDK, Microsoft C Compiler 6.0)
* Have purchased development software (OS/2 2.1, OS/2 DDK, Microsoft C Compiler 6.0)
* Knowledge of OS/2 2.x PDDs (attendance at workshop OS2DD101 recommended)
* Knowledge of OS/2 2.x PDDs (attendance at workshop OS2DD101 recommended)

Latest revision as of 07:48, 21 October 2024

This workshop enables programmers to write pointer device drivers to enable pointing devices, such as mice, trackballs, touch screens, light pens, tracking pens, and Braille pads, to be used with OS/2 2.x by OS/2, DOS, and Windows™ applications. This class describes how to communicate with other device drivers and the kernel using the DevHlp interface. Installation and debug techniques are also covered. The OS/2 Device Driver Kit (DDK) is used extensively to build and test the pointer device driver.

The target audience is IBM or IHV programmers who code device drivers for pointer devices such as mice, pens, etc.

Outline

  • OS/2 structure
  • Device driver types
  • Pointer device driver model
    • Character
    • Elements: physical, virtual
    • Device-dependent code versus device-independent code
    • Swappable/resident
    • Physical versus logical
    • FG / BG / detached request processing
  • Required functions
    • Collision check
    • Pointer positioning logic
    • Queue processing
  • IOCtl support
  • Request handler structure
  • Error handling
  • IDC to other modules
  • Monitor processing
  • Lab: Developing OEM pointer device drivers

Prerequisites

  • Programming expertise in C and Macro Assembler
  • Have written device drivers/utilities for OEM hardware (DOS device drivers, ROM BIOS, test utilities)
  • Have purchased development software (OS/2 2.1, OS/2 DDK, Microsoft C Compiler 6.0)
  • Knowledge of OS/2 2.x PDDs (attendance at workshop OS2DD101 recommended)

Download

  • N/A