baseband-devel

baseband-devel@lists.osmocom.org

3 participants
2004 discussions

Re: Cell_log > gsmmap
by Bogdan Alecu 26 Jan '11

26 Jan '11

Or even better, use Google API and this way you could also include the Signal strenght and Timing advance for a better position. See http://translate.google.com/translate?js=y&prev=_t&hl=en&ie=UTF-8&layout=1&… --- On Wed, 1/26/11, Bogdan Alecu <b.alecu(a)yahoo.com> wrote: From: Bogdan Alecu <b.alecu(a)yahoo.com> Subject: Re: Cell_log > gsmmap To: Cc: baseband-devel(a)lists.osmocom.org Date: Wednesday, January 26, 2011, 7:27 AM I just thought of another way of using cell_log without GPS. The resulting KML could be parsed and sent to opencellid project, this way we could get the lat-long coordinates and afterward create another kml and send it to Google. Ex: http://www.opencellid.org/cell/get?mcc=232&mnc=01&cellid=1721&lac=4269

1 0

[PATCH] Adjust top-level Makefile for arm-none-eabi toolchain
by Peter Stuge 25 Jan '11

25 Jan '11

The gnuarm.com toolchain works fine but is very old. And although it is based on newlib, the os name in the tuple that we used to configure for is arm-elf-linux, which is of course bogus since we are not building Linux applications. Finally, CC= should never be set, instead configure should detect the right compiler using the --host tuple. --- src/Makefile | 8 ++++---- 1 files changed, 4 insertions(+), 4 deletions(-) diff --git a/src/Makefile b/src/Makefile index b3594c1..e66f0ff 100644 --- a/src/Makefile +++ b/src/Makefile @@ -1,10 +1,10 @@ # this is not really used as we don't do 'make install'. You can still specify # it in case you _want_ to manually 'make install' the target libosmocore. -CROSS_INST_PREFIX=/usr/local/stow/osmocom-bb/arm-elf +CROSS_INST_PREFIX ?= /usr/local/stow/osmocom-bb/arm-2010.09 # this is the prefix of your cross-toolchain programs -CROSS_TOOL_PREFIX=arm-elf- +CROSS_TOOL_PREFIX ?= arm-none-eabi- TOPDIR=$(shell pwd) OSMOCORE_CONFIGURE_ENV= LIBOSMOCORE_LIBS=$(TOPDIR)/shared/libosmocore/build-host/src/.libs/libosmocore.a \ @@ -37,9 +37,9 @@ shared/libosmocore/build-target: shared/libosmocore/build-target/Makefile: shared/libosmocore/configure shared/libosmocore/build-target cd shared/libosmocore/build-target && ../configure \ - --host=arm-elf-linux --disable-vty --enable-panic-infloop \ + --host=arm-none-eabi --disable-vty --enable-panic-infloop \ --disable-shared --disable-talloc --disable-tests \ - CC="$(CROSS_TOOL_PREFIX)gcc" CFLAGS="-Os -ffunction-sections -I$(TOPDIR)/target/firmware/include -nostartfiles -nodefaultlibs" + CFLAGS="-Os -ffunction-sections -I$(TOPDIR)/target/firmware/include -nostartfiles -nodefaultlibs" shared/libosmocore/build-target/src/.libs/libosmocore.a: shared/libosmocore/build-target/Makefile cd shared/libosmocore/build-target && make -- 1.7.2

4 6

[PATCH] Adjust top-level Makefile for arm-none-eabi toolchain
by Peter Stuge 25 Jan '11

25 Jan '11

The gnuarm.com toolchain works fine but is very old. And although it is based on newlib, the tuple that we used to configure for was arm-elf-linux, which is of course bogus since we aren't building Linux applications. This patch optimizes for the CodeSourcery G++ Lite 2010.09 ARM EABI toolchain, and assumes that it was unpacked next to the old one. Download here: http://www.codesourcery.com/sgpp/lite/arm/portal/release1592 (I haven't gotten the Linux Installer to work, so I recommend the TAR.) And since CC is detected by configure when a valid host tuple is given and that toolchain is sane there's no need for us to hard-code the gnuarm.com compiler name in our Makefile. --- src/Makefile | 11 +++++++---- 1 files changed, 7 insertions(+), 4 deletions(-) diff --git a/src/Makefile b/src/Makefile index b3594c1..bb34175 100644 --- a/src/Makefile +++ b/src/Makefile @@ -1,10 +1,13 @@ # this is not really used as we don't do 'make install'. You can still specify # it in case you _want_ to manually 'make install' the target libosmocore. -CROSS_INST_PREFIX=/usr/local/stow/osmocom-bb/arm-elf +CROSS_INST_PREFIX ?= /usr/local/stow/osmocom-bb/arm-2010.09 + +# this is the host tuple of your cross-toolchain +HOST ?= arm-none-eabi- # this is the prefix of your cross-toolchain programs -CROSS_TOOL_PREFIX=arm-elf- +CROSS_TOOL_PREFIX ?= $(HOST)- TOPDIR=$(shell pwd) OSMOCORE_CONFIGURE_ENV= LIBOSMOCORE_LIBS=$(TOPDIR)/shared/libosmocore/build-host/src/.libs/libosmocore.a \ @@ -37,9 +40,9 @@ shared/libosmocore/build-target: shared/libosmocore/build-target/Makefile: shared/libosmocore/configure shared/libosmocore/build-target cd shared/libosmocore/build-target && ../configure \ - --host=arm-elf-linux --disable-vty --enable-panic-infloop \ + --host=$(HOST) --disable-vty --enable-panic-infloop \ --disable-shared --disable-talloc --disable-tests \ - CC="$(CROSS_TOOL_PREFIX)gcc" CFLAGS="-Os -ffunction-sections -I$(TOPDIR)/target/firmware/include -nostartfiles -nodefaultlibs" + CFLAGS="-Os -ffunction-sections -I$(TOPDIR)/target/firmware/include -nostartfiles -nodefaultlibs" shared/libosmocore/build-target/src/.libs/libosmocore.a: shared/libosmocore/build-target/Makefile cd shared/libosmocore/build-target && make -- 1.7.2 --nEsDIrWrg+hrB7l1--

