Difference between revisions of "Bus grant line"
m (Simpler) |
(Discuss priority) |
||
| Line 1: | Line 1: | ||
| − | '''Bus grant lines''' are used in a number of bus architectures (for example, the [[UNIBUS]] and [[QBUS]]) for the [[Central Processing Unit|CPU]] (or whatever circuitry is controlling the bus) to communicate to | + | '''Bus grant lines''' are used in a number of bus architectures (for example, the [[UNIBUS]] and [[QBUS]]) for the [[Central Processing Unit|CPU]] (or whatever circuitry is controlling the bus) to communicate to [[device controller]]s that their request for [[interrupt]]s and [[Direct Memory Access|DMA]] have been granted (hence the name). |
| − | They are wired in series, so that one device's 'grant out' line is connected to the next device's 'grant in' line, starting the the CPU's 'grant out' line. When a device sees a 'granted' pulse on one of its grant in lines, '''if''' the device had requested a DMA/interrupt, it 'consumes' the grant pulse, and goes on to do the type of operation it requested; if it was '''not''' requesting that type of operation, it 'passes' the grant by generating a 'granted' pulse on '''its''' grant out line. | + | They are often wired in series, so that one device's 'grant out' line is connected to the next device's 'grant in' line, starting the the CPU's 'grant out' line. When a device sees a 'granted' pulse on one of its grant in lines, '''if''' the device had requested a DMA/interrupt, it 'consumes' the grant pulse, and goes on to do the type of operation it requested; if it was '''not''' requesting that type of operation, it 'passes' the grant by generating a 'granted' pulse on '''its''' grant out line. |
| + | |||
| + | In other words, when there are conflicting requests for the bus, this kind of system prioritizes the requests based on the devices' location on the bus; the ones closest to the CPU have the highest priority. | ||
On systems which have [[backplane]]s into which devices can be plugged, it is usually necessary to provide some means for a grant to 'jump over' an empty backplane slot; for the UNIBUS, this is done with either a [[G727 grant continuity card|G727]] or a [[G7273 grant continuity card]]. | On systems which have [[backplane]]s into which devices can be plugged, it is usually necessary to provide some means for a grant to 'jump over' an empty backplane slot; for the UNIBUS, this is done with either a [[G727 grant continuity card|G727]] or a [[G7273 grant continuity card]]. | ||
Revision as of 16:34, 18 September 2018
Bus grant lines are used in a number of bus architectures (for example, the UNIBUS and QBUS) for the CPU (or whatever circuitry is controlling the bus) to communicate to device controllers that their request for interrupts and DMA have been granted (hence the name).
They are often wired in series, so that one device's 'grant out' line is connected to the next device's 'grant in' line, starting the the CPU's 'grant out' line. When a device sees a 'granted' pulse on one of its grant in lines, if the device had requested a DMA/interrupt, it 'consumes' the grant pulse, and goes on to do the type of operation it requested; if it was not requesting that type of operation, it 'passes' the grant by generating a 'granted' pulse on its grant out line.
In other words, when there are conflicting requests for the bus, this kind of system prioritizes the requests based on the devices' location on the bus; the ones closest to the CPU have the highest priority.
On systems which have backplanes into which devices can be plugged, it is usually necessary to provide some means for a grant to 'jump over' an empty backplane slot; for the UNIBUS, this is done with either a G727 or a G7273 grant continuity card.
