summaryrefslogtreecommitdiffstats
path: root/src/Makefile
diff options
context:
space:
mode:
authorAndreas Eversberg <jolly@eversberg.eu>2010-09-23 21:05:18 +0200
committerAndreas Eversberg <jolly@eversberg.eu>2016-09-25 08:11:41 +0200
commit620366a951572d9660583f76f99d78a72c6ecdaf (patch)
tree4a15dc138d0d483ae6bfbe6751ca0129bbea4a98 /src/Makefile
parentce3c88e075ee5d5e97f8497c0143aeedf3ad0f8c (diff)
[WIP] Safely change TPU offset on TS change or sync change
The TPU offset may vary some qbits, but on significant change, like a change to a new time slot, the TPU offset is always incremented. Changing backwards is performed by changing forwards and incrementing frame number. (This is because we wrap arround into the next frame.) The maximum amount of incrementation is half of a TDMA frame duration. This way we can be sure that the TPU always generates next IRQ later. If an incrmentation of more than half of a TDMA frame is required, the incrementation is performed in two steps, thus we can can be sure that each IRQ will always happen later. Example: TS 1 -> TS 2: increment by 625 qbits, keep same FN TS 1 -> TS 7: increment by 2500 qbits, then by 1250 qbits, keep same FN TS 7 -> TS 1: increment by 1250 qbits, increment FN TS 2 -> TS 1: increment by 2500 qbits, then by 1875 qbits, increment FN TODO: Prevent scheduling/transmission before and during change of TPU/FN.
Diffstat (limited to 'src/Makefile')
0 files changed, 0 insertions, 0 deletions