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)
Hi all,
I temporarily disabled a cron job we run at rhizomatica that purges the
hlr SMS table of sent messages every day.
After a few days I noticed slightly sluggish behaviour in the VTY, and
sure enough, the nitb was consuming 100% cpu, not always, but presumably
whenever it does a queue run. I also just heard that in the last few
days, we got a number of reports from users, some confirmed by photos of
the phones, about messages being delivered to the wrong destination.
Apologies if this has been touched on before. I am not finding where I
can directly search this list archives. Anyway, it might not be so bad
to bring it up, as the cron job purging via cron job calling sqlite3 is
not ideal, and anyway.. this crossed messages shouldn't happen, right? I
imagine we'd like to track this one down.
Keith.
Hi.
This has been asked last year but to no avail, let's try again.
How logical channels are (de)activated in osmo-bts-trx? For example in
all the other models there's sapi_deactivate_cb() callback but
osmo-bts-trx doesn't seem to be using sapi_cmd at all.
To put this into perspective - while working on
https://projects.osmocom.org/issues/1575 I got to activate/deactivate
lchans when SI3 is received. This already works for sysmobts but I'd
like to do the same for osmo-bts-trx as well.
Is there any documentation somewhere describing how it works there? Or
maybe someone more familiar with the code could help to shed the light
on it?
--
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
Hi.
There's strange thing about the way autoconf and debian/rules interact
for OpenBSC:
- in openbsc/include/openbsc/Makefile.am gsm_data_shared.h and
common_cs.h are in noinst_HEADERS
- in debian/openbsc-dev.install they are marked for installation
And this actually works! If you run "dpkg-buildpackage -uc -us -tc"
you'll get openbsc-dev*.deb with those headers properly installed.
It's nice but feels a bit too much like magic. Any ideas how dh_install
(or smth else?) manages to work around it?
Should we be worried that it might break some time in future? Should we
move those headers away from noinst_* section?
--
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
This is a bit vague again...
I have found across our sites several entries with a value of Inf for
IMSI on a create-on-demand subscriber:
For example:
sqlite> select * from Subscriber where id=284054;
284054|2017-03-08 21:19:40|2017-03-08 21:19:40|Inf||20649|0||0|
I also have some Inf values for IMEI in Equipment:
sqlite> select id,created,imei from Equipment where id = 95108;
95108|2014-03-13 03:18:06|Inf
Not a big deal for operations, just thought I'd mention it as I noticed
while restoring backups, (sqlite3 doesn't like to reimport the Inf value
it writes itself with .dump)
Hi,
I have a Siemens BS-11 with the factory cable for the LMT that has a
DSUB-9 plug on the non-BTS end.
When I connect a USB<-->RS232 adapter and run either $ cu -l /dev/ttyUSB
or bs11_config -p /dev/ttyUSB0 I do not get any output when I switch on
the BTS. I tried with nullmodem adapter and without just to be sure
since I often mix up the pinouts.
I was not able to measure any voltage on any of the DSUB-9 pins when the
BTS is powered up, but believe that on either RX or TX there should be
the voltage level of the serial line since RS232 is active low.
Has somebody seen this behavior?
-Alex
