OS2DD102 - OS/2 1.x Device Drivers: Difference between revisions
Jump to navigation
Jump to search
Created page with "OS/2 1.x Device Drivers - Course OS2DD102 Enabling hardware support for multiple OS/2 applications Objective ====================== To expedite Independent Hardware Vend..." |
No edit summary |
||
| Line 1: | Line 1: | ||
OS/2 1.x Device Drivers - Course OS2DD102 | OS/2 1.x Device Drivers - Course OS2DD102 | ||
Enabling hardware support for multiple OS/2 applications | |||
==Objective== | |||
To expedite Independent Hardware Vendors (IHV) support of OS/2 2.x by writing Physical Device Drivers (PDD) to support PC hardware. This will permit the hardware to be used by multiple OS/2 applications. | |||
This class will identify the protocol on how to communicate with the kernel using the DevHlp interface. Installation and debug techniques will also be covered. | |||
==Target audience== | |||
IBM or IHV programmers who code device drivers for... | IBM or IHV programmers who code device drivers for... | ||
a. I/O interfaces (i.e. Serial, parallel, etc) | a. I/O interfaces (i.e. Serial, parallel, etc) | ||
b. Bus type: ISA, EISA, VLB, or MCA. | b. Bus type: ISA, EISA, VLB, or MCA. | ||
Attendee prerequisites | ==Attendee prerequisites== | ||
a. Programming expertise: C and/or MASM | a. Programming expertise: C and/or MASM | ||
b. Have written other device drivers for IHV hardware | b. Have written other device drivers for IHV hardware | ||
| Line 27: | Line 22: | ||
Course length: 5 days | Course length: 5 days | ||
Outline | ==Outline== | ||
OS/2 Structure | OS/2 Structure | ||
Device Driver types | Device Driver types | ||
Revision as of 14:01, 28 June 2018
OS/2 1.x Device Drivers - Course OS2DD102
Enabling hardware support for multiple OS/2 applications
Objective
To expedite Independent Hardware Vendors (IHV) support of OS/2 2.x by writing Physical Device Drivers (PDD) to support PC hardware. This will permit the hardware to be used by multiple OS/2 applications.
This class will identify the protocol on how to communicate with the kernel using the DevHlp interface. Installation and debug techniques will also be covered.
Target audience
IBM or IHV programmers who code device drivers for...
a. I/O interfaces (i.e. Serial, parallel, etc) b. Bus type: ISA, EISA, VLB, or MCA.
Attendee prerequisites
a. Programming expertise: C and/or MASM
b. Have written other device drivers for IHV hardware
DOS, ROM BIOS code, utilities
c. Intimate knowledge of IHV hardware & programming protocol
d. Purchased development software (OS/2 2.1, DDK, MSC 6.0, MASM 5.1)
Course length: 5 days
Outline
OS/2 Structure Device Driver types Device Driver model Character vs Block Modes, Times Init, Kernel, Interrupt Timer, User Init sequence Config.sys processing Utilities, debuggers Compiler, Assembler, Linker usage Symbol Generation (MAPSYM) Kernel Debugger (KDB) Application & System Debug Tool (ASDT) Processor support Semaphores Address spaces Memory Management DOS Box support ROMCritSect Monitor implementations Lab: Developing OS/2 1.x Device Driver