|
|
Line 1: |
Line 1: |
| Course OS2DD101 - OS/2 PDD
| |
| Serial, Parallel Port Device Drivers
| |
|
| |
|
| '''Objective'''
| |
|
| |
| This five day workshop will enable programmers to write OS/2 Physical Device Drivers (PDD). A PDD enables I/O ports (serial, parallel, A/D, etc) to be shared by multiple OS/2 applications.
| |
|
| |
| This workshop describes how the PDD communicates with the OS/2 kernel using the DevHlp interface. Installation and debug techniques will also be covered. The Developer Connection Device Driver Kit for OS/2 (Devcon-DDK) will be used extensively in order to build and test the PDD.
| |
|
| |
| '''Target Audience'''
| |
|
| |
| IBM or OEM programmers who code device drivers for PC hardware, such as serial, parallel, SCSI, or proprietary interfaces. This workshop is a recommended prerequisite for all other device driver workshops, except PM Printer and Video workshops.
| |
|
| |
| '''Attendee prerequisites'''
| |
|
| |
| o Programming expertise: C and/or MASM
| |
|
| |
| o Have written device drivers/utilities for OEM hardware (DOS device drivers, ROM BIOS, test utilities)
| |
|
| |
| o Must be a licensee of the following software
| |
|
| |
| - OS/2 2.x, OS/2 Warp
| |
| - Developers Connection Device Driver Kit
| |
| - MSC 6.0
| |
|
| |
| '''Outline'''
| |
|
| |
| o OS/2 Structure
| |
| o Device Driver types
| |
| o Physical Device Driver
| |
| - Character vs Block
| |
| o Modes, Times
| |
| - Init, Kernel, Interrupt, Timer
| |
| o Init sequence
| |
| - Config.sys processing
| |
| o Utilities, debuggers
| |
| - Compiler, Assembler, Linker usage
| |
| - Symbol Generation (MAPSYM)
| |
| - Kernel Debugger (KDB)
| |
| o Processor support
| |
| o Semaphores
| |
| o PDD Address spaces
| |
| - Memory Management
| |
| o Monitor implementations
| |
|
| |
| o VDD Communication
| |
|
| |
| o Lab: Develop OEM Physical Device Driver
| |