OpenBSC January 2017

openbsc@lists.osmocom.org

24 participants
59 discussions

Quectel EC20 question
by Petr Štetiar 11 Jan '17

11 Jan '17

Hi, according to a lot of sources one would think, that EC20 is based around the Qualcomm MDM9615, but the picture of naked EC20[1] clearly shows, that there is Qualcomm MDM9215 chip soldered on the board. Which source is true? :-) Or it's just a wrong text on that BGA? 1. https://osmocom.org/attachments/download/2501/ec20-naked-top.jpg -- ynezz

2 2

[openbsc 0.15.0.621-80ab] testsuite: 3 5 failed
by Hossein Amini 10 Jan '17

10 Jan '17

hi I compliled OpenBSC in linux kernel 4.2.* and all test was successful but when upgrade my linux to kernel v4.8.* , we face 2 failed test. logs attached Regards Hossein

3 2

Relicensing optimized Viterbi decoder
by Vadim Yanitskiy 10 Jan '17

10 Jan '17

Hi Tom, Recently I already asked for your permission to relicense the GSM 05.03 code from OpenBTS, and now I am contacting you with the same purpose. I am going to move your optimized Viterbi decoder forward, but currently it is licensed under the LGPL v2.1 (or later). To avoid license mix within the core Osmocom library, it would be better to relicense your code to the same one, if you agree. So, the question is: do you agree to relicense your code under the GPLv2-or-later? With best regards, Vadim Yanitskiy.

3 2

RFC: OsmoDevCon 2017 planning
by Harald Welte 10 Jan '17

10 Jan '17

Dear Osmocom Community, [please respect the Reply-To and post all follow-up discussion to this to openbsc(a)lists.osmocom.org, so we avoid having long threads cross-posted to several mailing lists.] >From 2012 to 2016 we were running a series of small, invitation-only Osmocom Developer Conferences. Access was intentionally restricted to those community members who have demonstrated an existing track record of contribution to any of the projects under the Osmocom umbrella. This format of a small, tightly knit group of about 20 people has been successful over the years, and I have received a lot of positive feedback from past participants. On the other hand, the Osmocom project has grown in scope and diversity, and some of those projects don't have all that much relationship to each other - except being started by people from within the same group. There's the cellular communications (GSM/GPRS/EDGE/UMTS and hopefully at some point LTE) protocols which is attracting a lot of professional users. And then there's pure community projects like rtl-sdr, OsmocomBB, OsmocomGMR and many other efforts. Particularly the cellular infrastructure projects (OsmoBTS, OsmoPCU, OsmoBTS, OsmoNITB, OsmoSGSN, OpenGGSN, OsmoIuh & co) are somehow "standing out" of the othe projects in the context of having a wider user bsae, and in that user base also primarily commercial users. So I'd like to start a discussion on how to possibly change the event format to accomodate the various interests and parties. I definitely don't want to loose the "annual meeting of old friends" atmosphere, while at the same time also opening up to other interested parties. One idea would be to keep OsmoDevCon as-is and have a separate event where non-contributing/developing users / sysadmins / system integrators could also be attending. Another idea would be to split into a 'user day' and 'developer days' format. This is something the netfilter developer workshops have been using for many years, and from my limited insight quite successfully so. The "user day" is more like a traditional tech conference, with a large auditorium and talks oriented towards users / sysadmins / integrators of the software. The "developer days" are the invitation-only part, for known contributing developers only, similar to what we have at OsmoDevCon. Having both events (or both parts of an event) back-to-back has the advantage that a large number of potential speakers for the 'user day' are already present, and they don't have to travel yet another time. One could even structure it further and say we have one user day, one public 'Osmocom cellular developer day' and then the closed 'OsmoDevCon classic', maybe reduced from 4 days to 3 or even 2 days only? What is the general opinion about this? Are there people lurking on this list who would be interested in attending a public 'user day' or even 'developer day' about the Osmocom cellular projects, with presentations and workshops around topics such as running Osmocom based cellular networks? In terms of when/where, I would suggest to keep the tradition of April in Berlin/Germany. But I'm of course very happy if somebody wants to host it some place else... Regards, and looking forward to meeting you [again] in 2017, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

6 14

Contribute to Osmocom and receive a free 3.5G femtocell
by Harald Welte 09 Jan '17

09 Jan '17

