Is there any way to access the SCSI miniport’s interrupt object?
Thanks
Mark
Do You Yahoo!?
Yahoo! Health - your guide to health and wellness
Well there is always *some* way, but why would you need this in a
miniport, as the whole miniport is serialized from start to finish, head
to toe, front to back? I hope you aren’t trying to go around the
serialization from outside the miniport, as that generally will not
work.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Mark Lobo
Sent: Tuesday, April 30, 2002 8:26 PM
To: NT Developers Interest List
Subject: [ntdev] Miniport interrupt object
Is there any way to access the SCSI miniport’s interrupt object?
Thanks
Mark
Do You Yahoo!?
Yahoo! Health http: -
your guide to health and wellness — You are currently subscribed to
ntdev as: xxxxx@hollistech.com To unsubscribe send a blank email to
%%email.unsub%%</http:>
Well yeah I want to synchronize an external callback into the miniport by calling KeSync… on the interrupt object…IF I can get it. So…how do we get the interrupt object?
TIA,
Mark
Mark Roddy wrote: Well there is always some way, but why would you need this in a miniport, as the whole miniport is serialized from start to finish, head to toe, front to back? I hope you aren’t trying to go around the serialization from outside the miniport, as that generally will not work.-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Mark Lobo
Sent: Tuesday, April 30, 2002 8:26 PM
To: NT Developers Interest List
Subject: [ntdev] Miniport interrupt object
Is there any way to access the SCSI miniport’s interrupt object?
Thanks
Mark
---------------------------------
Do You Yahoo!?
Yahoo! Health - your guide to health and wellness — You are currently subscribed to ntdev as: xxxxx@hollistech.com To unsubscribe send a blank email to %%email.unsub%%—
You are currently subscribed to ntdev as: xxxxx@yahoo.com
To unsubscribe send a blank email to %%email.unsub%%
---------------------------------
Do You Yahoo!?
Yahoo! Health - your guide to health and wellness
You grovel through the undefined structure that contains your hardware
device extension looking for something that might be an interrupt object.
But you really really really do not want to be doing that. Instead you
should consider other ways to get into the miniport context. Search through
this list and through the related newsgroups for the many discussions of how
to work around miniport limitations.
--
Mark Roddy
Consultant, Microsoft DDK MVP
Hollis Technology Solutions
xxxxx@hollistech.com
www.hollistech.com
603-321-1032
For Windows Driver training see www.azius.com
"Mark Lobo" wrote in message news:xxxxx@ntdev...
Well yeah I want to synchronize an external callback into the miniport by
calling KeSync.. on the interrupt object..IF I can get it. So..how do we get
the interrupt object?
TIA,
Mark
Mark Roddy wrote:
Well there is always some way, but why would you need this in a miniport,
as the whole miniport is serialized from start to finish, head to toe, front
to back? I hope you aren't trying to go around the serialization from
outside the miniport, as that generally will not work.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Mark Lobo
Sent: Tuesday, April 30, 2002 8:26 PM
To: NT Developers Interest List
Subject: [ntdev] Miniport interrupt object
Is there any way to access the SCSI miniport's interrupt object?
Thanks
Mark
Do You Yahoo!?
Yahoo! Health - your guide to health and wellness --- You are currently
subscribed to ntdev as: xxxxx@hollistech.com To unsubscribe send a blank
email to %%email.unsub%%
---
You are currently subscribed to ntdev as: xxxxx@yahoo.com
To unsubscribe send a blank email to %%email.unsub%%
Do You Yahoo!?
Yahoo! Health - your guide to health and wellness
MessageTo bolster what Mark said … NO!!!
Oh you can go traipsing through the device objects chain in the driver object until you find the one that has the device extension that contains the pointer to the interrupt object. And with a lot patience and effort you can dump that device extension and most likely find the pointer to the interrupt object. Yup … you can do that. You can even use the offset within the device extension to use that interrupt object. You really really can. Until some software engineer in the chain farts and the offset changes and now your driver winds up in the toilette until you go traipsing through the device objects chain in the driver object until you find the one that has the device extension that contains the pointer to the interrupt object. And with a lot patience and effort you can dump that device extension and most likely find the pointer to the interrupt object. Yup … you can do that. You can even use the offset within the device extension to use that interrupt object. You really really can. Until some software engineer in the chain farts and the offset changes and now your driver winds up in the toilette until you …
Now why on earth would you want to do that?
–
Gary G. Little
xxxxx@broadstor.com
xxxxx@inland.net
“Mark Roddy” wrote in message news:xxxxx@ntdev…
Well there is always some way, but why would you need this in a miniport, as the whole miniport is serialized from start to finish, head to toe, front to back? I hope you aren’t trying to go around the serialization from outside the miniport, as that generally will not work.
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Mark Lobo
Sent: Tuesday, April 30, 2002 8:26 PM
To: NT Developers Interest List
Subject: [ntdev] Miniport interrupt object
Is there any way to access the SCSI miniport’s interrupt object?
Thanks
Mark
----------------------------------------------------------------------------
Do You Yahoo!?
Yahoo! Health - your guide to health and wellness — You are currently subscribed to ntdev as: xxxxx@hollistech.com To unsubscribe send a blank email to %%email.unsub%%