osmocom-commitlog

osmocom-commitlog@lists.osmocom.org

7948 discussions

libosmocore.git branch neels/mnc3 updated. 0.10.2-187-gfc05404a
by gitosis＠osmocom.org 27 Feb '18

27 Feb '18

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 a5bae465eafd50657c4e5314d7e14477f23a0e48 (commit) discards b042ef1252d25d6e6513456d56df029472f30cd1 (commit) discards a4f39f52220f6ce560425860da2e64a9fc842d20 (commit) discards 1d118e28c50127d88b8445b9b8c1b4d349dc4ad9 (commit) discards 6c0204d57ff0df3b06a28256ee29152702ebb67f (commit) discards 913d8503a3f705ffb43f43418c245d52a5b1d481 (commit) via fc05404aeb9edb9a6b4b29fcc743d5d395b8be55 (commit) via c64b2c2d196913fde2ae97d748a4276c2c265807 (commit) via 064148308ca41b986613c4764d8032fa5e4fa020 (commit) via 9372368c5b92ca3956cc8370b5730db50aa678d5 (commit) via 11d9c3a3cb0286f2980a17d05642b9d5db95fb4e (commit) via ed6255ecdddd46e087a700cb3d46948c19822773 (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 (a5bae465eafd50657c4e5314d7e14477f23a0e48) \ N -- N -- N (fc05404aeb9edb9a6b4b29fcc743d5d395b8be55) 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=fc05404aeb9edb9a6b4b29fcc743… commit fc05404aeb9edb9a6b4b29fcc743d5d395b8be55 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=c64b2c2d196913fde2ae97d748a4… commit c64b2c2d196913fde2ae97d748a4276c2c265807 Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Tue Feb 20 21:38:00 2018 +0100 gsm: add osmo_mnc_from_str(), osmo_mnc_cmp(), osmo_plmn_cmp() for 3-digit MNC osmo_mnc_from_str() preserves leading zeros in the string and is useful for VTY config parsing (osmo-bsc, osmo-msc, osmo-sgsn, osmo-pcu). osmo_{plmn,mnc}_cmp() takes care of the slight intricacy of ignoring the 3-digit flag if the MNC is anyway >99. Will be used by osmo-sgsn.git and osmo-bsc.git. (All current users just care about identical MNC, but a proper cmp doesn't hurt.) Change-Id: Ib7176b1d65a03b76f41f94bc9d3293a8a07d24c6 http://cgit.osmocom.org/libosmocore/commit/?id=064148308ca41b986613c4764d80… commit 064148308ca41b986613c4764d8032fa5e4fa020 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=9372368c5b92ca3956cc8370b573… commit 9372368c5b92ca3956cc8370b5730db50aa678d5 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=11d9c3a3cb0286f2980a17d05642… commit 11d9c3a3cb0286f2980a17d05642b9d5db95fb4e 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=ed6255ecdddd46e087a700cb3d46… commit ed6255ecdddd46e087a700cb3d46948c19822773 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 structs gprs_ra_id, osmo_plmn_id, osmo_cell_global_id, ... by adding an mnc_3_digits flag. Change ordering in gprs_ra_id because the canonical oder is {Mobile Country Code, Mobile Network Code}, so have the mcc member first. ABI compatibility cannot be maintained for struct gprs_ra_id, since it 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. Similarly, osmo_plmn_id is a direct member of osmo_location_area_id, and so forth. Add new API to set and read this additional flag to preserve leading zeros: - osmo_plmn_to_bcd(), osmo_plmn_from_bcd() after gsm48_mcc_mnc_to_bcd() and gsm48_mcc_mnc_from_bcd(). - osmo_decode_lai(), osmo_generate_lai() after gsm48_decode_lai(), gsm48_generate_lai(). - gsm0808_create_layer3_2() after gsm0808_create_layer3() and gsm0808_create_layer3_aoip(). - various osmo_*_name() functions in gsm23003.h (osmo_rai_name() still in gsm48.h close to struct gprs_ra_id definition). The amount and duplication of these may seem a bit overboard, but IMO they do make sense in this way. Though most code will soon see patches unifying the data structures used, in some cases (vty, ctrl) they are required singled out. Without these functions, the formatting ("%0*u", mnc_3_digits ? 3 : 2, mnc) would be duplicated all over our diverse repositories. 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 immediately break all builds of dependent projects: it would require immediate merging of numerous patches in other repositories, and it would make compiling older code against a newer libosmocore unneccessarily hard. Change-Id: Id2240f7f518494c9df6c8bda52c0d5092f90f221 ----------------------------------------------------------------------- Summary of changes: include/osmocom/gsm/gsm23003.h | 14 +++ include/osmocom/gsm/gsm48.h | 16 +-- src/gsm/gsm23003.c | 204 +++++++++++++++++++++++++++++++++++++ src/gsm/gsm48.c | 226 +++-------------------------------------- 4 files changed, 232 insertions(+), 228 deletions(-) hooks/post-receive -- An utility library for Open Source Mobile Communications

1 0

osmo-trx.git branch master updated. 0.2.0-54-g3da1f83
by gitosis＠osmocom.org 27 Feb '18

27 Feb '18

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 3da1f8352e337fb032bf7a58c2909d3ba918e237 (commit) via 5ea1817dc299611808532eda489981f09f87cba3 (commit) from 49d42e979eb08cef124e8ceab7d402bed204c015 (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=3da1f8352e337fb032bf7a58c2909d3… commit 3da1f8352e337fb032bf7a58c2909d3ba918e237 Author: Pau Espin Pedrol <pespin(a)sysmocom.de> Date: Tue Feb 20 20:01:10 2018 +0100 Logger: Use libosmocore logging system We still need an intermediate class Logger due to osmo-trx being multi-threaded and requiring to have a lock to use libosmocore, which is not thread safe. Change-Id: I30baac89f53e927f8699d0586b43cccf88ecd493 http://cgit.osmocom.org/osmo-trx/commit/?id=5ea1817dc299611808532eda489981f… commit 5ea1817dc299611808532eda489981f09f87cba3 Author: Pau Espin Pedrol <pespin(a)sysmocom.de> Date: Tue Feb 20 16:48:15 2018 +0100 Add initial support for logging, vty, ctrl Up to this point, the logging system, vty and ctrl are initialized and can be used fine, though they don't have a lot of use yet. Depends on libosmocore Change-Id Ib79cdb62d45d8c78445c7b064e58eb7e9faeccf9 Related: OS#2184 Change-Id: I08982c37b4f873966304b3cfb38a10ee86eb3dad ----------------------------------------------------------------------- Summary of changes: CommonLibs/Logger.cpp | 73 +------------------ CommonLibs/Logger.h | 66 +++++++----------- CommonLibs/Makefile.am | 11 ++- CommonLibs/debug.c | 18 +++++ CommonLibs/debug.h | 8 +++ CommonLibs/trx_vty.c | 162 +++++++++++++++++++++++++++++++++++++++++++ CommonLibs/trx_vty.h | 13 ++++ Transceiver52M/Makefile.am | 6 +- Transceiver52M/osmo-trx.cpp | 69 ++++++++++++++---- configure.ac | 3 + tests/CommonLibs/LogTest.cpp | 44 ++++++++---- tests/CommonLibs/LogTest.err | 27 +------- tests/CommonLibs/LogTest.ok | 29 -------- tests/CommonLibs/Makefile.am | 3 +- 14 files changed, 335 insertions(+), 197 deletions(-) create mode 100644 CommonLibs/debug.c create mode 100644 CommonLibs/debug.h create mode 100644 CommonLibs/trx_vty.c create mode 100644 CommonLibs/trx_vty.h hooks/post-receive -- OpenBTS' transceiver retro-fit

1 0

osmo-trx.git branch master updated. 0.2.0-52-g49d42e9
by gitosis＠osmocom.org 27 Feb '18

27 Feb '18

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 49d42e979eb08cef124e8ceab7d402bed204c015 (commit) from 3a3b2207517eaa29dc51e971ee795017aa333047 (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=49d42e979eb08cef124e8ceab7d402b… commit 49d42e979eb08cef124e8ceab7d402bed204c015 Author: Pau Espin Pedrol <pespin(a)sysmocom.de> Date: Mon Feb 26 00:56:10 2018 +0100 debian: Depend on libtalloc and libosmocore Change-Id: If4bf03d164e9d19a8a21399a2c74b2984c48cc70 ----------------------------------------------------------------------- Summary of changes: debian/control | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) hooks/post-receive -- OpenBTS' transceiver retro-fit

1 0

osmo-iuh.git branch neels/mnc3 updated. 0.2.0-55-g99d6481
by gitosis＠osmocom.org 27 Feb '18

27 Feb '18

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 updated discards f3652e6c5c169c47cdc8b3883309cf477d245860 (commit) via 99d6481f7aff32ebe6feb49a9e2ad8f76963e62d (commit) via c964a2cfa1b08e5bbda5d721a7a0095d26b53791 (commit) via e1c01a02624b12a5c6396d47902482fa97217b23 (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 (f3652e6c5c169c47cdc8b3883309cf477d245860) \ N -- N -- N (99d6481f7aff32ebe6feb49a9e2ad8f76963e62d) 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-iuh/commit/?id=99d6481f7aff32ebe6feb49a9e2ad8f… commit 99d6481f7aff32ebe6feb49a9e2ad8f76963e62d 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 ----------------------------------------------------------------------- Summary of changes: contrib/jenkins.sh | 2 +- include/osmocom/iuh/hnbgw.h | 6 ++++- src/hnbgw.c | 16 +++++++++---- src/hnbgw_hnbap.c | 57 ++++++++++++++++++++++++++++++++++++++++++++- src/tests/hnb-test.c | 8 +++---- 5 files changed, 78 insertions(+), 11 deletions(-) hooks/post-receive -- Osmocom code for Iuh interface

1 0

libosmocore.git branch neels/mnc3 updated. 0.10.2-187-ga5bae465
by gitosis＠osmocom.org 27 Feb '18

27 Feb '18

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 2b389ddd9ab23ce8e928def27e942a43dd4af4df (commit) discards 7484778e18a650ebc77c55ebd229f96ad302307f (commit) discards 322b4deae2799159130caffba64e7d204f9eb9ed (commit) discards 14e995070e632f626b41eb73f87d983ce9141d11 (commit) discards aa8e052ef9538c43940179384e85dda0ba1bc933 (commit) discards 487f9d8d9f41e5dc3c184b7bd1d71128fab8b8b9 (commit) via a5bae465eafd50657c4e5314d7e14477f23a0e48 (commit) via b042ef1252d25d6e6513456d56df029472f30cd1 (commit) via a4f39f52220f6ce560425860da2e64a9fc842d20 (commit) via 1d118e28c50127d88b8445b9b8c1b4d349dc4ad9 (commit) via 6c0204d57ff0df3b06a28256ee29152702ebb67f (commit) via 913d8503a3f705ffb43f43418c245d52a5b1d481 (commit) via cc81722736c9bd2a0a16cf2247eda6b82074a198 (commit) via 888dc7d31aa4b39ba8e08884c39be1c09c92f82a (commit) via 6950b191e84c73687f9dc77462ff66cbeaec5686 (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 (2b389ddd9ab23ce8e928def27e942a43dd4af4df) \ N -- N -- N (a5bae465eafd50657c4e5314d7e14477f23a0e48) 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=a5bae465eafd50657c4e5314d7e1… commit a5bae465eafd50657c4e5314d7e14477f23a0e48 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=b042ef1252d25d6e6513456d56df… commit b042ef1252d25d6e6513456d56df029472f30cd1 Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Tue Feb 20 21:38:00 2018 +0100 gsm: add osmo_mnc_from_str(), osmo_mnc_cmp(), osmo_plmn_cmp() for 3-digit MNC osmo_mnc_from_str() preserves leading zeros in the string and is useful for VTY config parsing (osmo-bsc, osmo-msc, osmo-sgsn, osmo-pcu). osmo_{plmn,mnc}_cmp() takes care of the slight intricacy of ignoring the 3-digit flag if the MNC is anyway >99. Will be used by osmo-sgsn.git and osmo-bsc.git. (All current users just care about identical MNC, but a proper cmp doesn't hurt.) Change-Id: Ib7176b1d65a03b76f41f94bc9d3293a8a07d24c6 http://cgit.osmocom.org/libosmocore/commit/?id=a4f39f52220f6ce560425860da2e… commit a4f39f52220f6ce560425860da2e64a9fc842d20 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=1d118e28c50127d88b8445b9b8c1… commit 1d118e28c50127d88b8445b9b8c1b4d349dc4ad9 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=6c0204d57ff0df3b06a28256ee29… commit 6c0204d57ff0df3b06a28256ee29152702ebb67f 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=913d8503a3f705ffb43f43418c24… commit 913d8503a3f705ffb43f43418c245d52a5b1d481 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 structs gprs_ra_id, osmo_plmn_id, osmo_cell_global_id, ... by adding an mnc_3_digits flag. Change ordering in gprs_ra_id because the canonical oder is {Mobile Country Code, Mobile Network Code}, so have the mcc member first. ABI compatibility cannot be maintained for struct gprs_ra_id, since it 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. Similarly, osmo_plmn_id is a direct member of osmo_location_area_id, and so forth. Add new API to set and read this additional flag to preserve leading zeros: - osmo_plmn_to_bcd(), osmo_plmn_from_bcd() after gsm48_mcc_mnc_to_bcd() and gsm48_mcc_mnc_from_bcd(). - gsm0808_create_layer3_aoip2() after gsm0808_create_layer3_aoip(). - osmo_decode_lai(), osmo_generate_lai() after gsm48_decode_lai(), gsm48_generate_lai(). - gsm0808_create_layer3_2() after gsm0808_create_layer3() and gsm0808_create_layer3_aoip(). - various osmo_*_name() functions. The amount and 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 ("%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 immediately break all builds of dependent projects: it would require immediate merging of numerous patches in other repositories, and it would make compiling older code against a newer libosmocore unneccessarily hard. Change-Id: Id2240f7f518494c9df6c8bda52c0d5092f90f221 ----------------------------------------------------------------------- Summary of changes: include/osmocom/coding/gsm0503_coding.h | 10 +- include/osmocom/gsm/gsm0808.h | 8 +- include/osmocom/gsm/gsm23003.h | 2 +- include/osmocom/gsm/gsm48.h | 23 +++-- src/coding/gsm0503_coding.c | 46 ++++++++- src/coding/libosmocoding.map | 2 + src/fsm.c | 2 + src/gsm/gsm0808.c | 36 ++++---- src/gsm/gsm48.c | 159 ++++++++++++++++++-------------- src/gsm/libosmogsm.map | 22 ++--- src/vty/fsm_vty.c | 12 ++- tests/coding/coding_test.c | 4 +- tests/fsm/fsm_test.c | 7 ++ tests/fsm/fsm_test.err | 8 +- tests/gsm0408/gsm0408_test.c | 39 ++++---- tests/gsm0408/gsm0408_test.ok | 44 ++++----- 16 files changed, 256 insertions(+), 168 deletions(-) hooks/post-receive -- An utility library for Open Source Mobile Communications

1 0

osmo-bts.git branch neels/mnc3 updated. 0.7.0-121-gc7621ce
by gitosis＠osmocom.org 27 Feb '18

27 Feb '18

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 8fc29594c09b00680d76afbebc40d2c8ef9fea02 (commit) via c7621ce223cd28510f253e8ad580e1058da3be97 (commit) via 0d6c3e811007be828207c0f69ff4e2dddeeb64db (commit) via 3a80a56b9befe5f47cae5e4210ebc81d343b04f8 (commit) via 6381900677001088b8f2a74905cd3ac1994f33ba (commit) via bcc20a871c61c9ab6188d6abe183dbced7ac241f (commit) via 591c8993e9533da419fe1d995748b545a374416f (commit) via f100992a20ea1f833f44c8f97efcd58cd18016e0 (commit) via 49a8969bd6ff2cf89984a101677c5f09191a48ea (commit) via de3b4a248e46b5bed1cce20774dceafc74c74073 (commit) via 989f779cfcaa89a6e1d979a3ba7d5ab8b16613b6 (commit) via 9c4ea743fdf0501be64bc09f8c6ae982da21627c (commit) via 756bfca599630ee64393d877343a9034416d20c3 (commit) via 681be20a8c32331dcb44db2ec0e99294f1eb89ba (commit) via 42c50727b50c3efd45654504dfcaa9eb3885a7da (commit) via d3875a8fcbf8caf5e9c0180c4f9672d2cc9eac9b (commit) via 84de287da02f0c4392a8b1d482ee5d4d3bb4a8ff (commit) via d7f8a1c16e8a6337539b5dae291f435cf0cf426e (commit) via c1135015135f9c664dd6735f30fc94772c0d9ce8 (commit) via 19da7fdea8912831b19d9aeed51cd2226f342283 (commit) via 6e92255cc7694ad02094036a87aba46c6d8ec950 (commit) via fc169ba7bba831f00de3490c49d0e2583c29db8a (commit) via 815ff00d239b5b20bb077e210b533c7ff32cb102 (commit) via aa9ce821a09ebbe95364926a54aed6871d59d026 (commit) via 1effad1004d203c755b475ea6ef26586d45153f0 (commit) via 2de8f6c7ec3d7a2fd1520c09a5b4ba2a4a5b9248 (commit) via b82b81b256b7e98872065600fc4e0daf6c0d430a (commit) via a38deee5f1b714336cec253a730a6e3c254c64d2 (commit) via 232f53adf0e7ea3211bdfe60f7c3b629a9648fa1 (commit) via ac0254c000d1eaad9a48a11922d538cd53f622bd (commit) via 6eb37525112be96aa9be5ae91973894e22392aa4 (commit) via 22c07d1f1f174a8eb64edfe668c694129e929394 (commit) via 04719d19b94b52a915d149ff553385e857ec8441 (commit) via a4bca115557feb0268e6cfda30238ded16328ae6 (commit) via b93748a1707fa4e20c3a8c3a241dd9e3fb03ea87 (commit) via bfe9af4ae1c1d72a5a94546093913083a0eaeda8 (commit) via e0bfd675d1356a349df9674f78723ff33ed6b634 (commit) via 4847a1688ba6fee8e5b44c25317c2e221b4b0ae0 (commit) via 5e60186bec02e558a1f08bac1683c73a8f70b6c8 (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 (8fc29594c09b00680d76afbebc40d2c8ef9fea02) \ N -- N -- N (c7621ce223cd28510f253e8ad580e1058da3be97) 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=c7621ce223cd28510f253e8ad580e10… commit c7621ce223cd28510f253e8ad580e1058da3be97 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: include/osmo-bts/bts.h | 19 +- include/osmo-bts/gsm_data.h | 8 +- include/osmo-bts/gsm_data_shared.h | 10 +- include/osmo-bts/logging.h | 12 + include/osmo-bts/measurement.h | 2 +- include/osmo-bts/scheduler.h | 33 + src/common/Makefile.am | 2 +- src/common/bts.c | 89 ++- src/common/gsm_data_shared.c | 5 + src/common/l1sap.c | 84 +-- src/common/load_indication.c | 11 +- src/common/main.c | 1 + src/common/measurement.c | 191 +++-- src/common/oml.c | 4 +- src/common/paging.c | 37 +- src/common/rsl.c | 293 +++++--- src/common/scheduler.c | 795 +-------------------- src/common/{scheduler.c => scheduler_mframe.c} | 951 +------------------------ src/common/vty.c | 21 + src/osmo-bts-litecell15/l1_if.c | 40 +- src/osmo-bts-litecell15/main.c | 6 + src/osmo-bts-litecell15/tch.c | 17 +- src/osmo-bts-octphy/l1_if.c | 93 ++- src/osmo-bts-octphy/l1_tch.c | 16 +- src/osmo-bts-sysmo/l1_if.c | 28 +- src/osmo-bts-sysmo/main.c | 17 +- src/osmo-bts-sysmo/tch.c | 14 +- src/osmo-bts-trx/Makefile.am | 2 +- src/osmo-bts-trx/l1_if.c | 2 +- src/osmo-bts-trx/main.c | 17 +- src/osmo-bts-virtual/Makefile.am | 2 +- src/osmo-bts-virtual/l1_if.c | 30 +- src/osmo-bts-virtual/main.c | 7 + src/osmo-bts-virtual/scheduler_virtbts.c | 107 ++- src/osmo-bts-virtual/virtual_um.c | 5 + tests/misc/misc_test.c | 30 +- 36 files changed, 831 insertions(+), 2170 deletions(-) copy src/common/{scheduler.c => scheduler_mframe.c} (68%) hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)

1 0

osmocom-bb.git branch fixeria/trx updated. osmocon_v0.0.0-2024-gf3541369
by gitosis＠osmocom.org 27 Feb '18

27 Feb '18

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 "The Open Source GSM Base Band stack". The branch, fixeria/trx has been updated via f35413691db5a78640a05d22586a03a7badcea62 (commit) via 615faadcfb28e4f92105ab0336ef32aa5c8420c1 (commit) via 24e30142aa51aa070e83e3c6b339662d5c038f12 (commit) via 23446011afef95c4e83cbce8dfec736831878563 (commit) via e5480d2c2bc703ed1b387df753220506db2aceec (commit) from 05ea7248f8e6c1aed7665efa82eeb92264027f86 (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/osmocom-bb/commit/?id=f35413691db5a78640a05d22586a0… commit f35413691db5a78640a05d22586a03a7badcea62 Author: Vadim Yanitskiy <axilirator(a)gmail.com> Date: Tue Feb 27 07:00:45 2018 +0700 fake_trx/burst_fwd.py: use DATAMSG transformation API As the DATAMSG classes were introduced, let's use them. This approach abstracts one from dealing with raw bytes. Also, now BurstForwarder randomizes both RSSI and ToA values, as this feature is supported from-the-box by the DATAMSG_TRX2L1. Change-Id: Ib15018eab749150e244914dab4b6e433ce0c9209 http://cgit.osmocom.org/osmocom-bb/commit/?id=615faadcfb28e4f92105ab0336ef3… commit 615faadcfb28e4f92105ab0336ef32aa5c8420c1 Author: Vadim Yanitskiy <axilirator(a)gmail.com> Date: Tue Feb 27 06:46:15 2018 +0700 fake_trx/data_msg.py: implement message transformation API This change introduces two new methods, which allow to perform L12TRX <-> TRX2L1 message type transformations. Change-Id: Ic99cf74baa1864bf20a8fc0fc025604bc160084c http://cgit.osmocom.org/osmocom-bb/commit/?id=24e30142aa51aa070e83e3c6b3396… commit 24e30142aa51aa070e83e3c6b339662d5c038f12 Author: Vadim Yanitskiy <axilirator(a)gmail.com> Date: Tue Feb 27 04:57:58 2018 +0700 fake_trx/udp_link.py: set SO_REUSEADDR socket option Setting this option allows one to reuse existing connections, for example, by injecting CTRL commands or DATA bursts into existing connections between fake_trx.py and trxcon. Change-Id: I0882c76affa9a668a12d10967081054d2b666ed1 http://cgit.osmocom.org/osmocom-bb/commit/?id=23446011afef95c4e83cbce8dfec7… commit 23446011afef95c4e83cbce8dfec736831878563 Author: Vadim Yanitskiy <axilirator(a)gmail.com> Date: Tue Feb 27 04:50:28 2018 +0700 fake_trx/udp_link.py: drop useless UDPLink.loop() API So far, this API is not used anywhere. Let's drop it. Change-Id: I87ea2436f0b6bbeb62fe17700af48a048be143bb http://cgit.osmocom.org/osmocom-bb/commit/?id=e5480d2c2bc703ed1b387df753220… commit e5480d2c2bc703ed1b387df753220506db2aceec Author: Vadim Yanitskiy <axilirator(a)gmail.com> Date: Tue Feb 27 04:40:28 2018 +0700 fake_trx/udp_link.py: close socket in destructor Previously it was required to call the UDPLink.shutdown() method manually in order to close a socket. Let's do this automatically using the destructor of UDPLink. Change-Id: I59c3dc61ec58cd9effeb789947d28fd602ca91f4 ----------------------------------------------------------------------- Summary of changes: src/target/fake_trx/burst_fwd.py | 83 +++++++++++++++++++++++++++++--------- src/target/fake_trx/burst_gen.py | 6 --- src/target/fake_trx/burst_send.py | 7 ---- src/target/fake_trx/clck_gen.py | 1 - src/target/fake_trx/ctrl_cmd.py | 1 - src/target/fake_trx/ctrl_if_bb.py | 4 -- src/target/fake_trx/ctrl_if_bts.py | 4 -- src/target/fake_trx/data_msg.py | 37 +++++++++++++++++ src/target/fake_trx/fake_trx.py | 12 ------ src/target/fake_trx/udp_link.py | 17 ++------ 10 files changed, 105 insertions(+), 67 deletions(-) hooks/post-receive -- The Open Source GSM Base Band stack

1 0

libosmocore.git branch neels/mnc3 updated. 0.10.2-184-g2b389ddd
by gitosis＠osmocom.org 27 Feb '18

27 Feb '18

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 4615bd65427d8bd72caffb3da93f1b8bcb09d107 (commit) discards 58c904774e33cd1c69217f000df16f7b3d739a03 (commit) discards b834794958c3889ab963df046c780be828b44159 (commit) discards d99e40f3e8da67576e3400592825283022720fce (commit) discards e228f70c14acbddc474571db10df72c16c567786 (commit) discards f4f141ef4315968f9f333ceb1d725fb54b33a5d2 (commit) via 2b389ddd9ab23ce8e928def27e942a43dd4af4df (commit) via 7484778e18a650ebc77c55ebd229f96ad302307f (commit) via 322b4deae2799159130caffba64e7d204f9eb9ed (commit) via 14e995070e632f626b41eb73f87d983ce9141d11 (commit) via aa8e052ef9538c43940179384e85dda0ba1bc933 (commit) via 487f9d8d9f41e5dc3c184b7bd1d71128fab8b8b9 (commit) via 175a4ae93aaf1068b61041dca12962059d65ed55 (commit) via 218c4de84f6d94a882e3a945332f53732bf2e134 (commit) via 92decf2aa916353564a9dabe6871ab00e0f06a80 (commit) via 98a7a2646bcb561b9f55b4096a0d672d4ed89c87 (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 (4615bd65427d8bd72caffb3da93f1b8bcb09d107) \ N -- N -- N (2b389ddd9ab23ce8e928def27e942a43dd4af4df) 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=2b389ddd9ab23ce8e928def27e94… commit 2b389ddd9ab23ce8e928def27e942a43dd4af4df 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=7484778e18a650ebc77c55ebd229… commit 7484778e18a650ebc77c55ebd229f96ad302307f 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 (osmo-bsc, osmo-msc, osmo-sgsn, osmo-pcu). gsm48_mnc_cmp() takes care of the slight intricacy of ignoring the 3-digit flag if the MNC is anyway >99. Will be used by osmo-sgsn.git and osmo-bsc.git. (All current users just care about identical MNC, but a proper cmp doesn't hurt.) Change-Id: Ib7176b1d65a03b76f41f94bc9d3293a8a07d24c6 http://cgit.osmocom.org/libosmocore/commit/?id=322b4deae2799159130caffba64e… commit 322b4deae2799159130caffba64e7d204f9eb9ed 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=14e995070e632f626b41eb73f87d… commit 14e995070e632f626b41eb73f87d983ce9141d11 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=aa8e052ef9538c43940179384e85… commit aa8e052ef9538c43940179384e85dda0ba1bc933 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=487f9d8d9f41e5dc3c184b7bd1d7… commit 487f9d8d9f41e5dc3c184b7bd1d71128fab8b8b9 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: include/osmocom/core/rate_ctr.h | 9 +++++++++ include/osmocom/ctrl/ports.h | 3 +++ include/osmocom/gsm/gsm48.h | 1 - include/osmocom/vty/ports.h | 2 ++ src/gsm/gsm48.c | 16 ---------------- src/gsm/libosmogsm.map | 1 - src/vty/fsm_vty.c | 12 ++++++++++++ 7 files changed, 26 insertions(+), 18 deletions(-) hooks/post-receive -- An utility library for Open Source Mobile Communications

1 0

libosmocore.git branch master updated. 0.10.2-181-gcc817227
by gitosis＠osmocom.org 26 Feb '18

26 Feb '18

1 0

libosmocore.git branch master updated. 0.10.2-180-g888dc7d3
by gitosis＠osmocom.org 26 Feb '18

26 Feb '18

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 888dc7d31aa4b39ba8e08884c39be1c09c92f82a (commit) from 6950b191e84c73687f9dc77462ff66cbeaec5686 (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/libosmocore/commit/?id=888dc7d31aa4b39ba8e08884c39b… commit 888dc7d31aa4b39ba8e08884c39be1c09c92f82a Author: Stefan Sperling <ssperling(a)sysmocom.de> Date: Mon Feb 26 19:17:02 2018 +0100 print BIG FAT ERROR message if osmo_fsm lacks event names Event names are displayed in VTY commands so all FSM should have them. Print an error message if an FSM is registered without event names. We could also return an error code, however at present no caller checks the return value of osmo_fsm_register() so this would be pointless. Add event names to the test FSM and update expected output accordingly. Change-Id: I08b100d62b5c50bf025ef87d31ea39072539cf37 Related: OS#3008 ----------------------------------------------------------------------- Summary of changes: src/fsm.c | 2 ++ tests/fsm/fsm_test.c | 7 +++++++ tests/fsm/fsm_test.err | 8 ++++---- 3 files changed, 13 insertions(+), 4 deletions(-) hooks/post-receive -- An utility library for Open Source Mobile Communications

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

osmocom-commitlog