Dear all, not everyone might have seen the news item that was posted in late December on our website at http://osmocom.org/news/62 I'm looking forward to receiving your proposal on how you would contribute to the Osmocom project if you were to receive one of those free 3.5G femtocells. Quote of the news item below: ------ So please excuse me to cross-post this over several Osmocom project mailing lists. I know that a number of people have either hacked on femtocells in the past, or at least expressed interest in doing so... Osmocom's support for 2G/GSM is mature and widespread. Since 2016, we're taking on the next level: 3G/3.5G. The key to running your own 3G network is to obtain actual 3G cell hardware -- here is an exciting opportunity to get started: No less than 50 femtocells will be given away for free by sysmocom, one of the main drivers of the Osmocom project. To receive a free 3G femtocell, tell us how you will help the Osmocom project drive 3.5G forward if you had one, before the end of January 2017. This marks the launch of the 3.5G Acceleration Project, backed by the Osmocom community. Join us! Find further details on the 3.5G Acceleration Project and receiving your own 3G femtocell for free at https://sysmocom.de/downloads/accelerate_3g5_cfp.pdf. ------ Best regards and happy hacking, Harald Welte -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0

Re: libosmocore[master]: libosmocoding: migrate transcoding routines from OsmoBTS
by Harald Welte 09 Jan '17

09 Jan '17

On Wed, Jan 04, 2017 at 08:55:45AM +0000, Vadim Yanitskiy wrote: > I think it's due to --enable-sanitize, because > when I am trying to compile libosmocore this way: > > ./configure --enable-static --enable-sanitize > make check > > Some other tests fail (current master version, clang-3.6): > > Regression tests. > 8: gea FAILED (testsuite.at:51) > 9: msgfile FAILED (testsuite.at:59) > 15: lapd FAILED (testsuite.at:96) > 16: gsm0808 FAILED (testsuite.at:102) > 17: gsm0408 FAILED (testsuite.at:108) > 30: bssgp-fc FAILED (testsuite.at:190) I pushed some fixes,see https://gerrit.osmocom.org/1530 and https://gerrit.osmocom.org/1531 - the remaining failures are all LeakSanitizer warnings, and I suspect that while we release all memory back to talloc, talloc itself doesn't release it back to glibc malloc/free, and hence LeakSanitizer is kicking in. A quick online search didn't seem like anyone else has yet come up with a solution for this, so I guess we should turn it off. I remember some discussion on the list about a year ago where the concensus was to disable LeakSanitizer by environment variables on the buildhost anyway? -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

4 3

log messages summary
by Neels Hofmeyr 09 Jan '17

09 Jan '17

Hi Max, you recently tend to have very general commit log summaries. The summary should best contain a hint at the general area the patch is about, so a reader can quickly know whether a patch could be related to a given other topic. I've asked so on gerrit a few times, and now also found a couple of commits merged IMHO with ETOOGENERAL, so I thought I'd drop a note: osmo-bts: 2017-01-06 17:30 Max o Log socket path on error 2017-01-02 18:17 Max o Move code to libosmocore 2016-11-11 17:44 Max o Remove duplicated code osmo-pcu: 2017-01-06 17:20 Max o Log socket path on connection 2017-01-05 18:26 Max o Improve logging Would be nice to add an indicator to the summary in the future. A small word or phrase in the beginning is enough, like 'rsl: frobnicate', or include a function name or -prefix for code dup / moved code. Thanks! ~N -- - Neels Hofmeyr <nhofmeyr(a)sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschäftsführer / Managing Directors: Harald Welte

1 0

[libosmocore 0.9.6.48-3419] testsuite: 28 failed
by Martin Hauke 08 Jan '17

08 Jan '17

-------------------------------------------------------------------- 28: stats FAILED (testsuite.at:177) -------------------------------------------------------------------- os: openSUSE Tumbleweed arch: armv7l compiler: gcc (SUSE Linux) 6.2.1 20161209 [gcc-6-branch revision 243481] configure options: default I have attached testsuite.log best regards, Martin

1 0

[libosmocore 0.9.6.35-3faa] testsuite: 8 9 15 16 17 30 failed
by Vadim Yanitskiy 06 Jan '17

06 Jan '17

Ubuntu 16.04.1 LTS gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) Configured with: --enable-static --enable-sanitize See attachment please. With best regards, Vadim Yanitskiy.

2 1

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC January 2017