8 Jul
2013
8 Jul
'13
4:13 p.m.
On Mon, Jul 8, 2013 at 3:54 PM, Alexander Chemeris
<alexander.chemeris(a)gmail.com> wrote:
And this leads us to the question that POWEROFF in the
umtrx_dual_test
is not implemented at all.
This is not a problem caused by the dual_trx branch. POWEROFF has
never been implemented in _any_ branch. It has been always been dummy
command since the first OpenBTS release. The dual_trx branch does
maintain slightly stricter state variables in order to manage shared
resource control, and may return more error conditions (instead of
ignoring them). That's the likely the cause of different behaviour.
Yes, as you know, it's a major problem and the transceiver code
doesn't release resources in a sane way. Shutdown is broken, and it
always has been.
Thomas, could you please rebase the umtrx_dual_test
onto the recent
"fairwaves/master" branch? The DriveLoop/Transceiver split breaks a
number of patches and it would be better if you do it yourself.
I will do that.
Thomas