1 0

[PATCH] Adjust top-level Makefile for arm-none-eabi toolchain
by Peter Stuge 25 Jan '11

25 Jan '11

The gnuarm.com toolchain works fine but is very old. And although it is based on newlib, the tuple that we used to configure for was arm-elf-linux, which is of course bogus since we aren't building Linux applications. This patch optimizes for the CodeSourcery G++ Lite 2010.09 ARM EABI toolchain, and assumes that it was unpacked next to the old one. Download here: http://www.codesourcery.com/sgpp/lite/arm/portal/release1592 (I haven't gotten the Linux Installer to work, so I recommend the TAR.) And since CC is detected by configure when a valid host tuple is given and that toolchain is sane there's no need for us to hard-code the gnuarm.com compiler name in our Makefile. --- src/Makefile | 11 +++++++---- 1 files changed, 7 insertions(+), 4 deletions(-) diff --git a/src/Makefile b/src/Makefile index b3594c1..f2d935b 100644 --- a/src/Makefile +++ b/src/Makefile @@ -1,10 +1,13 @@ # this is not really used as we don't do 'make install'. You can still specify # it in case you _want_ to manually 'make install' the target libosmocore. -CROSS_INST_PREFIX=/usr/local/stow/osmocom-bb/arm-elf +CROSS_INST_PREFIX ?= /usr/local/stow/osmocom-bb/arm-2010.09 + +# this is the host tuple of your cross-toolchain +HOST ?= arm-none-eabi- # this is the prefix of your cross-toolchain programs -CROSS_TOOL_PREFIX=arm-elf- +CROSS_TOOL_PREFIX ?= $(CROSS)- TOPDIR=$(shell pwd) OSMOCORE_CONFIGURE_ENV= LIBOSMOCORE_LIBS=$(TOPDIR)/shared/libosmocore/build-host/src/.libs/libosmocore.a \ @@ -37,9 +40,9 @@ shared/libosmocore/build-target: shared/libosmocore/build-target/Makefile: shared/libosmocore/configure shared/libosmocore/build-target cd shared/libosmocore/build-target && ../configure \ - --host=arm-elf-linux --disable-vty --enable-panic-infloop \ + --host=$(HOST) --disable-vty --enable-panic-infloop \ --disable-shared --disable-talloc --disable-tests \ - CC="$(CROSS_TOOL_PREFIX)gcc" CFLAGS="-Os -ffunction-sections -I$(TOPDIR)/target/firmware/include -nostartfiles -nodefaultlibs" + CFLAGS="-Os -ffunction-sections -I$(TOPDIR)/target/firmware/include -nostartfiles -nodefaultlibs" shared/libosmocore/build-target/src/.libs/libosmocore.a: shared/libosmocore/build-target/Makefile cd shared/libosmocore/build-target && make -- 1.7.2 --dMyqICaxQaaUjrCL--

1 0

[PATCH] Allow top-level Makefile to use arm-none-eabi toolchain
by Peter Stuge 25 Jan '11

25 Jan '11

