summaryrefslogtreecommitdiffstats
path: root/src/target/firmware/layer1/afc.c
AgeCommit message (Collapse)AuthorFilesLines
2011-01-11fixed typos in commentsThomas Waldmann1-1/+1
Signed-off-by: Steve Markgraf <steve@steve-m.de>
2010-05-20AFC: Add afc_reset() function to re-set AFCDAC to default valueHarald Welte1-1/+8
2010-05-19layer1/l1ctl: Split L1CTL_NEW_CCCH_REQ in FBSB_REQ nad SYNC_REQHarald Welte1-0/+1
We really want to have those two as distinct operations - and we want proper state machines in L1 to quickly return if they've managed to acquire a FB or SB or not. Otherwise scanning will take ages... This code now introduces a new l1ctl_fbsb_req that is sent via L1CTL to ask for a bitmask of FB0/FB1/SB operations. The actual FB0/FB1 detection now no longer runs for 500 TDMA interrupts but completes as soon as we either know there is no FCCH, or that our frequency error is smaller than a caller-specified threshold. FB0/FB1 are already working, SB is not yet, sorry.
2010-05-17layer1: Use measured VCTCXO AFC DAC slope as AFC_SLOPEHarald Welte1-4/+3
2010-03-07start to use libosmocore within the firmwareHarald Welte1-3/+3
* remove linuxlist.h copy and use osmocore * don't put 'struct gsm_time' into l1ctl packets * include rx_level and snr for each burst in l1ctl * properly build libosmocore.a for target * move gsmtime functions into libosmocore * move ctype.h to standard location
2010-02-18frequency error is actually twice of what we thought.Harald Welte1-1/+2
The cause is really not clear. The formual using 2*Pi to convert from radians to frequency is perfectly correct. However, measurements with various test equipment (including Racal 6103) have shown our frequency error estimate is always off by a power of two...
2010-02-18Initial import of OsmocomBB into git repositoryHarald Welte1-0/+122
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-01 07:38:01 +0000