|
|
| PM5358 |
|
|
| Data Structures |
|
|
|
|
|
|
|
|
| Field Name | Field Type | Field Description |
|
|
|
|
| lof | UINT2 | Los of frame |
|
|
|
|
| oof | UINT2 | Out of frame |
|
|
|
|
| lot | UINT2 | Loss of transition |
|
|
|
|
| dool | UINT2 | Recovered data out of lock |
|
|
|
|
| rool | UINT2 | Recovered reference out of lock |
|
|
|
|
| ese | UINT2 | Elastic store FIFO error |
|
|
|
|
| pj | UINT2 | Pointer Justification |
|
|
|
|
3.3Structures in the Driver’s Allocated Memory
These structures are defined and used by the driver and are part of the context memory allocated when the driver is opened. These structures are the Module Data Block (MDB), the Device Data Block (DDB).
Module Data Block: MDB
The MDB is the
•errModule most of the module API functions return a specific error code directly. When the returned code is SUNI4x622_FAILURE, this indicates that the
•valid indicates that this structure has been properly initialized and may be read by the USER.
•stateModule contains the current state of the module and could be set to:
SUNI4x622_MOD_START, SUNI4x622_MOD_IDLE or SUNI4x622_MOD_READY.
Table 8:
Field Name | Field Type | Field Description |
|
|
|
errModule | INT4 | Global error Indicator for module calls |
|
|
|
valid | UINT2 | Indicates that this structure has been |
|
|
|
Proprietary and Confidential to | 33 |
Document ID: |
|