Is there a reason for the calibration option to be an int? A eng_float looks much more logical to me, as it is used the spec a freq.
Gr. Sim
On Tue, Mar 01, 2011 at 02:52:31PM +0100, Sim IJskes wrote:
Is there a reason for the calibration option to be an int? A eng_float looks much more logical to me, as it is used the spec a freq.
It indeed does not make sense to have this in integer. Feel free to test+submit a patch.
On 01-03-11 19:18, Harald Welte wrote:
On Tue, Mar 01, 2011 at 02:52:31PM +0100, Sim IJskes wrote:
Is there a reason for the calibration option to be an int? A eng_float looks much more logical to me, as it is used the spec a freq.
It indeed does not make sense to have this in integer. Feel free to test+submit a patch.
Like this you mean? Testing is not possible other then running it. I've no working tetra reception yet.
As you can see, i've changed the default to 0 to align with usrp1-tetra_demod.py behaviour.
Gr. Sim
Hi Sim,
On Tue, Mar 01, 2011 at 09:42:01PM +0100, Sim IJskes wrote:
Like this you mean? Testing is not possible other then running it. I've no working tetra reception yet.
you could ask somebody to provide a trace to you :)
As you can see, i've changed the default to 0 to align with usrp1-tetra_demod.py behaviour.
ok, thanks. applied.
-
Harald Welte -
Sim IJskes