Common library for all Osmocom projects (libosmocore, libosmogsm, libosmovty, libosmogb, libosmosim, libosmousb, ...) https://osmocom.org/projects/libosmocore
Go to file
Pau Espin c3b904a87d vty: Allow using hex representations in cmd numeric ranges
Ranges can now be specified in hexadecimal notation. In this case, only
hexadecimal values are accepted (prefixed with "0x").

In order to allow using a hexadecimal value as an input argument, the
command must specify the range in hexadecimal form.
This way all existing commands (decimal) won't get an hexadecimal value
unless they are further extended in the future, avoiding hard to notice
breakage due to use of stroul() without using base=0 or even worse,
using atoi() directly (which only understands decimal and provides no
error checking mechanism).

A command argument can be expanded to accept both decimal and hex in a
range by means of specifying both, example:
"mycmd (<0-255>|<0x0-0xff>)".

Related: OS#5631
Change-Id: Ia2b7fbbf5502c28374c21dbff548232680da27d4
2022-09-15 16:25:56 +02:00
contrib Bump version: 1.6.0.132-0239-dirty → 1.7.0 2022-06-28 17:00:51 +02:00
debian Bump version: 1.6.0.132-0239-dirty → 1.7.0 2022-06-28 17:00:51 +02:00
doc merge_doc.xsl: move to osmo-gsm-manuals.git 2018-11-12 14:07:05 +01:00
include utils.h: protect param with parenthesis in OSMO_BYTES_FOR_BITS() 2022-09-08 15:03:44 +02:00
m4 Add code coverage support 2019-11-30 02:17:23 +00:00
src vty: Allow using hex representations in cmd numeric ranges 2022-09-15 16:25:56 +02:00
tapset support for stats static userspace probes via systemtap 2021-02-22 09:58:00 +01:00
tests vty: Allow using hex representations in cmd numeric ranges 2022-09-15 16:25:56 +02:00
utils osmo-arfcn: Fix false positive in gcc 12.1.0 2022-05-13 13:20:48 +02:00
.gitignore Ignore osmo-ns-dummy 2022-08-09 08:55:57 +00:00
.gitreview add .gitreview 2016-05-19 06:39:13 +00:00
.mailmap Add .mailmap file for mapping mail addresses in shortlog 2016-08-08 13:12:17 +02:00
COPYING add GPL to project source 2010-02-21 09:21:30 +01:00
Doxyfile.codec.in Set HTML_TIMESTAMP to NO to make build reproducible 2019-07-17 11:03:44 +00:00
Doxyfile.coding.in doxygen: enable cross referencing everywhere 2019-02-04 16:43:57 +00:00
Doxyfile.core.in Set HTML_TIMESTAMP to NO to make build reproducible 2019-07-17 11:03:44 +00:00
Doxyfile.ctrl.in doxygen: enable cross referencing everywhere 2019-02-04 16:43:57 +00:00
Doxyfile.gb.in doxygen: enable cross referencing everywhere 2019-02-04 16:43:57 +00:00
Doxyfile.gsm.in Set HTML_TIMESTAMP to NO to make build reproducible 2019-07-17 11:03:44 +00:00
Doxyfile.vty.in Set HTML_TIMESTAMP to NO to make build reproducible 2019-07-17 11:03:44 +00:00
Makefile.am cosmetic tweak in Makefile.am 2022-06-14 19:45:02 +02:00
README.md update git URLs (git -> https; gitea) 2022-06-17 23:20:26 +02:00
TODO-RELEASE Bump version: 1.6.0.132-0239-dirty → 1.7.0 2022-06-28 17:00:51 +02:00
configure.ac update git URLs (git -> https; gitea) 2022-06-17 23:20:26 +02:00
git-version-gen add git-version-gen magic to automatically generate package version 2010-03-23 00:30:19 +08:00
libosmocodec.pc.in clean-up pkg-config files: Make use of "Requires" as documented 2022-03-24 14:57:22 +00:00
libosmocoding.pc.in clean-up pkg-config files: Make use of "Requires" as documented 2022-03-24 14:57:22 +00:00
libosmocore.pc.in configure: Support libsctp < 1.0.17 without libsctp.pc 2022-03-29 11:59:51 +02:00
libosmoctrl.pc.in clean-up pkg-config files: Make use of "Requires" as documented 2022-03-24 14:57:22 +00:00
libosmogb.pc.in libosmo{gb,vty}.pc.in: Add talloc to 'Requires' 2022-03-25 09:45:42 +00:00
libosmogsm.pc.in clean-up pkg-config files: Make use of "Requires" as documented 2022-03-24 14:57:22 +00:00
libosmosim.pc.in clean-up pkg-config files: Make use of "Requires" as documented 2022-03-24 14:57:22 +00:00
libosmousb.pc.in clean-up pkg-config files: Make use of "Requires" as documented 2022-03-24 14:57:22 +00:00
libosmovty.pc.in libosmo{gb,vty}.pc.in: Add talloc to 'Requires' 2022-03-25 09:45:42 +00:00
osmo-release.mk Fixup severe build performance issues 2017-10-04 16:26:37 +02:00
osmo-release.sh osmo-release.sh: Use variable containing bumpversion path everywhere 2022-01-05 23:09:17 +00:00

README.md

libosmocore - set of Osmocom core libraries

This repository contains a set of C-language libraries that form the core infrastructure of many Osmocom Open Source Mobile Communications projects.

Historically, a lot of this code was developed as part of the OpenBSC project, but which are of a more generic nature and thus useful to (at least) other programs that we develop in the sphere of Free Software / Open Source mobile communications.

There is no clear scope of it. We simply move all shared code between the various Osmocom projects in this library to avoid code duplication.

The libosmocore.git repository build multiple libraries:

  • libosmocore contains some general-purpose functions like select-loop abstraction, message buffers, timers, linked lists
  • libosmovty contains routines related to the interactive command-line interface called VTY
  • libosmogsm contains definitions and helper code related to GSM protocols
  • libosmoctrl contains a shared implementation of the Osmocom control interface
  • libosmogb contains an implementation of the Gb interface with its NS/BSSGP protocols
  • libosmocodec contains an implementation of GSM voice codecs
  • libosmocoding contains an implementation of GSM channel coding
  • libosmosim contains infrastructure to interface SIM/UICC/USIM cards

Homepage

The official homepage of the project is https://osmocom.org/projects/libosmocore/wiki/Libosmocore

GIT Repository

You can clone from the official libosmocore.git repository using

git clone https://gitea.osmocom.org/osmocom/libosmocore

There is a web interface at https://gitea.osmocom.org/osmocom/libosmocore

Documentation

Doxygen-generated API documentation is generated during the build process, but also available online for each of the sub-libraries at https://ftp.osmocom.org/api/latest/libosmocore/

Mailing List

Discussions related to libosmocore are happening on the openbsc@lists.osmocom.org mailing list, please see https://lists.osmocom.org/mailman/listinfo/openbsc for subscription options and the list archive.

Please observe the Osmocom Mailing List Rules when posting.

Contributing

Our coding standards are described at https://osmocom.org/projects/cellular-infrastructure/wiki/Coding_standards

We us a gerrit based patch submission/review process for managing contributions. Please see https://osmocom.org/projects/cellular-infrastructure/wiki/Gerrit for more details

The current patch queue for libosmocore can be seen at https://gerrit.osmocom.org/#/q/project:libosmocore+status:open