Reliablility problem in current git?

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/baseband-devel@lists.osmocom.org/.

Tim Ehlers osmocom at ehlers.info
Thu Feb 23 08:47:38 UTC 2012


On Thu, 23 Feb 2012, Sylvain Munaut wrote:

Hi Sylvain,

>> yesterday I made a quick call test and you are right, calling is still
>> broken. I could call a number, it is ringing and after pickup the call is
>> released (that happend in my quick test yesterday; I didn't have the time to
>> test more/again).
>
> Did you use the sylvain/testing branch as a base this time ?

as I can see you mean this patch, right?:

http://bb.osmocom.org/trac/changeset/fe3c81ecc454266b0ccd14a3c0f502db1413f041/

It's the only difference between master and sylvain/testing.

This patch I tried. It doesn't change a thing in this issue. And the call 
yesterday was your testing branch plus:

--- mframe_sched.c      2012-02-20 19:37:42.000000000 +0100
+++ mframe_sched.c~     2012-02-20 19:33:24.000000000 +0100
@@ -200,7 +200,11 @@
  /* Measurement for MF 51 */
  static const struct mframe_sched_item mf_neigh_pm51[] = {
+       { .sched_set = NEIGH_PM   , .modulo = 51, .frame_nr = 50 },
-       { .sched_set = NEIGH_PM   , .modulo = 51, .frame_nr = 0 },
-       { .sched_set = NEIGH_PM   , .modulo = 51, .frame_nr = 10 },
-       { .sched_set = NEIGH_PM   , .modulo = 51, .frame_nr = 20 },
-       { .sched_set = NEIGH_PM   , .modulo = 51, .frame_nr = 30 },
-       { .sched_set = NEIGH_PM   , .modulo = 51, .frame_nr = 40 },
         { .sched_set = NULL }
  };

Cheers

Tim




More information about the baseband-devel mailing list