Unibrain API-810, Руководство пользователя

Страница: 56 / 77

ubCore™ 3.1 User Guide
fifo [RcvSize AsynchXmitSize IsochXmitSize]
When executed without any parameters it displays the current FIFO
settings of the current adapter.
When executed with parameters it changes the current FIFO configuration
of the adapter.
For example typing FIFO in the command prompt of FIRECOMMANDER
would display the following output (with a PCILynx2-based board):
----------------------------------------------
FIFO settings are dynamically changable.
FIFO auto-zero IsoXmit is SUPPORTED.
FIFO auto-zero IsoXmit is ACTIVE.
IsoXmit FIFO replacement policy is FIFO_FAVOUR_TRANSMIT.
Receive FIFO : Setup(2048) Current(2048).
Asynch Xmit FIFO: Setup(1024) Current(2048).
Isoch Xmit FIFO : Setup(1024) Current(0).
----------------------------------------------
This means that the 1394 stack is setup to use 2KB for receive (both
asynchronous and isochronous), 1KB for asynchronous transmit, and 1KB
for isochronous transmit.
However, when there is no isochronous transmit activity on the system,
then the drivers will favour the asynchronous transmit FIFO rather than the
receive FIFO, and add the
setup size of the isochronous transmit FIFO to
the asynchronous transmit FIFO.
This yields the
current values which in the above example are 2KB for
receive and 2KB for asynchronous transmit.
When the FIFO command is run with parameters, it updates the
setup
values. For example, if someone wanted to perform extensive isochronous
receive operations, very small asynchronous transmit operations, and no
isochronous transmits, and wanted to configure the FIFO with 3.5KB for
receive and 512 bytes for asynchronous transmit, then it would have to type
the following command:
FIFO 3584 256 256
This would make the
setup size of isochronous transmit FIFO equal to 256
bytes, and since there would be no isochronous transmit activity, this value
would be added to the current value of asynchronous transmit.
lock | l busID phyID offset function [32|64] data_value arg_value
Sends a lock transaction request to the node with physical ID phyID on bus
busID.
The available lock functions are:
FETCH_ADD
LITTLE_ADD
MASK_SWAP
COMPARE_SWAP
BOUNDED_ADD
WRAP_ADD
.
56