Prev: KMDF and WDF documentation
Next: Virtual video capture device driver
From: krby_xtrm on 28 Dec 2005 08:55
hi

I find it in many driver sample especially pci driver sample that
READ_PORT_ULONG is mainly on the OnInterrupt routine?

what if my device has no support for interrupt, say its a custom
hardware.
Where should such READ_PORT be?

ps.
How a StartDevice() routine is called?

krby_xtrm

From: Doron Holan [MS] on 28 Dec 2005 11:57
you can read the port from any routine as long as the device is powered on.
you can read the port in start device or a DPC or whatever context you
choose.

d

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.


"krby_xtrm" <kerby.martino(a)gmail.com> wrote in message
news:1135778137.201931.148370(a)f14g2000cwb.googlegroups.com...
> hi
>
> I find it in many driver sample especially pci driver sample that
> READ_PORT_ULONG is mainly on the OnInterrupt routine?
>
> what if my device has no support for interrupt, say its a custom
> hardware.
> Where should such READ_PORT be?
>
> ps.
> How a StartDevice() routine is called?
>
> krby_xtrm
>


From: krby_xtrm on 28 Dec 2005 12:31
i see.
but how does a StartDevice() is called?coz i cant find in many driver
samples that the routine is assigned or called?

-krby_xtrm-

From: Ali on 28 Dec 2005 12:48
StartDevice is a helper routine you write to handle the details of
extracting and dealing with configuration information. In sample
drivers of Walter O. book "Windows Driver Model" , you can check the
source module named READWRITE.CPP for StartDevice understanding.

/ali

From: Eric Ahn on 28 Dec 2005 12:59
It just helper function. don't mind driver model. but, check carefully
power of device.
If you know wdm or NT driver model, just use it.

 |  Next  |  Last
Pages: 1 2 3 4 5
Prev: KMDF and WDF documentation
Next: Virtual video capture device driver