fixeria has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmocom-bb/+/39605?usp=email )

Change subject: trx_toolkit: fix typos in Transceiver API doc ......................................................................

trx_toolkit: fix typos in Transceiver API doc

Change-Id: I59c6c75bb2a76fa082d0ad110930a2982ee6728f --- M src/target/trx_toolkit/transceiver.py 1 file changed, 4 insertions(+), 4 deletions(-)

git pull ssh://gerrit.osmocom.org:29418/osmocom-bb refs/changes/05/39605/1

diff --git a/src/target/trx_toolkit/transceiver.py b/src/target/trx_toolkit/transceiver.py index e6af013..672c261 100644 --- a/src/target/trx_toolkit/transceiver.py +++ b/src/target/trx_toolkit/transceiver.py @@ -126,12 +126,12 @@ by default, at the moment of writing this patch).

In order to reflect that delay in a virtual environment, this - implementation, just like a normal transceiver (e.g. osmo-trx), - queues all to be transmitted (L12TRX) bursts, so hey remain in - the transmit queue until the appropriate time of transmission. + implementation, just like osmo-trx, queues all to be transmitted + (L12TRX) bursts, so that they remain in the transmit queue until + the appropriate time of transmission.

The API user is supposed to call recv_data_msg() in order to obtain - a L12TRX message on the TRXD (data) inteface, so it gets queued by + a L12TRX message on the TRXD (data) interface, so it gets queued by this function. Then, to ensure the timeous transmission, the user of this implementation needs to call clck_tick() on each TDMA frame. Both functions are thread-safe (queue mutex).