| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | include: reorganize headers file to include/osmocom/[gsm|core] | Pablo Neira Ayuso | 2011-03-23 | 1 | -2/+2 |
| | | | | | | | | | | | | | This patch moves all GSM-specific definitions to include/osmocom/gsm. Moreover, the headers in include/osmocore/ have been moved to include/osmocom/core. This has been proposed by Harald Welte and Sylvain Munaunt. Tested with `make distcheck'. Signed-off-by: Pablo Neira Ayuso <pablo@gnumonks.org> | ||||
| * | vty: integration with logging framework | Pablo Neira Ayuso | 2011-03-19 | 1 | -2/+3 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The logging categories are registered by the applications, like osmo-nitb, during startup. Thus, the VTY have to provide the logging commands according to the logging categories that the application has registered. Before this patch, the VTY contained the logging categories hardcoded. Thus, any change in the logging categories by the application would not be shown by the VTY. So far, this was not a problem because all applications used the same logging categories. However, according to what Harald told me, this may be a problem in the future. This patch resolve the lack of integration between the logging framework and the VTY by generating the VTY logging commands from the logging categories registered. Since this patch changes one function of the libosmocore API, it follows another patch for the openbsc application to get in sync with the new function layout. I have reworked and renamed the functions: * log_vty_category_string() * log_vty_level_string() to provide the new ones that generate the exact output that VTY requires. This patch does not release the memory allocated by talloc_zero_size() to store the VTY strings for the commands and the description. I found no exit function that can clean up resources that were allocated. | ||||
| * | LOGGING: remove duplicated code between vty-logging and cfg-logging | Harald Welte | 2011-02-18 | 1 | -0/+2 |
| | | |||||
| * | LOGGING: configure logging from the vty | Harald Welte | 2011-02-18 | 1 | -0/+1 |
| | | | | | | We can now configure logging to (multiple) files, stderr and syslog from the vty command line in a persistent way (config file) | ||||
| * | vty: Add functions to access index and node | Holger Hans Peter Freyther | 2010-09-14 | 1 | -0/+2 |
| | | | | | | | It is easier to call these two functions from bindings than wrapping the vty structure and figuring out the alignment of the enum on all different ABIs. | ||||
| * | vty: Make the talloc ctx extern void* to avoid duplicate symbols | Holger Hans Peter Freyther | 2010-08-31 | 1 | -1/+1 |
| | | |||||
| * | vty: Add a new callback to let code decide if it is a config node or not | Holger Hans Peter Freyther | 2010-08-26 | 1 | -0/+1 |
| | | |||||
| * | vty: Forward delcare the logging command. | Holger Hans Peter Freyther | 2010-08-04 | 1 | -0/+2 |
| | | |||||
| * | vty: Mark app info strings as const char*. | Holger Hans Peter Freyther | 2010-06-08 | 1 | -3/+3 |
| | | |||||
| * | [VTY] Remove all application specific VTY node definitions from enum | Harald Welte | 2010-05-31 | 1 | -41/+2 |
| | | |||||
| * | [VTY] Introduce "struct vty_app_info" for vty_init() function | Harald Welte | 2010-05-25 | 2 | -6/+10 |
| | | |||||
| * | make sure we actually install the vty headers | Harald Welte | 2010-05-25 | 1 | -2/+4 |
| | | |||||
| * | Create libosmovty as library from OpenBSC VTY functions | Harald Welte | 2010-05-25 | 7 | -0/+758 |
 |
index : libosmocore | |
| [no description] |
| summaryrefslogtreecommitdiffstats |