EP0271582A1 - Bus mediation system - Google Patents

Bus mediation system Download PDF

Info

Publication number
EP0271582A1
EP0271582A1 EP87903403A EP87903403A EP0271582A1 EP 0271582 A1 EP0271582 A1 EP 0271582A1 EP 87903403 A EP87903403 A EP 87903403A EP 87903403 A EP87903403 A EP 87903403A EP 0271582 A1 EP0271582 A1 EP 0271582A1
Authority
EP
European Patent Office
Prior art keywords
bus
module
signal
request signal
modules
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
EP87903403A
Other languages
German (de)
French (fr)
Other versions
EP0271582A4 (en
EP0271582B1 (en
Inventor
Mikio Yonekura
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Fanuc Corp
Original Assignee
Fanuc Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Fanuc Corp filed Critical Fanuc Corp
Publication of EP0271582A1 publication Critical patent/EP0271582A1/en
Publication of EP0271582A4 publication Critical patent/EP0271582A4/en
Application granted granted Critical
Publication of EP0271582B1 publication Critical patent/EP0271582B1/en
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/14Handling requests for interconnection or transfer
    • G06F13/20Handling requests for interconnection or transfer for access to input/output bus
    • G06F13/24Handling requests for interconnection or transfer for access to input/output bus using interrupt
    • G06F13/26Handling requests for interconnection or transfer for access to input/output bus using interrupt with priority control
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/14Handling requests for interconnection or transfer
    • G06F13/36Handling requests for interconnection or transfer for access to common bus or bus system
    • G06F13/368Handling requests for interconnection or transfer for access to common bus or bus system with decentralised access control
    • G06F13/37Handling requests for interconnection or transfer for access to common bus or bus system with decentralised access control using a physical-position-dependent priority, e.g. daisy chain, round robin or token passing

Definitions

  • the present invention relates to a bus regulating system employing a so-called daisy chain, and more particularly to a bus regulating system for changing bus usage priority with software.
  • FIG. 4 Designated in FIG. 4 at 1 is a bus regulating circuit for determining a module that is permitted to use a bus, 2 a bus, and 3 a request signal line for transferring a request signal * RQ by which each module requests use of the bus.
  • a bus usage permit signal line 4 transfers a bus usage permit signal * BG issued by the bus regulating circuit 1 for permitting each module to use the bus.
  • the bus is shared by modules 10, 20, 30. (In the present description, a signal which is of a logic "0" when it is effective is associated with the sign " * " in front of the alphabetical letters that denote the signal.)
  • the bus regulating circuit 1 when one of the modules issues a bus usage request signal * RQ, the bus regulating circuit 1 sends a bus usage permit signal * BG to the line 4 if the bus is not occupied.
  • Each module receives the bus usage permit signal * BG and exclusively uses the bus if it has issued the request signal * RQ. If a module has not issued the request signal * RQ, then it transfers the bus usage permit signal * BG to the next module.
  • bus usage permist signal line is in the form of a daisy chain, those modules closer to the left have higher bus usage priority and those closer to the right have lower bus usage priority. Therefore, bus usage priority is determined by the hardware arrangement, and a module which is processing a task with higher priority may not necessarily be allowed to use the bus with priority.
  • a bus regulating system having a plurality of modules, a bus shared by the modules, a bus regulating circuit, a bus usage permit signal line, and a bus usage permit signal line in the form of a daisy chain, said bus regulating system comprising:
  • overlapping request determining means for determining whether an overlapping request signal is to be issued or not when a request signal is being issued from another module
  • a module which is processing a task of lower priority inhibits the issuance of a request signal when a request signal is being issued from another module, and gives the right to use the bus to a module which is processing a task of higher priority. Conversely, when a module is processing a task of higher priority, it issues a request signal even if a request signal is being issued from another module, so that the right to use the bus is obtained positively.
  • the module When a module with the right to use the bus is processing a task of higher priority, the module does not immediately abandon but keeps the bus at the time the use of the bus is finished. When a module with the right to use the bus is processing a task of lower priority, the module immediately abandons the bus and gives the bus to a module that is processing a task of higher priority at the time the use of the bus is over.
  • FIG. 1 shows in block form a bus regulating system according to an embodiment of the present invention.
  • Designated in FIG. 1 at 1 is a bus regulating circuit for determining a module that is permitted to use a bus, 2 a bus, and 3 a request signal line for transferring a request signal * RQ by which each module requests use of the bus.
  • a signal which is of a logic "0" when it is effective is associated with the sign " * " in front of the alphabetical letters that denote the signal.
  • a bus usage permit signal line 4 transfers a bus usage permit signal * BG issued by the bus regulating circuit 1 for permitting each module to use the bus.
  • Denoted at 5 is a bus busy signal line for transferring a bus busy signal * BBSY.
  • the bus is shared by modules 10, 20, 30. Although the modules are not necessarily identical in structure, they have at least CPUs 11, 21, 31, respectively, and bus control circuits (BC) 12, 22, 32, respectively. Since the modules operate in the same manner for bus control, module 10 will hereinafter be described.
  • the CPU 11 has a ROM and a RAM contained therein, though not shown.
  • the CPU 11 applies, to the bus control circuit 12, a bus request signal * IRQ and outputs D01, D02 representative of conditions for controlling the bus.
  • the bus control circuit 12 is responsive to the bus request signal * IRQ and the outputs D01, D02 from the CPU 11 for performing various control modes such as for requesting the bus, maintaining the right to use the bus, and abandon the right to use the bus.
  • the bus control circuit 12 and controlling of the bus will be described in detail below.
  • the bus control circuits 22, 23 are of the same circuit arrangement.
  • FIG. 2 shows a circuit arrangement of the bus control circuit 12.
  • a signal IRQ is a request signal from the CPU 11.
  • the bus control circuit 12 decides whether it should issue a request signal or not.
  • a signal DO1 is a DO signal from the CPU 11.
  • the module 10 does not issue a request signal * RQ if a request signal is issued from another module even when a request signal IRQ is issued from the internal CPU 11.
  • the signal DOl is of a logic "0”
  • the module 10 issues a request signal * RQ if a request signal IRQ is issued from the internal CPU 11 even when a request signal is issued from another module.
  • a signal * BG is a bus usage permit signal which is issued from the bus regulating circuit 1.
  • the module 10 can, in principle, obtain the right to use the bus. If the module 10 is not issuing a request signal * RQ, another module is request the use of the bus, and the signal * BG is applied to the other module.
  • a signal D02 is a DO signal from the CPU 11.
  • this signal is of a logic "1”
  • the module 10 is using the bus. Even when the use of the bus by the module 10 is over, unless a request signal * RQ is issued from another module, the module 10 does not abandon the exclusive use of the bus, but maintains the right to use the bus.
  • this DO signal is "0"
  • the module 10 abandons the right to use the bus immediately upon completion of use of the bus, and gives the right to use the bus to another module.
  • a signal * RQ is a request signal which is delivered over the request signal line 3 to the bus regulating circuit 1.
  • a signal * BG is a bus usage permit signal. When the module 10 does not use the bus, this signal is transferred to the next module.
  • a signal * BBSY is a bus busy signal which is issued when the module 10 is using the bus.
  • a request signal IRQ is issued from the CPU 11.
  • the module 10 does not use the bus. Therefore, if a request signal * RQ is being issued from another module, the output * RQ becomes "0" since the common bus line type is employed, and the NG1 issues an output of "0".
  • the FF1 is not set, no request signal * RQ is issued out even if the request signal IRQ is given from the CPU 11, and the bus is not used.
  • the IV3, FF2, FF3, AG2 jointly constitute a negative-going edge detector circuit 13. More specifically, when the bus usage permit signal * BG becomes "0", the AG2 issues an output of "I”. If the module 10 is attempting to get the right to use the bus at this time, since the FF1 has been set to "1", the output of the AG4 becomes “1", setting the FF5, and the bus busy signal * BBSY becomes “0". The module 10 now informs the bus regulating circuit 1 of exclusive use of the bus, and keeps the right to use the bus.
  • the module 10 When the D02 is "1", the module 10, even if it has finished the use of the bus, occupies the bus and keeps it so that the module 10 can use it immediately, unless there is a request signal * RQ from another module. More specifically, even when the request signal IRQ becomes "0" after the CPU 11 has finished the use of the bus, the output of the IV4 is "0", and the output of the NOG 1 is “1” unless the request signal * RQ becomes "0", i.e., the output of the IV2 becomes “1". The output of the AG5 is "0", and the FF5 is not reset, so taht the right to use the bus is maintained. Therefore, when the CPU 11 tries to use the bus next time, it can immediately use the bus without communicating with the bus regulating circuit 1.
  • FIG. 3 shows a timing chart of controlling of the bus.
  • IRQ is a request signal issued from the CPU 11 in the module
  • RQ a request signal from the module
  • BG a bus usage permit signal
  • BBSY a bus busy signal
  • BUS the condition of how the module 10 uses the bus.
  • the module 10 issues a request signal * RQ irrespective of the status of request signals * RQ from the other modules.
  • the bus regulating circuit 1 When the request signal * RQ is applied to the bus regulating circuit 1, the bus regulating circuit 1 produces a bus usage permit signal * BG unless the bus is not being used by another module.
  • the module 10 When the bus usage permit signal * BG is fed to the module 10, the module 10 obtains the right to use the bus and issues a bus busy signal * BBSY.
  • the bus regulating circuit 1 and the other modules 20, 30 are informed of the fact that the bus is occupied by the module 10.
  • the module 10 When the module 10 has finished the use of the bus, and if the output of the D02 is "1", the module 10 does not abandon the right to use the bus, and the bus is kept by the module 10 unless there is a request signal * RQ from another module. When a next request signal IRQ is issued from the CPU 11, the module 10 can immediately use the bus. Conversely, when the output of the D02 is "0", the bus is made open to use by other modules immediately upon completion of the use of the bus by the bus 10. This condition is indicated by the dotted lines in FIG. 3. If a request signal * RQ is issued from another module before a next request signal IRQ is produced, the right to use the bus is given to the other module, and the module 10 cannot immediately use the bus.
  • the priority can be changed according to tasks to be processed by issuing a request signal * RQ or abandon the right to use the bus after the usage of the bus. Therefore, the processing of software can be performed efficiently.
  • each module has means for determining overlapping requests and means for determining continued use.
  • Each module can use the bus with priority according to the priority of the task that is processed by the module. As a result, the processing of software can be performed efficiently.

Abstract

A plurality of modules (10,20,30) share a bus, a use-of- bus permission signal line (4) takes the form of a daisy chain, and the bus is flexibly used depending upon the tasks processed by the modules (10,20,30). Each of bus control circuits (12,22,32) of the modules (10,20,30) is provided with: overlapped-request discrimination means which, when the task of a high level is being processed, issues a request signal in an overlapped manner irrespective of request signals issued from other modules and which, when the task of a low level is being processed, does not issue the request signal if request signals are being issued from other modules; and continuation-of-use discrimination means which, when the task of a high level is being processed, permits the bus to be used continuously and which, when the task of a low level is being processed, abandons the use of the bus immediately after its use has been finished.

Description

    Technical Field
  • The present invention relates to a bus regulating system employing a so-called daisy chain, and more particularly to a bus regulating system for changing bus usage priority with software.
  • Background Art
  • There has heretofore been used a bus regulating system having a bus usage permit signal line in the form of a daisy chain. One example of such a bus regulating system is shown in FIG. 4 of the accompanying drawings. Designated in FIG. 4 at 1 is a bus regulating circuit for determining a module that is permitted to use a bus, 2 a bus, and 3 a request signal line for transferring a request signal *RQ by which each module requests use of the bus. A bus usage permit signal line 4 transfers a bus usage permit signal *BG issued by the bus regulating circuit 1 for permitting each module to use the bus. The bus is shared by modules 10, 20, 30. (In the present description, a signal which is of a logic "0" when it is effective is associated with the sign "*" in front of the alphabetical letters that denote the signal.)
  • In FIG. 4, when one of the modules issues a bus usage request signal *RQ, the bus regulating circuit 1 sends a bus usage permit signal *BG to the line 4 if the bus is not occupied. Each module receives the bus usage permit signal *BG and exclusively uses the bus if it has issued the request signal *RQ. If a module has not issued the request signal *RQ, then it transfers the bus usage permit signal *BG to the next module.
  • With the conventional system, when the modules 10, 20, 30 shown in FIG. 4 simultaneously issue request signals *RG, since the bus usage permist signal line is in the form of a daisy chain, those modules closer to the left have higher bus usage priority and those closer to the right have lower bus usage priority. Therefore, bus usage priority is determined by the hardware arrangement, and a module which is processing a task with higher priority may not necessarily be allowed to use the bus with priority.
  • Disclosure of the Invention
  • It is an object of the present invention to provide a bus regulating system which will solve the aforesaid problem and can allow use of a bus with priority according to the priority of tasks processed by modules.
  • To eliminate the above-mentioned problem, there is provided a bus regulating system having a plurality of modules, a bus shared by the modules, a bus regulating circuit, a bus usage permit signal line, and a bus usage permit signal line in the form of a daisy chain, said bus regulating system comprising:
  • overlapping request determining means for determining whether an overlapping request signal is to be issued or not when a request signal is being issued from another module; and
  • continued use determining means for determining whether the obtained right to use the bus is to be abandoned or continuously kept after said bus has been used.
  • A module which is processing a task of lower priority inhibits the issuance of a request signal when a request signal is being issued from another module, and gives the right to use the bus to a module which is processing a task of higher priority. Conversely, when a module is processing a task of higher priority, it issues a request signal even if a request signal is being issued from another module, so that the right to use the bus is obtained positively.
  • When a module with the right to use the bus is processing a task of higher priority, the module does not immediately abandon but keeps the bus at the time the use of the bus is finished. When a module with the right to use the bus is processing a task of lower priority, the module immediately abandons the bus and gives the bus to a module that is processing a task of higher priority at the time the use of the bus is over.
  • Brief Description of the Drawings
    • FIG. 1 is a block diagram of a bus regulating system according to an embodiment of the present invention;
    • FIG. 2 is a circuit diagram of a bus control circuit shown in FIG. 1;
    • FIG. 3 is a timing chart of bus control operation of the embodiment of the invention; and
    • FIG. 4 is a block diagram of a conventional bus regulating system employing a daisy chain.
    Best Mode for Carrying Out the Invention
  • An embodiment of the present invention will hereinafter be described in specific detail with reference to the drawings.
  • FIG. 1 shows in block form a bus regulating system according to an embodiment of the present invention. Designated in FIG. 1 at 1 is a bus regulating circuit for determining a module that is permitted to use a bus, 2 a bus, and 3 a request signal line for transferring a request signal *RQ by which each module requests use of the bus. (In the present description, as described above, a signal which is of a logic "0" when it is effective is associated with the sign "*" in front of the alphabetical letters that denote the signal.) A bus usage permit signal line 4 transfers a bus usage permit signal *BG issued by the bus regulating circuit 1 for permitting each module to use the bus. Denoted at 5 is a bus busy signal line for transferring a bus busy signal *BBSY. The bus is shared by modules 10, 20, 30. Although the modules are not necessarily identical in structure, they have at least CPUs 11, 21, 31, respectively, and bus control circuits (BC) 12, 22, 32, respectively. Since the modules operate in the same manner for bus control, module 10 will hereinafter be described.
  • The CPU 11 has a ROM and a RAM contained therein, though not shown. The CPU 11 applies, to the bus control circuit 12, a bus request signal *IRQ and outputs D01, D02 representative of conditions for controlling the bus. The bus control circuit 12 is responsive to the bus request signal *IRQ and the outputs D01, D02 from the CPU 11 for performing various control modes such as for requesting the bus, maintaining the right to use the bus, and abandon the right to use the bus.
  • The bus control circuit 12 and controlling of the bus will be described in detail below. The bus control circuits 22, 23 are of the same circuit arrangement.
  • FIG. 2 shows a circuit arrangement of the bus control circuit 12.
  • Various reference characters for circuit elements are defined as follows:
    • AG1 - AG5 AND circuits
    • NG1 - NG2 NAND circuits
    • NOGl NOR circuit
    • IVl - IV5 NOT circuit
    • FF1 - FF5 flip-flops
    Various signals are as follows:
  • A signal IRQ is a request signal from the CPU 11. In response to this signal, the bus control circuit 12 decides whether it should issue a request signal or not.
  • A signal DO1 is a DO signal from the CPU 11. When it is of a logic "1", the module 10 does not issue a request signal *RQ if a request signal is issued from another module even when a request signal IRQ is issued from the internal CPU 11. When the signal DOl is of a logic "0", the module 10 issues a request signal *RQ if a request signal IRQ is issued from the internal CPU 11 even when a request signal is issued from another module.
  • A signal *BG is a bus usage permit signal which is issued from the bus regulating circuit 1. When this signal is applied at the time the module 10 is issuing a request signal *RG, the module 10 can, in principle, obtain the right to use the bus. If the module 10 is not issuing a request signal *RQ, another module is request the use of the bus, and the signal *BG is applied to the other module.
  • A signal D02 is a DO signal from the CPU 11. When this signal is of a logic "1", the module 10 is using the bus. Even when the use of the bus by the module 10 is over, unless a request signal *RQ is issued from another module, the module 10 does not abandon the exclusive use of the bus, but maintains the right to use the bus. When this DO signal is "0", the module 10 abandons the right to use the bus immediately upon completion of use of the bus, and gives the right to use the bus to another module.
  • A signal *RQ is a request signal which is delivered over the request signal line 3 to the bus regulating circuit 1.
  • A signal *BG is a bus usage permit signal. When the module 10 does not use the bus, this signal is transferred to the next module.
  • A signal *BBSY is a bus busy signal which is issued when the module 10 is using the bus.
  • Operation of the bus control circuit will be described.
  • A request signal IRQ is issued from the CPU 11. When the signal D01 from the CPU 11 is "1" and if a request signal *RQ is being issued from another module, the module 10 does not use the bus. Therefore, if a request signal *RQ is being issued from another module, the output *RQ becomes "0" since the common bus line type is employed, and the NG1 issues an output of "0". The FF1 is not set, no request signal *RQ is issued out even if the request signal IRQ is given from the CPU 11, and the bus is not used. Conversely, when the output signal DOl is "0" and the request signal IRQ is issued, the output from the NG1 is "1" even if a request signal *RQ is issued from another module and the request signal *RQ is "0". With the output from the CPU 11 being "1", the FF1 is set, and the module 10 attempts to obtain the right to use the bus.
  • The case where a bus usage permit signal *BG is issued from the bus regulating circuit 1 will then be described.
  • The IV3, FF2, FF3, AG2 jointly constitute a negative-going edge detector circuit 13. More specifically, when the bus usage permit signal *BG becomes "0", the AG2 issues an output of "I". If the module 10 is attempting to get the right to use the bus at this time, since the FF1 has been set to "1", the output of the AG4 becomes "1", setting the FF5, and the bus busy signal *BBSY becomes "0". The module 10 now informs the bus regulating circuit 1 of exclusive use of the bus, and keeps the right to use the bus. Conversely, even when the AG2 becomes "1" at a negative-going edge of the bus usage permit signal "BG, the output of the AG4 does not become "1" unless the FF1 has been set, and the output of the AG3 becomes "1", setting the FF4. With the FF4 being thus set, the bus usage permit signal *BG is applied through the FF2, FF3 to cause the output of the NG2 to become "0". The bus usage permit signal *BG is now transferred to the next module, and the bus 10 does not keep the right to use the bus.
  • The function of the signal D02 from.the CPU 11 will be described below. When the D02 is "1", the module 10, even if it has finished the use of the bus, occupies the bus and keeps it so that the module 10 can use it immediately, unless there is a request signal *RQ from another module. More specifically, even when the request signal IRQ becomes "0" after the CPU 11 has finished the use of the bus, the output of the IV4 is "0", and the output of the NOG 1 is "1" unless the request signal *RQ becomes "0", i.e., the output of the IV2 becomes "1". The output of the AG5 is "0", and the FF5 is not reset, so taht the right to use the bus is maintained. Therefore, when the CPU 11 tries to use the bus next time, it can immediately use the bus without communicating with the bus regulating circuit 1.
  • Conversely, when the D02 is "0", the output of the IV4 is "1" and the output of the NOG1 becomes "0". When the use of the bus is over and the request signal IRQ from the CPU 11 becomes "0", the output of the AG5 becomes "1", resetting the FFS, and the bus busy signal *BBSY becomes "1". The bus is now open to use by the other modules.
  • The sequence of operation will be described with reference to a timing chart. FIG. 3 shows a timing chart of controlling of the bus. Denoted in FIG. 3 at *IRQ is a request signal issued from the CPU 11 in the module, *RQ a request signal from the module, *BG a bus usage permit signal, a *BBSY a bus busy signal, and BUS the condition of how the module 10 uses the bus. These signals are denoted by the same reference characters as those used in FIG. 2.
  • When the CPU 11 issues a request signal IRQ and the signal D01 is "0", the module 10 issues a request signal *RQ irrespective of the status of request signals *RQ from the other modules.
  • When the request signal *RQ is applied to the bus regulating circuit 1, the bus regulating circuit 1 produces a bus usage permit signal *BG unless the bus is not being used by another module.
  • When the bus usage permit signal *BG is fed to the module 10, the module 10 obtains the right to use the bus and issues a bus busy signal *BBSY.
  • Upon issuance of the bus busy signal *BBSY, the bus regulating circuit 1 and the other modules 20, 30 are informed of the fact that the bus is occupied by the module 10.
  • When the module 10 has finished the use of the bus, and if the output of the D02 is "1", the module 10 does not abandon the right to use the bus, and the bus is kept by the module 10 unless there is a request signal *RQ from another module. When a next request signal IRQ is issued from the CPU 11, the module 10 can immediately use the bus. Conversely, when the output of the D02 is "0", the bus is made open to use by other modules immediately upon completion of the use of the bus by the bus 10. This condition is indicated by the dotted lines in FIG. 3. If a request signal *RQ is issued from another module before a next request signal IRQ is produced, the right to use the bus is given to the other module, and the module 10 cannot immediately use the bus.
  • Thus, where there is a conflict among modules about the use of the bus, the priority can be changed according to tasks to be processed by issuing a request signal *RQ or abandon the right to use the bus after the usage of the bus. Therefore, the processing of software can be performed efficiently.
  • While only three modules are involved in the above description, the invention is not limited to the three modules.
  • With the present invention, as described above, each module has means for determining overlapping requests and means for determining continued use. Each module can use the bus with priority according to the priority of the task that is processed by the module. As a result, the processing of software can be performed efficiently.

Claims (2)

1. A bus regulating system having a plurality of modules, a bus shared by the modules, a bus regulating circuit, a bus usage permit signal line, and a bus usage permit signal line in the form of a daisy chain, said bus regulating system comprising:
overlapping request determining means for determining whether an overlapping request signal is to be issued or not when a request signal is being issued from another module; and
continued use determining means for determining whether the obtained right to use the bus is to be abandoned or continuously kept after said bus has been used.
2. A bus regulating system according to claim 1, wherein said overlapping request determining means and said continued use determining means can be rewritten by software.
EP87903403A 1986-05-29 1987-05-16 Bus mediation system Expired - Lifetime EP0271582B1 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
JP124236/86 1986-05-29
JP61124236A JPS62280948A (en) 1986-05-29 1986-05-29 Bus arbitration system
PCT/JP1987/000306 WO1987007409A1 (en) 1986-05-29 1987-05-16 Bus mediation system

Publications (3)

Publication Number Publication Date
EP0271582A1 true EP0271582A1 (en) 1988-06-22
EP0271582A4 EP0271582A4 (en) 1989-10-04
EP0271582B1 EP0271582B1 (en) 1994-07-13

Family

ID=14880339

Family Applications (1)

Application Number Title Priority Date Filing Date
EP87903403A Expired - Lifetime EP0271582B1 (en) 1986-05-29 1987-05-16 Bus mediation system

Country Status (5)

Country Link
US (1) US4959775A (en)
EP (1) EP0271582B1 (en)
JP (1) JPS62280948A (en)
DE (1) DE3750216T2 (en)
WO (1) WO1987007409A1 (en)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0562222A1 (en) * 1992-03-27 1993-09-29 ALCATEL BELL Naamloze Vennootschap Access control arrangement
GB2298340A (en) * 1994-12-22 1996-08-28 Motorola Israel Ltd Method of operating a communication system
GB2318487A (en) * 1994-03-01 1998-04-22 Intel Corp Bus arbitration system
SG81236A1 (en) * 1994-03-01 2001-06-19 Intel Corp High performance symmetric arbitration protcocol with support for i/o requirements
GB2411266A (en) * 2004-02-20 2005-08-24 Samsung Electronics Co Ltd Bus system

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5276818A (en) * 1989-04-24 1994-01-04 Hitachi, Ltd. Bus system for information processing system and method of controlling the same
US5263163A (en) * 1990-01-19 1993-11-16 Codex Corporation Arbitration among multiple users of a shared resource
CN1092538A (en) * 1993-03-16 1994-09-21 Ht研究公司 A kind of casing that is used for multicomputer system
EP0654743A1 (en) * 1993-11-19 1995-05-24 International Business Machines Corporation Computer system having a DSP local bus
US6434638B1 (en) 1994-12-09 2002-08-13 International Business Machines Corporation Arbitration protocol for peer-to-peer communication in synchronous systems
US5740380A (en) * 1996-07-15 1998-04-14 Micron Electronics, Inc. Method and system for apportioning computer bus bandwidth
US6092219A (en) * 1997-12-03 2000-07-18 Micron Technology, Inc. Method for use of bus parking states to communicate diagnostic information
US6112316A (en) * 1997-12-03 2000-08-29 Micron Electronics, Inc. System for use of bus parking states to communicate diagnostic information
US6609171B1 (en) * 1999-12-29 2003-08-19 Intel Corporation Quad pumped bus architecture and protocol
US6928501B2 (en) * 2001-10-15 2005-08-09 Silicon Laboratories, Inc. Serial device daisy chaining method and apparatus
JP2005092780A (en) * 2003-09-19 2005-04-07 Matsushita Electric Ind Co Ltd Real time processor system and control method
US8296488B2 (en) 2009-04-27 2012-10-23 Abl Ip Holding Llc Automatic self-addressing method for wired network nodes

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPS5654535A (en) * 1979-10-08 1981-05-14 Hitachi Ltd Bus control system
WO1982003931A1 (en) * 1981-04-27 1982-11-11 Kris Bryan Multi-master processor bus
US4494192A (en) * 1982-07-21 1985-01-15 Sperry Corporation High speed bus architecture
JPS59226922A (en) * 1983-06-07 1984-12-20 Nec Corp Bus controller
US4602327A (en) * 1983-07-28 1986-07-22 Motorola, Inc. Bus master capable of relinquishing bus on request and retrying bus cycle

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
ELEKTRONISCHE RECHEN ANLAGEN, vol. 21, no. 4, August 1979, pages 171-183; G.C. NICOLAE et al.: "Multiprocessor system for the real-time digital processing of video-image series" *
IBM TECHNICAL DISCLOSURE BULLETIN, vol. 28, no. 4, September 1985, pages 1555-1556, New York, US; "Prioritized data communication system using a common bus" *
PROCEEDINGS OF THE FALL JOINT COMPUTER CONFERENCE, Araheim, California, 14th-16th November 1967, vol. 31, pages 621-633, AFIPS, Palo Alto (115), Washington, US; M. PIRTLE:"Intercommunication of processors and memory" *
See also references of WO8707409A1 *
WESCON/79 CONFERENCE RECORD, San Francisco, CA, 18th-20th September 1979, paper 28/1, pages 1-6, Electronic Conventions, Inc., North Hollywood, US; L. SOLTESZ: "Multiprocessing with single board computers - hardware considerations" *

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0562222A1 (en) * 1992-03-27 1993-09-29 ALCATEL BELL Naamloze Vennootschap Access control arrangement
US5434984A (en) * 1992-03-27 1995-07-18 Alcatel N.V. Priority based access control arrangement
GB2318487B (en) * 1994-03-01 1998-12-16 Intel Corp High performance symmetric arbitration protocol with support for I/O requirements
GB2318487A (en) * 1994-03-01 1998-04-22 Intel Corp Bus arbitration system
GB2324230A (en) * 1994-03-01 1998-10-14 Intel Corp Symmetric arbitration protocol with priority override
GB2324230B (en) * 1994-03-01 1998-12-16 Intel Corp High performance symmetric arbitration protocol with support for I/O requirements
SG81236A1 (en) * 1994-03-01 2001-06-19 Intel Corp High performance symmetric arbitration protcocol with support for i/o requirements
SG104916A1 (en) * 1994-03-01 2004-07-30 Intel Corp High performance symmetric arbitration protocol with support for i/o requirements
GB2298340A (en) * 1994-12-22 1996-08-28 Motorola Israel Ltd Method of operating a communication system
GB2298340B (en) * 1994-12-22 1999-06-23 Motorola Israel Ltd Method of operating a communication system
GB2411266A (en) * 2004-02-20 2005-08-24 Samsung Electronics Co Ltd Bus system
GB2411266B (en) * 2004-02-20 2006-08-02 Samsung Electronics Co Ltd Bus system and method thereof
US7412550B2 (en) 2004-02-20 2008-08-12 Samsung Electronics Co., Ltd. Bus system with protocol conversion for arbitrating bus occupation and method thereof

Also Published As

Publication number Publication date
EP0271582A4 (en) 1989-10-04
JPS62280948A (en) 1987-12-05
DE3750216T2 (en) 1995-03-02
WO1987007409A1 (en) 1987-12-03
EP0271582B1 (en) 1994-07-13
DE3750216D1 (en) 1994-08-18
US4959775A (en) 1990-09-25

Similar Documents

Publication Publication Date Title
EP0271582A1 (en) Bus mediation system
CA1241762A (en) Interrupt mechanism for multi-microprocessing system having multiple busses
EP0428330A2 (en) Computer interface circuit
JPH0773137A (en) Method, adaptor and system for arbitration of multilevel bus
EP0675444A1 (en) Multiple arbitration scheme
US5530903A (en) System for reassigning a higher priority to an interrupted user by inhibiting the access of other users until the interrupted user has completed its task
EP0464237A1 (en) Bus arbitration scheme
US5202991A (en) Reducing the effect processor blocking
US5557756A (en) Chained arbitration
AU4735989A (en) Method for unblocking a multibus multiprocessor system
TW369632B (en) Computer system
EP0367816B1 (en) Reducing the effect of processor blocking
JP2538874B2 (en) Common bus arbitration method
JPS57211628A (en) Controller for shared input and output loop bus of multicomputer system
JPS58217071A (en) Information processing system
WO1994009437A1 (en) Signal handling system with a shared data memory
KR920007945B1 (en) Slot address
JPH01263762A (en) Multiprocessor system
JP2946561B2 (en) Multiprocessor system
JPS62272345A (en) Bus arbitrating system
KR950012503B1 (en) Bus access arbitrating apparatus by bus master's priority
JPS6041782B2 (en) Interrupt request method
KR910006685Y1 (en) Arbitration circuit for implementing multiprocessor using shared system bus
KR960009906Y1 (en) Common memory using system
JP2564321B2 (en) Bus control method

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 19880218

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): DE FR GB

A4 Supplementary search report drawn up and despatched

Effective date: 19891004

17Q First examination report despatched

Effective date: 19920807

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): DE FR GB

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FR

Effective date: 19940713

REF Corresponds to:

Ref document number: 3750216

Country of ref document: DE

Date of ref document: 19940818

EN Fr: translation not filed
PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Effective date: 19950516

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed
GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 19950516

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 19960513

Year of fee payment: 10

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 19980203