Dear list members, dear Mr. Tsou,
we had a couple of problems with the SSE support in Transceiver52 of
osmo-trx. The problem was that the -march=native, that is used when
compiling the x86 code in Transceiver52M/x86/. This would create a
platform dependent binary that can not be easily moved to another
platform. (e.g. binary is compiled on a machine that does support
SSE4.1, but used on a machine that only supports SSE3)
In order to solve the problem, we have added logic to detect the CPU
type at runtime and to switch between the base implementation
(Transceiver52M/common) and between the platform specific implementation.
Since there might be different compilers out there, which do not support
the -msse3 and -msse4.1 options, we also modified the build system to
detect if the compiler supports -msse3 and -msse4.1. If no support can
be detected, there is a hard fallback to the generic implementation.
The patches are currently in the review process, you can find them below:
https://gerrit.osmocom.org/2098 buildenv: Turn off native architecture
builds
https://gerrit.osmocom.org/2099 cosmetic: Make parameter lists uniform
https://gerrit.osmocom.org/2100 ssedetect: Add runtime CPU detection
https://gerrit.osmocom.org/2101 cosmetic: Add info about SSE support
https://gerrit.osmocom.org/2102 buildenv: Make build CPU invariant
https://gerrit.osmocom.org/2103 cosmetic: remove code duplication
https://gerrit.osmocom.org/2104 Add test program to verify convolution
implementation
https://gerrit.osmocom.org/2134 buildenv: Split up SSE3 and SSE4.1 code
There is also a readmine ticket concerning this change:
https://osmocom.org/issues/1869
It would be very kind if you could have a look at the changes and, if
possible, to approve them.
regards,
Philipp Maier
--
Philipp Maier <pmaier(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
* Geschaeftsfuehrer / Managing Director: Harald Welte
Hi,
this is the BTS test report for week12 2017.
BTS models which have been tested with OsmoNITB are:
- sysmoBTS1002
- octasic OCTBTS3500
- ettus USRP B200
- nanoBTS model:165G
All test cases have passed.
For additional information related to test cases, timeslots
configuration and voice codecs used, please visit:
https://osmocom.org/projects/cellular-infrastructure/wiki/Weekly_BTS_Tests
following are some git hashes/version strings of tested components:
libosmo-abis: 1e04d4b7a2c845589da20d891cc5e3c471cfe983
libosmocore: 62d6f2570358730965162f7dd756a6e2d07627b2
libosmo-netif: 3a060c59bec7a4a5b22849938b8b4c7b7ecb4c01
libosmo-sccp: 8e708d1f2da1b187f631bf08172a5194a85b1a23
libsmpp34: cc0bcd6bc051d5ccaf32cdbbc28f073369900857
openbsc: dd22a30d75090ebe2ba08056bfa04a92aa8d6ba1
openggsn: 19e19e3609508d121ba46c165e5ed1502a3cf9da
osmo-bts: b609ee879eb798f8f3836223b4702745f3f6491e
osmo-bts-octphy: b609ee879eb798f8f3836223b4702745f3f6491e
osmo-pcu: 0a8fae8d141c2cfa4387ffe9b35402d5b8cc85cd
osmo-trx: 14d13b67dcd4fa35b03cbbef0c5ddd2622b89155
sysmobts: OsmoBTS version 0.4.0.410-b609
sysmobts: Osmo-PCU version 0.2.896-0a8f
octbts: (name='octsdr_gsm', desc='Software Define Radio',
ver='02.07.00-B1039', ver_hdr='02.07.00-B1039')
octbts: (platform='Opus2', version='OCTSYS_VERSION=01.02.19.B1
OCTODK_VERSION=01.15.01-B1;OCTADF_VERSION=04.05.01-B2637;')
nanobts: Equipment_Version='165g029_79'
nanobts: Software_Version='168d462_v200b202d0'
if you are interested in the details, drop me a mail and i'll forward
the whole report.
kind regards
--
- Joachim Steiger <jsteiger(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
* Geschaeftsfuehrer / Managing Directors: Harald Welte
Hi,
this is the BTS test report for week11 2017.
BTS models which have been tested with OsmoNITB are:
- sysmoBTS1002
- octasic OCTBTS3500
- ettus USRP B200
- nanoBTS model:165G
All test cases passed except for one for one config of the octasic bts:
3 TCH/H, 3 PDCH
in this config the gprs did not work as expected. sorry no logs this time.
For additional information related to test cases, timeslots
configuration and voice codecs used, please visit:
https://osmocom.org/projects/cellular-infrastructure/wiki/Weekly_BTS_Tests
if you are interested in the details, drop me a mail and i'll forward
the whole report.
kind regards
--
- Joachim Steiger <jsteiger(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
* Geschaeftsfuehrer / Managing Directors: Harald Welte
Review at https://gerrit.osmocom.org/1999
debian: Make a new release with the new feature
Change-Id: Ibe86b761b494e0fb78bbbc78e3c1982e44185750
---
M debian/changelog
1 file changed, 6 insertions(+), 0 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-pcap refs/changes/99/1999/1
diff --git a/debian/changelog b/debian/changelog
index fd4259c..6e4df55 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+osmo-pcap (0.0.11) UNRELEASED; urgency=medium
+
+ * Add "source ip A.B.C.D" option to use specific address.
+
+ -- Holger Hans Peter Freyther <holger(a)moiji-mobile.com> Tue, 17 Jan 2017 09:12:52 +0100
+
osmo-pcap (0.0.10) unstable; urgency=medium
* New release with new features
--
To view, visit https://gerrit.osmocom.org/1999
To unsubscribe, visit https://gerrit.osmocom.org/settings
Gerrit-MessageType: newchange
Gerrit-Change-Id: Ibe86b761b494e0fb78bbbc78e3c1982e44185750
Gerrit-PatchSet: 1
Gerrit-Project: osmo-pcap
Gerrit-Branch: master
Gerrit-Owner: Holger Freyther <holger(a)freyther.de>
Hi.
A little heads-up - the current master of OpenBSC is failing at 'make
check' stage - see
http://jenkins.osmocom.org/jenkins/job/OpenBSC-gerrit/2019/IU=--disable-iu,…
for example.
Until this is fixed, any patches for OpenBSC won't be accepted by
jenkins. If you hit this - please retrigger corresponding failed build
in jenkins once it's fixed.
--
Max Suraev <msuraev(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
* Geschaeftsfuehrer / Managing Director: Harald Welte
openggsn failed because README was renamed to README.md without adjusting the debian installation rules (possibly the same change occured in other repositories, Harald?)
the osmo-auc-gen_test.sh still fails on 32bit systems, to be fixed by https://gerrit.osmocom.org/2089 (please review)
~N
Hi all,
today I've deployed some cgit improvements on https://git.osmocom.org/,
in the hope that it makes this tool even more useful:
1) syntax highlighting of source code (requested by Hoernchen)
The source code is now highlighted by pygments. I don't really
understand why somebody would want to look at source code a lot in a
browser, but well, it was as easy as to enable the existing pygments
based filter plugin.
2) rendering of "about" page from README.md
As you might have noticed, I've introduced a README.md in a number of
repositoires, and cgit is now rendering an about page for every
repository, e.g. at http://git.osmocom.org/libosmo-abis/about/
3) gerrit change-ID hyperlink generation
All gerrit Change-IDs in commit messages are now automatically converted
to hyperlinks to the respective gerrit change, see e.g. the below
example:
http://git.osmocom.org/openbsc/commit/?id=6dd0fc685b7149f67a5fe17a5bce55c44…
Please note that this works for the "Change-Id" line of the actual
change, but also for change-ids in the free text (e.g. "this depends on
change-id ... in libosmocore")
4) Osmocom ticket/issue hyperlink generation
Any Line that matches the "^((Relate|Close|Fixe)[ds]):" prefix is
scanned for occurrences of "OS#(\d+)" which are then amended with
hyperlinks to the respective issue on osmocom.org
Please note the OS# prefix is mandatory, so things like "OS#1614, 1615"
will not work, as can be seen at
http://git.osmocom.org/osmo-pcu/commit/?id=0a8fae8d141c2cfa4387ffe9b35402d5…
Please format your commit messages accordingly.
Regards,
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)
It seems that we won't be merging vlr_2G or vlr_3G into openbsc.git's
master, at least not soon. Instead we're likely to move to a new git
repository altogether to mark the changed setup.
We could switch 'Osmocom' over to vlr_3G and assume that it includes the
others, but that's not accurate at all. The VLR stuff cuts away half the
code from openbsc.git's master and 3G the other half. well, almost :)
So I thought we could repurpose two of the unused coverity scan projects
we have for the vlr_2G and vlr_3G branches. Or maybe one for vlr_3G would
be enough.
It seems we can't change the name of a coverity project. Maybe we can
just use the OpenBSC one for vlr_3G without changing the name?
We could possibly also include a separate build within the tar sent to
the Osmocom job, I can also check that out.
Or I can try and register a brand new one.
Any preferences?
~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
FYI, Philipp has been working on some patches to do the OsmoTRX cpu
instruction set extension detection at runtime rather than compile-time.
See "Bug #1869: osmo-trx binary cannot be moved to similar CPU"
https://osmocom.org/issues/1869#change-3394
As not everyone is following each redmine ticket or gerrit patch:
I would like the OsmoTRX folks (Tom, Alexander, ...) to have a look at
this. For convenience, the latest update to the ticket and the
associated links to the gerrit patches below:
---
The matching implementation is now selected dynamically during runtime.
In order to be sure that the convolution part did not break, I wrote a
small test program to compute some testvectors. I compared the results
before and after my changes. They match up. I made only minimal changes
to the conversion code, so I skipped testing that as well.
The SSE relevant sources are compiled with $(SIMD_FLAGS) now. The
sources only contain the SSE implementation and the decision logic to
defer to the correct implementation during runtime. That should run fine
on non SSE3 / SSE4.1 CPUs, since the decision logic is not
vectorize-able. However, we can divide this up further as discussed.
https://gerrit.osmocom.org/2098 buildenv: Turn off native architecture builds
https://gerrit.osmocom.org/2099 cosmetic: Make parameter lists uniform
https://gerrit.osmocom.org/2100 ssedetect: Add runtime CPU detection
https://gerrit.osmocom.org/2101 cosmetic: Add info about SSE support
https://gerrit.osmocom.org/2102 buildenv: Make build CPU invariant
https://gerrit.osmocom.org/2103 cosmetic: remove code duplication
https://gerrit.osmocom.org/2104 Add test program to verify convolution implementation
---
--
- 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)