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/osmocom-commitlog@lists.osmocom.org/.
gitosis at osmocom.org gitosis at osmocom.orgThis 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=fc05404aeb9edb9a6b4b29fcc743d5d395b8be55
commit fc05404aeb9edb9a6b4b29fcc743d5d395b8be55
Author: Neels Hofmeyr <neels at 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=c64b2c2d196913fde2ae97d748a4276c2c265807
commit c64b2c2d196913fde2ae97d748a4276c2c265807
Author: Neels Hofmeyr <neels at 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=064148308ca41b986613c4764d8032fa5e4fa020
commit 064148308ca41b986613c4764d8032fa5e4fa020
Author: Neels Hofmeyr <neels at 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=9372368c5b92ca3956cc8370b5730db50aa678d5
commit 9372368c5b92ca3956cc8370b5730db50aa678d5
Author: Neels Hofmeyr <neels at 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=11d9c3a3cb0286f2980a17d05642b9d5db95fb4e
commit 11d9c3a3cb0286f2980a17d05642b9d5db95fb4e
Author: Neels Hofmeyr <neels at 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=ed6255ecdddd46e087a700cb3d46948c19822773
commit ed6255ecdddd46e087a700cb3d46948c19822773
Author: Neels Hofmeyr <neels at 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