https://osmocom.org/https://osmocom.org/favicon.ico?16647414092017-01-05T13:46:28ZOpen Source Mobile CommunicationsOsmoBTS - Feature #1902: unify/refactor dynamic timeslot codehttps://osmocom.org/issues/1902?journal_id=27262017-01-05T13:46:28Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/2726/diff?detail_id=3990">diff</a>)</li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Low</i></li></ul><p>(accidentally hit enter when there was no description yet, adding description now)</p> OsmoBTS - Feature #1902: unify/refactor dynamic timeslot codehttps://osmocom.org/issues/1902?journal_id=27272017-01-05T13:48:09Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Assignee</strong> set to <i>118</i></li></ul> OsmoBTS - Feature #1902: unify/refactor dynamic timeslot codehttps://osmocom.org/issues/1902?journal_id=66682017-12-10T19:59:24Zlaforge
<ul><li><strong>Project</strong> changed from <i>OpenBSC</i> to <i>OsmoBSC</i></li></ul> OsmoBTS - Feature #1902: unify/refactor dynamic timeslot codehttps://osmocom.org/issues/1902?journal_id=70272018-01-04T10:54:43Zlaforge
<ul><li><strong>Assignee</strong> changed from <i>118</i> to <i>4368</i></li><li><strong>Priority</strong> changed from <i>Low</i> to <i>Normal</i></li></ul><p>I think this should be done together with the introduction of osmo_fsm for handling a lchan, i.e. one FSM per lchan whihc then tracks all of it's activation/deactivation state.</p> OsmoBTS - Feature #1902: unify/refactor dynamic timeslot codehttps://osmocom.org/issues/1902?journal_id=86582018-04-04T09:50:12Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-3 priority-2 priority-default closed" href="/issues/3131">Bug #3131</a>: dynamic timeslots not tested by BTS_Tests.ttcn</i> added</li></ul> OsmoBTS - Feature #1902: unify/refactor dynamic timeslot codehttps://osmocom.org/issues/1902?journal_id=86622018-04-04T09:54:30Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-3 priority-2 priority-default closed" href="/issues/3099">Bug #3099</a>: dynamic timeslots not tested by BSC_Tests.ttcn</i> added</li></ul> OsmoBTS - Feature #1902: unify/refactor dynamic timeslot codehttps://osmocom.org/issues/1902?journal_id=86642018-04-04T09:54:51Zlaforge
<ul></ul><p>I think this should wait until we have proper test cases, e.g. <a class="issue tracker-1 status-3 priority-2 priority-default closed" title="Bug: dynamic timeslots not tested by BSC_Tests.ttcn (Resolved)" href="https://osmocom.org/issues/3099">#3099</a></p> OsmoBTS - Feature #1902: unify/refactor dynamic timeslot codehttps://osmocom.org/issues/1902?journal_id=87042018-04-06T08:00:27Zlaforge
<ul><li><strong>Category</strong> set to <i>A-bis RSL</i></li></ul> OsmoBTS - Feature #1902: unify/refactor dynamic timeslot codehttps://osmocom.org/issues/1902?journal_id=109192018-08-22T10:53:27Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li></ul><p>In the course introducing the new timeslot FSM in osmo-bsc, the dynamic timeslot handling has been overhauled, and both dyn ts kinds now use the same data structures, namely</p>
<ul>
<li>ts.pchan_from_config = vty config setting,</li>
<li>.pchan_on_init = same as pchan_from_config but is not affected by telnet vty changes, and</li>
<li>.pchan_is = the current actual pchan.</li>
</ul>
<ul>
<li>For static timeslots, pchan_is = pchan_on_init,</li>
<li>for dynamic ones,
<ul>
<li>pchan_on_init = {TCH_F_TCH_H_PDCH, TCH_F_PDCH}</li>
<li>pchan_is = {TCH_F, TCH_H, PDCH, NONE}</li>
</ul></li>
</ul>
<p>However, the osmo-bts code base still employs the old separate data structures to track the dynamic timeslot status.</p> OsmoBTS - Feature #1902: unify/refactor dynamic timeslot codehttps://osmocom.org/issues/1902?journal_id=109202018-08-22T10:54:53Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Project</strong> changed from <i>OsmoBSC</i> to <i>OsmoBTS</i></li><li><strong>Category</strong> deleted (<del><i>A-bis RSL</i></del>)</li><li><strong>Status</strong> changed from <i>Resolved</i> to <i>New</i></li></ul><p>ok, let me just re-open this in the OsmoBTS project, then.</p> OsmoBTS - Feature #1902: unify/refactor dynamic timeslot codehttps://osmocom.org/issues/1902?journal_id=153072019-07-18T06:08:32Zlaforge
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Low</i></li></ul> OsmoBTS - Feature #1902: unify/refactor dynamic timeslot codehttps://osmocom.org/issues/1902?journal_id=171032020-01-08T22:56:14Zlaforge
<ul><li><strong>Assignee</strong> deleted (<del><i>4368</i></del>)</li></ul>