Prev: MS Win DDK on WindowsXP: programs can run on other earlierOperative Systems (Vista, Windows 7)?
Next: Writing a 1394 interface driver
From: Tim Roberts on 15 Sep 2010 01:33 dsrking <dsrking2006(a)gmail.com> wrote: > >'KeStallExecutionProcessor' is working for my case. Remember that KeStallExecutionProcessor runs a tight CPU loop, using 100% of the CPU. KeDelayExecutionThread is a better choice, because it releases the CPU during the wait. -- Tim Roberts, timr(a)probo.com Providenza & Boekelheide, Inc.
From: RossettoeCioccolato on 15 Sep 2010 02:08 Tim, The premise is that the OP only wants to wait a few useconds, which makes KeStallExecutionProcessor the better choice. KeDelayExecutionThread is the better choice for longer waits, measured in milliseconds. Regards, Rossetoecioccolato.
From: dsrking on 15 Sep 2010 08:19 Thanks Tim & Rossetoecioccolato. i have one more doubt regarding ISA non PNP interrupt handling. It is clear for PNP interrupt handling is done by WDF layer. But for ISA non PNP devices, we need to mention the interrupt number in LogConfig - IRQConfig entry. I mentioned my interrupt number in IRQConfig entry. But I did not get any interrupt for my device. should we do anything inside the code for interrupt register and etc., for non pnp isa device in WDF driver? Currently I am using amcc5933 sample in WDK. For polling mode, i can get interrupt but in interrupt mode, i didn't get any interrupt. So only i got doubt in registering interrupt number, vector for isa non pnp device. Awaiting for response. Thanks in advance. D.
From: Maxim S. Shatskih on 16 Sep 2010 06:17
> But I did not get any interrupt for my device. should we do anything > inside the code for interrupt register and etc., for non pnp isa > device in WDF driver? No. NonPnP ISA and PnP ISA are the same in driver code. The only difference is that you must register the IRQs in the INF file. -- Maxim S. Shatskih Windows DDK MVP maxim(a)storagecraft.com http://www.storagecraft.com |