https://osmocom.org/https://osmocom.org/favicon.ico?16647414092016-06-13T13:17:09ZOpen Source Mobile CommunicationsOsmoBTS - Feature #1576: consider using hLayer2 as a pointer storagehttps://osmocom.org/issues/1576?journal_id=15832016-06-13T13:17:09Zlaforge
<ul><li><strong>Assignee</strong> changed from <i>laforge</i> to <i>neels</i></li></ul> OsmoBTS - Feature #1576: consider using hLayer2 as a pointer storagehttps://osmocom.org/issues/1576?journal_id=16582016-06-22T22:22:46Zlaforge
<ul></ul><p>this is probably obsolete as we now use hLayer3?</p> OsmoBTS - Feature #1576: consider using hLayer2 as a pointer storagehttps://osmocom.org/issues/1576?journal_id=17852016-07-11T14:06:24Zneelsnhofmeyr@sysmocom.de
<ul></ul><p>There seems to be a bit of a mix-up.</p>
<p>For example, in osmo-bts-sysmo/oml.c, this:<br /><pre>
struct gsm_lchan *
l1if_hLayer_to_lchan(struct gsm_bts_trx *trx, uint32_t hLayer2)
</pre><br />is always called with an hLayer3 argument instead, e.g.:<br /><pre>
lchan = l1if_hLayer_to_lchan(trx, cc->hLayer3);
</pre></p>
<p>However, this is not related to the addition of hLayer3 in <a class="external" href="https://gerrit.osmocom.org/264">https://gerrit.osmocom.org/264</a><br />and we should take another look at how much of this is going on in parallel (see <a class="issue tracker-2 status-1 priority-1 priority-lowest" title="Feature: osmo-bts-sysmo L1: unify hLayer3 handling (New)" href="https://osmocom.org/issues/1755">#1755</a>).</p>
<p>This issue mentions efficiency ("speed up"), which so far has not been part of my<br />considerations.</p>
<p>My conclusion is that we would need to spend some time to look at and discuss this<br />before rejecting this issue.</p> OsmoBTS - Feature #1576: consider using hLayer2 as a pointer storagehttps://osmocom.org/issues/1576?journal_id=17862016-07-11T14:06:36Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-1 priority-1 priority-lowest" href="/issues/1755">Feature #1755</a>: osmo-bts-sysmo L1: unify hLayer3 handling</i> added</li></ul> OsmoBTS - Feature #1576: consider using hLayer2 as a pointer storagehttps://osmocom.org/issues/1576?journal_id=21002016-08-30T12:07:58Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-5 priority-4 priority-high2 closed child" href="/issues/1712">Feature #1712</a>: 3G Voice</i> added</li></ul> OsmoBTS - Feature #1576: consider using hLayer2 as a pointer storagehttps://osmocom.org/issues/1576?journal_id=21022016-08-30T12:08:04Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Related to</strong> deleted (<i><a class="issue tracker-2 status-5 priority-4 priority-high2 closed child" href="/issues/1712">Feature #1712</a>: 3G Voice</i>)</li></ul> OsmoBTS - Feature #1576: consider using hLayer2 as a pointer storagehttps://osmocom.org/issues/1576?journal_id=29862017-02-02T16:11:39Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Assignee</strong> changed from <i>neels</i> to <i>118</i></li></ul>