| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
We have to determine the SAPI ourselves inside the LAPDm header.
|
|
|
|
|
|
|
|
| |
... I should do more testing :(
Conflicts:
src/logging.c
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
We do this by using a trick: library-internal log categories use
negative subsystem numbers, which are converted into positive
array indexes at the time of logging.
library-internal log categories need to be knwo at compile-time,
while application-specified categories now are of unlimited number,
as they are dynamically allocated.
|
| |
|
| |
|
|
|
|
| |
(from openbsc's rsl_number_of_paging_subchannels)
|
| |
|
| |
|
|
|
|
|
| |
Written-by: Andreas Eversberg <jolly@eversberg.eu>
Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
|
|
|
|
|
| |
those two are used in the RSL SACCH FILLING messages and delivered
like SI5 / SI6.
|
| |
|
| |
|
|
|
|
|
| |
The idea here is to use the osmocom core primitive code ot abstract out
primitives for inter-layer comunication in GSM.
|
| |
|
|
|
|
|
|
|
|
| |
This extends the socket infrastructure in libosmocore to allow
to create non-blocking sockets.
Basically, it replaces the connect0_bind1 parameter by one
flags parameter.
|
|\ |
|
| |
| |
| |
| | |
(otherwise 'struct value_string' would not be defined)
|
| | |
|
| |
| |
| |
| | |
This will tell getaddrinfo() that we want a INADDR_ANY style socket
|
| |
| |
| |
| |
| | |
This file is using enums in that might or might not be
known to the compiler. Forward declare them.
|
| |
| |
| |
| |
| |
| | |
write_queue already frees the message after the callback is called.
Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
|
| |
| |
| |
| |
| |
| | |
0xff is the maximum value ... so there is 256 elements.
Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Apparently getifaddrs() returns ifa's without an ifa_addr set.
|
|\| |
|
| | |
|
| |
| |
| |
| |
| | |
rename autoconf input file to align with osmocom-bb host applications,
and because that suffix is preferred nowadays.
|
| |
| |
| |
| |
| |
| | |
autoconf >=2.68 demands the body of an AC_COMPILE_IFELSE to be wrapped in
an AC_LANG_SOURCE macro, otherwise outputs annoying warnings on the
invocation of `autoreconf -i`. this patch follows that demand.
|
| | |
|
| |
| |
| |
| | |
warning: array ‘abis_nm_obj_class_names’ assumed to have one element
|
| |
| |
| |
| |
| |
| |
| |
| | |
and export the underlying raw value_string arrays instead:
abis_nm_obj_class_names / abis_nm_adm_state_names.
This permits the caller to use get_string_value() as well as
get_value_string().
|
| | |
|
|\| |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
osmo_sock_init_ofd() is a wrapper around osmo_sock_init() which will
take care of initializing and registering a 'struct osmo_fd' for the
newly-created socket.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
* use write_queue where applicable
* provide functions that work on raw FD and those with osmo_fd
* add support for multiple gsmtap instances (no global variables)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Harald reported a problem in the logging:
http://lists.osmocom.org/pipermail/openbsc/2011-May/002896.html
Reverting 81e9636454294ae10ef9bc8bf149dd0248afce76 seems to
fix the problem. However, that workaround looks ugly.
Holger gives us another clue on what was wrong:
http://lists.osmocom.org/pipermail/openbsc/2011-May/002905.html
While digging in the manpage, I found this:
"The functions vprintf(), vfprintf(), vsprintf(), vsnprintf()
are equivalent to the functions printf(), fprintf(), sprintf(),
snprintf(), respectively, except that they are called with a
va_list instead of a variable number of arguments. These functions
do not call the va_end macro. Consequently, the value of ap is
undefined after the call. The application should call va_end(ap)
itself afterwards."
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Harald reported a problem in the logging:
http://lists.osmocom.org/pipermail/openbsc/2011-May/002896.html
Reverting 81e9636454294ae10ef9bc8bf149dd0248afce76 seems to
fix the problem. However, that workaround looks ugly.
Holger gives us another clue on what was wrong:
http://lists.osmocom.org/pipermail/openbsc/2011-May/002905.html
While digging in the manpage, I found this:
"The functions vprintf(), vfprintf(), vsprintf(), vsnprintf()
are equivalent to the functions printf(), fprintf(), sprintf(),
snprintf(), respectively, except that they are called with a
va_list instead of a variable number of arguments. These functions
do not call the va_end macro. Consequently, the value of ap is
undefined after the call. The application should call va_end(ap)
itself afterwards."
|
|
|
|
|
|
|
|
|
| |
The plan is to collect structs and routines for application
setup and remove many copies of the boilerplate code we have
right now. This starts with routines to ignore certain signals
and the stderr init code.
Increment the age of the library because a new interface was added.
|