Re: Re[2]: PCI Interrupts

["John R Pierce" <pierce@scruznet.com>]

Henry Lau <henrylau@cts.com> wrote...
> 
> At 06:51 PM 9/30/96 EST, mrose@nectech.com wrote:
> >     Henry,
> >     
> >     Now, if the Routing register(s), the ELCR, and the Intline registers 
> >     are all setup, when the appropriate channel is unmasked (21h/A1h) and 
> >     the PCI asserts its INTA line, the interrupt assigned in the Intline 
> >     register should fire. Getting called from VPIC services is another 
> >     matter.
> >     
> What do you mean by the VPIC services?  Virtual Programmable Interrupt
> Controller?  How can I find out if VPIC services is setup properly?

VPICD refers to the Virtual PIC device of windows/windows95.  It has a whole
API, but normally windows applications layer software should just be able to
use the SetInterruptVector calls to hook the desired interrupt, and unmask the
appropriate IRQ.  If you have access to the Windows  3.x or Windows95 DDK
(device driver kit), I'd suggest you look at the IRQ code in some of the sample
drivers.

If your application/driver/whatever isn't running under windows, then you can
ignore this.  I'm afraid I don't remember the original context of your device
driver or interrupt handler.  If your device IS running under windows95, you
probably are going to want/need to write a 'virtual device driver' for it (aka
a VxD) as handling IRQ's in ring 3 (application mode) is rather fraught with
peril and overhead.

-jrp
S€o