The gnuarm.com toolchain works fine but is very old. And although it is based on newlib, the tuple that we used to configure for was arm-elf-linux, which is bogus since we aren't building for Linux. This patch optimizes for the CodeSourcery G++ Lite 2010.09 ARM EABI toolchain instead, and for libosmocore installation it assumes that the new toolchain was unpacked next to the old one. Download it here: http://www.codesourcery.com/sgpp/lite/arm/portal/release1592 (The Linux Installer seems not to work reliably so I recommend the TAR.) Since CC is detected by configure when the host tuple points to a sane toolchain we shouldn't hard-code the gnuarm.com compiler. The patch autodetects arm-elf-gcc installed in PATH, and uses arm-elf as prefix if it is found. Otherwise, it defaults to arm-none-eabi. make CROSS_HOST=arm-xyzzy can be used to override on the command line. --- src/Makefile | 11 +++++++---- 1 files changed, 7 insertions(+), 4 deletions(-) diff --git a/src/Makefile b/src/Makefile index b3594c1..402f28a 100644 --- a/src/Makefile +++ b/src/Makefile @@ -1,10 +1,13 @@ # this is not really used as we don't do 'make install'. You can still specify # it in case you _want_ to manually 'make install' the target libosmocore. -CROSS_INST_PREFIX=/usr/local/stow/osmocom-bb/arm-elf +CROSS_INST_PREFIX ?= /usr/local/stow/osmocom-bb/arm-2010.09 + +# this is the host tuple of your cross-toolchain +CROSS_HOST ?= $(shell which arm-elf-gcc >/dev/null 2>&1 && echo arm-elf || echo arm-none-eabi) # this is the prefix of your cross-toolchain programs -CROSS_TOOL_PREFIX=arm-elf- +CROSS_TOOL_PREFIX=$(CROSS_HOST)- TOPDIR=$(shell pwd) OSMOCORE_CONFIGURE_ENV= LIBOSMOCORE_LIBS=$(TOPDIR)/shared/libosmocore/build-host/src/.libs/libosmocore.a \ @@ -37,9 +40,9 @@ shared/libosmocore/build-target: shared/libosmocore/build-target/Makefile: shared/libosmocore/configure shared/libosmocore/build-target cd shared/libosmocore/build-target && ../configure \ - --host=arm-elf-linux --disable-vty --enable-panic-infloop \ + --host=$(CROSS_HOST) --disable-vty --enable-panic-infloop \ --disable-shared --disable-talloc --disable-tests \ - CC="$(CROSS_TOOL_PREFIX)gcc" CFLAGS="-Os -ffunction-sections -I$(TOPDIR)/target/firmware/include -nostartfiles -nodefaultlibs" + CFLAGS="-Os -ffunction-sections -I$(TOPDIR)/target/firmware/include -nostartfiles -nodefaultlibs" shared/libosmocore/build-target/src/.libs/libosmocore.a: shared/libosmocore/build-target/Makefile cd shared/libosmocore/build-target && make -- 1.7.2 --ibvzjYYg+QDzMCy1--

1 0

C99 [was Fwd: Cell_log > gsmmap]
by Dieter Spaar 25 Jan '11

25 Jan '11

Hello Holger, On Tue, 25 Jan 2011 16:51:02 +0100, "Holger Hans Peter Freyther" <holger(a)freyther.de> wrote: > > Almost perfect. I can apply and modify myself or you could do two things. We > tend to avoid the '//' comments, they were only added in C99 and used to be a > GCC extension for C. This is a good one ;-) One of the biggest problems when I tried a long time ago to compile any of OpenBSC or OsmocomBB with a different compiler than GCC were designated initializer which are _heavily_ used all over the sources (I don't question their advantage, I only mention it). They are a C99 feature (besides the library function snprintf() in the patch you commented). So I would not care about the '//', this was the smallest problem I had when I did my porting experiment (in fact the compilers I am aware of silently accept it). Just out of interest, do we really want to to avoid C99 ? I know there is this implicit "kernel style" coding rule, does it include C99 ? Please note that I don't want to discuss this, I use GCC from Cygwin and can find workarounds for Linux specific issues on Windows on my own, so I don't care that much. I am just interested in the reasons for using C99 or not. Best regards, Dieter -- Dieter Spaar, Germany spaar(a)mirider.augusta.de

5 5

RE:Cell_log > gsmmap
by Bogdan Alecu 25 Jan '11

25 Jan '11

A Wiki on how to use it would be great!

2 3

Fwd: Cell_log > gsmmap
by MArc Richter 25 Jan '11

25 Jan '11

Do i need a GPS Reciver ? I tought that it will calculate the location over Triangulation ? On Tue, Jan 25, 2011 at 10:34 AM, Holger Hans Peter Freyther < holger(a)freyther.de> wrote: > On 01/25/2011 08:33 AM, MArc Richter wrote: > > > But when i convert it into a kml file with gsmmap i can't see any GPS > > koordinates. Why ? > > Do you have a GPS receiver attached to your computer? > >

12 42

Cell_log > gsmmap
by MArc Richter 25 Jan '11

25 Jan '11

Hey! I've tryed out the Cell_log tool to get the Location of the GSM cells. But when i convert it into a kml file with gsmmap i can't see any GPS koordinates. Why ? I use the Sylvain branch an compiled with TX support thx

2 1

question on pirelli dp l10
by Scott Weisman 25 Jan '11

25 Jan '11

I looked more into this phone recently and found out it supported SIP over WiFi as well. Does anyone know about the software running the phone? How are the VOIP codecs handled? Is there hardware support for them? Finally, does code and/or drivers already exist for the hardware components? I happened to be looking for something exactly like this anyway. Cool to know that OsmocomBB can (potentially) work on it too. Scott

2 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel