[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Re[2]: PCI Interrupts
- To: Mailing List Recipients <pci-sig-request@znyx.com>
- Subject: Re: Re[2]: PCI Interrupts
- From: henrylau@cts.com (Henry Lau)
- Date: Wed, 2 Oct 96 06:58 PDT
- Resent-Date: Wed, 2 Oct 96 06:58 PDT
- Resent-From: pci-sig-request@znyx.com
- Resent-Message-Id: <"eaopI3.0.AN.cnfKo"@dart>
- Resent-Sender: pci-sig-request@znyx.com
At 12:10 AM 10/2/96 -0700, John R Pierce wrote:
>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.
>
The origin of this mail is that I am writing some code to test out the
interrupt generation of a WAN PCI adapter card. I am writing the program
using Phar Lap Extender and Microsoft Visual C compiler but it is a
command line program running from the DOS Prompt under Windows/95.
Does the VPIC services still apply in this case?
Thank you
+-----------------------------------------+----------------------------+
| Henry Lau | Phone: 619-674-5000 x222 |
| Director of Software Development | Fax: 619-674-5005 |
| METACOMP, Inc. | Email: henrylau@cts.com |
| 10989 Via Frontera, San Diego, CA 92127 | http://www.metacompinc.com |
+-----------------------------------------+----------------------------+
V € o