Article View: comp.sys.dec
Article #3111Re: "passive release"? What is it?
From: Terry Kennedy, Operations Mgr.
Date: Tue, 12 Feb 1991 04:45
Date: Tue, 12 Feb 1991 04:45
22 lines
1502 bytes
1502 bytes
In article <GOEHRING.91Feb11202106@ai.mit.edu>, goehring@ai.mit.edu (Not Marc Spencer) writes: > The _VAX Architecture Reference Manual_ specifies that SCB vector 00 > is for a "passive release" interrupt. What is a "passive release", > what causes one, what is the OS expected to do with one of these, and > what parameters are pushed on the stack? In brief, when a device asks for the bus via interrupt request, but then decides to ignore the interrupt ack from the Unibus adapter. Thus, the ack progresses through the backplane. If no other device grabs it, it hits the terminator. Thus, no vector is passed to the processor, and you get the default vector. From an application point of view, you'll never see this. From the driver's point of view, it won't either (but it should avoid placing the hardware in a state where it will generate passive releases, as they delay bus operations. Terry Kennedy Operations Manager, Academic Computing terry@spcvxa.bitnet St. Peter's College, US terry@spcvxa.spc.edu (201) 915-9381
Technical Details
Message-ID:
<1991Feb12.044547.1097@spcvxb.spc.edu>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!psuvax1!hsdndev!cmcl2!uupsi!njin!spcvxb.spc.edu!terryReferences:
<GOEHRING.91Feb11202106@ai.mit.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!psuvax1!hsdndev!cmcl2!uupsi!njin!spcvxb.spc.edu!terry From: terry@spcvxb.spc.edu (Terry Kennedy, Operations Mgr.) Newsgroups: comp.sys.dec Subject: Re: "passive release"? What is it? Message-ID: <1991Feb12.044547.1097@spcvxb.spc.edu> Date: 12 Feb 91 04:45:47 GMT References: <GOEHRING.91Feb11202106@ai.mit.edu> Organization: St. Peter's College, US Lines: 22