summaryrefslogtreecommitdiffstats
path: root/include/osmocom/core
Commit message (Collapse)AuthorAgeFilesLines
* linuxrbtree: don't use 'new' as argument name to avoid C++ incompatibilityHarald Welte2012-06-181-1/+1
|
* signal: add SS_L_NS as a signal subsystem for NS code in libosmo-gbHarald Welte2012-06-161-0/+1
|
* doc: Fix the Doxygen section endingsSylvain Munaut2012-04-1816-16/+16
| | | | Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
* misc: Fix warning when compiling telnet_interface.cHolger Hans Peter Freyther2012-03-161-0/+1
| | | | | | | | In file included from telnet_interface.c:30:0: osmocom/core/socket.h:25:4: warning: 'struct osmo_fd' declared inside parameter list [enabled by default] telnet_interface.c: In function 'telnet_init_dynif': telnet_interface.c:84:4: warning: passing argument 1 of 'osmo_sock_init_ofd' from incompatible pointer type [enabled by default] osmocom/core/socket.h:24:5: note: expected 'struct osmo_fd *' but argument is of type 'struct osmo_fd *'
* gsmtap: Add GSMTAP_GPRS_CS() / GSMTAP_GPRS_MCS()Harald Welte2012-02-081-0/+8
| | | | | | | | As requested by Mike Morrin <Mike.Morrin@ipaccess.com>, we introduce GSMTAP sub-types for all the different GPRS and EGPRS coding schemes. This is neccessary due to the fact that the RLC PDU doesn't contain any explicit indication of the coding scheme used on the radio layer.
* gsmtap: make sure we agree with wireshark on GSMTAP channel typesHarald Welte2012-01-261-2/+2
|
* msgb_trim(): actually trim to an absolute length, as the comment statesHarald Welte2012-01-141-5/+3
| | | | | The previous commit introduced a new msgb_trim() but the implementation differed from the specification.
* msgb: introduce msgb_trim() and msgb_l3trim() to trim msgb'sHarald Welte2012-01-141-0/+28
|
* core/conv: Add utility methods to know length of coded/decoded vectorsSylvain Munaut2011-11-241-0/+6
| | | | Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
* core/conv: Add support for other termination types (trunc & tail biting)Sylvain Munaut2011-11-241-6/+25
| | | | | | | | Note that this breaks the ABI and the low level API. But it shouldn't break the high level API, nor the conv code definitions (because fields default to 0, and for new fields '0' is the previous behavior) Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
* core/conv: Minor documentation improvementsSylvain Munaut2011-11-241-12/+18
| | | | Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
* utils: Add declaration back for osmo_osmo_hexdump_nospcSylvain Munaut2011-11-131-0/+1
| | | | | | | | As it turns out, if a project uses the old name but without a declaration, it'll causes a segfault on 64 bits platform (because of the implicit int return type which doesn't apply since here it's a pointer). Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
* gsm/sms: Added DLSMS debuggingAndreas Eversberg2011-11-121-1/+2
| | | | | Written-by: Andreas Eversberg <jolly@eversberg.eu> Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
* core/rbtree: add const qualifier to some functionsSylvain Munaut2011-11-121-4/+4
| | | | | | | | | | | | | | | | | | | | | | See kernel commit f4b477c47332367d35686bd2b808c2156b96d7c7 ---- The 'rb_first()', 'rb_last()', 'rb_next()' and 'rb_prev()' calls take a pointer to an RB node or RB root. They do not change the pointed objects, so add a 'const' qualifier in order to make life of the users of these functions easier. Indeed, if I have my own constant pointer &const struct my_type *p, and I call 'rb_next(&p->rb)', I get a GCC warning: warning: passing argument 1 of ?~@~Xrb_next?~@~Y discards qualifiers from pointer target type Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com> Signed-off-by: David Woodhouse <David.Woodhouse@intel.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> ---- Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
* utils: Fix a bad double osmo_ prefix for osmo_hexdump_nospcSylvain Munaut2011-11-101-1/+1
| | | | | | Hopefully no project where using them it seems Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
* timer: Add compatibility header with timer helpersSylvain Munaut2011-10-212-0/+81
| | | | | | Some of these are not always present, especially when cross compiling Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
* timer: add scalable RB-tree based timer infrastructurePablo Neira Ayuso2011-10-171-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds RB-tree based timers which scales better than the previous list-based implementation. It does not require any API changes. It breaks ABI because the osmo_timer_list structure has changed though (to avoid this in the future, we can put internal data in some private structure). The following table summarizes the worst-case computational complexity of this new implementation versus the previous one: rb-tree list-based ------- ---------- calculate next timer to expire O(1) O(n) insertion of new timer O(log n) O(n) deletion of timer O(log n) O(1) timer-fired scheduler O(log n) O(3n) The most repeated cases are: * the calculation of the next timer to expire, that happens in every loop of our select function. * the timer-fired scheduler execution. This new implementation only loses in the deletion of timer scenario, this happens because we may need to rebalance the tree after the removal. So I think there is some real gain if we have some situation in which we have to handle lots of timers.
* add rb-tree implementation to libosmocorePablo Neira Ayuso2011-10-172-1/+161
| | | | | | | | | This patch adds red black trees implementation to libosmocore. This data structure is very useful to search for elements in ordered sets in O(log n) instead of O(n) that lists provide. The first client of this code will be one follow up patch that implements rbtree-based timer scheduler.
* Added defines to use primitive/operation tuples in switch/case statementsAndreas Eversberg2011-10-101-0/+3
|
* Changed logging of LAPD from DLLAPDM to DLLAPDroot2011-10-101-1/+1
|
* gsmtap: Add type/subtypes for GMR-1 protocolSylvain Munaut2011-10-091-0/+23
| | | | Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
* GSMTAP: Add comments to explain how to make GSMTAP changesHarald Welte2011-10-081-0/+24
|
* GSMTAP: Import changes from WiresharkHarald Welte2011-10-081-0/+11
| | | | | | | | There have been some changes in the wireshark source code that have never been submitted to gsmtap.h GSMTAP_CHANNEL_PACCH has been defined in an incompatible way in mainline wirshark :(
* gsmtap: Add a _ex version of gsmtap_{makemsg,send} to specify content typeSylvain Munaut2011-09-261-0/+9
| | | | | From: iZsh <izsh@fail0verflow.com> Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
* bring gsmtap.h in sync with recent wireshark additionsHarald Welte2011-09-261-0/+4
|
* core: Add generic CRC functions (templates expended to 8 16 32 64 bits)Sylvain Munaut2011-09-163-1/+106
| | | | Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
* core/serial: Add utilities to deal with serial portsSylvain Munaut2011-09-022-0/+47
| | | | Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
* build/include: Only install headers for enabled optionsSylvain Munaut2011-09-021-1/+9
| | | | Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
* logging: include stdarg.h for va_listChristoph Fritz2011-09-011-0/+1
| | | | | | | | | | fixes tiny compile error: CC socket.lo In file included from socket.c:13: ../include/osmocom/core/logging.h:31: error: expected declaration specifiers or ‘...’ before ‘va_list’ make[3]: *** [socket.lo] Error 1
* add functions for bit-reversalHarald Welte2011-09-011-0/+27
| | | | | Sometimes we need stuff like reversing every bit in each byte (but not the byte-order).
* logging: add osmo_vlogp() as vararg / va_list compatible functionHarald Welte2011-08-311-0/+3
|
* signal: Fix compiler warning about signedness of constantHolger Hans Peter Freyther2011-08-221-2/+2
| | | | | | | Use the u suffix to mark the constant as unsiged integer. This fixes: warning: this decimal constant is unsigned only in ISO C90
* doxygen: Add documentation for gsmtap_util.[ch]Harald Welte2011-08-171-15/+10
|
* doxygen: Add documentation to signal.[ch]Harald Welte2011-08-171-2/+10
|
* doxygen: Add documentation for prim.hHarald Welte2011-08-171-9/+26
|
* doxygen: document panic.[ch]Harald Welte2011-08-171-1/+10
|
* doxygen: Add docs for rate_ctrHarald Welte2011-08-171-26/+34
|
* doxygen: Add 'write_queue' moduleHarald Welte2011-08-171-24/+6
|
* doxygen: add doxygen module 'utils'Harald Welte2011-08-171-54/+7
|
* doxygen documentation for logging frameworkHarald Welte2011-08-171-25/+44
|
* some more doxygen work (include the notion of modules)Harald Welte2011-08-178-195/+84
|
* start to add doxygen documentation to libosmocore headersHarald Welte2011-08-169-52/+507
|
* fix off-by-one error in OSMO_NUM_DLIBHarald Welte2011-07-291-1/+1
| | | | | This bug was introduced in 95f7eb288c4b8b69d61fa8d68957fb21f09e11e5 and it caused a segfault on 'write terminal'
* add definition of OSMO_MIN macro, similar to OSMO_MAXHarald Welte2011-07-271-0/+1
|
* remove DLRSL and DLNM, we don't need themHarald Welte2011-07-211-3/+1
| | | | | They are not used anywhere in our libraries, so they should be defined by the respective applications
* make sure we don't have namespace clashes between libraries and appsHarald Welte2011-07-192-9/+9
| | | | | | | | * All loging prefixes in libraries should be DL like DLINP * All signals / subsystems should be called S_L_* SS_L_* * All command nodes should be called L_*_NODE This makes sure existinc code still compiles as expected
* mkae the new 'void *dst' member part of a union with the trx pointerHarald Welte2011-07-181-3/+4
| | | | | this ensures struct msgb is the same size as before, which will ensure binary compatibility
* msgb: add ->dst attribute to store routing informationPablo Neira Ayuso2011-07-181-0/+3
| | | | | | | | | | This patch adds a new attribute to msgb objects. This new attribute will store a pointer to the routing information, in the case of the A-bis link, this will be used to store e1inp_sign_link instead of struct gsm_bts_trx. This deprecates msg->trx, that can be removed once all application are ported to use msg->dst.
* logging: add libosmo-abis logging subsystemsPablo Neira Ayuso2011-07-181-1/+7
| | | | | | This adds the libosmo-abis logging subsystems to libosmocore, it uses the new change that harald proposed based on negative numbers for library logging subsystems.
* signal: reserve signal subsystems >= INT_MAX/2 for librariesPablo Neira Ayuso2011-07-181-0/+23
| | | | | | | | | The first range (from 0 to INT_MAX/2) of signal subsystems can be used by client applications while the second range (from INT_MAX) is reserved for libraries. This is useful to support signals defined in libraries that may be used by different client applications.
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-02 08:51:39 +0000