osmocom-commitlog May 2015

osmocom-commitlog@lists.osmocom.org

1 participants
139 discussions

osmo-pcu.git branch jerlbeck/wip/ms-struct updated. 0.2-441-ga098c19
by gitosis＠osmocom.org 28 May '15

28 May '15

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, jerlbeck/wip/ms-struct has been updated discards 2218dc2ad1d69b6e5c95d1b7d84de1d110281710 (commit) via a098c19b5531e175a308fbe4aee39c54cb3c71f1 (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 (2218dc2ad1d69b6e5c95d1b7d84de1d110281710) \ N -- N -- N (a098c19b5531e175a308fbe4aee39c54cb3c71f1) 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 ----------------------------------------------------------------- ----------------------------------------------------------------------- Summary of changes: src/pcu_vty.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- UNNAMED PROJECT

1 0

osmo-pcu.git branch jerlbeck/master updated. 0.2-441-ga098c19
by gitosis＠osmocom.org 28 May '15

28 May '15

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, jerlbeck/master has been updated discards 2218dc2ad1d69b6e5c95d1b7d84de1d110281710 (commit) via a098c19b5531e175a308fbe4aee39c54cb3c71f1 (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 (2218dc2ad1d69b6e5c95d1b7d84de1d110281710) \ N -- N -- N (a098c19b5531e175a308fbe4aee39c54cb3c71f1) 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=a098c19b5531e175a308fbe4aee39c5… commit a098c19b5531e175a308fbe4aee39c54cb3c71f1 Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Thu May 28 16:11:19 2015 +0200 tbf: Set MS timeout This commit sets the MS timeout when the MS object is created. The value is taken from the ms_idle_sec field in gprs_rlcmac_bts which can be changed by the VTY commands shown below. The following VTY commands are added to the config-pcu node: - ms-idle-time <1-7200> Set the timeout in seconds - no ms-idle-time Disable the timeout Another timer that is related is T3314 (Ready Timer, default 44s, GSM 24.008, 11.2.2) which requires the SGSN to use paging after its expiry. Longer timeouts can help if adaptive coding scheme selection is used (not yet implemented). On the other hand, measurement values (TA, signal quality) can get invalid after some time, especially with a moving MS. So a value slightly above T3314 is probably a good value to start with. Sponsored-by: On-Waves ehf ----------------------------------------------------------------------- Summary of changes: src/pcu_vty.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- UNNAMED PROJECT

1 0

osmo-pcu.git branch jerlbeck/master updated. 0.2-441-g2218dc2
by gitosis＠osmocom.org 28 May '15

28 May '15

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, jerlbeck/master has been updated via 2218dc2ad1d69b6e5c95d1b7d84de1d110281710 (commit) via d9e102472a97c767cba1bd5687db30028436d623 (commit) via 1db67e0a35a479ef20b871c459ea3f3e0155b620 (commit) via 9200ce60196a289968144582f1acfac25e17eed5 (commit) via ddfc0d57632c5f57aeb123f6506d3923fcec69dc (commit) via d3eac2867a84d009fa3c1c7d8da9502f8468fbca (commit) via 1c68abaffab6b7f8472d54b7881c3618d72e00d9 (commit) via 71e55118f52002af433077251a5a7fee2017b40b (commit) via 7b9f825ae8f8a39c072413820a1a0557f420499d (commit) via b0e5eaf59adbefc44e01850a6784c9da0c3abbf9 (commit) via 9a2845d491b088cb9e1962ba6dc8af5a4e279401 (commit) via 0e50ce614569b9ae7bcc6e7becc4aeec46e8369d (commit) via 767193e20b4172dfb0e76ec63444115dc5ae8806 (commit) via d1cb41bfd020eb9b94b17e5bcaa5be36bceccc12 (commit) via 5752285bc55c00ddcba45c0168eef0cb0238a3a7 (commit) via b75e23143b1d8733a0fdf155f431dcea8146296c (commit) via 4f459799e31ee8fe34ae5f7b584860f699019cfc (commit) via be0cbc1b7ede65ff6c5390905fc956d52a5d88b1 (commit) via 87597358cfe216a80405c21559ba640eedf44ad2 (commit) via 939904672961fa7e28397e27f942a7d1fff4bbdf (commit) via e43460b50fc152026ab96b5095b94fbac6939ab2 (commit) via 536708617505a017b6b263a32f592471913ec464 (commit) via dfef28de887eba43747bca52584f8310450e243a (commit) via 67c385046dbf4fe00871bb9f56b6b82e1f9d1348 (commit) via fecece0e59ab5ff705887a1247df6e02836d7c66 (commit) via e04e0b0a20fb2b93855de0106873c90a88c53052 (commit) via 6eeb7c7e74ed8cc1e23b19453012f43563055e12 (commit) via 6e4ccec6c4b69681e94e4d3b27ef022e4aab81a9 (commit) via 0288cdb0a8d4011905da55a5b74319e38e27e70d (commit) via 3d62fc55d89fe1f2da0f0ca1950ab97da7e07418 (commit) via 87d7341fbe290582ac4a03f67349496e5306eb04 (commit) via 29d91e92715945f53aff4530602add765d63946e (commit) from 801d6fe40cd5bd11257074c7aaf113a57919fb2d (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: .gitignore | 2 + configure.ac | 2 +- src/Makefile.am | 9 +- src/bts.cpp | 114 ++-- src/bts.h | 33 +- src/cxx_linuxlist.h | 133 +++++ src/encoding.cpp | 4 +- src/gprs_bssgp_pcu.cpp | 198 ++++++- src/gprs_bssgp_pcu.h | 8 + src/gprs_ms.cpp | 325 +++++++++++ src/gprs_ms.h | 141 +++++ src/gprs_ms_storage.cpp | 100 ++++ src/{ta.h => gprs_ms_storage.h} | 34 +- src/openbts_sock.cpp | 5 +- src/pcu_main.cpp | 2 - src/pcu_vty.c | 174 ++++++ src/sysmo_l1_if.c | 10 +- src/ta.cpp | 142 ----- src/tbf.cpp | 250 +++++---- src/tbf.h | 45 +- src/tbf_dl.cpp | 90 +-- tests/Makefile.am | 21 +- tests/alloc/AllocTest.cpp | 12 +- tests/llist/LListTest.cpp | 87 +++ tests/{types/TypesTest.err => llist/LListTest.err} | 0 tests/llist/LListTest.ok | 10 + tests/ms/MsTest.cpp | 522 ++++++++++++++++++ tests/ms/MsTest.err | 56 ++ tests/ms/MsTest.ok | 18 + tests/tbf/TbfTest.cpp | 271 ++++++++- tests/tbf/TbfTest.err | 609 +++++++++++++++------ tests/tbf/TbfTest.ok | 6 + tests/testsuite.at | 14 + 33 files changed, 2807 insertions(+), 640 deletions(-) create mode 100644 src/cxx_linuxlist.h create mode 100644 src/gprs_ms.cpp create mode 100644 src/gprs_ms.h create mode 100644 src/gprs_ms_storage.cpp rename src/{ta.h => gprs_ms_storage.h} (58%) delete mode 100644 src/ta.cpp create mode 100644 tests/llist/LListTest.cpp copy tests/{types/TypesTest.err => llist/LListTest.err} (100%) create mode 100644 tests/llist/LListTest.ok create mode 100644 tests/ms/MsTest.cpp create mode 100644 tests/ms/MsTest.err create mode 100644 tests/ms/MsTest.ok hooks/post-receive -- UNNAMED PROJECT

1 0

osmo-pcu.git branch jerlbeck/wip/ms-struct updated. 0.2-441-g2218dc2
by gitosis＠osmocom.org 28 May '15

28 May '15

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, jerlbeck/wip/ms-struct has been updated via 2218dc2ad1d69b6e5c95d1b7d84de1d110281710 (commit) via d9e102472a97c767cba1bd5687db30028436d623 (commit) from 1db67e0a35a479ef20b871c459ea3f3e0155b620 (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=2218dc2ad1d69b6e5c95d1b7d84de1d… commit 2218dc2ad1d69b6e5c95d1b7d84de1d110281710 Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Thu May 28 16:11:19 2015 +0200 tbf: Set MS timeout This commit sets the MS timeout when the MS object is created. The value is taken from the ms_idle_sec field in gprs_rlcmac_bts which can be changed by the VTY commands shown below. The following VTY commands are added to the config-pcu node: - ms-idle-time <1-5000> Set the timeout in seconds - no ms-idle-time Disable the timeout Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=d9e102472a97c767cba1bd5687db300… commit d9e102472a97c767cba1bd5687db30028436d623 Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Thu May 28 15:43:53 2015 +0200 ms: Add timer Currently the MS object is immediately idle when all TBFs are detached and if no guard is being used. Since the plan is to use the MS objects to pass information from one TBF to the next one even across the gap of some seconds of inactivity, a mechanism is needed to keep the MS objects around for some time. This commit extends the GprsMs class by a timer that keeps the MS objects in non-idle state for some time after all TBFs have been detached. The set_timeout method must be used with a non-zero value to activate this feature. Sponsored-by: On-Waves ehf ----------------------------------------------------------------------- Summary of changes: src/bts.h | 1 + src/gprs_ms.cpp | 57 +++++++++++++++++++++++++++++++++++++++---- src/gprs_ms.h | 21 +++++++++++++++- src/pcu_vty.c | 27 +++++++++++++++++++++ src/tbf.cpp | 4 ++- tests/ms/MsTest.cpp | 70 +++++++++++++++++++++++++++++++++++++++++++++++++++++ tests/ms/MsTest.err | 7 ++++++ tests/ms/MsTest.ok | 4 +++ 8 files changed, 184 insertions(+), 7 deletions(-) hooks/post-receive -- UNNAMED PROJECT

1 0

osmo-pcu.git branch jerlbeck/wip/ms-struct updated. 0.2-439-g1db67e0
by gitosis＠osmocom.org 28 May '15

28 May '15

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, jerlbeck/wip/ms-struct has been updated discards c299cee15cabb2a8c2ad7eb54da182f2b73d3f16 (commit) discards aa9c1199e40d19c2f65dfcb6d3239483b2dbc2bf (commit) discards 1c96d98d9c392f60e457d3dac310e5826489c50e (commit) discards d4b882dd013c6a2069995a7cb89eecde283d92e1 (commit) discards 1c674ff4826c18741acf685c0073236e2f431fb6 (commit) discards 0ef422fe0307183b6281aca77074827cb61f2024 (commit) discards 24ebf9022f7d76b00771b32c9557a50106329ba3 (commit) discards 69381940f40a2d42f75e060e79d63feed54ff609 (commit) via 1db67e0a35a479ef20b871c459ea3f3e0155b620 (commit) via 9200ce60196a289968144582f1acfac25e17eed5 (commit) via ddfc0d57632c5f57aeb123f6506d3923fcec69dc (commit) via d3eac2867a84d009fa3c1c7d8da9502f8468fbca (commit) via 1c68abaffab6b7f8472d54b7881c3618d72e00d9 (commit) via 71e55118f52002af433077251a5a7fee2017b40b (commit) via 7b9f825ae8f8a39c072413820a1a0557f420499d (commit) via b0e5eaf59adbefc44e01850a6784c9da0c3abbf9 (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 (c299cee15cabb2a8c2ad7eb54da182f2b73d3f16) \ N -- N -- N (1db67e0a35a479ef20b871c459ea3f3e0155b620) 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=1db67e0a35a479ef20b871c459ea3f3… commit 1db67e0a35a479ef20b871c459ea3f3e0155b620 Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Fri May 22 18:02:51 2015 +0200 tbf: Remove TimingAdvance storage Currently the TA storage stores up to 30 TLLI->TA mappings, if more entries are created the oldest one is dropped. In theory this can lead to missing TA information if many MS are present. This commit removes the TimingAdvance class completely, since the TA value is now stored in the GprsMs objects. Note that the GprsMs objects are currently not kept after the TBFs have detached from them, so the TA values are now kept for a shorter time than before. Ticket: #1674 Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=9200ce60196a289968144582f1acfac… commit 9200ce60196a289968144582f1acfac25e17eed5 Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Fri May 22 17:48:04 2015 +0200 tbf: Store the timing advance (TA) value in the GprsMs object The TA value rather relates to an MS and not to a single TBF. So all TBFs share the same TA value. Currently the TA value is stored per TBF and eventually copied from an old TBF to a new one. It is in general only passed with an RACH request when the TLLI and thus the MS is not yet known. This commit adds a TA member to the GprsMs class and uses that one when the TBF is associated to an MS object. Since the TBF is not always associated with an MS object (after RACH or when it has been replaced by another TBF), the TA value is still stored in each TBF and that value is used as long as no MS object is being associated. Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=ddfc0d57632c5f57aeb123f6506d392… commit ddfc0d57632c5f57aeb123f6506d3923fcec69dc Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Wed May 27 13:03:15 2015 +0200 tbf/test: Add tests for single and two phase access These tests cover the message exchange from receiving from the first RACH request to the first data block when establishing an uplink TBF. This will be used to check, whether TA and other values are passed to an MS object correctly. In addition, the RX RACH log message in rcv_rach is extended to contain the single block fn. Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=d3eac2867a84d009fa3c1c7d8da9502… commit d3eac2867a84d009fa3c1c7d8da9502f8468fbca Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Fri May 22 15:47:55 2015 +0200 tbf: Remove TBF chaining (m_new_tbf and m_old_tbf) Currently a new TBF is chained to an existing older one, either of the other direction (active or releasing) or of the same direction (releasing). This does not work properly work if and uplink and a downlink TBF are being established at the same time while an old TBF is being released. In that case, one of them is thrown away and the pending procedure is cancelled. The chaining is no longer necessary since the GprsMs objects have been introduced which keep track of the active TBFs. This commit removes the TBF members m_new_tbf and m_old_tbf and the related methods and code paths. Note that a new TBF can replace an older TBF entry of the same direction within an MS object when it is associated with an MS (e.g. by TLLI or because it is assigned via another, already associated TBF). In that case, the old TBF is no longer associated with an MS object. Ticket: #1674 Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=1c68abaffab6b7f8472d54b7881c361… commit 1c68abaffab6b7f8472d54b7881c3618d72e00d9 Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Fri May 22 15:40:08 2015 +0200 tbf/test: Attach TLLI and MS objects to TBFs Currently the DL TBF's TLLI are not set. This will have to change in the future, when the m_new_tbf chaining is replaced by the usage of MS object to group TBFs. This commit just calls update_ms() on newly created TBFs. This changes many of the lines written to stderr due to the TLLI change, but doesn't change other aspects or messages beside creating and destroying MS objects. Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=71e55118f52002af433077251a5a7fe… commit 71e55118f52002af433077251a5a7fee2017b40b Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Thu May 21 11:10:15 2015 +0200 tbf: Remove IMSI handling from trigger_dl_ass Currently the BTS::trigger_dl_ass() method assigns the IMSI to the MS object. This should be (and is already) done earlier where the MS object is retrieved/created. This commit removes the corresponding code along with the 'imsi' parameter from trigger_dl_ass. Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=7b9f825ae8f8a39c072413820a1a055… commit 7b9f825ae8f8a39c072413820a1a0557f420499d Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Thu May 21 11:07:53 2015 +0200 ms: Use the IMSI to retrieve the MS object This commit extends get_ms() to really compare the IMSI if it has been given. Matching by TLLI has a higher precedence than matching by IMSI. Ticket: #1674 Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=b0e5eaf59adbefc44e01850a6784c9d… commit b0e5eaf59adbefc44e01850a6784c9da0c3abbf9 Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Thu May 21 11:07:16 2015 +0200 tbf: Move IMSI to MS object Currently the IMSI is stored in the TBFs. Since it directly refers to an MS, it should rather be stored in an MS object. This patch move the m_imsi field from gprs_rlcmac_tbf to GprsMs, changes gprs_rlcmac_tbf::imsi() to get the IMSI from the associated MS object, and adds getter and setter to GprsMs. Before changing the IMSI of the associated MS object, assign_imsi() checks if there is already another MS object with the same IMSI and eventually resets the IMSI of that one. So using update_ms() and assign_imsi() ensures that there are not two MS object entries is the storage with the same TLLI or the same IMSI. Ticket: #1674 Sponsored-by: On-Waves ehf ----------------------------------------------------------------------- Summary of changes: src/gprs_ms.cpp | 2 +- src/gprs_ms_storage.cpp | 33 ++++++++++++++++++------------ src/tbf.cpp | 32 +++++++++++++++++++++++++++++ src/tbf.h | 1 + src/tbf_dl.cpp | 9 +++++---- tests/tbf/TbfTest.cpp | 54 +++++++++++++++++++++++++++++++++++++++++++++++++ tests/tbf/TbfTest.err | 45 +++++++++++++++++++++++++++++++++++++++++ tests/tbf/TbfTest.ok | 2 ++ 8 files changed, 160 insertions(+), 18 deletions(-) hooks/post-receive -- UNNAMED PROJECT

1 0

gr-osmosdr.git branch master updated. v0.1.4-31-gb3fdf5b
by gitosis＠osmocom.org 27 May '15

27 May '15

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 "GNU Radio block for interfacing with various radio hardware". The branch, master has been updated via b3fdf5b83dc79575405f524df889d92908fecc72 (commit) via 594391982845b4ac0e4e48bbb91b4b85552f2af6 (commit) from 44c223cb5d473a760877e8c8b2d58e2638173192 (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/gr-osmosdr/commit/?id=b3fdf5b83dc79575405f524df889d… commit b3fdf5b83dc79575405f524df889d92908fecc72 Author: Marcus Müller <Marcus.Mueller(a)ettus.com> Date: Thu May 21 23:46:58 2015 -0700 Fix config error with CMake version 2.8.7 Replace find_package(SoapySDR CONFIG) with find_package(SoapySDR NO_MODULE), which has an identical effect but is supported by CMake 2.8.7 on Ubuntu 12.10 http://cgit.osmocom.org/gr-osmosdr/commit/?id=594391982845b4ac0e4e48bbb91b4… commit 594391982845b4ac0e4e48bbb91b4b85552f2af6 Author: Dimitri Stolnikov <horiz0n(a)gmx.net> Date: Wed May 27 23:55:00 2015 +0200 hackrf: introduce bias=0|1 and bias_tx=0|1 parameters ... to support antenna/phantom power via a new device argument "bias" (to match Airspy's existing bias power syntax). 0=disable and 1=enable. I also added a device argument to control bias power at transmit time. I named this option differently - "bias_tx" - to avoid accidentally enabling bias power in transmit mode when an LNA may be attached in an input amplifier configuration. Original patch provided by Brad Hein ----------------------------------------------------------------------- Summary of changes: CMakeLists.txt | 2 +- grc/gen_osmosdr_blocks.py | 2 +- lib/hackrf/hackrf_sink_c.cc | 18 ++++++++++++++++++ lib/hackrf/hackrf_source_c.cc | 18 ++++++++++++++++++ 4 files changed, 38 insertions(+), 2 deletions(-) hooks/post-receive -- GNU Radio block for interfacing with various radio hardware

1 0

openbsc.git branch fairwaves/rebase-no-queue updated. 0.14.0-82-g90459a0
by gitosis＠osmocom.org 27 May '15

27 May '15

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 OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)". The branch, fairwaves/rebase-no-queue has been updated via 90459a0507b7b0fc66a7c764c48c8f244ce66989 (commit) from ade03887bbfee19b970dcaed1220cc3a19867eaf (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/openbsc/commit/?id=90459a0507b7b0fc66a7c764c48c8f24… commit 90459a0507b7b0fc66a7c764c48c8f244ce66989 Author: Alexander Chemeris <Alexander.Chemeris(a)gmail.com> Date: Sun May 17 20:52:26 2015 -0400 libmsc: Update 'max_power_red' VTY command. Changes: * Apply change even if the supplied value is odd, just warn that it is rounded. * Apply change even if the supplied value is higher than the 24dB maximum suggested by the standard, just warn about this. * Apply change to the BTS over OML immediately. ----------------------------------------------------------------------- Summary of changes: openbsc/src/libbsc/bsc_vty.c | 33 ++++++++++++++++++++++++--------- 1 file changed, 24 insertions(+), 9 deletions(-) hooks/post-receive -- The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)

1 0

openbsc.git branch fairwaves/rebase-no-queue updated. 0.14.0-81-gade0388
by gitosis＠osmocom.org 27 May '15

27 May '15

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 OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)". The branch, fairwaves/rebase-no-queue has been updated via ade03887bbfee19b970dcaed1220cc3a19867eaf (commit) from d38e96df2a94c74304540b9cd6ec6a2d5f95f77e (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/openbsc/commit/?id=ade03887bbfee19b970dcaed1220cc3a… commit ade03887bbfee19b970dcaed1220cc3a19867eaf Author: Ivan Kluchnikov <kluchnikovi(a)gmail.com> Date: Wed May 27 16:15:37 2015 +0300 debian: build only osmo-nitb package - enable smpp support - disable the gbproxy test (failing) ----------------------------------------------------------------------- Summary of changes: debian/control | 88 ++-------------------------------------------- debian/rules | 8 +---- openbsc/tests/testsuite.at | 6 ---- 3 files changed, 3 insertions(+), 99 deletions(-) hooks/post-receive -- The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)

1 0

osmo-bts.git branch fairwaves/debian updated. 0.3.0-255-g6fc4521
by gitosis＠osmocom.org 27 May '15

27 May '15

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, fairwaves/debian has been updated discards 28a0d6e6e342e1e882ca0930c80daff7081ee18d (commit) discards ce8fee2baa964dcb1b42b2f9ad0e1080eb6aabb4 (commit) discards 0de292473551733229ac2947dc7ab72d6e2038bf (commit) via 6fc45218417a738a2e25da8f25b1d43c84c39e31 (commit) via 16c55999ca4d3fd6dde57a02297b301b6b7f4b27 (commit) via 6fe1aa9b302c637ff250a48240c1cba8ff888ec7 (commit) via 90b4e07e425198bbe651461c0fb259f7fecf33dd (commit) via 209e33a8fb437b1ae388e4e96ec02cc20044e849 (commit) via e510c8486082c9434b981358866f93878c0f7258 (commit) via 9b7e7f76220410be755d27c05486ee3ddfc49bb8 (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 (28a0d6e6e342e1e882ca0930c80daff7081ee18d) \ N -- N -- N (6fc45218417a738a2e25da8f25b1d43c84c39e31) 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=6fc45218417a738a2e25da8f25b1d43… commit 6fc45218417a738a2e25da8f25b1d43c84c39e31 Author: Ivan Kluchnikov <kluchnikovi(a)gmail.com> Date: Tue Sep 23 14:34:02 2014 +0400 debian: Add gsm_data_shared.h file to make packaging possible http://cgit.osmocom.org/osmo-bts/commit/?id=16c55999ca4d3fd6dde57a02297b301… commit 16c55999ca4d3fd6dde57a02297b301b6b7f4b27 Author: Ivan Kluchnikov <kluchnikovi(a)gmail.com> Date: Tue Sep 23 13:49:09 2014 +0400 debian: Add debian directory to ease building packages http://cgit.osmocom.org/osmo-bts/commit/?id=6fe1aa9b302c637ff250a48240c1cba… commit 6fe1aa9b302c637ff250a48240c1cba8ff888ec7 Author: Ivan Kluchnikov <kluchnikovi(a)gmail.com> Date: Tue Sep 23 13:40:11 2014 +0400 debian: Add gsm_data_shared.c file to make packaging possible ----------------------------------------------------------------------- Summary of changes: src/common/abis.c | 1 + src/common/oml.c | 2 +- src/osmo-bts-trx/gsm0503_coding.c | 322 +++++++++++++++++++------------------- src/osmo-bts-trx/gsm0503_coding.h | 37 ++++- src/osmo-bts-trx/l1_if.c | 33 ++-- src/osmo-bts-trx/l1_if.h | 6 +- src/osmo-bts-trx/scheduler.c | 78 +++++---- tests/bursts/bursts_test.c | 39 +++-- tests/bursts/bursts_test.ok | 20 +++ 9 files changed, 327 insertions(+), 211 deletions(-) hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)

1 0

osmo-pcu.git branch jerlbeck/wip/ms-struct updated. 0.2-439-gc299cee
by gitosis＠osmocom.org 27 May '15

27 May '15

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, jerlbeck/wip/ms-struct has been updated discards 20296a48676094a09c7928006e62e890c2e69e0f (commit) discards 87e6ed022df45b70d93c96581cc1c99b76a80718 (commit) discards 6e3311b641b51cb4cc790f2e488e45602724ce36 (commit) discards 7044acabf5ac371a4e80bb1fc81650b36187deaa (commit) discards 7e64d5f11482efb55766ea1696e799fde6b66b2b (commit) discards 95abc21ff352cff1c57453262b998e32b8ea7afd (commit) discards 50b6e02a859561d2044a5e6bc20af2f11f6ebaad (commit) discards 8a26db1dd366a540288cec634f6a02afc851fb3e (commit) discards a12e11c98d30f075c7e2f33cc4400c34d446f541 (commit) discards f0045d04d3cd03579005231b7dcbbac3cac3b83b (commit) discards 2ee112c2e134146c501601e0faf01014393bd7b7 (commit) via c299cee15cabb2a8c2ad7eb54da182f2b73d3f16 (commit) via aa9c1199e40d19c2f65dfcb6d3239483b2dbc2bf (commit) via 1c96d98d9c392f60e457d3dac310e5826489c50e (commit) via d4b882dd013c6a2069995a7cb89eecde283d92e1 (commit) via 1c674ff4826c18741acf685c0073236e2f431fb6 (commit) via 0ef422fe0307183b6281aca77074827cb61f2024 (commit) via 24ebf9022f7d76b00771b32c9557a50106329ba3 (commit) via 69381940f40a2d42f75e060e79d63feed54ff609 (commit) via 9a2845d491b088cb9e1962ba6dc8af5a4e279401 (commit) via 0e50ce614569b9ae7bcc6e7becc4aeec46e8369d (commit) via 767193e20b4172dfb0e76ec63444115dc5ae8806 (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 (20296a48676094a09c7928006e62e890c2e69e0f) \ N -- N -- N (c299cee15cabb2a8c2ad7eb54da182f2b73d3f16) 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=c299cee15cabb2a8c2ad7eb54da182f… commit c299cee15cabb2a8c2ad7eb54da182f2b73d3f16 Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Fri May 22 18:02:51 2015 +0200 tbf: Remove TimingAdvance storage Currently the TA storage stores up to 30 TLLI->TA mappings, if more entries are created the oldest one is dropped. In theory this can lead to missing TA information if many MS are present. This commit removes the TimingAdvance class completely, since the TA value is now stored in the GprsMs objects. Note that the GprsMs objects are currently not kept after the TBFs have detached from them, so the TA values are now kept for a shorter time than before. Ticket: #1674 Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=aa9c1199e40d19c2f65dfcb6d323948… commit aa9c1199e40d19c2f65dfcb6d3239483b2dbc2bf Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Fri May 22 17:48:04 2015 +0200 tbf: Store the timing advance (TA) value in the GprsMs object The TA value rather relates to an MS and not to a single TBF. So all TBFs share the same TA value. Currently the TA value is stored per TBF and eventually copied from an old TBF to a new one. It is in general only passed with an RACH request when the TLLI and thus the MS is not yet known. This commit adds a TA member to the GprsMs class and uses that one when the TBF is associated to an MS object. Since the TBF is not always associated with an MS object (after RACH or when it has been replaced by another TBF), the TA value is still stored in each TBF and that value is used as long as no MS object is being associated. Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=1c96d98d9c392f60e457d3dac310e58… commit 1c96d98d9c392f60e457d3dac310e5826489c50e Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Wed May 27 13:03:15 2015 +0200 tbf/test: Add tests for single and two phase access These tests cover the message exchange from receiving from the first RACH request to the first data block when establishing an uplink TBF. This will be used to check, whether TA and other values are passed to an MS object correctly. In addition, the RX RACH log message in rcv_rach is extended to contain the single block fn. Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=d4b882dd013c6a2069995a7cb89eecd… commit d4b882dd013c6a2069995a7cb89eecde283d92e1 Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Fri May 22 15:47:55 2015 +0200 tbf: Remove TBF chaining (m_new_tbf and m_old_tbf) Currently a new TBF is chained to an existing older one, either of the other direction (active or releasing) or of the same direction (releasing). This does not work properly work if and uplink and a downlink TBF are being established at the same time while an old TBF is being released. In that case, one of them is thrown away and the pending procedure is cancelled. The chaining is no longer necessary since the GprsMs objects have been introduced which keep track of the active TBFs. This commit removes the TBF members m_new_tbf and m_old_tbf and the related methods and code paths. Note that a new TBF can replace an older TBF entry of the same direction within an MS object when it is associated with an MS (e.g. by TLLI or because it is assigned via another, already associated TBF). In that case, the old TBF is no longer associated with an MS object. Ticket: #1674 Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=1c674ff4826c18741acf685c0073236… commit 1c674ff4826c18741acf685c0073236e2f431fb6 Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Fri May 22 15:40:08 2015 +0200 tbf/test: Attach TLLI and MS objects to TBFs Currently the DL TBF's TLLI are not set. This will have to change in the future, when the m_new_tbf chaining is replaced by the usage of MS object to group TBFs. This commit just calls update_ms() on newly created TBFs. This changes many of the lines written to stderr due to the TLLI change, but doesn't change other aspects or messages beside creating and destroying MS objects. Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=0ef422fe0307183b6281aca77074827… commit 0ef422fe0307183b6281aca77074827cb61f2024 Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Thu May 21 11:10:15 2015 +0200 tbf: Remove IMSI handling from trigger_dl_ass Currently the BTS::trigger_dl_ass() method assigns the IMSI to the MS object. This should be (and is already) done earlier where the MS object is retrieved/created. This commit removes the corresponding code along with the 'imsi' parameter from trigger_dl_ass. Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=24ebf9022f7d76b00771b32c9557a50… commit 24ebf9022f7d76b00771b32c9557a50106329ba3 Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Thu May 21 11:07:53 2015 +0200 ms: Use the IMSI to retrieve the MS object This commit extends get_ms() to really compare the IMSI if it has been given. Note that the MS object list will be traversed only once and that the first entry with a matching TLLI or a matching IMSI will be returned. Thus there is no precedence. Ticket: #1674 Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=69381940f40a2d42f75e060e79d63fe… commit 69381940f40a2d42f75e060e79d63feed54ff609 Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Thu May 21 11:07:16 2015 +0200 tbf: Move IMSI to MS object Currently the IMSI is stored in the TBFs. Since it directly refers to an MS, it should rather be stored in an MS object. This patch move the m_imsi field from gprs_rlcmac_tbf to GprsMs, changes gprs_rlcmac_tbf::imsi() to get the IMSI from the associated MS object, and adds getter and setter to GprsMs. Note that the assign_imsi() method is now called set_imsi() for consistency within the GprsMs class. Ticket: #1674 Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=9a2845d491b088cb9e1962ba6dc8af5… commit 9a2845d491b088cb9e1962ba6dc8af5a4e279401 Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Thu May 21 12:06:58 2015 +0200 tbf/test: Fix IMSI creation Currently the generated IMSI contains blanks due to a missing '0' flag in the corresponding snprintf statement. In addition, the buffer is effectively limited to 15 bytes which is shorter than the generated character sequence, such that the last character of the IMSI is removed. This patch fixes both issues. Since snprintf itself will add a terminating \0 character, the whole buffer can be passed to snprintf. Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=0e50ce614569b9ae7bcc6e7becc4aee… commit 0e50ce614569b9ae7bcc6e7becc4aeec46e8369d Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Thu May 21 16:58:22 2015 +0200 tbf: Always call set_tlli/confirm_tlli in update_ms Currently the m_tlli member in GprsMs is set by the constructor, circumventing the TLLI confirmation mechanism. This commit replaces the get_or_create_ms() method by a create_ms() method which takes the TLLI and the direction (UL or DL) as parameters to select either set_tlli() or confirm_tlli(). The MS object is instantiated with TLLI = 0, and therefore GprsMs::tlli() is extended to return the DL TLLI if both of the other TLLI are not set. Note that create_ms() will not check whether an MS object with a matching TLLI is already stored in the list, so it should only be called after a corresponding get_ms() in general. Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=767193e20b4172dfb0e76ec63444115… commit 767193e20b4172dfb0e76ec63444115dc5ae8806 Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Wed May 20 12:06:46 2015 +0200 tbf: Remove the TLLI from the TBFs Currently the TLLI is stored in each TBF. Since each MS is now represented by a GprsMs object which takes care of TLLI updating, and each TBF that has been associated with an TLLI also contains a reference to a GprsMs object, per TBF TLLI handling is no longer needed. Keeping all TBF m_tlli members up to date is complex and doesn't currently work correctly in all circumstances. This commit removes m_tlli and related members from the TBF class and the tbf_by_tlli functions from the BTS class. Ticket: #1674 Sponsored-by: On-Waves ehf ----------------------------------------------------------------------- Summary of changes: src/bts.h | 1 - 1 file changed, 1 deletion(-) hooks/post-receive -- UNNAMED PROJECT

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

osmocom-commitlog May 2015