Tightly Coupled drivers - Need help!

NTDEV
1

Hi,

I have a driver which talks with two other drivers to send and retieve
information. The other two drivers speak with actual hardware. The
communication occurs frequently.

I read in previous postings that we can do this by exposing pointers
to driver functions to the calling driver. It would be helpful if
anyone can explain how this can be done.

I am a newbie to the device driver development and it would be nice if
anyone could point to some sample code to do this.

Thanks.

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

2

Look at the Toaster example.

However, if you think of a driver as nothing more than a DLL with SYS
extension, and linked with the kernel libraries, it should be clearer.

Gary G. Little
Broadband Storage, Inc.
xxxxx@broadstor.com
xxxxx@inland.net

-----Original Message-----
From: Senthil Kumar [mailto:xxxxx@synthesysresearch.com]
Sent: Wednesday, January 30, 2002 4:54 PM
To: NT Developers Interest List
Subject: [ntdev] Tightly Coupled drivers - Need help!

Hi,

I have a driver which talks with two other drivers to send and retieve
information. The other two drivers speak with actual hardware. The
communication occurs frequently.

I read in previous postings that we can do this by exposing pointers
to driver functions to the calling driver. It would be helpful if
anyone can explain how this can be done.

I am a newbie to the device driver development and it would be nice if
anyone could point to some sample code to do this.

Thanks.

You are currently subscribed to ntdev as: xxxxx@broadstor.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

3

Take a look at IRP_MN_QUERY_INTERFACE ioctl.
Probaly it is what you need. See Toaster example
for implementation details.

----- Original Message -----
From: “Senthil Kumar”
To: “NT Developers Interest List”
Sent: Wednesday, January 30, 2002 5:54 PM
Subject: [ntdev] Tightly Coupled drivers - Need help!

> Hi,
>
> I have a driver which talks with two other drivers to send and retieve
> information. The other two drivers speak with actual hardware. The
> communication occurs frequently.
>
> I read in previous postings that we can do this by exposing pointers
> to driver functions to the calling driver. It would be helpful if
> anyone can explain how this can be done.
>
> I am a newbie to the device driver development and it would be nice if
> anyone could point to some sample code to do this.
>
> Thanks.
>
> —
> You are currently subscribed to ntdev as: xxxxx@setengineering.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

4

In driver ‘A’, declare a function pointer and keep it in deivce extension
structure. In the driver ‘B’, Try getting the driver 'A’s device object
and extract the function pointer from the device extension.

Senthil Kumar wrote:

Hi,

I have a driver which talks with two other drivers to send and retieve
information. The other two drivers speak with actual hardware. The
communication occurs frequently.

I read in previous postings that we can do this by exposing pointers
to driver functions to the calling driver. It would be helpful if
anyone can explain how this can be done.

I am a newbie to the device driver development and it would be nice if
anyone could point to some sample code to do this.

Thanks.

You are currently subscribed to ntdev as: xxxxx@uiscpl.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

–

************************************************************************
This e-mail message (including any attachments) may contain confidential,
legally privileged and proprietary information to U&I System Design or any

of its group companies and may also be protected by product immunity. If
you
have erroneously received this message, please notify the sender by return

e-mail and delete this message from your system. Any unauthorized use or
dissemination of this message in whole or part is strictly prohibited.

E-mail transmission cannot be guaranteed to be secure or free of errors,
viruses,
interceptions or interferences and U&I System Design shall not be liable
for
any delay in its receipt or damage to your system or for any violation of
intellectual property right of any person.

Any views, opinions and other information in this message that do not
relate to the official business of U&I SYSTEM DESIGN or any of its group
companies shall be understood as neither given nor endorsed by it.
*************************************************************************

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com