This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "An utility library for Open Source Mobile Communications".
The branch, master has been updated
via d5a577b043aab7d27608601ed751e8e17ec5457f (commit)
via b9fd7eba1558328802ae9dff79f708bd6ba7b10b (commit)
via c38b32dde94ae5547a11c4d59adb3510576300b0 (commit)
via 0bf93a6482e620b773fe3eea926c70c15d95b962 (commit)
via 22da145e4cbfee53039562b318516b3d8d1a49d0 (commit)
from f4cd228f1e238fbc824cdbdbd5eb30d99c44e079 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
-----------------------------------------------------------------------
Summary of changes:
tests/gsm0408/gsm0408_test.c | 74 +++++++++++++++++++++++++++++++++++++------
tests/gsm0408/gsm0408_test.ok | 36 ++++++++++++++++++---
2 files changed, 96 insertions(+), 14 deletions(-)
hooks/post-receive
--
An utility library for Open Source Mobile Communications
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "UNNAMED PROJECT".
The branch, neels/mnc3 has been updated
discards 676894a5c957f7a730e99f75246a688a4ef070cb (commit)
via c0391519d1e211cdb457c868088186991bcc1bb8 (commit)
This update added new revisions after undoing existing revisions. That is
to say, the old revision is not a strict subset of the new revision. This
situation occurs when you --force push a change and generate a repository
containing something like this:
* -- * -- B -- O -- O -- O (676894a5c957f7a730e99f75246a688a4ef070cb)
\
N -- N -- N (c0391519d1e211cdb457c868088186991bcc1bb8)
When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
http://cgit.osmocom.org/osmo-pcu/commit/?id=c0391519d1e211cdb457c8680881869…
commit c0391519d1e211cdb457c868088186991bcc1bb8
Author: Neels Hofmeyr <neels(a)hofmeyr.de>
Date: Wed Feb 21 00:39:07 2018 +0100
implement support for 3-digit MNC with leading zeros
Receive the mnc_3_digits flag from the PCU interface. Bump the PCU interface
version from 7 to 9 to match osmo-bts (see
I49cd762c3c9d7ee6a82451bdf3ffa2a060767947 there).
Add 3-digit flags and use the new RAI and LAI API from libosmocore throughout
the code base to be able to handle an MNC < 100 that has three digits (leading
zeros).
Depends: Id2240f7f518494c9df6c8bda52c0d5092f90f221 (libosmocore),
Ib7176b1d65a03b76f41f94bc9d3293a8a07d24c6 (libosmocore),
I49cd762c3c9d7ee6a82451bdf3ffa2a060767947 (osmo-bts)
Change-Id: I787fed84a7b613158a5618dd5cffafe4e4927234
-----------------------------------------------------------------------
Summary of changes:
tests/alloc/AllocTest.cpp | 1 +
tests/alloc/MslotTest.cpp | 1 +
tests/edge/EdgeTest.cpp | 1 +
tests/emu/pcu_emu.cpp | 3 ++-
tests/fn/FnTest.cpp | 1 +
tests/llc/LlcTest.cpp | 1 +
tests/ms/MsTest.cpp | 1 +
tests/tbf/TbfTest.cpp | 11 ++++++-----
tests/types/TypesTest.cpp | 1 +
9 files changed, 15 insertions(+), 6 deletions(-)
hooks/post-receive
--
UNNAMED PROJECT
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Osmocom code for Iuh interface".
The branch, neels/mnc3 has been created
at f3652e6c5c169c47cdc8b3883309cf477d245860 (commit)
- Log -----------------------------------------------------------------
http://cgit.osmocom.org/osmo-iuh/commit/?id=f3652e6c5c169c47cdc8b3883309cf4…
commit f3652e6c5c169c47cdc8b3883309cf477d245860
Author: Neels Hofmeyr <neels(a)hofmeyr.de>
Date: Thu Feb 22 04:04:22 2018 +0100
hnb-test: log accurate three-digit MNC with leading zeros
Depends: Id2240f7f518494c9df6c8bda52c0d5092f90f221 (libosmocore)
Change-Id: Ie3dd206bca2f38a0ef7ee7f9d3b6bf2eacc899a4
-----------------------------------------------------------------------
hooks/post-receive
--
Osmocom code for Iuh interface
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Osmocom BTS-side code (Abis, scheduling, ...)".
The branch, neels/mnc3 has been updated
discards d8e49baed8ccaa5c93246fadb9902cf19d90c222 (commit)
via 8fc29594c09b00680d76afbebc40d2c8ef9fea02 (commit)
This update added new revisions after undoing existing revisions. That is
to say, the old revision is not a strict subset of the new revision. This
situation occurs when you --force push a change and generate a repository
containing something like this:
* -- * -- B -- O -- O -- O (d8e49baed8ccaa5c93246fadb9902cf19d90c222)
\
N -- N -- N (8fc29594c09b00680d76afbebc40d2c8ef9fea02)
When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
http://cgit.osmocom.org/osmo-bts/commit/?id=8fc29594c09b00680d76afbebc40d2c…
commit 8fc29594c09b00680d76afbebc40d2c8ef9fea02
Author: Neels Hofmeyr <neels(a)hofmeyr.de>
Date: Wed Feb 21 00:38:05 2018 +0100
implement support for 3-digit MNC with leading zeros
Record the mnc_3_digits flag from SI and pass on via the PCU interface.
Bump the PCU interface version from 7 to 9, since osmo-bsc.git had a pcuif of
version 8 already, and its addition of the mnc_3_digits flag bumped to 9. I am
actually not sure whether this needs to match.
See I78f30aef7aa224b2e9db54c3a844d8f520b3aee0
Depends: Id2240f7f518494c9df6c8bda52c0d5092f90f221 (libosmocore)
Change-Id: I49cd762c3c9d7ee6a82451bdf3ffa2a060767947
-----------------------------------------------------------------------
Summary of changes:
hooks/post-receive
--
Osmocom BTS-side code (Abis, scheduling, ...)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "An utility library for Open Source Mobile Communications".
The branch, neels/mnc3 has been updated
discards 3d8879bfbcc3ff16ef955876a1a989d26fb692ba (commit)
discards e08e9c479a3360b74c6fb947b706a43840acd639 (commit)
discards 2aa1badcd17eafc7648ac6ada81d4fbfc724c00a (commit)
discards 91892abac66e9bbf538f4453f452e67a54f876ee (commit)
discards b7199612d6e2cce676cb099ac41c96a738494ba6 (commit)
discards be4fbeaf8c61ddc2f496bb2ad520118b53c6f645 (commit)
via 4615bd65427d8bd72caffb3da93f1b8bcb09d107 (commit)
via 58c904774e33cd1c69217f000df16f7b3d739a03 (commit)
via b834794958c3889ab963df046c780be828b44159 (commit)
via d99e40f3e8da67576e3400592825283022720fce (commit)
via e228f70c14acbddc474571db10df72c16c567786 (commit)
via f4f141ef4315968f9f333ceb1d725fb54b33a5d2 (commit)
This update added new revisions after undoing existing revisions. That is
to say, the old revision is not a strict subset of the new revision. This
situation occurs when you --force push a change and generate a repository
containing something like this:
* -- * -- B -- O -- O -- O (3d8879bfbcc3ff16ef955876a1a989d26fb692ba)
\
N -- N -- N (4615bd65427d8bd72caffb3da93f1b8bcb09d107)
When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
http://cgit.osmocom.org/libosmocore/commit/?id=4615bd65427d8bd72caffb3da93f…
commit 4615bd65427d8bd72caffb3da93f1b8bcb09d107
Author: Neels Hofmeyr <neels(a)hofmeyr.de>
Date: Tue Feb 20 15:14:14 2018 +0100
introduce GSM_MCC_MNC_INVALID
In some cases, we want to mark an unset MCC-MNC. Define uint16-max for this
purpose.
osmo-bsc code is already doing so with a -1 and using int data types, which
will become inconvenient with the new API that handles MCC and MNC as uint16_t.
Change-Id: Ieee7add0bd6d94cf84743a49794bbcd38561b72f
http://cgit.osmocom.org/libosmocore/commit/?id=58c904774e33cd1c69217f000df1…
commit 58c904774e33cd1c69217f000df16f7b3d739a03
Author: Neels Hofmeyr <neels(a)hofmeyr.de>
Date: Tue Feb 20 21:38:00 2018 +0100
gsm: add gsm48_mnc_from_str() and gsm48_mnc_cmp(), for 3-digit MNC
gsm48_mnc_from_str() preserves leading zeros in the string and is useful for
VTY config parsing.
gsm48_mnc_cmp() will be used by osmo-sgsn.git
Change-Id: Ib7176b1d65a03b76f41f94bc9d3293a8a07d24c6
http://cgit.osmocom.org/libosmocore/commit/?id=b834794958c3889ab963df046c78…
commit b834794958c3889ab963df046c780be828b44159
Author: Neels Hofmeyr <neels(a)hofmeyr.de>
Date: Tue Feb 20 22:20:42 2018 +0100
gsm0408_test: add test cases for MNC with leading zeros
Change-Id: I9b387e09293a6bbef84b9620ccf21ee2f9ec751c
http://cgit.osmocom.org/libosmocore/commit/?id=d99e40f3e8da67576e3400592825…
commit d99e40f3e8da67576e3400592825283022720fce
Author: Neels Hofmeyr <neels(a)hofmeyr.de>
Date: Tue Feb 20 22:19:56 2018 +0100
gsm0408_test: test new gsm48_{decode,generate}_lai2() functions
Change-Id: I4c8492b8055803d2857f1ef30aede088778b085b
http://cgit.osmocom.org/libosmocore/commit/?id=e228f70c14acbddc474571db10df…
commit e228f70c14acbddc474571db10df72c16c567786
Author: Neels Hofmeyr <neels(a)hofmeyr.de>
Date: Tue Feb 20 15:12:23 2018 +0100
gsm0408_test: check for new mnc_3_digits flag
Note that on the input side, the 3-digits flag may be left false when the MNC
is >99 anyway. On the decoded side, the flag is set accurately.
Change-Id: I89765613d8c5bd939a6957f7443ac88475f1b93c
http://cgit.osmocom.org/libosmocore/commit/?id=f4f141ef4315968f9f333ceb1d72…
commit f4f141ef4315968f9f333ceb1d725fb54b33a5d2
Author: Neels Hofmeyr <neels(a)hofmeyr.de>
Date: Tue Feb 20 13:47:08 2018 +0100
implement support for 3-digit MNC with leading zeros
Enable representing three-digit MNC with leading zeros. The MNCs 23 and 023 are
actually different; so far we treated both as 23. Re-encode an incoming BCD or
string of 023 as it were, i.e. not dropping the leading zero as 23.
Break ABI compatibility by changing the size and ordering of struct gprs_ra_id.
Ordering is changed because the canonical oder is {Mobile Country Code, Mobile
Network Code}, so have the mcc member first. Change size (and ordering) by
inserting a flag to indicate a three-digit MNC after the mnc member. ABI
compatibility cannot be maintained, since struct gprs_ra_id is a direct member
of structs bssgp_bvc_ctx and bssgp_paging_info, and even just adding a flag to
the end would cause ABI changes of those structs.
Add new API to set and read this additional flag to preserve leading zeros:
- gsm48_mcc_mnc_to_bcd2(), gsm48_mcc_mnc_from_bcd2() after
gsm48_mcc_mnc_to_bcd() and gsm48_mcc_mnc_from_bcd().
- gsm0808_create_layer3_aoip2() after gsm0808_create_layer3_aoip().
- gsm48_decode_lai2(), gsm48_generate_lai2() after
gsm48_decode_lai(), gsm48_generate_lai().
- The equivalent of gsm0808_create_layer3() for preserving leading zeros is
gsm0808_create_layer3_aoip2() with the scl argument passed as NULL; instead
of introducing a new shim function like gsm0808_create_layer3_2(), indicate
such in the API docs, only.
- gsm48_mnc_from_str() to encode leading zeros from string, useful for VTY
config parsing.
- gsm48_mnc_cmp() to compare MNC values including leading zeros.
- various osmo_*_name() functions. The amount and seeming duplication of these
may seem a bit overboard, but IMO they do make sense in this way. The root
reason is that the use of MCC and MNC is quite diverse throughout the osmocom
code base: in certain code, they are single uint16_t, in others they are
embedded in structs along with lac and rac; sometimes, all should be printed
in one go (repeatedly), in other cases (vty, ctrl) they are required singled
out. Without these functions, the formatting kind of ("%0*u", mnc_3_digits ?
3 : 2, mnc) would be duplicated all over our diverse repositories, or
printing MCC-MNC or RAI would otherwise end up to be more code.
In various log output, include the leading MNC zeros.
Mark one TODO in card_fs_sim.c, I am not sure how to communicate a leading zero
to/from a SIM card FS. The focus here is on the core network / BSS.
To indicate ABI incompatibility, bump libosmogsm and libosmogb LIBVERSIONs;
adjust debian files accordingly.
Implementation choices:
- The default behavior upon zero-initialization will be the mnc_3_digits flag
set to false, which yields exactly the previous behavior.
- I decided against packing the mnc with the mnc_3_digits field into a
sub-struct because it would enlarge this patch; plus, with a separate flag,
current code can decide when to start heeding leading zeros.
Change-Id: Id2240f7f518494c9df6c8bda52c0d5092f90f221
-----------------------------------------------------------------------
Summary of changes:
hooks/post-receive
--
An utility library for Open Source Mobile Communications
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "An utility library for Open Source Mobile Communications".
The branch, neels/mnc3 has been updated
discards ab26997fa3b8a999b18a4c4977fc049044a180a7 (commit)
discards a1fa6488ad0c02753a4d7026e90f23f3e31edd4f (commit)
discards a689ce7ff408b621809b0a96f3a722bcf7853b81 (commit)
discards c328958e74dee88b550b085f5a074be13fbc26fa (commit)
discards 67d34280264c954a18b12dc7861d7f27c277c577 (commit)
discards 5aa8115fa87b860a9920b5b709eb5bb7fb50d117 (commit)
discards 1e4a480d5b2d545ab191e66d5ca3d54f4cf247fe (commit)
discards 9b0f7c1d66c48bfec919b951c97357709ab1d029 (commit)
discards 901b5f9e6c6e256bb48cf0f8bb446a0a5683d100 (commit)
via 3d8879bfbcc3ff16ef955876a1a989d26fb692ba (commit)
via e08e9c479a3360b74c6fb947b706a43840acd639 (commit)
via 2aa1badcd17eafc7648ac6ada81d4fbfc724c00a (commit)
via 91892abac66e9bbf538f4453f452e67a54f876ee (commit)
via b7199612d6e2cce676cb099ac41c96a738494ba6 (commit)
via be4fbeaf8c61ddc2f496bb2ad520118b53c6f645 (commit)
via d5a577b043aab7d27608601ed751e8e17ec5457f (commit)
via b9fd7eba1558328802ae9dff79f708bd6ba7b10b (commit)
via c38b32dde94ae5547a11c4d59adb3510576300b0 (commit)
This update added new revisions after undoing existing revisions. That is
to say, the old revision is not a strict subset of the new revision. This
situation occurs when you --force push a change and generate a repository
containing something like this:
* -- * -- B -- O -- O -- O (ab26997fa3b8a999b18a4c4977fc049044a180a7)
\
N -- N -- N (3d8879bfbcc3ff16ef955876a1a989d26fb692ba)
When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
http://cgit.osmocom.org/libosmocore/commit/?id=3d8879bfbcc3ff16ef955876a1a9…
commit 3d8879bfbcc3ff16ef955876a1a989d26fb692ba
Author: Neels Hofmeyr <neels(a)hofmeyr.de>
Date: Tue Feb 20 15:14:14 2018 +0100
GSM_MNC_INVALID
Change-Id: Ieee7add0bd6d94cf84743a49794bbcd38561b72f
http://cgit.osmocom.org/libosmocore/commit/?id=e08e9c479a3360b74c6fb947b706…
commit e08e9c479a3360b74c6fb947b706a43840acd639
Author: Neels Hofmeyr <neels(a)hofmeyr.de>
Date: Tue Feb 20 21:38:00 2018 +0100
gsm: add gsm48_mnc_from_str() and gsm48_mnc_cmp(), for 3-digit MNC
gsm48_mnc_from_str() preserves leading zeros in the string and is useful for
VTY config parsing.
gsm48_mnc_cmp() will be used by osmo-sgsn.git
http://cgit.osmocom.org/libosmocore/commit/?id=2aa1badcd17eafc7648ac6ada81d…
commit 2aa1badcd17eafc7648ac6ada81d4fbfc724c00a
Author: Neels Hofmeyr <neels(a)hofmeyr.de>
Date: Tue Feb 20 22:20:42 2018 +0100
gsm0408_test: add test cases for MNC with leading zeros
Change-Id: I9b387e09293a6bbef84b9620ccf21ee2f9ec751c
http://cgit.osmocom.org/libosmocore/commit/?id=91892abac66e9bbf538f4453f452…
commit 91892abac66e9bbf538f4453f452e67a54f876ee
Author: Neels Hofmeyr <neels(a)hofmeyr.de>
Date: Tue Feb 20 22:19:56 2018 +0100
gsm0408_test: test new gsm48_{decode,generate}_lai2() functions
Change-Id: I4c8492b8055803d2857f1ef30aede088778b085b
http://cgit.osmocom.org/libosmocore/commit/?id=b7199612d6e2cce676cb099ac41c…
commit b7199612d6e2cce676cb099ac41c96a738494ba6
Author: Neels Hofmeyr <neels(a)hofmeyr.de>
Date: Tue Feb 20 15:12:23 2018 +0100
gsm0408_test: check for new mnc_3_digits flag
Note that on the input side, the 3-digits flag may be left false when the MNC
is >99 anyway. On the decoded side, the flag is set accurately.
Change-Id: I89765613d8c5bd939a6957f7443ac88475f1b93c
http://cgit.osmocom.org/libosmocore/commit/?id=be4fbeaf8c61ddc2f496bb2ad520…
commit be4fbeaf8c61ddc2f496bb2ad520118b53c6f645
Author: Neels Hofmeyr <neels(a)hofmeyr.de>
Date: Tue Feb 20 13:47:08 2018 +0100
implement support for 3-digit MNC with leading zeros
Enable representing three-digit MNC with leading zeros. The MNCs 23 and 023 are
actually different; so far we treated both as 23. Re-encode an incoming BCD or
string of 023 as it were, i.e. not dropping the leading zero as 23.
Break ABI compatibility by changing the size and ordering of struct gprs_ra_id.
Ordering is changed because the canonical oder is {Mobile Country Code, Mobile
Network Code}, so have the mcc member first. Change size (and ordering) by
inserting a flag to indicate a three-digit MNC after the mnc member. ABI
compatibility cannot be maintained, since struct gprs_ra_id is a direct member
of structs bssgp_bvc_ctx and bssgp_paging_info, and even just adding a flag to
the end would cause ABI changes of those structs.
Add new API to set and read this additional flag to preserve leading zeros:
- gsm48_mcc_mnc_to_bcd2(), gsm48_mcc_mnc_from_bcd2() after
gsm48_mcc_mnc_to_bcd() and gsm48_mcc_mnc_from_bcd().
- gsm0808_create_layer3_aoip2() after gsm0808_create_layer3_aoip().
- gsm48_decode_lai2(), gsm48_generate_lai2() after
gsm48_decode_lai(), gsm48_generate_lai().
- The equivalent of gsm0808_create_layer3() for preserving leading zeros is
gsm0808_create_layer3_aoip2() with the scl argument passed as NULL; instead
of introducing a new shim function like gsm0808_create_layer3_2(), indicate
such in the API docs, only.
- gsm48_mnc_from_str() to encode leading zeros from string, useful for VTY
config parsing.
- gsm48_mnc_cmp() to compare MNC values including leading zeros.
In various log output, include the leading MNC zeros.
Mark one TODO in card_fs_sim.c, I am not sure how to communicate a leading zero
to/from a SIM card FS. The focus here is on the core network / BSS.
To indicate ABI incompatibility, bump libosmogsm and libosmogb LIBVERSIONs;
adjust debian files accordingly.
Implementation choices:
- The default behavior upon zero-initialization will be the mnc_3_digits flag
set to false, which yields exactly the previous behavior.
- I decided against packing the mnc with the mnc_3_digits field into a
sub-struct because it would enlarge this patch; plus, with a separate flag,
current code can decide when to start heeding leading zeros.
Change-Id: Id2240f7f518494c9df6c8bda52c0d5092f90f221
http://cgit.osmocom.org/libosmocore/commit/?id=d5a577b043aab7d27608601ed751…
commit d5a577b043aab7d27608601ed751e8e17ec5457f
Author: Neels Hofmeyr <neels(a)hofmeyr.de>
Date: Tue Feb 20 21:48:07 2018 +0100
gsm0408_test: also test gsm48_generate_lai() and gsm48_decode_lai()
Change-Id: Idd6cee090464bc92b654332904a9a08edf16e5c9
http://cgit.osmocom.org/libosmocore/commit/?id=b9fd7eba1558328802ae9dff79f7…
commit b9fd7eba1558328802ae9dff79f708bd6ba7b10b
Author: Neels Hofmeyr <neels(a)hofmeyr.de>
Date: Tue Feb 20 15:14:03 2018 +0100
gsm0408_test: RA test: include min/max value cases
(Preparation for adding 3-digit MNC)
Change-Id: Ifbc167de0cc039858112677b8d0cd14a2c8af086
http://cgit.osmocom.org/libosmocore/commit/?id=c38b32dde94ae5547a11c4d59adb…
commit c38b32dde94ae5547a11c4d59adb3510576300b0
Author: Neels Hofmeyr <neels(a)hofmeyr.de>
Date: Tue Feb 20 15:13:18 2018 +0100
gsm0408_test: include BCD and leading zeros in test output
(Preparation for adding 3-digit MNC)
Change-Id: I7f8ae05fa3e4a6fc004212757b05ca8a14c9ef45
-----------------------------------------------------------------------
Summary of changes:
include/osmocom/gsm/gsm23003.h | 1 +
include/osmocom/gsm/gsm48.h | 10 +++-
src/gb/gprs_bssgp.c | 6 +-
src/gb/gprs_bssgp_vty.c | 9 +--
src/gsm/gsm48.c | 79 ++++++++++++++++++++++++
src/gsm/libosmogsm.map | 7 +++
tests/gsm0408/gsm0408_test.c | 45 +++++++-------
tests/gsm0408/gsm0408_test.ok | 132 ++++++++++++++++++++---------------------
8 files changed, 186 insertions(+), 103 deletions(-)
hooks/post-receive
--
An utility library for Open Source Mobile Communications
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "UNNAMED PROJECT".
The branch, neels/mnc3 has been updated
discards 622c7c4090118f7f75a38227eacae0e5fec46a31 (commit)
via 676894a5c957f7a730e99f75246a688a4ef070cb (commit)
via 731e2bb328f6b0d739fa21913eb30cff8a46c70c (commit)
via 77988d469d5cd0d876188a829b93890049cc6830 (commit)
via 847ed9f8cd4fd95776052c8d1934813f0ea2c813 (commit)
This update added new revisions after undoing existing revisions. That is
to say, the old revision is not a strict subset of the new revision. This
situation occurs when you --force push a change and generate a repository
containing something like this:
* -- * -- B -- O -- O -- O (622c7c4090118f7f75a38227eacae0e5fec46a31)
\
N -- N -- N (676894a5c957f7a730e99f75246a688a4ef070cb)
When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
http://cgit.osmocom.org/osmo-pcu/commit/?id=676894a5c957f7a730e99f75246a688…
commit 676894a5c957f7a730e99f75246a688a4ef070cb
Author: Neels Hofmeyr <neels(a)hofmeyr.de>
Date: Wed Feb 21 00:39:07 2018 +0100
implement support for 3-digit MNC with leading zeros
-----------------------------------------------------------------------
Summary of changes:
src/gprs_rlcmac_ts_alloc.cpp | 303 ++++++++++++-------------
src/mslot_class.c | 43 ++++
src/mslot_class.h | 4 +
src/pdch.cpp | 16 +-
src/tbf.cpp | 82 +++++--
src/tbf.h | 21 +-
src/tbf_dl.cpp | 2 +-
src/tbf_ul.cpp | 2 +-
tests/alloc/MslotTest.cpp | 10 +
tests/alloc/MslotTest.ok | 513 +++++++++++++++++++++++++++++++++++++++++++
tests/tbf/TbfTest.err | 2 +-
11 files changed, 798 insertions(+), 200 deletions(-)
hooks/post-receive
--
UNNAMED PROJECT
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "OpenBTS' transceiver retro-fit".
The branch, master has been updated
via c92dad32dd403d84617236e98db892d7d285cd35 (commit)
from 61837c0420781b601dd7fe8e62800b75869277db (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
http://cgit.osmocom.org/osmo-trx/commit/?id=c92dad32dd403d84617236e98db892d…
commit c92dad32dd403d84617236e98db892d7d285cd35
Author: Pau Espin Pedrol <pespin(a)sysmocom.de>
Date: Tue Feb 20 13:22:58 2018 +0100
configure.ac: Check for pkg-config
Change-Id: I1a851181a99f2f35ea4ff1b38c7afe27a04e5f18
-----------------------------------------------------------------------
Summary of changes:
configure.ac | 7 +++++++
1 file changed, 7 insertions(+)
hooks/post-receive
--
OpenBTS' transceiver retro-fit
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "UNNAMED PROJECT".
The branch, master has been updated
via 731e2bb328f6b0d739fa21913eb30cff8a46c70c (commit)
via 77988d469d5cd0d876188a829b93890049cc6830 (commit)
from 847ed9f8cd4fd95776052c8d1934813f0ea2c813 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
http://cgit.osmocom.org/osmo-pcu/commit/?id=731e2bb328f6b0d739fa21913eb30cf…
commit 731e2bb328f6b0d739fa21913eb30cff8a46c70c
Author: Max <msuraev(a)sysmocom.de>
Date: Mon Feb 5 16:15:30 2018 +0100
Simplify TS alloc: move slot check into functions
Move timeslot applicability check outside of nested for loop into
separate functions and document them. Add corresponding tests.
This allows us to clarify types used in TS-related computations.
Change-Id: Ic39e848da47dc11357782362fdf6206d2c1457c2
Related: OS#2282
http://cgit.osmocom.org/osmo-pcu/commit/?id=77988d469d5cd0d876188a829b93890…
commit 77988d469d5cd0d876188a829b93890049cc6830
Author: Max <msuraev(a)sysmocom.de>
Date: Mon Feb 19 18:00:38 2018 +0100
Simplify TS alloc: move slot assignment
Move into separate functions:
* move timeslot reservation
* move UL timeslot assignment
* move DL timeslot assignment
Change-Id: I64cf78c5cfc78664766f9769dd5cde632dab92b0
Related: OS#2282
-----------------------------------------------------------------------
Summary of changes:
src/gprs_rlcmac_ts_alloc.cpp | 303 ++++++++++++-------------
src/mslot_class.c | 43 ++++
src/mslot_class.h | 4 +
tests/alloc/MslotTest.cpp | 10 +
tests/alloc/MslotTest.ok | 513 +++++++++++++++++++++++++++++++++++++++++++
tests/tbf/TbfTest.err | 2 +-
6 files changed, 710 insertions(+), 165 deletions(-)
hooks/post-receive
--
UNNAMED PROJECT
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "UNNAMED PROJECT".
The branch, master has been updated
via 847ed9f8cd4fd95776052c8d1934813f0ea2c813 (commit)
from 4da385998acedd83e2f2bb029340d3c1ce710faf (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
http://cgit.osmocom.org/osmo-pcu/commit/?id=847ed9f8cd4fd95776052c8d1934813…
commit 847ed9f8cd4fd95776052c8d1934813f0ea2c813
Author: Max <msuraev(a)sysmocom.de>
Date: Tue Feb 20 18:16:11 2018 +0100
TBF: make network counters internal
* store N310* counters in shared array similar to corresponding timers
* add functions to increment/reset counters
This avoids direct access to TBF counters from PDCH.
Change-Id: I8ffff9c7186f74bde7e6ac5f6e98f0b3e4c35274
Related: OS#1539
-----------------------------------------------------------------------
Summary of changes:
src/pdch.cpp | 16 ++++++------
src/tbf.cpp | 82 +++++++++++++++++++++++++++++++++++++++++++++-------------
src/tbf.h | 21 ++++++++++-----
src/tbf_dl.cpp | 2 +-
src/tbf_ul.cpp | 2 +-
5 files changed, 88 insertions(+), 35 deletions(-)
hooks/post-receive
--
UNNAMED PROJECT