Yes, video port driver is opened exclusively. So the one possible variant is
Escape() or ExtEscape() from user-mode. Or may be create additional device
object for communication golas in miniport driver?
Bye,
SaB
-----Original Message-----
From: xxxxx@iee.org [mailto:xxxxx@iee.org]
Sent: 7 ÷åðâíÿ 2001 ð. 21:30
To: NT Developers Interest List
Subject: [ntdev] Re: Video Miniport question
I am currently implementing a video miniport driver that I would like
to send an IOCTL to from another driver (a regular system
driver). Anyone know of a way to do this (or is it just not possible)?Ex.)
—IOCTL CALL—> Video Port Driver —> Video Miniport driver
Good question! I’ve often wondered the same thing myself. I may be
wrong but I’ve a feeling that the video port driver is exclusively
opened in behalf of the corresponding display driver - so you may not
even be able to create/open the video port driver from another system
driver. The display driver isn’t exactly accessible from other system
drivers either, so it isn’t even obvious how you might get it to act
as an intermediary.
If I’m wrong someone please tell me.
I’ve been thwarted by this one a number of times, so if anyone has
acheived this I’d certainly be interesting in hearing how - especially
if it doesn’t break ‘the whole “port-miniport”’ model.
Re: documentation. Aside from the DDK and knowledge base articles
there’s a (all too) short chapter in the OSR Windows NT Device Driver
Development book. It’s a pretty good overview/introduction more than
it is reference. The only other documentation I’ve seen is code.
Gordon
—
You are currently subscribed to ntdev as: xxxxx@mastereye.kiev.ua
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