![](/images/backgrounds/120559/120559-377265x1.png)
|
|
|
| User’s Manual |
|
| IBM PowerPC 750GX and 750GL RISC Microprocessor | ||
|
|
|
|
|
| Negated | Indicates that the 750GX is not granted next | ||
Timing |
|
| ||
Assertion | Might occur on any cycle; not recognized until the cycle | TS | is asserted, or | |
|
| later. | ||
| Negation | Might occur on any cycle to indicate the 750GX cannot assume | ||
|
| ownership. |
The
State | Asserted | If two or more data tenure requests are pending for the 750GX due to | ||
|
| address pipelining, indicates that the 750GX should run the | ||
|
| for the next pipelined write transaction even if a read address tenure was | ||
|
| pipelined on the bus before the write address tenure. DBWO allows write | ||
|
| data tenures to be run ahead of read data tenures. However, it does not | ||
|
| allow write data tenures to be run ahead of other write data tenures. If no | ||
|
| write requests are pending, the 750GX will ignore DBWO and assume data- | ||
|
| bus ownership for the next pending read request. | ||
| Negated | Indicates that the 750GX must run its read and write | ||
|
| same order as their address tenures. | ||
Timing |
|
| ||
Assertion/ | Sampled by the 750GX only on the clock that a qualified | DBG | is recognized. | |
| Negation |
|
|
|
| See Table | |||
|
| tion of the |
The data bus busy (DBB) signal is both an input and output signal on the 750GX.
Data Bus Busy |
| |
State | Asserted | Indicates that the 750GX is the current |
|
| always assume |
|
| a qualified |
| Negated | Indicates that the 750GX is not the current |
|
| retry (DRTRY) signal has extended the data tenure for the last or only data |
|
| beat. |
gx_07.fm.(1.2) | Signal Descriptions |
March 27, 2006 | Page 265 of 377 |