From ptrkrysik at gmail.com Sat Aug 1 13:44:03 2015 From: ptrkrysik at gmail.com (Piotr Krysik) Date: Sat, 01 Aug 2015 15:44:03 +0200 Subject: Adding features from osmocom-bb to libosmocore Message-ID: <55BCCD23.6030800@gmail.com> Hi all, I'm developing gr-gsm project which uses GNU Radio framework in order to build infrastructure for receiving GSM data. Recently we've added libosmocore as a dependency in order to use it's implementation of ciphering algorithms. I would like to use more of the code that was already implemented thanks to your work, but I've found some parts that I would expect to be in libosmocore are not in there but in osmocom-bb. One of the examples is interpretation of system information messages that is in src/host/layer23/src/common/sysinfo.c. Is it possible to move parts that are usable for projects outside of osmocom into libsomocore? If yes - how can I proceed with that? I'm aware that it is not simple process as it involves also removing these parts from osmocom-bb and maybe also editing them in order to make them independent of osmocom-bb. -- Best Regards, Piotr Krysik From radiarisainanasitraka at yahoo.fr Sat Aug 1 18:56:34 2015 From: radiarisainanasitraka at yahoo.fr (Radiarisainana Sitraka) Date: Sat, 1 Aug 2015 18:56:34 +0000 (UTC) Subject: c113a works In-Reply-To: References: Message-ID: <1184722557.274399.1438455394166.JavaMail.yahoo@mail.yahoo.com> I would like to have some information about the phone that you use , about the motorola c123 and motorola c155 : 1-if it's possible i would like to have a version of the two phones , to make it ,you should tape #02# and click down button until you see "SW Vr : ..." , 2-if it's possible i would like to have also the text following this line , normally like : "FFE ..." ? De?: Sylvain Munaut <246tnt at gmail.com> ??: Craig Comstock Cc?: Baseband-devel Envoy? le : Mardi 16 juin 2015 7h28 Objet?: Re: c113a works Good to know. Do you know if the hw is exactly the same as the c123 ? Cheers, ? Sylvain -------------- next part -------------- An HTML attachment was scrubbed... URL: From 246tnt at gmail.com Sat Aug 1 19:07:34 2015 From: 246tnt at gmail.com (Sylvain Munaut) Date: Sat, 1 Aug 2015 21:07:34 +0200 Subject: Adding features from osmocom-bb to libosmocore In-Reply-To: <55BCCD23.6030800@gmail.com> References: <55BCCD23.6030800@gmail.com> Message-ID: Hi Piotr, > Recently we've added libosmocore as a dependency in order to use it's > implementation of ciphering algorithms. Nice :) > I would like to use more of the code that was already implemented thanks > to your work, but I've found some parts that I would expect to be in > libosmocore are not in there but in osmocom-bb. One of the examples is > interpretation of system information messages that is in > src/host/layer23/src/common/sysinfo.c. Usually we only move things to libosmocore when the case effectively happens that we want to re-use it somewhere else. Since so far we never needed the "MS" side of those any where else, they remained in osmocom-bb. > Is it possible to move parts that are usable for projects outside of > osmocom into libsomocore? If yes - how can I proceed with that? I'm > aware that it is not simple process as it involves also removing these > parts from osmocom-bb and maybe also editing them in order to make them > independent of osmocom-bb. Yes it's possible to move parts. We've done it in the past for several things. (for example the whole SMS stuff was born in osmocom-bb and moved over to libosmocore when we reused it in OpenBSC). As you said, it's not a trivial process, but if you go through with it and sumbmit the patches, we'll review then and comment for merging. You might want to post them on the OpenBSC mailing list though (which is the official list for libosmocore) since it's more active and more people will review them. You'll indeed need to make sure to make them independent from the osmocom bb codebase, modify them to be generic if need be. For libosmocore we also require test suite for any new code, since there is none in osmocom-bb you'll need to write those for any library function added. Once you have the patch to add the functions to libosmocore, you'll also need to write the patch to convert osmocom-bb to the new API (which may have been modified to make it generic). Cheers, Sylvain From modemip at yandex.ru Wed Aug 19 11:14:35 2015 From: modemip at yandex.ru (Anton Guryanov) Date: Wed, 19 Aug 2015 16:14:35 +0500 Subject: AMR support and B_PLAY_UL Message-ID: <1713101439982875@web26o.yandex.ru> Hi, I tried to add simple AMR support in osmocombb project. I tested it with C123 (DSP API v 36). I set AMR config from assigment command, set AMR detection thresholds, make sync, etc. It looks like downlink works fine, but I have problem with uplink: it send data directly from microphone and ignore data in dsp_api.ndb->a_du_1 even if I set dsp_api.ndb->d_tch_mode|=B_PLAY_UL. Also, I can see uplink data on dsp_api.ndb->a_du_0 like B_PLAY_UL is fully ignored. Did anyone have that issue before? I know that AMR codec is more complex that TCH, but did someone know a way to send custom data from host using AMR codec? Best regards, Anton From 246tnt at gmail.com Sun Aug 23 15:08:52 2015 From: 246tnt at gmail.com (Sylvain Munaut) Date: Sun, 23 Aug 2015 17:08:52 +0200 Subject: AMR support and B_PLAY_UL In-Reply-To: <1713101439982875@web26o.yandex.ru> References: <1713101439982875@web26o.yandex.ru> Message-ID: Hi, > I tried to add simple AMR support in osmocombb project. I tested it with C123 (DSP API v 36). I set AMR config from assigment command, set AMR detection thresholds, make sync, etc. > It looks like downlink works fine, but I have problem with uplink: it send data directly from microphone and ignore data in dsp_api.ndb->a_du_1 even if I set dsp_api.ndb->d_tch_mode|=B_PLAY_UL. Also, I can see uplink data on dsp_api.ndb->a_du_0 like B_PLAY_UL is fully ignored. > Did anyone have that issue before? I know that AMR codec is more complex that TCH, but did someone know a way to send custom data from host using AMR codec? TBH I'm not sure anyone tried AMR at all ... Can you post the diff you're using atm ? AFAIK The v36 DSP has buggy AMR support and the normal firmware loads some DSP patches to make it work properly. Cheers, Sylvain