🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.os.os2.programmer
Article #2217

Re: OS/2 2.0 Physical Device Drivers.

#2217
From: Bob Pebly
Date: Thu, 01 Oct 1992 11:37
19 lines
1319 bytes
In <1992Oct1.004911.3881@netcom.com> Leonid Crossman writes:
>:
>Could someone experienced in OS/2 drivers developing tell me the simpliest
>way for the physical device driver to talk to another PDD?
>It is obvious in init mode when you can use API calls but I wonder about
>the kernel and interrupt mode.
>   Thanks in advance, Leonid

The mechanism for physical device drivers to directly call each other
during kernel and interrupt mode is called IDC (Inter-Device Driver
Communication).  The driver provides an IDC entry point and sets a bit
in its header to indicate that it supports IDC.  Other drivers obtain
the entry point by calling DevHelp_AttachDD with the name of the driver.
The IDC mechanism is documented in the Physical Device Driver Reference
in the OS/2 2.0 Technical Library.

Bob Pebly

Disclaimer: This posting represents the poster's view, not those of IBM.
Technical Details
Message-ID: <19921001.045257.288@almaden.ibm.com>
Path: arc1-ca.pugleaf.net!sparky!uunet!vnet.ibm.com
References: <1992Oct1.004911.3881@netcom.com>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!vnet.ibm.com
From: pebly@vnet.ibm.com (Bob Pebly)
Message-ID: <19921001.045257.288@almaden.ibm.com>
Date: Thu, 1 Oct 92 07:37:57 EDT
Newsgroups: comp.os.os2.programmer
Subject: Re: OS/2 2.0 Physical Device Drivers.
Reply-To: pebly@vnet.ibm.com
Organization: IBM Industrial Sector Division, Boca Raton, FL
News-Software: UReply 3.0
References: <1992Oct1.004911.3881@netcom.com>
Lines: 20