From mattjevans at btinternet.com Fri Feb 4 10:08:53 2011 From: mattjevans at btinternet.com (MATTHEW EVANS) Date: Fri, 4 Feb 2011 10:08:53 +0000 (GMT) Subject: Non Standard Baud Rates? Message-ID: <599484.47741.qm@web86604.mail.ird.yahoo.com> *bump* Anyone have any thoughts / advice on this? Many Thanks, Matt. ----- Original Message ---- From: MATTHEW EVANS To: baseband-devel at lists.osmocom.org Sent: Friday, 21 January, 2011 21:08:36 Subject: Non Standard Baud Rates? Hi, I'm trying to get the burst_ind branch working at the higher speed baud rates. I have a USB to Serial FTDI Cable (FT232R) plus the T191. This setup works fine with the main trunk of osmocombb. When I fire up osmocon, layer1 appears to download to the phone and runs successfully. Osmocon then logs 'Received DOWNLOAD ACK from phone, your code is running now!'. The phone has layer1.bin displayed as usual. However it goes no further and just hangs. Could anyone please give any advice on what to try next? Thanks, Matt. From dario.lombardo at libero.it Tue Feb 1 08:43:09 2011 From: dario.lombardo at libero.it (Dario Lombardo) Date: Tue, 01 Feb 2011 09:43:09 +0100 Subject: Fwd: Cell_log > gsmmap In-Reply-To: References: <4D3E9940.3080109@freyther.de> <4D3E9B93.4040202@freyther.de> <4D3EADA3.3090409@libero.it> <4D42C2BA.5020308@libero.it> <4D43061C.9050408@gmx.de> <4D46AC48.3010206@libero.it> <2e464f1e06e30d1199879dff023e8be0@auth.se> Message-ID: <4D47C79D.2060405@libero.it> On 01/31/2011 05:08 PM, S?bastien Lorquet wrote: > I don't see a huge problem here. > > Why not just parse whatever message with interesting info we get? > > if (!strcmp("$GPGLL") { > // extract coordinates and update buffer > } else if(!strcmp("$GPGGA)) { > // extract coordinates and update buffer > } else if(!strcmp("$GPRMC)) { > // extract coordinates and update buffer > } else if(!strcmp("$GPSuperProprietaryMessageWithAwesomePrecisionData")) { > // extract coordinates and update buffer > } else { > // no luck with this message > return; > } > I agree with this approach. I think that is scales well if a new device (even not nmea) wants to be supported. From mardnh at gmx.de Tue Feb 1 19:13:43 2011 From: mardnh at gmx.de (Martin Hauke) Date: Tue, 01 Feb 2011 20:13:43 +0100 Subject: Fwd: Cell_log > gsmmap In-Reply-To: <4D47C79D.2060405@libero.it> References: <4D3E9940.3080109@freyther.de> <4D3E9B93.4040202@freyther.de> <4D3EADA3.3090409@libero.it> <4D42C2BA.5020308@libero.it> <4D43061C.9050408@gmx.de> <4D46AC48.3010206@libero.it> <2e464f1e06e30d1199879dff023e8be0@auth.se> <4D47C79D.2060405@libero.it> Message-ID: <4D485B67.1050105@gmx.de> On 01.02.2011 09:43, Dario Lombardo wrote: > > On 01/31/2011 05:08 PM, S?bastien Lorquet wrote: >> I don't see a huge problem here. >> >> Why not just parse whatever message with interesting info we get? >> >> if (!strcmp("$GPGLL") { >> // extract coordinates and update buffer >> } else if(!strcmp("$GPGGA)) { >> // extract coordinates and update buffer >> } else if(!strcmp("$GPRMC)) { >> // extract coordinates and update buffer >> } else >> if(!strcmp("$GPSuperProprietaryMessageWithAwesomePrecisionData")) { >> // extract coordinates and update buffer >> } else { >> // no luck with this message >> return; >> } >> > I agree with this approach. I think that is scales well if a new > device (even not nmea) wants to be supported. how about a proper gpsd-integration? I've some spare time in the end of this month to try it. I would parse only one least common NMEA-sentence. As Mad said the "GPRMC"-sentence should be a good candidate for this. All other GPS-input-messages could be read via libgpsd from gpsd (which seems to be able to read even most obscure GPS-binary formats). best regards, Martin From vogelchr at vogel.cx Tue Feb 1 20:22:55 2011 From: vogelchr at vogel.cx (Christian Vogel) Date: Tue, 01 Feb 2011 21:22:55 +0100 Subject: Fwd: Cell_log > gsmmap In-Reply-To: <4D485B67.1050105@gmx.de> References: <4D3E9940.3080109@freyther.de> <4D3E9B93.4040202@freyther.de> <4D3EADA3.3090409@libero.it> <4D42C2BA.5020308@libero.it> <4D43061C.9050408@gmx.de> <4D46AC48.3010206@libero.it> <2e464f1e06e30d1199879dff023e8be0@auth.se> <4D47C79D.2060405@libero.it> <4D485B67.1050105@gmx.de> Message-ID: Hi, >>> if (!strcmp("$GPGLL") { ... > how about a proper gpsd-integration? I've some spare time in the end of > this month to try it. I would parse only one least common NMEA-sentence. > As Mad said the > "GPRMC"-sentence should be a good candidate for this. > All other GPS-input-messages could be read via libgpsd from gpsd (which > seems to be able to read even most obscure GPS-binary formats). if anyone wants to continue on that, I had started with something similar already in the past, but not continued: http://vogel.cx/git/0001-GPS-Support-for-GPRMC-sentence.patch You can already use gpsd by creating a fifo, and telling it to osmocom as a device. Then, in another session, run gpspipe -r >fifo. Greetings, Chris From hrmnnmaier at googlemail.com Thu Feb 3 09:52:41 2011 From: hrmnnmaier at googlemail.com (Hermann Maier) Date: Thu, 3 Feb 2011 01:52:41 -0800 (PST) Subject: Fwd: Cell_log > gsmmap In-Reply-To: <4D485B67.1050105@gmx.de> References: <4D3E9B93.4040202@freyther.de> <4D3EADA3.3090409@libero.it> <4D42C2BA.5020308@libero.it> <4D43061C.9050408@gmx.de> <4D46AC48.3010206@libero.it> <2e464f1e06e30d1199879dff023e8be0@auth.se> <4D47C79D.2060405@libero.it> <4D485B67.1050105@gmx.de> Message-ID: <1296726761881-2412091.post@n3.nabble.com> It would also be nice to have a dummy-GPS mode, where you could put the longtitude/latitude as a command line argument for gsmmap. I think most people won't move much debugging with osmocon, so a static position is sufficient. But: there is already an application for GPSd, gpsfake which can fake positions (and can give a static position). If full GPSd-compatibility is made, this would be redundant. http://gpsd.berlios.de/ -- View this message in context: http://baseband-devel.722152.n3.nabble.com/Cell-log-gsmmap-tp2327658p2412091.html Sent from the baseband-devel mailing list archive at Nabble.com. From dario.lombardo at libero.it Mon Feb 7 08:35:57 2011 From: dario.lombardo at libero.it (Dario Lombardo) Date: Mon, 07 Feb 2011 09:35:57 +0100 Subject: Fwd: Cell_log > gsmmap In-Reply-To: <4D485B67.1050105@gmx.de> References: <4D3E9940.3080109@freyther.de> <4D3E9B93.4040202@freyther.de> <4D3EADA3.3090409@libero.it> <4D42C2BA.5020308@libero.it> <4D43061C.9050408@gmx.de> <4D46AC48.3010206@libero.it> <2e464f1e06e30d1199879dff023e8be0@auth.se> <4D47C79D.2060405@libero.it> <4D485B67.1050105@gmx.de> Message-ID: <4D4FAEED.7050102@libero.it> On 02/01/2011 08:13 PM, Martin Hauke wrote: > how about a proper gpsd-integration? I've some spare time in the end of I took a look at the gpsd integration libs and these are my considerations: PROS: - lib seems easy to use and easy to integrate to existing osmocom code - using gpsd avoids to parse lines directly and makes osmocom work with any (gpsd-supported) device CONS: - the use of it makes the presence of gpsd necessary and creates a dependancy from libgpsd when compiling - if we use libgpsd, this is not backward-compatible with existing serial parsing code Finally, my opinion is that using gpsd is better then reading from the port, so if the mantainers of the code agree with me I think I could write the code. Let me know. Dario. From lbernal at gmail.com Mon Feb 7 08:40:54 2011 From: lbernal at gmail.com (n0p [Luis Bernal]) Date: Mon, 7 Feb 2011 09:40:54 +0100 Subject: Fwd: Cell_log > gsmmap In-Reply-To: <4D4FAEED.7050102@libero.it> References: <4D3E9940.3080109@freyther.de> <4D3E9B93.4040202@freyther.de> <4D3EADA3.3090409@libero.it> <4D42C2BA.5020308@libero.it> <4D43061C.9050408@gmx.de> <4D46AC48.3010206@libero.it> <2e464f1e06e30d1199879dff023e8be0@auth.se> <4D47C79D.2060405@libero.it> <4D485B67.1050105@gmx.de> <4D4FAEED.7050102@libero.it> Message-ID: I would leave the possibility of using the current GPS code by using a define at compile time, so when compiling for an embeeded platform (like android, armstrong or equivalent) you do not rely on having the gpsd library and daemon available 2011/2/7 Dario Lombardo > > > On 02/01/2011 08:13 PM, Martin Hauke wrote: > >> how about a proper gpsd-integration? I've some spare time in the end of >> > I took a look at the gpsd integration libs and these are my considerations: > > PROS: > - lib seems easy to use and easy to integrate to existing osmocom code > - using gpsd avoids to parse lines directly and makes osmocom work with any > (gpsd-supported) device > > CONS: > - the use of it makes the presence of gpsd necessary and creates a > dependancy from libgpsd when compiling > - if we use libgpsd, this is not backward-compatible with existing serial > parsing code > > Finally, my opinion is that using gpsd is better then reading from the > port, so if the mantainers of the code agree with me I think I could write > the code. > > Let me know. > Dario. > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From 246tnt at gmail.com Mon Feb 7 08:45:54 2011 From: 246tnt at gmail.com (Sylvain Munaut) Date: Mon, 7 Feb 2011 09:45:54 +0100 Subject: Fwd: Cell_log > gsmmap In-Reply-To: <4D4FAEED.7050102@libero.it> References: <4D3E9940.3080109@freyther.de> <4D3E9B93.4040202@freyther.de> <4D3EADA3.3090409@libero.it> <4D42C2BA.5020308@libero.it> <4D43061C.9050408@gmx.de> <4D46AC48.3010206@libero.it> <2e464f1e06e30d1199879dff023e8be0@auth.se> <4D47C79D.2060405@libero.it> <4D485B67.1050105@gmx.de> <4D4FAEED.7050102@libero.it> Message-ID: > CONS: > - the use of it makes the presence of gpsd necessary and creates a > dependancy from libgpsd when compiling > - if we use libgpsd, this is not backward-compatible with existing serial > parsing code Make _sure_ it's not required. The configure should test for it and disable its usage (and fall back to either the old code, or no GPS support at all). Cheers, Sylvain From list_mailing at libero.it Thu Feb 10 08:58:03 2011 From: list_mailing at libero.it (list_mailing) Date: Thu, 10 Feb 2011 00:58:03 -0800 (PST) Subject: R: Re: FCCH and SCH In-Reply-To: <20110128153553.GC11241@prithivi.gnumonks.org> References: <1296147689456-2363201.post@n3.nabble.com> <20110128153553.GC11241@prithivi.gnumonks.org> Message-ID: <18012664.962481297328270789.JavaMail.defaultUser@defaultHost> Thanks for your answer. I did :-) and found it...but it is a little bit tricky to trace the function call flow.however I think to have resolved.Thanks again. ----Messaggio originale---- Da: ml-node+2379398-1244552887-320183 at n3.nabble.com Data: 30-gen-2011 4.44 A: "list_mailing" Ogg: Re: FCCH and SCH On Thu, Jan 27, 2011 at 09:01:29AM -0800, list_mailing wrote: > > Hello, > I'm newbie to osmocomm and GSM too....I'm studying the protocol and the > source code...but I have many doubts...the first one is the following: > 1. Which are the routines handling FCCH and SCH in osmocom source code? have you ever even bothered to use 'grep' to search for what you are looking for? layer1/prim_fbsb.c:/* Layer 1 - FCCH and SCH burst handling */ -- - Harald Welte <[hidden email]> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) If you reply to this email, your message will be added to the discussion below: http://baseband-devel.722152.n3.nabble.com/FCCH-and-SCH-tp2363201p2379398.html To unsubscribe from FCCH and SCH, click here. -- View this message in context: http://baseband-devel.722152.n3.nabble.com/FCCH-and-SCH-tp2363201p2464699.html Sent from the baseband-devel mailing list archive at Nabble.com. -------------- next part -------------- An HTML attachment was scrubbed... URL: From laforge at gnumonks.org Wed Feb 2 07:52:35 2011 From: laforge at gnumonks.org (Harald Welte) Date: Wed, 2 Feb 2011 08:52:35 +0100 Subject: SIMtrace issues In-Reply-To: <20110131154632.27701.qmail@stuge.se> References: <4D45E0C7.4070201@mail.tsaitgaist.info> <20110131150816.GF3786@prithivi.gnumonks.org> <20110131154632.27701.qmail@stuge.se> Message-ID: <20110202075235.GA3942@prithivi.gnumonks.org> Peter, On Mon, Jan 31, 2011 at 04:46:32PM +0100, Peter Stuge wrote: > Harald Welte wrote: > > > 2. when using a usb hub, having a lot of USB traffic, or poor USB > > > signal quality (I don't know exactly), bulk read timeouts can > > > occur in host program simtrace/at91sam7/host/main.c line 230: > > > rc = usb_bulk_read(udev, SIMTRACE_IN_EP, buf, sizeof(buf), 100000); > > > > ok, interesting. I think its not really something we need to care > > about, if it works reliably using good cables/hubs. > > The issue is probably with the fact that bulk transfers are used for > the data. > > Bulk transfers have no bound latency, they will be delivered "as soon > as possible" but this can very well mean indefinite delay on a loaded > bus. Interrupt transfers and isochronous transfer both have > guaranteed bus time, the latter are lossy (think UDP) so I'd suggest > using interrupt transfer if there's a choice. IIRC interrupt transfers had a size limit, though. The other issue I've had in a number of projects is that libusb only provides a synchronous interface, and it is impossible (without custom additional code) to receive from both a bulk and and interrupt endpoint at the same time. This is not really an issue with SIMTRACE, but it has made me avoid interrupt endpoints at all cost when using libusb. > Programmatically they work very much like bulk so switching over > should be simple. yes, it should be simple. > Oh, and in host programs please don't use the old libusb-0.1 API with > usb_ functions as it has been deprecated and unmaintained for years, > please start using the libusb-1.0 API with libusb_ functions instead; > it fixes bugs, has better performance and is actually being worked > on. :) I'm happy for anyone who has time to update the program. I'm only familiar with the old API and have thus used it again to quickly get something going. the entire simtrace stuff was just a quick hack to debug STK stuff, where the latter being the 'real' work that needed to be done. Regards, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From laforge at gnumonks.org Wed Feb 2 07:53:58 2011 From: laforge at gnumonks.org (Harald Welte) Date: Wed, 2 Feb 2011 08:53:58 +0100 Subject: [PATCH] Two minor patches for the firmware In-Reply-To: <4D46D4A5.2020103@selfish.org> References: <4D46B0F1.6000001@selfish.org> <20110131151208.GH3786@prithivi.gnumonks.org> <4D46D4A5.2020103@selfish.org> Message-ID: <20110202075358.GB3942@prithivi.gnumonks.org> On Mon, Jan 31, 2011 at 04:26:29PM +0100, Holger Freyther wrote: > On 01/31/2011 04:12 PM, Harald Welte wrote: > > Zecke, > > > > > sure, feel free to just commit them to master. no need to ask for such > > trivial compile and typo fixes. > > You will have to grant me access first. sorry, didn't realize it was in the openpcd tree. I've applied your patches meanwhile. The real solution is probably to bring some modularity into the openpcd tree and find a way how the shared code can come from the openpcd repo, while only the simtrace specific code comes from the simtrace repository. However, the OpenPCD firmware and its build system was not designed that way :( Regards, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From squalyl at gmail.com Mon Feb 7 12:02:15 2011 From: squalyl at gmail.com (=?UTF-8?Q?S=C3=A9bastien_Lorquet?=) Date: Mon, 7 Feb 2011 13:02:15 +0100 Subject: thinking about the sim In-Reply-To: <4D474761.3040505@steve-m.de> References: <4D474761.3040505@steve-m.de> Message-ID: hi, thinking more about the SIM. I started to look at the code and I now have some ideas on how to do that. Just a question for the moment: The SIM code is common to all apps so I'm looking at src/host/layer23/src/common/main.c . I see that the handle_options() is the proper place to add a --sim option that would become available to all l23 apps to choose the SIM implementation to use (l1ctl, pcsclite, etc.) But the handle_options() function does not take the struct osmocom_ms *ms pointer as a parameter. And I would need that to setup the proper functions for the SIM. Is this lack of parameters on purpose? Can I do this sort of change without being (understandably) barked at? There is no API breaking involved, handle_options() is static. The result is that for the moment, handle_options() can only access a struct l23_app_info *app. So for my own amusement, I will do the required changes until someone discourages me with a serious reason (in my own branch, in my own repository) I'm just playing with the code now. Sebastien On Tue, Feb 1, 2011 at 12:36 AM, Steve Markgraf wrote: > Hi, > > [just for completeness] > > On 31.01.2011 18:36, Sylvain Munaut wrote: > >> There was some plan to use BTSAP as an internal interface to allow >> plugging of SIM interface .. not sure where it's at. > > Yeah, prom started to work on this some months back, the unfinished > target-side code is in the prom/simaccess branch. > > Regards, > Steve > From 246tnt at gmail.com Mon Feb 7 12:05:15 2011 From: 246tnt at gmail.com (Sylvain Munaut) Date: Mon, 7 Feb 2011 13:05:15 +0100 Subject: thinking about the sim In-Reply-To: References: <4D474761.3040505@steve-m.de> Message-ID: > The SIM code is common to all apps so I'm looking at > src/host/layer23/src/common/main.c . Well, I would change that. And just make the SIM a separate module that the app can choose to unit however it'd like. then in 'mobile', you'd read the config out of VTY. Cheers, Sylvain From squalyl at gmail.com Tue Feb 1 09:33:16 2011 From: squalyl at gmail.com (=?UTF-8?Q?S=C3=A9bastien_Lorquet?=) Date: Tue, 1 Feb 2011 10:33:16 +0100 Subject: http mirror for osmocom-bb.git ? Message-ID: Hi, I know we have a http git mirror for openbsc. Do we have the same for osmocom-bb.git? the git tcp port is censored where I'm connected from. Sorry if I misread the list archive :( Sebastien From holger at freyther.de Tue Feb 1 11:49:42 2011 From: holger at freyther.de (Holger Hans Peter Freyther) Date: Tue, 01 Feb 2011 12:49:42 +0100 Subject: http mirror for osmocom-bb.git ? In-Reply-To: References: Message-ID: <4D47F356.2020002@freyther.de> On 02/01/2011 10:33 AM, S?bastien Lorquet wrote: > Hi, > > I know we have a http git mirror for openbsc. Do we have the same for > osmocom-bb.git? > The easiest way is to go to http://repo.or.cz/ and create a new repository and ask it to mirror the osmocom-bb one. From squalyl at gmail.com Tue Feb 1 13:06:05 2011 From: squalyl at gmail.com (=?UTF-8?Q?S=C3=A9bastien_Lorquet?=) Date: Tue, 1 Feb 2011 14:06:05 +0100 Subject: http mirror for osmocom-bb.git ? In-Reply-To: <4D47F356.2020002@freyther.de> References: <4D47F356.2020002@freyther.de> Message-ID: My question was indeed an attempt to know it that was already done. A mirror-mode osmocom-bb git repository has been set up at http://repo.or.cz/w/osmocom-bb.git According to http://lists.gnumonks.org/pipermail/openbsc/2009-July/000565.html, it will also be synchronized every hour. Sebastien On Tue, Feb 1, 2011 at 12:49 PM, Holger Hans Peter Freyther wrote: > On 02/01/2011 10:33 AM, S?bastien Lorquet wrote: >> Hi, >> >> I know we have a http git mirror for openbsc. Do we have the same for >> osmocom-bb.git? >> > > The easiest way is to go to http://repo.or.cz/ and create a new repository and > ask it to mirror the osmocom-bb one. > > From laforge at gnumonks.org Tue Feb 1 17:36:35 2011 From: laforge at gnumonks.org (Harald Welte) Date: Tue, 01 Feb 2011 18:36:35 +0100 Subject: http mirror for osmocom-bb.git ? In-Reply-To: References: <4D47F356.2020002@freyther.de> Message-ID: feel free to add the external http url to the wiki, indicating firewalls and the git port. -- Sent from a mobile device, excuse my short response From dario.lombardo at libero.it Tue Feb 1 10:48:43 2011 From: dario.lombardo at libero.it (Dario Lombardo) Date: Tue, 01 Feb 2011 11:48:43 +0100 Subject: cell_log and debug Message-ID: <4D47E50B.90102@libero.it> Shame on me when I'm not able to print debug messages from cell_log :) but... cell_log -d DRR,3 doesn't give me any additional output. I would like to see the line LOGP(DRR, LOGL_INFO, "IMMEDIATE ASSIGNMENT:\n"); from cell_log.c. Can anybody help me? From mardnh at gmx.de Tue Feb 1 18:55:51 2011 From: mardnh at gmx.de (Martin Hauke) Date: Tue, 01 Feb 2011 19:55:51 +0100 Subject: cell_log and debug In-Reply-To: <4D47E50B.90102@libero.it> References: <4D47E50B.90102@libero.it> Message-ID: <4D485737.3050802@gmx.de> On 01.02.2011 11:48, Dario Lombardo wrote: > Shame on me when I'm not able to print debug messages from cell_log :) > but... > > cell_log -d DRR,3 > > doesn't give me any additional output. I would like to see the line > > LOGP(DRR, LOGL_INFO, "IMMEDIATE ASSIGNMENT:\n"); > > from cell_log.c. > Can anybody help me? > > Hi Dario, it seems that the -d option is not use by the cell_log app. You can change the log_parse_category_mask in "src/host/layer23/src/misc/app_cell_log.c" and recompile the app. --snip--- log_parse_category_mask(stderr_target, "DL1C:DRSL:DRR:DGPS:DSUM"); // log_parse_category_mask(stderr_target, "DSUM"); log_set_log_level(stderr_target, LOGL_INFO); ---snip--- best regards, Martin From mailsarfraz03 at gmail.com Thu Feb 3 07:11:41 2011 From: mailsarfraz03 at gmail.com (Sarfraz Alam Khan) Date: Thu, 3 Feb 2011 12:41:41 +0530 Subject: in deep trouble Message-ID: hi, i am having errors while bulding osmocom.I tried finding the solution in archives(that of zaki and others) but was unable to figure out. the error is: configure: error: in `/home/gsm/pro/osmocom-bb/src/shared/libosmocore/build-target': configure: error: C compiler cannot create executables See `config.log' for more details make: *** [shared/libosmocore/build-target/Makefile] Error 77 i am also attaching the config.log file plz help me out. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: config.log Type: text/x-log Size: 7676 bytes Desc: not available URL: From wolfram at the-dreams.de Thu Feb 3 08:26:35 2011 From: wolfram at the-dreams.de (Wolfram Sang) Date: Thu, 03 Feb 2011 09:26:35 +0100 Subject: in deep trouble In-Reply-To: References: Message-ID: <4D4A66BB.7070005@the-dreams.de> On 03/02/11 08:11, Sarfraz Alam Khan wrote: > i am also attaching the config.log file > > plz help me out. Did you read the logfile yourself? It states clearly what went wrong... Wolfram From b.alecu at yahoo.com Thu Feb 3 14:22:42 2011 From: b.alecu at yahoo.com (Bogdan Alecu) Date: Thu, 3 Feb 2011 06:22:42 -0800 (PST) Subject: in deep trouble Message-ID: <572326.61601.qm@web46206.mail.sp1.yahoo.com> Make sure of the following: 1. Edit ~/.bashrc and put export PATH=$PATH:/install/bin , where "yourpath" is your full path to where arm-elf-gcc is located 2. restart your computer (sometimes it helps) 3. run the "make" under the same user that has the above path (no sudo make !!!) -------------- next part -------------- An HTML attachment was scrubbed... URL: From wolfram at the-dreams.de Thu Feb 3 14:43:13 2011 From: wolfram at the-dreams.de (Wolfram Sang) Date: Thu, 03 Feb 2011 15:43:13 +0100 Subject: in deep trouble In-Reply-To: <572326.61601.qm@web46206.mail.sp1.yahoo.com> References: <572326.61601.qm@web46206.mail.sp1.yahoo.com> Message-ID: <4D4ABF01.2070505@the-dreams.de> > 2. restart your computer (sometimes it helps) That should never be needed. Regards, Wolfram From peter at stuge.se Thu Feb 3 15:02:05 2011 From: peter at stuge.se (Peter Stuge) Date: Thu, 3 Feb 2011 16:02:05 +0100 Subject: in deep trouble In-Reply-To: <4D4ABF01.2070505@the-dreams.de> References: <572326.61601.qm@web46206.mail.sp1.yahoo.com> <4D4ABF01.2070505@the-dreams.de> Message-ID: <20110203150205.12742.qmail@stuge.se> Wolfram Sang wrote: > > 2. restart your computer (sometimes it helps) > > That should never be needed. Indeed. Just log out, and log back in. In fact, closing and opening your terminal emulator window may be quite enough. //Peter From drasko.draskovic at gmail.com Thu Feb 3 17:38:41 2011 From: drasko.draskovic at gmail.com (Drasko DRASKOVIC) Date: Thu, 3 Feb 2011 18:38:41 +0100 Subject: in deep trouble In-Reply-To: <572326.61601.qm@web46206.mail.sp1.yahoo.com> References: <572326.61601.qm@web46206.mail.sp1.yahoo.com> Message-ID: On Thu, Feb 3, 2011 at 3:22 PM, Bogdan Alecu wrote: > > Make sure of the following: > 1. Edit ~/.bashrc and put > > export PATH=$PATH:/install/bin , where "yourpath" is your full path to where > arm-elf-gcc is located > > 2. restart your computer (sometimes it helps) > 3. run the "make" under the same user that has the above path (no sudo make !!!) Bogdan, evidently there is a good reason why Wolfram's answer is as it is. Evidently there is a?http://bb.osmocom.org/trac/wiki/GettingStarted, where evidently is written : If your GCC binary that produces ARM code is not called?arm-elf-gcc you will need to invoke the following statement and provide the basename of the toolchain with the ending?-. $ cd src $ make -e CROSS_TOOL_PREFIX=arm-OTHER_NAME- Evidently the person who posts questions like this did not read Getting Started page (which is the most sane thing to do in the beginning), nor understood this (or any other, if you want) mailing list netiquette (which is by the way underlined here : http://bb.osmocom.org/trac/wiki/PreliminaryRequirements). I do not get how someone can miss this sentences from the OsmocomBB home page : To get started, checkout the PreliminaryRequirements and then GettingStarted unless he/she really do not care. I strongly opt for Wolfram's kind of response on a questions like this (at least it forces people read what they should have red in the first place). Otherwise September will never end. BR, Drasko From mailsarfraz03 at gmail.com Thu Feb 3 07:54:53 2011 From: mailsarfraz03 at gmail.com (Sarfraz Alam Khan) Date: Thu, 3 Feb 2011 13:24:53 +0530 Subject: in little deep trouble Message-ID: hi, i typed "make osmocon" and "make layer23" and got some output.but i did not get the firmware binaries in *src/target/firmware/board/compal_e88 *and* in **src/host/osmocon/osmocon*, in *src/host/layer23/src/misc* and * layer23/src/mobile*. instead i got files like *.o,*.c etc.. plz help -------------- next part -------------- An HTML attachment was scrubbed... URL: From 246tnt at gmail.com Thu Feb 3 09:25:11 2011 From: 246tnt at gmail.com (Sylvain Munaut) Date: Thu, 3 Feb 2011 10:25:11 +0100 Subject: in little deep trouble In-Reply-To: References: Message-ID: > i typed "make osmocon" and "make layer23" and got some output.but i did not > get the firmware binaries in src/target/firmware/board/compal_e88 and in > src/host/osmocon/osmocon, in src/host/layer23/src/misc and > layer23/src/mobile. > > instead i got files like *.o,*.c etc.. Go read http://bb.osmocom.org/trac/wiki/PreliminaryRequirements and come back when you've completed what's asked on that page. Cheers, Sylvain From leonardo.nve at gmail.com Thu Feb 3 13:14:03 2011 From: leonardo.nve at gmail.com (Leonardo Nve) Date: Thu, 3 Feb 2011 14:14:03 +0100 Subject: AGCH question. Message-ID: <087DC816-6F27-4BB5-B6FB-9FF875651794@gmail.com> Hi everyone. I?m coding a fuzzer with osmocombb API, I expect send you something good in a mounth or two (It depends how much work i have). I have two questions. First, I triying a simple SMS handler, to send and receive. With wireshark I don?t see RACH request, I suppose it is because the DSP inside the phone manage it, am I wrong? About this, I don?t have knowledge about electronics, so I don?t want touch, any filter. So I need to see the RACH of the same phone were osmo is running, not another. The second question is about SI AGCH response, I didn?t find the algorithm to know which SDCCH channel gives the BTS to the MS to send/recv LAPDm bursts. --- Leonardo Nve leonardo.nve at gmail.com --- From 246tnt at gmail.com Thu Feb 3 13:54:14 2011 From: 246tnt at gmail.com (Sylvain Munaut) Date: Thu, 3 Feb 2011 14:54:14 +0100 Subject: AGCH question. In-Reply-To: <087DC816-6F27-4BB5-B6FB-9FF875651794@gmail.com> References: <087DC816-6F27-4BB5-B6FB-9FF875651794@gmail.com> Message-ID: Hi, > First, I triying a simple SMS handler, to send and receive. With wireshark I don?t see RACH request, I suppose it is because the DSP inside the phone manage it, am I wrong? About this, I don?t have knowledge about electronics, so I don?t want touch, any filter. So I need to see the RACH of the same phone were osmo is running, not another. We only send to GSMTAP recomposed L2 packets from Normal Bursts. We don't have debug support for other burst types like dummy/sch/rach, I'm not even sure the gsmtap has a "spec" for it, or that the wireshark dissector has code to process it. Feel free to add support for all of this tough. > The second question is about SI AGCH response, I didn?t find the algorithm to know which SDCCH channel gives the BTS to the MS to send/recv LAPDm bursts. There is none specified ... the BTS is free to allocate whatever it wants ... (well technically it's not the BTS itself, but other component of the core network). Cheers, Sylvain From mad at auth.se Thu Feb 3 14:45:16 2011 From: mad at auth.se (Mad) Date: Thu, 03 Feb 2011 15:45:16 +0100 Subject: AGCH question. In-Reply-To: References: <087DC816-6F27-4BB5-B6FB-9FF875651794@gmail.com> Message-ID: <1e635eb21bc61fb5528e7dcc061cfb0a@auth.se> On Thu, 3 Feb 2011 14:54:14 +0100, Sylvain Munaut wrote: > We only send to GSMTAP recomposed L2 packets from Normal Bursts. > > We don't have debug support for other burst types like > dummy/sch/rach, > I'm not even sure the gsmtap has a "spec" for it, or that the > wireshark dissector has code to process it. > As gsmtap supports the payload type raw GSM Um burst and all possible burst types like GSMTAP_BURST_ACCESS, ..._SCH and so on, it should be possible to send these out to wireshark. But I'm not sure whether the dissector already decodes them as it doesn't do it with normal bursts. >> The second question is about SI AGCH response, I didn?t find the >> algorithm to know which SDCCH channel gives the BTS to the MS to >> send/recv LAPDm bursts. > > There is none specified ... the BTS is free to allocate whatever it > wants ... (well technically it's not the BTS itself, but other > component of the core network). > But there is at least some kind of predictability. The assigned arfcn and time slot is usually the same until a certain load it reached and a second ts or even other arfcn/ts is used. The subchannel is hard to predict as I've never seen a stable pattern, it looks quite random. At least these are my observations with some live networks. Regards, Mad From 246tnt at gmail.com Thu Feb 3 14:56:05 2011 From: 246tnt at gmail.com (Sylvain Munaut) Date: Thu, 3 Feb 2011 15:56:05 +0100 Subject: AGCH question. In-Reply-To: <1e635eb21bc61fb5528e7dcc061cfb0a@auth.se> References: <087DC816-6F27-4BB5-B6FB-9FF875651794@gmail.com> <1e635eb21bc61fb5528e7dcc061cfb0a@auth.se> Message-ID: > But I'm not sure whether the dissector already decodes them as it doesn't > do it with normal bursts. It doesn't dissect anything, just display the raw burst bits. There is however a GSMTAP_CHANNEL_RACH channel type (using GSMTAP_TYPE_UM) that could just carry the 8 encoded bits. Not dissected either but much easier to read than the raw burst bits. Neither is sent by osmocom thus far. > But there is at least some kind of predictability. The assigned arfcn > and time slot is usually the same until a certain load it reached and > a second ts or even other arfcn/ts is used. The subchannel is hard to > predict as I've never seen a stable pattern, it looks quite random. > At least these are my observations with some live networks. Well, it highly depends on the network ... and on channel types you want. I've seen plenty of behaviors, some very predictable, some seemingly random. Point is: You can't really rely on it. Cheers, Sylvain From labadjala6 at gmail.com Thu Feb 3 23:47:50 2011 From: labadjala6 at gmail.com (labad jala) Date: Fri, 4 Feb 2011 00:47:50 +0100 Subject: hmm, sorry, data cable question Message-ID: Hello techies! I am new to the list and I acquired a c139. I'd like to buy a rs232/jack 2,5mm named t191 flash (and not unlock) cable. They look 100% the same (even stickers). Is this important? I understand that I have also to use a rs232/usb adapter. The one I have (U232P9 with link/tx/rx leds) gives +/-9,4 v. So my concern is to not fry the Moto..Any advise welcome. Cheers. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ml at mail.tsaitgaist.info Fri Feb 4 00:59:33 2011 From: ml at mail.tsaitgaist.info (tsaitgaist) Date: Fri, 04 Feb 2011 01:59:33 +0100 Subject: hmm, sorry, data cable question In-Reply-To: References: Message-ID: <4D4B4F75.9050606@mail.tsaitgaist.info> hi, please read the wiki : http://bb.osmocom.org/trac/wiki/CalypsoSerialCable -> only use 3.3V kevin On 04.02.2011 00:47, labad jala wrote: > Hello techies! > I am new to the list and I acquired a c139. I'd like to buy a rs232/jack > 2,5mm named t191 flash (and not unlock) cable. They look 100% the same > (even stickers). Is this important? I understand that I have also to use > a rs232/usb adapter. The one I have (U232P9 with link/tx/rx leds) gives > +/-9,4 v. So my concern is to not fry the Moto..Any advise welcome. > > Cheers. From laforge at gnumonks.org Fri Feb 4 07:50:31 2011 From: laforge at gnumonks.org (Harald Welte) Date: Fri, 4 Feb 2011 08:50:31 +0100 Subject: hmm, sorry, data cable question In-Reply-To: References: Message-ID: <20110204075031.GH6627@prithivi.gnumonks.org> On Fri, Feb 04, 2011 at 12:47:50AM +0100, labad jala wrote: > I am new to the list and I acquired a c139. I'd like to buy a rs232/jack > 2,5mm named t191 flash (and not unlock) cable. They look 100% the same (even > stickers). Is this important? I understand that I have also to use a > rs232/usb adapter. The one I have (U232P9 with link/tx/rx leds) gives +/-9,4 > v. So my concern is to not fry the Moto..Any advise welcome. if you put a usb/rs232 converter and then a rs232/2.5mm cable behind each other, there should be no problem, at least not voltage-wise. The usb/rs232 converter cable with DB-9 will up-convert to +/- 9V, and the T191 cable with DB-9 will then down-convert again to 3.3V In case of any doubt, simply use a multimeter to verify. RS323 is low-active, i.e. in idle state the lines are at their highest voltage. Regards, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From m.crabro at gmail.com Fri Feb 4 10:57:35 2011 From: m.crabro at gmail.com (Maylandia Crabro) Date: Fri, 4 Feb 2011 11:57:35 +0100 Subject: begginer problem Message-ID: Hello, I have the problem connecting to the phone with osmocom tool. For what I have read on this list trying to run helloworld example app should work, and if there are problems connecting they stem from the cable/adapter being low quality. For now I have tried with three different usb-rs232 adapters (2 on winchiphead ch341 chip then I switched to prolific PL-2303 chip) and with 3 different phones (1xC155 and 2xC121) but in any of those configs I am not able to successfully run helloworld - it doesn't receive 'prompt' message as written in wiki - CompalRamLoader. Instead for C121 I always get: ./osmocon -p /dev/ttyUSB0 -m c123 ../../target/firmware/board/compal_e88/hello_world.compalram.bin got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 7e ~ got 5 bytes from modem, data looks like: 82 bf 7d fd 7f ..}.. got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 51 Q got 1 bytes from modem, data looks like: d2 . got 1 bytes from modem, data looks like: 51 Q got 1 bytes from modem, data looks like: 0a . got 1 bytes from modem, data looks like: 3a : got 1 bytes from modem, data looks like: 02 . got 1 bytes from modem, data looks like: a3 . got 1 bytes from modem, data looks like: a3 . got 1 bytes from modem, data looks like: da . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . I tried to stty different port speeds but still only got above sequence. Have you got any suggestion what could be the problem or what direction should I follow to get it working? -------------- next part -------------- An HTML attachment was scrubbed... URL: From mad at auth.se Fri Feb 4 13:40:35 2011 From: mad at auth.se (Mad) Date: Fri, 04 Feb 2011 14:40:35 +0100 Subject: begginer problem In-Reply-To: References: Message-ID: <5411d56b8ae04513087bfdf44f0d368e@auth.se> On Fri, 4 Feb 2011 11:57:35 +0100, Maylandia Crabro wrote: > Hello, > > I have the problem connecting to the phone with osmocom tool. For > what > I have read on this list trying to run helloworld example app should > work, and if there are problems connecting they stem from the > cable/adapter being low quality. > For now I have tried with three different usb-rs232 adapters (2 on > winchiphead ch341 chip then I switched to? prolific PL-2303 chip) and > with 3 different phones (1xC155 and 2xC121) but in any of those > configs I am not able to successfully run helloworld - it doesnt > receive prompt message as written in wiki - CompalRamLoader. Instead > for C121 I always get: > > ./osmocon -p /dev/ttyUSB0 -m c123? Did you try -m c123xor with the prolific? Regards, Mad From wpatan at gmail.com Mon Feb 28 06:12:45 2011 From: wpatan at gmail.com (wpatan) Date: Sun, 27 Feb 2011 22:12:45 -0800 (PST) Subject: begginer problem In-Reply-To: References: Message-ID: <1298873565751-2592856.post@n3.nabble.com> Hi! Where you able to solve this problem? We have exactly the same data received from the phone... - wpatan -- View this message in context: http://baseband-devel.722152.n3.nabble.com/begginer-problem-tp2423389p2592856.html Sent from the baseband-devel mailing list archive at Nabble.com. From sweisman at pobox.com Fri Feb 4 14:00:39 2011 From: sweisman at pobox.com (Scott Weisman) Date: Fri, 4 Feb 2011 16:00:39 +0200 Subject: how to dump phone firmware Message-ID: I recently acquired the Pirelli phone. I was wondering if there was a way to dump the stock firmware in the phone for exploration? Thanks, Scott -------------- next part -------------- An HTML attachment was scrubbed... URL: From steve at steve-m.de Sat Feb 5 01:58:34 2011 From: steve at steve-m.de (Steve Markgraf) Date: Sat, 05 Feb 2011 02:58:34 +0100 Subject: how to dump phone firmware In-Reply-To: References: Message-ID: <4D4CAECA.6090708@steve-m.de> Hi, On 04.02.2011 15:00, Scott Weisman wrote: > I recently acquired the Pirelli phone. I was wondering if there was a > way to dump the stock firmware in the phone for exploration? http://bb.osmocom.org/trac/wiki/loader.bin http://bb.osmocom.org/trac/wiki/osmoload Regards, Steve From logs1973 at gmail.com Sun Feb 6 10:33:40 2011 From: logs1973 at gmail.com (Luca Antani) Date: Sun, 6 Feb 2011 11:33:40 +0100 Subject: Wiki & Osmocom.cfg Message-ID: Hi list! Thanks to the mailing-list's archive i found how to activate the "sim reader" option on osmocom.cfg. Now i'm trying to find on the wiki some more infos about osmocom.cfg configuration, but seems to be missing. Some hints?! Thank you for attention Regards Luca -------------- next part -------------- An HTML attachment was scrubbed... URL: From b.alecu at yahoo.com Sun Feb 6 12:49:40 2011 From: b.alecu at yahoo.com (Bogdan Alecu) Date: Sun, 6 Feb 2011 04:49:40 -0800 (PST) Subject: GsmMap without GPS Message-ID: <567757.7809.qm@web46202.mail.sp1.yahoo.com> As I said in a previous post, I don't see why I need to have a GPS to get an approximation of my location. I then suggested using an open source cell list or Google API. So, I have just finished writing a program that parses your kml file from the gsmmap, send the request to Google and it will get your approx location (just like Google Maps on your mobile) and write the result in another kml file. The program is written in Java. To run it under windows: C:\Program Files\Java\jdk1.6.0_17\bin>java -jar glocation.jar Usage: glocation -i -o C:\Program Files\Java\jdk1.6.0_17\bin>java -jar glocation.jar -i c:\gsm.kml -o final.kml Name : MNC 03 (T-Mobile) Name : LAC 3030 Name : CELL-ID 0031 Name : CELL-ID 0032 Name : CELL-ID 135c Name : CELL-ID 24a7 Name : CELL-ID 4c2a Name : CELL-ID 4c31 Name : CELL-ID 4d10 Name : CELL-ID 51e3 Name : CELL-ID 537b Name : CELL-ID 5567 Name : CELL-ID 5f8a Name : LAC 4010 Name : CELL-ID 4c34 Name : CELL-ID 5b4b --------------------------------------- Sending data to Google... {"location":{"latitude":48.21451,"longitude":16.356414,"accuracy":511.0},"access _token":"2:BaEsaRey871FCt1e:A5vJ-lyJuPrukpMV"} lat=48.21451 long=16.356414 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: glocation.jar Type: application/java-archive Size: 9296 bytes Desc: not available URL: From 246tnt at gmail.com Sun Feb 6 13:57:46 2011 From: 246tnt at gmail.com (Sylvain Munaut) Date: Sun, 6 Feb 2011 14:57:46 +0100 Subject: GsmMap without GPS In-Reply-To: <567757.7809.qm@web46202.mail.sp1.yahoo.com> References: <567757.7809.qm@web46202.mail.sp1.yahoo.com> Message-ID: > As I said in a previous post, I don't see why I need to have a GPS to get an approximation of my location. I then suggested using an open source cell list or Google API. But cell_log is _not_ about finding _your_ location ... It's about trying to find the location of the _bts_ and for that you need a _precise_ location for you. (or else you're just gonna get unusable garbage out ...) cell_log would typically be used to create the database like google has to locate (using another software) you only using the bts you can see. Cheers, Sylvain From b.alecu at yahoo.com Sun Feb 6 14:03:57 2011 From: b.alecu at yahoo.com (Bogdan Alecu) Date: Sun, 6 Feb 2011 06:03:57 -0800 (PST) Subject: GsmMap without GPS In-Reply-To: Message-ID: <553003.69462.qm@web46205.mail.sp1.yahoo.com> Well, then I'm happy I found another way of how gsm_map can be used :) I would be glad if you could get me some results on how accurate it got your location. Regards, Bogdan --- On Sun, 2/6/11, Sylvain Munaut <246tnt at gmail.com> wrote: From: Sylvain Munaut <246tnt at gmail.com> Subject: Re: GsmMap without GPS To: "Bogdan Alecu" Cc: baseband-devel at lists.osmocom.org Date: Sunday, February 6, 2011, 1:57 PM > As I said in a previous post, I don't see why I need to have a GPS to get an approximation of my location. I then suggested using an open source cell list or Google API. But cell_log is _not_ about finding _your_ location ... It's about trying to find the location of the _bts_ and for that you need a _precise_ location for you. (or else you're just gonna get unusable garbage out ...) cell_log would typically be used to create the database like google has to locate (using another software) you only using the bts you can see. Cheers, ? ? Sylvain -------------- next part -------------- An HTML attachment was scrubbed... URL: From laforge at gnumonks.org Sun Feb 6 15:17:55 2011 From: laforge at gnumonks.org (Harald Welte) Date: Sun, 6 Feb 2011 16:17:55 +0100 Subject: GsmMap without GPS In-Reply-To: <567757.7809.qm@web46202.mail.sp1.yahoo.com> References: <567757.7809.qm@web46202.mail.sp1.yahoo.com> Message-ID: <20110206151755.GE17884@prithivi.gnumonks.org> Dear Bogdan, while I value your interest in contributing to our projects, I would like to request you to refrain from distributing software through this list that is * object code only * lacks any information on licensing If you wish to share code on this list, please in source code form and under a Free Software license. Thanks in advance. Regards, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From b.alecu at yahoo.com Mon Feb 7 06:20:14 2011 From: b.alecu at yahoo.com (Bogdan Alecu) Date: Sun, 6 Feb 2011 22:20:14 -0800 (PST) Subject: GsmMap without GPS Message-ID: <152383.1422.qm@web46209.mail.sp1.yahoo.com> Hi all, Harald - I will put the sourcecode later on today. The reason I didn't was because the code it's not so clean and good - but it works. Martynas - my phone remain stationary and in fact I have over 40 cells (from other networks too). I don't find it to be a lot. About the precision, Google returned "accuracy":3875.0" which is surprisingly true. I was about 3-4km? away from the final coordinates. Maybe I'll modify the code to give the position for each cell it finds. Tomas - No proprietary libraries, the code will be here in the evening. It's not so professional done, but considering that it took me somewhere around 30 minutes, I'm good with it. Regards, Bogdan -------------- next part -------------- An HTML attachment was scrubbed... URL: From b.alecu at yahoo.com Mon Feb 7 06:30:50 2011 From: b.alecu at yahoo.com (Bogdan Alecu) Date: Sun, 6 Feb 2011 22:30:50 -0800 (PST) Subject: Emergency number Message-ID: <679311.43050.qm@web46215.mail.sp1.yahoo.com> Hello, What number is it dialed when I place the emergency call? Maybe you could also point me to where I find that number as I want to modify it. Thanks. Regards, Bogdan -------------- next part -------------- An HTML attachment was scrubbed... URL: From holger at freyther.de Mon Feb 7 08:06:10 2011 From: holger at freyther.de (Holger Hans Peter Freyther) Date: Mon, 07 Feb 2011 09:06:10 +0100 Subject: Emergency number In-Reply-To: <679311.43050.qm@web46215.mail.sp1.yahoo.com> References: <679311.43050.qm@web46215.mail.sp1.yahoo.com> Message-ID: <4D4FA7F2.10008@freyther.de> On 02/07/2011 07:30 AM, Bogdan Alecu wrote: > Hello, > > What number is it dialed when I place the emergency call? Maybe you could also > point me to where I find that number as I want to modify it. Thanks. Do you run your own network? How do you plan to test your modifications? From laforge at gnumonks.org Mon Feb 7 09:22:52 2011 From: laforge at gnumonks.org (Harald Welte) Date: Mon, 7 Feb 2011 10:22:52 +0100 Subject: Emergency number In-Reply-To: <679311.43050.qm@web46215.mail.sp1.yahoo.com> References: <679311.43050.qm@web46215.mail.sp1.yahoo.com> Message-ID: <20110207092252.GR17884@prithivi.gnumonks.org> On Sun, Feb 06, 2011 at 10:30:50PM -0800, Bogdan Alecu wrote: > Hello, > > What number is it dialed when I place the emergency call? Maybe you could > also point me to where I find that number as I want to modify it. Thanks. OpenBSC configures the SI to state 'emergency calls not supported'. We don't have support for routing emergency calls internally, but if you use lcr, lcr can route them to any telephone number. DO NOT EXPERIMENT WITH EMERGENCY CALLS UNLESS YOU ARE IN A SHIELDED FARDAY CAGE. The risk of accidentially inhibiting a real emergency call is significant, and we're talking about something that can make the difference between life and death. I'm serious. Regards, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From b.alecu at yahoo.com Mon Feb 7 13:16:11 2011 From: b.alecu at yahoo.com (Bogdan Alecu) Date: Mon, 7 Feb 2011 05:16:11 -0800 (PST) Subject: Emergency number Message-ID: <531785.48219.qm@web46211.mail.sp1.yahoo.com> >Do you run your own network? How do you plan to test your modifications? ? No, I'm not running my own network. I tried to make an emergency call and I got a voice saying to call to different numbers (police, fire dept, etc). That's why I need to know exactly what number is dialed from Osmocom and where I can modify it. I looked on the code but couldn't find (maybe I'm too tired). -------------- next part -------------- An HTML attachment was scrubbed... URL: From steve at steve-m.de Mon Feb 7 13:36:07 2011 From: steve at steve-m.de (Steve Markgraf) Date: Mon, 07 Feb 2011 14:36:07 +0100 Subject: Emergency number In-Reply-To: <531785.48219.qm@web46211.mail.sp1.yahoo.com> References: <531785.48219.qm@web46211.mail.sp1.yahoo.com> Message-ID: <4D4FF547.1070008@steve-m.de> Hi, On 07.02.2011 14:16, Bogdan Alecu wrote: >That's why I need to know exactly what number is dialed from > Osmocom and where I can modify it. I looked on the code but couldn't > find (maybe I'm too tired). There is no such number. The network decides where the call is routed. GSM 04.08 4.5.1.5 MM connection establishment for emergency calls > When a user requests an emergency call establishment the mobile > station will send a CM SERVICE REQUEST message to the network with a > CM service type information element indicating emergency call > establishment. Regards, Steve From b.alecu at yahoo.com Mon Feb 7 14:47:53 2011 From: b.alecu at yahoo.com (Bogdan Alecu) Date: Mon, 7 Feb 2011 06:47:53 -0800 (PST) Subject: Emergency number In-Reply-To: <4D4FF547.1070008@steve-m.de> Message-ID: <66069.97936.qm@web46204.mail.sp1.yahoo.com> >The network decides where the call is routed. So this means that the network routes the call to a wrong number...interesting. --- On Mon, 2/7/11, Steve Markgraf wrote: From: Steve Markgraf Subject: Re: Emergency number To: "Bogdan Alecu" Cc: holger at freyther.de, baseband-devel at lists.osmocom.org Date: Monday, February 7, 2011, 1:36 PM Hi, On 07.02.2011 14:16, Bogdan Alecu wrote: > That's why I need to know exactly what number is dialed from > Osmocom and where I can modify it. I looked on the code but couldn't > find (maybe I'm too tired). There is no such number. The network decides where the call is routed. GSM 04.08 4.5.1.5 MM connection establishment for emergency calls > When a user requests an emergency call establishment the mobile > station will send a CM SERVICE REQUEST message to the network with a > CM service type information element indicating emergency call > establishment. Regards, Steve -------------- next part -------------- An HTML attachment was scrubbed... URL: From rade.girel at web.de Mon Feb 7 16:22:13 2011 From: rade.girel at web.de (Rade Girel) Date: Mon, 7 Feb 2011 17:22:13 +0100 (CET) Subject: Hello, Fonts and a LCDgui Message-ID: <56151691.11396314.1297095733313.JavaMail.fmail@mwmweb013> An HTML attachment was scrubbed... URL: From 246tnt at gmail.com Mon Feb 7 16:48:10 2011 From: 246tnt at gmail.com (Sylvain Munaut) Date: Mon, 7 Feb 2011 17:48:10 +0100 Subject: Hello, Fonts and a LCDgui In-Reply-To: <56151691.11396314.1297095733313.JavaMail.fmail@mwmweb013> References: <56151691.11396314.1297095733313.JavaMail.fmail@mwmweb013> Message-ID: Whatever mail provider / client you use ... please change it. Your mail is just unreadable ... From steve at steve-m.de Mon Feb 7 16:53:59 2011 From: steve at steve-m.de (Steve Markgraf) Date: Mon, 07 Feb 2011 17:53:59 +0100 Subject: Hello, Fonts and a LCDgui In-Reply-To: References: <56151691.11396314.1297095733313.JavaMail.fmail@mwmweb013> Message-ID: <4D5023A7.1070002@steve-m.de> Hi, On 07.02.2011 17:48, Sylvain Munaut wrote: > Whatever mail provider / client you use ... please change it. Your > mail is just unreadable ... Ack, don't post HTML mails on this list. http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110207/c913e96f/attachment.htm is readable though. Regards, Steve From rade.girel at web.de Mon Feb 7 17:45:10 2011 From: rade.girel at web.de (Rade Girel) Date: Mon, 7 Feb 2011 18:45:10 +0100 Subject: Hello, Fonts and a LCDgui (plain text) Message-ID: <20110207184510.1af151c5@tardis> Hello OsmocomBB list members, To shortly introduce myself, i am a sysadmin with much spare time and a Motorola C115 mobile phone. I came to this place after watching a recording of the OsmocomBB talk at the 27c3. That really started my interest on opensource GSM. After reading the wikipages and the mailing list archives i downloaded the sources and had a fully compiling OsmocomBB setup within a few hours. Great work! After slaying some headphonecables and an usbcable i hooked my c115 onto the serialport of my pc and it booted out of the box! Since i am neither a programmer nor an electronic engineer i thought about what i could be interested in doing that contrbiutes to OsmocomBB. (Learning a little C has not hurt too many people i think. so i am on it.) I didnt find it at http://bb.osmocom.org/trac/wiki/AreasOfWork but in the Mailinglistarchives of April-2010 i stumbled upon Christian Vogels post "Subject: PATCH: 5x8 font". After some manual patching i made it to compile the demo app (Printing all available characters in the font from upper left corner down to the bottom. Now that looked allmost like a phone :) It seems like there have not been any follow ups on proportional fonts and the remaining ascii characters as well as the possibility to view different sizes of fonts on the screen. Because there is not much to see on the C115 and there is no navigationsystem of any kind implemented in the compal_e88 firmware I typed together a ericsson clone menu structure with a total of 330 menuitems (transations english to german allmost finished) to have something to display once the proportional 5x8 fonts are finished. now i would continue to write a menu action handler that checks if a navigation key is pressed if a entry in the menu is selected lets look if there is a PhoneMenu "muid" with the siblings "suid" the menu is drawn. if it is a sibling only a switch case list where all actions get caught and processed will handle it. Well, what do you think about that? Should it be built in another way? Am i to early in typing menue structures while the whole "rendering" is not sorted out in any way? Does anyone work on the fonts or a UI? I really am not able judge whether a nested structure monster like this really is the right solution. What it definitly is it is easy to read understand and extend. at least for me ;) if someone wants it i can post the complete menu (~1200 lines) somewhere. Best wishes, Rade Below are some snipplets of the things i allready did: ...sniplets... struct PhoneMenu {  int muid; /* menu uid */  const char* menuLabel_en; /* menu name, english */  const char* menuLabel_de; /* menu name, german */  char siblings; /* amount of siblings within the menu */  struct PhoneMenuSibling pms[]; /* nested structure below */ }; struct PhoneMenuSibling {  int suid; /* sibling uid */  const char* siblingLabel_en; /* label in english */  const char* siblingLabel_de; /* label in german */ }; .... A Menu looks like this: struct PhoneMenu menu = /* the startscreen */ { 0, "Main Menu", /* menu label */ "Hauptmen??", /* menu label in german language */ 6, /* 6 items in the list below */ { {1, "Phonebook", "Telefonbuch"}, {2, "Messages", "Nachrichten"}, {3, "Call information", "Anrufinformation"}, {4, "Active call", "Aktive Verbindung"}, {5, "Settings", "Einstellungen"}, {6, "Extras", "Extras"} } }; struct PhoneMenu menu_phone_book = { 1, "Phone book", "Telefonbuch", 10, { {11, "Call Contact", "Kontak Anrufen"}, {12, "Add Contact", "Kontakt hinzuf??gen"}, {13, "Edit Contact", "Kontakte bearbeiten"}, {14, "Business Cards", "Visitenkarten"}, {15, "Call from SIM", "Adresse aus SIM"}, {16, "Groups", "Gruppen"}, {17, "Calling Cards", "Rufkarten"}, {18, "Options", "Optionen"}, {19, "Memory status", "Speicherverbrauch"} {10, "Special numbers", "Spezialnummern"} } }; ....... struct PhoneMenu menu_phone_book_business_cards_receive = { 143, "Receive", "empfange Visitenkarte", 2, { {1431, "Via Infrared", "via Infrarot"}, {1432, "Via Bluetooth", "via Bluetooth"} } }; From vogelchr at vogel.cx Mon Feb 7 20:16:08 2011 From: vogelchr at vogel.cx (Christian Vogel) Date: Mon, 07 Feb 2011 21:16:08 +0100 Subject: Hello, Fonts and a LCDgui (plain text) In-Reply-To: <20110207184510.1af151c5@tardis> References: <20110207184510.1af151c5@tardis> Message-ID: Hello Rade, > It seems like there have not been any follow ups on proportional fonts > and the remaining ascii characters as well as the possibility to view > different sizes of fonts on the screen. There has been a followup on 2010-10-11, which is http://lists.osmocom.org/pipermail/baseband-devel/2010-October/000665.html This will give you a pixel-addressable framebuffer on the C123 and C155, with a choice of fonts to choose from and can draw lines and boxes. Unfortunately this is not too useful these days, because the stack currently runs separated into layer1 (on the phone) and mobile (on the host pc), so that the indication of the loaded firmware is more or less sufficient. Furthermore, the "nicer" fonts need quite a lot of memory, and most people still run the firmware from RAM, so memory is a scarce resource, for little gain. (in Flash the fonts wouldn't really But I also think that some kind of user-amusement wouldn't be that bad, so please feel free to elaborate on what I've done last year. Greetings, Chris From rade.girel at web.de Tue Feb 8 08:08:40 2011 From: rade.girel at web.de (Rade Girel) Date: Tue, 8 Feb 2011 09:08:40 +0100 Subject: Hello, Fonts and a LCDgui (plain text) In-Reply-To: References: <20110207184510.1af151c5@tardis> Message-ID: <20110208090840.456097ab@tardis> Hello Christian, On Mon, 07 Feb 2011 21:16:08 +0100 "Christian Vogel" wrote: > Hello Rade, > > > It seems like there have not been any follow ups on proportional > > fonts and the remaining ascii characters as well as the possibility > > to view different sizes of fonts on the screen. > > There has been a followup on 2010-10-11, which is > http://lists.osmocom.org/pipermail/baseband-devel/2010-October/000665.html > This looks great! Shame on me for missing this. Ill dedicate my next weekenend to getting into this. Id like to rephrase my previous post regarding followup on the ui to: There has been a lot of progress on the GUI and fonts. > This will give you a pixel-addressable framebuffer on the C123 and > C155, with a choice of fonts to choose from and can draw lines and > boxes. > Just perfect! Cant wait to make those pixels talk. Ill try to get a c155 phone at the fleamarkets to also have a color lcd device for testing. > Unfortunately this is not too useful these days, because the stack > currently > runs separated into layer1 (on the phone) and mobile (on the host > pc), so that the indication of the loaded firmware is more or less > sufficient. > Thats true, but i for myself hope that one day the layer23 code is moved into the phone. At that time i would really like to have a tested, accepted in short usable UI on th osmocomBB compal phones. > Furthermore, the "nicer" fonts need quite a lot of memory, and most > people still > run the firmware from RAM, so memory is a scarce resource, for little > gain. (in Flash the fonts wouldn't really > Well this for shure will not be the case anymore if layer23 is running on the arm7tdmi. Until now i too have not written a single bit to the flash of the phone because of my fear of bricking it but i guess i will get over it soon since as far as i understand, besides removing the bootloader and therefore making the device inaccessable, not much bad can happen. > But I also think that some kind of user-amusement wouldn't be that > bad, so please > feel free to elaborate on what I've done last year. > Hopefully i didnt underestimate the task too much and am able to contribute a bit osmocomBB. Thanks for the great work! Best wishes, Rade > Greetings, > > Chris > From sweisman at pobox.com Tue Feb 8 08:17:59 2011 From: sweisman at pobox.com (Scott Weisman) Date: Tue, 8 Feb 2011 10:17:59 +0200 Subject: Hello, Fonts and a LCDgui (plain text) In-Reply-To: <20110208090840.456097ab@tardis> References: <20110207184510.1af151c5@tardis> <20110208090840.456097ab@tardis> Message-ID: > > Thats true, but i for myself hope that one day the layer23 code is > moved into the phone. At that time i would really like to have a > tested, accepted in short usable UI on th osmocomBB compal phones. > I second this! Now that I know just how vulnerable cell phones are to all sorts of tricks, I very much would like to be toting around a phone with completely open firmware, and as soon as possible! I'm not much help on the GSM stack, but maybe I can give some time over to helping on this. Scott -------------- next part -------------- An HTML attachment was scrubbed... URL: From rade.girel at web.de Tue Feb 8 22:03:48 2011 From: rade.girel at web.de (Rade Girel) Date: Tue, 8 Feb 2011 23:03:48 +0100 Subject: Hello, Fonts and a LCDgui (plain text) In-Reply-To: References: <20110207184510.1af151c5@tardis> <20110208090840.456097ab@tardis> Message-ID: <20110208230348.07dc78e2@tardis> Hello Scott, On Tue, 8 Feb 2011 10:17:59 +0200 Scott Weisman wrote: > > I'm not much help on the GSM stack, but maybe I can give some time > over to helping on this. > Great! Im going to look into the new fb based display driver and all the other GUI goodies done by Christian on this weekend. Best wishes, Rade From azet at azet.org Mon Feb 14 07:20:22 2011 From: azet at azet.org (Aaron Zauner) Date: Mon, 14 Feb 2011 08:20:22 +0100 Subject: Hello, Fonts and a LCDgui (plain text) In-Reply-To: References: <20110207184510.1af151c5@tardis> <20110208090840.456097ab@tardis> <20110208230348.07dc78e2@tardis> Message-ID: sounds quite interesting, but is it even possible to run osmocombb natively without host and target program (thus with connection to a pc/notebook)? azet -- "I have no certainties, at most probabilities." -- Renato Caccioppoli -------------- next part -------------- An HTML attachment was scrubbed... URL: From khorben at defora.org Tue Feb 8 17:59:35 2011 From: khorben at defora.org (Pierre Pronchery) Date: Tue, 08 Feb 2011 18:59:35 +0100 Subject: UI for Osmocom and funding [was: Hello, Fonts and a LCDgui (plain text)] In-Reply-To: <20110207184510.1af151c5@tardis> References: <20110207184510.1af151c5@tardis> Message-ID: <4D518487.7060704@defora.org> Hi Rade, list, On 07/02/2011 18:45, Rade Girel wrote: > > Well, what do you think about that? Should it be built in another way? > Am i to early in typing menue structures while the whole "rendering" > is not sorted out in any way? Does anyone work on the fonts or a UI? well, I am currently working on a UI, but not on the same level. On an Openmoko Freerunner, the application processor can control the baseband one itself, while taking care of the interface. I happen to have written a Gtk+-based GSM daemon and telephony application, which I have recently modified to function independently of the GSM backend in use. You can find this work in the "khorben-phone" branch of the DeforaOS project, found at http://www.defora.org/: You can obtain the source code this way: $ cvs -d:pserver:anonymous at anoncvs.defora.org:/Data/CVS co -r \ khorben-phone DeforaOS/Apps/Desktop/src/Phone (you will also need the "libSystem" library from the same project to compile it: $ cvs -d:pserver:anonymous at anoncvs.defora.org:/Data/CVS co \ DeforaOS/System/src/libSystem So technically now, "all that is left" is to write a plug-in for osmocom in "src/modems". As of the current way the project is implemented, it seems like this plug-in would implement a telnet client and connect to port 4247 locally. I'll welcome suggestions on how to proceed otherwise in a more practical way :) Last but not least, I had to rush to meet the submission deadline when I first heard about this possibility, but I have submitted this project for funding by the CELF forum: http://elinux.org/CELF_Open_Project_Proposal_2011 http://elinux.org/Add_Osmocore_support_to_the_DeforaOS_Phone_GSM_stack Of course I have listed myself in the "Contractor candidates", but I expect development to be (primarily) funded through work in the Osmocom project itself, where I'll welcome anyone, and the most active current developers in particular, to add themselves here (or just ask me to get it done). I hope taking this step sounds good to you all too, and will be good publicity whatever happens (eg whether being funded or not). Cheers, -- khorben From laforge at gnumonks.org Tue Feb 8 08:49:31 2011 From: laforge at gnumonks.org (Harald Welte) Date: Tue, 8 Feb 2011 09:49:31 +0100 Subject: moving layer23 into the phone Message-ID: <20110208084931.GH4847@prithivi.gnumonks.org> On Tue, Feb 08, 2011 at 09:08:40AM +0100, Rade Girel wrote: > Thats true, but i for myself hope that one day the layer23 code is > moved into the phone. At that time i would really like to have a > tested, accepted in short usable UI on th osmocomBB compal phones. I think we can start by moving the stuff step by step into the phone, if anyone wants to work on this, it would be much appreciated. Layer2 (LAPDm) should be relatively simple, but starting from RR/MM/CC and the cell reselection I expect some more difficulties... Regards, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From 246tnt at gmail.com Tue Feb 8 09:38:37 2011 From: 246tnt at gmail.com (246tnt at gmail.com) Date: Tue, 08 Feb 2011 09:38:37 +0000 Subject: moving layer23 into the phone In-Reply-To: <20110208084931.GH4847@prithivi.gnumonks.org> Message-ID: <90e6ba615180e464f6049bc21c7d@google.com> > I think we can start by moving the stuff step by step into the phone, > if anyone wants to work on this, it would be much appreciated. > Layer2 (LAPDm) should be relatively simple, but starting from RR/MM/CC > and the cell reselection I expect some more difficulties... One thing to keep in mind for anyone trying that is that you can't do unaligned access ... and we do plenty of them ... So either you need to fix that in the code, or catch the exception, and emulate the access ... Cheers, Sylvain -------------- next part -------------- An HTML attachment was scrubbed... URL: From sweisman at pobox.com Wed Feb 9 06:08:50 2011 From: sweisman at pobox.com (Scott Weisman) Date: Wed, 9 Feb 2011 08:08:50 +0200 Subject: moving layer23 into the phone In-Reply-To: <90e6ba615180e464f6049bc21c7d@google.com> References: <20110208084931.GH4847@prithivi.gnumonks.org> <90e6ba615180e464f6049bc21c7d@google.com> Message-ID: > > One thing to keep in mind for anyone trying that is that you can't do > unaligned access ... > and we do plenty of them ... > > So either you need to fix that in the code, or catch the exception, and > emulate the access ... > Fixing the unaligned accesses should be cross-platform, right? So this kind of thing can be done at a measured pace even while the code still runs PC-side. Not being a GCC expert, is there some way to find out where these problem accesses are? Scott -------------- next part -------------- An HTML attachment was scrubbed... URL: From rade.girel at web.de Tue Feb 8 22:48:38 2011 From: rade.girel at web.de (Rade Girel) Date: Tue, 8 Feb 2011 23:48:38 +0100 Subject: moving layer23 into the phone In-Reply-To: <20110208084931.GH4847@prithivi.gnumonks.org> References: <20110208084931.GH4847@prithivi.gnumonks.org> Message-ID: <20110208234838.439c4952@tardis> On Tue, 8 Feb 2011 09:49:31 +0100 Harald Welte wrote: > On Tue, Feb 08, 2011 at 09:08:40AM +0100, Rade Girel wrote: > > > Thats true, but i for myself hope that one day the layer23 code is > > moved into the phone. At that time i would really like to have a > > tested, accepted in short usable UI on th osmocomBB compal phones. > > I think we can start by moving the stuff step by step into the phone, > if anyone wants to work on this, it would be much appreciated. > > Layer2 (LAPDm) should be relatively simple, but starting from RR/MM/CC > and the cell reselection I expect some more difficulties... > I honestly cant estimate the amount of work necessary to move "mobile&co" on the arm7tdmi since i never did any porting or the like. But looking at the arm mmu i can guess that there are some fundamental differences between x86 & arm7. Much to read. I think about getting a e-reader for all those datasheets and specifications. Best wishes, Rade From peter at stuge.se Tue Feb 8 23:08:51 2011 From: peter at stuge.se (Peter Stuge) Date: Wed, 9 Feb 2011 00:08:51 +0100 Subject: moving layer23 into the phone In-Reply-To: <20110208234838.439c4952@tardis> References: <20110208084931.GH4847@prithivi.gnumonks.org> <20110208234838.439c4952@tardis> Message-ID: <20110208230851.16318.qmail@stuge.se> Rade Girel wrote: > I honestly cant estimate the amount of work necessary to move > "mobile&co" on the arm7tdmi since i never did any porting or > the like. But looking at the arm mmu i can guess that there > are some fundamental differences between x86 & arm7. Note arm7tdmi is very different from arm-v7. Many arm7tdmi don't have much of a mmu. Calypso might though. //Peter From rade.girel at web.de Wed Feb 9 07:47:56 2011 From: rade.girel at web.de (Rade Girel) Date: Wed, 9 Feb 2011 08:47:56 +0100 Subject: moving layer23 into the phone In-Reply-To: <20110208230851.16318.qmail@stuge.se> References: <20110208084931.GH4847@prithivi.gnumonks.org> <20110208234838.439c4952@tardis> <20110208230851.16318.qmail@stuge.se> Message-ID: <20110209084756.141bded2@tardis> Hello Peter On Wed, 9 Feb 2011 00:08:51 +0100 Peter Stuge wrote: > Rade Girel wrote: > > I honestly cant estimate the amount of work necessary to move > > "mobile&co" on the arm7tdmi since i never did any porting or > > the like. But looking at the arm mmu i can guess that there > > are some fundamental differences between x86 & arm7. > > Note arm7tdmi is very different from arm-v7. Many arm7tdmi don't have > much of a mmu. Calypso might though. > Thank you for pointing this out. As far as i read the datasheet i couldnt find any traces of a mmu, besides the mentioning that it per default has none but you can order one if you like to. (ARM7TDMI, Technical Reference Manual, calypso1,2 doc). Best wishes, Rade From dario.lombardo at libero.it Wed Feb 9 08:31:05 2011 From: dario.lombardo at libero.it (Dario Lombardo) Date: Wed, 09 Feb 2011 09:31:05 +0100 Subject: moving layer23 into the phone In-Reply-To: <20110209084756.141bded2@tardis> References: <20110208084931.GH4847@prithivi.gnumonks.org> <20110208234838.439c4952@tardis> <20110208230851.16318.qmail@stuge.se> <20110209084756.141bded2@tardis> Message-ID: <4D5250C9.6070608@libero.it> Experts will excuse me, but can anyone explain quickly what would be the advantages of moving the layer2 into the phone? Dario From 246tnt at gmail.com Wed Feb 9 08:34:51 2011 From: 246tnt at gmail.com (246tnt at gmail.com) Date: Wed, 09 Feb 2011 08:34:51 +0000 Subject: moving layer23 into the phone In-Reply-To: <4D5250C9.6070608@libero.it> Message-ID: <0015174bdf66ab7cbc049bd5560a@google.com> > Experts will excuse me, but can anyone explain quickly what would be the > advantages of moving the layer2 into the phone? It's just a step towards running it entirely on the phone ... But if your interest in osmocom is mainly as a research tool (like it is for me), then there is no advantage. Cheers, Sylvain -------------- next part -------------- An HTML attachment was scrubbed... URL: From public at grzegusz.it.pl Tue Feb 8 22:51:42 2011 From: public at grzegusz.it.pl (Grzegusz) Date: Tue, 08 Feb 2011 23:51:42 +0100 Subject: Requesting SIM file 0x2fe2 - mobile application problem Message-ID: <20110208235142.w82az6auscgs80kw@webmail.gtsenergis.pl> Hi, I have problem with ./mobile application. When I run this application I have only information that sending APDU (class 0xa0, ins 0xa4). Some more information: 1. At first I started layer1 firmware n motorola C115 ./osmocon -p /dev/ttyS0 -m c123xor /root/osmocom-bb/src/target/firmware/board/compal_e88/layer1.compalram.bin 2. Second I execute ./mobile ./mobile -i 224.0.0.0 3. I pressed power button on my phone. After this I received only this following information: <000e> sim.c:1206 init SIM client <0005> gsm48_cc.c:61 init Call Control <0001> gsm48_rr.c:4944 init Radio Ressource process <0004> gsm48_mm.c:1220 init Mobility Management process <0004> gsm48_mm.c:971 Selecting PLMN SEARCH state, because no SIM. <0002> gsm322.c:3471 init PLMN process <0003> gsm322.c:3472 init Cell Selection process <0003> gsm322.c:3522 Read stored BA list (mcc=260 mnc=02 Poland, Era) <0003> gsm322.c:3522 Read stored BA list (mcc=260 mnc=01 Poland, Plus) <0003> gsm322.c:3522 Read stored BA list (mcc=260 mnc=06 Poland, Play) <0003> gsm322.c:3522 Read stored BA list (mcc=260 mnc=03 Poland, Orange) Mobile '1' initialized, please start phone now! VTY available on port 4247. <0004> subscriber.c:556 Requesting SIM file 0x2fe2 <000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004) <000e> sim.c:697 go MF <000e> sim.c:241 SELECT (file=0x3f00) <000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4) I am waiting, waiting, waiting but unfortunately without progress... Bellow my osmocom.cfg file: ! ! OsmocomBB () configuration saved from vty !! ! line vty no login ! gps device /dev/ttyACM0 gps baudrate default no gps enable ! ms 1 layer2-socket /tmp/osmocom_l2 sap-socket /tmp/osmocom_sap sim reader network-selection-mode auto imei 000000000000000 0 imei-fixed no emergency-imsi no call-waiting no auto-answer no clip no clir tx-power auto no simulated-delay no stick location-updating codec full-speed prefer codec half-speed no abbrev support sms a5/1 a5/2 p-gsm e-gsm r-gsm dcs class-900 4 class-dcs 1 channel-capability sdcch+tchf+tchh full-speech-v1 full-speech-v2 half-speech-v1 min-rxlev -106 dsc-max 90 exit test-sim imsi 001010000000000 ki xor 00 00 00 00 00 00 00 00 00 00 00 00 no barred-access no rplmn hplmn-search foreign-country exit no shutdown exit ! Unfortunately I have no idea how to resolve this problem so please help me... br, Grzegusz From dario.lombardo at libero.it Wed Feb 9 08:28:11 2011 From: dario.lombardo at libero.it (Dario Lombardo) Date: Wed, 09 Feb 2011 09:28:11 +0100 Subject: Requesting SIM file 0x2fe2 - mobile application problem In-Reply-To: <20110208235142.w82az6auscgs80kw@webmail.gtsenergis.pl> References: <20110208235142.w82az6auscgs80kw@webmail.gtsenergis.pl> Message-ID: <4D52501B.7080208@libero.it> On 02/08/2011 11:51 PM, Grzegusz wrote: > > I am waiting, waiting, waiting but unfortunately without progress... > As far as I know, mobile app in master branch doesn't work for the reason you say (can't read file from sim). You have to use sylvain/testing branch that works. Follow this useful quick guide http://blog.rot13.org/2011/01/osmocom-bb_-_free_software_finally_comes_to_gsm.html From dario.lombardo at libero.it Wed Feb 9 14:42:36 2011 From: dario.lombardo at libero.it (Dario Lombardo) Date: Wed, 09 Feb 2011 15:42:36 +0100 Subject: gpsd support Message-ID: <4D52A7DC.9050603@libero.it> Hi all here I am with the first patch to support gpsd. The new code is used only if libgps is found, otherwise old code is used. There is an issue I had to bypass when integrating old code: the osmocom gps_* funcs have identical names to the libgps api :(. So I had to rename the osmocom gps functions to osmo_gps_*. Unfortunately when using logic names for functions sometimes it creates collisions with other code :). Hope this doesn't create new issues. Tell me if you think it can be considered good from coding approach and if it works :). Cheers Dario. -------------- next part -------------- A non-text attachment was scrubbed... Name: gpsd_support.patch Type: text/x-patch Size: 13664 bytes Desc: not available URL: From laforge at gnumonks.org Wed Feb 9 19:12:37 2011 From: laforge at gnumonks.org (Harald Welte) Date: Wed, 9 Feb 2011 20:12:37 +0100 Subject: gpsd support In-Reply-To: <4D52A7DC.9050603@libero.it> References: <4D52A7DC.9050603@libero.it> Message-ID: <20110209191237.GR5246@prithivi.gnumonks.org> Hi Dario, thanks a lot for your patch. I would like to suggest not making it a compile time option but a runtime option. This would get rid of the #ifdefs and be much more elegant. You simply configure in the config file if you want to use gpsd or the raw device... -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From 246tnt at gmail.com Wed Feb 9 19:32:11 2011 From: 246tnt at gmail.com (Sylvain Munaut) Date: Wed, 9 Feb 2011 20:32:11 +0100 Subject: gpsd support In-Reply-To: <20110209191237.GR5246@prithivi.gnumonks.org> References: <4D52A7DC.9050603@libero.it> <20110209191237.GR5246@prithivi.gnumonks.org> Message-ID: > I would like to suggest not making it a compile time option but a > runtime option. ?This would get rid of the #ifdefs and be much more > elegant. ?You simply configure in the config file if you want to use > gpsd or the raw device... Well, it would be annoying to _have_to_ install gpsd just to compile cell_log ... However, having gpsd shouldn't prevent device access if supported, just add new functions. A few comments on the patch itself: - I would split the rename and adding the gpsd in two patches - You erroneously activated TX in your patch ... - You add whitespaces at the end of some lines. (it's always a good idea to reread the patch you post. :) Cheers, Sylvain From peter at stuge.se Wed Feb 9 19:45:49 2011 From: peter at stuge.se (Peter Stuge) Date: Wed, 9 Feb 2011 20:45:49 +0100 Subject: gpsd support In-Reply-To: References: <4D52A7DC.9050603@libero.it> <20110209191237.GR5246@prithivi.gnumonks.org> Message-ID: <20110209194549.1012.qmail@stuge.se> Sylvain Munaut wrote: > > I would like to suggest not making it a compile time option but a > > runtime option. > > Well, it would be annoying to _have_to_ install gpsd just to compile > cell_log ... Default the build time option to enabled. //Peter From dario.lombardo at libero.it Thu Feb 10 08:41:06 2011 From: dario.lombardo at libero.it (Dario Lombardo) Date: Thu, 10 Feb 2011 09:41:06 +0100 Subject: gpsd support In-Reply-To: References: <4D52A7DC.9050603@libero.it> <20110209191237.GR5246@prithivi.gnumonks.org> Message-ID: <4D53A4A2.5060000@libero.it> On 02/09/2011 08:32 PM, Sylvain Munaut wrote: >> I would like to suggest not making it a compile time option but a >> runtime option. This would get rid of the #ifdefs and be much more >> elegant. You simply configure in the config file if you want to use >> gpsd or the raw device... > Well, it would be annoying to _have_to_ install gpsd just to compile > cell_log ... Yes. That's why I used defines. If you all give me a definitive answer I can modify the patch in order to fulfil the needs. My opinion is that if someone doesn't have gps or doesn't want to use gpsd, the libgps dependency would be bad. > However, having gpsd shouldn't prevent device access if supported, > just add new functions. > > > A few comments on the patch itself: > - I would split the rename and adding the gpsd in two patches ok, I can do it. > - You erroneously activated TX in your patch ... > - You add whitespaces at the end of some lines. > > (it's always a good idea to reread the patch you post. :) You are right :), but I sent it for commenting. When sending the definitive I will do all the needed checks. From dario.lombardo at libero.it Thu Feb 10 13:29:59 2011 From: dario.lombardo at libero.it (Dario Lombardo) Date: Thu, 10 Feb 2011 14:29:59 +0100 Subject: gpsd support In-Reply-To: <4D53A4A2.5060000@libero.it> References: <4D52A7DC.9050603@libero.it> <20110209191237.GR5246@prithivi.gnumonks.org> <4D53A4A2.5060000@libero.it> Message-ID: <4D53E857.4010905@libero.it> These are the 2 patches for renaming functions and gpsd support throught conditional compilation. Dario. From dario.lombardo at libero.it Thu Feb 10 08:56:33 2011 From: dario.lombardo at libero.it (Dario Lombardo) Date: Thu, 10 Feb 2011 09:56:33 +0100 Subject: [PATCH] Renamed gps_* functions to osmo_gps_* functions to avoid overlap with libgps functions. Message-ID: --- src/host/layer23/include/osmocom/bb/common/gps.h | 10 +++++----- src/host/layer23/src/common/gps.c | 16 ++++++++-------- src/host/layer23/src/misc/cell_log.c | 6 +++--- src/host/layer23/src/mobile/app_mobile.c | 4 ++-- src/host/layer23/src/mobile/vty_interface.c | 12 ++++++------ 5 files changed, 24 insertions(+), 24 deletions(-) diff --git a/src/host/layer23/include/osmocom/bb/common/gps.h b/src/host/layer23/include/osmocom/bb/common/gps.h index e45cbc5..467cee5 100644 --- a/src/host/layer23/include/osmocom/bb/common/gps.h +++ b/src/host/layer23/include/osmocom/bb/common/gps.h @@ -19,7 +19,7 @@ * */ -struct gps { +struct osmo_gps { /* GPS device */ uint8_t enable; char device[32]; @@ -31,10 +31,10 @@ struct gps { double latitude, longitude; }; -extern struct gps gps; +extern struct osmo_gps gps; -int gps_open(void); -void gps_close(void); -void gps_init(void); +int osmo_gps_open(void); +void osmo_gps_close(void); +void osmo_gps_init(void); diff --git a/src/host/layer23/src/common/gps.c b/src/host/layer23/src/common/gps.c index a092cd0..dfca3b2 100644 --- a/src/host/layer23/src/common/gps.c +++ b/src/host/layer23/src/common/gps.c @@ -33,7 +33,7 @@ #include #include -struct gps gps = { +struct osmo_gps gps = { 0, "/dev/ttyACM0", 0, @@ -46,7 +46,7 @@ struct gps gps = { static struct bsc_fd gps_bfd; static struct termios gps_termios, gps_old_termios; -static int gps_line(char *line) +static int osmo_gps_line(char *line) { time_t gps_now, host_now; struct tm *tm; @@ -141,7 +141,7 @@ static int nmea_checksum(char *line) return (strtoul(line+1, NULL, 16) == checksum); } -int gps_cb(struct bsc_fd *bfd, unsigned int what) +int osmo_gps_cb(struct bsc_fd *bfd, unsigned int what) { char buff[128]; static char line[128]; @@ -165,7 +165,7 @@ int gps_cb(struct bsc_fd *bfd, unsigned int what) if (!nmea_checksum(line)) fprintf(stderr, "NMEA checksum error\n"); else - gps_line(line); + osmo_gps_line(line); continue; } line[lpos++] = buff[i++]; @@ -176,7 +176,7 @@ int gps_cb(struct bsc_fd *bfd, unsigned int what) return 0; } -int gps_open(void) +int osmo_gps_open(void) { int baud = 0; @@ -187,7 +187,7 @@ int gps_open(void) gps_bfd.data = NULL; gps_bfd.when = BSC_FD_READ; - gps_bfd.cb = gps_cb; + gps_bfd.cb = osmo_gps_cb; gps_bfd.fd = open(gps.device, O_RDONLY); if (gps_bfd.fd < 0) return gps_bfd.fd; @@ -227,7 +227,7 @@ int gps_open(void) return 0; } -void gps_close(void) +void osmo_gps_close(void) { if (gps_bfd.fd <= 0) return; @@ -243,7 +243,7 @@ void gps_close(void) gps_bfd.fd = -1; /* -1 or 0 indicates: 'close' */ } -void gps_init(void) +void osmo_gps_init(void) { memset(&gps_bfd, 0, sizeof(gps_bfd)); } diff --git a/src/host/layer23/src/misc/cell_log.c b/src/host/layer23/src/misc/cell_log.c index 93616f2..a0f9769 100644 --- a/src/host/layer23/src/misc/cell_log.c +++ b/src/host/layer23/src/misc/cell_log.c @@ -787,8 +787,8 @@ int scan_init(struct osmocom_ms *_ms) memset(&timer, 0, sizeof(timer)); osmol2_register_handler(ms, &rcv_rsl); gps.enable = 1; - gps_init(); - if (gps_open()) + osmo_gps_init(); + if (osmo_gps_open()) gps.enable = 0; if (!strcmp(logname, "-")) @@ -809,7 +809,7 @@ int scan_exit(void) { LOGP(DSUM, LOGL_INFO, "Scanner exit\n"); if (gps.valid) - gps_close(); + osmo_gps_close(); if (logfp) fclose(logfp); unregister_signal_handler(SS_L1CTL, &signal_cb, NULL); diff --git a/src/host/layer23/src/mobile/app_mobile.c b/src/host/layer23/src/mobile/app_mobile.c index 822ea64..1bedb55 100644 --- a/src/host/layer23/src/mobile/app_mobile.c +++ b/src/host/layer23/src/mobile/app_mobile.c @@ -333,7 +333,7 @@ int l23_app_exit(void) unregister_signal_handler(SS_L1CTL, &mobile_signal_cb, NULL); unregister_signal_handler(SS_GLOBAL, &global_signal_cb, NULL); - gps_close(); + osmo_gps_close(); return 0; } @@ -353,7 +353,7 @@ int l23_app_init(int (*mncc_recv)(struct osmocom_ms *ms, int, void *), mncc_recv_app = mncc_recv; - gps_init(); + osmo_gps_init(); vty_init(&vty_info); ms_vty_init(); diff --git a/src/host/layer23/src/mobile/vty_interface.c b/src/host/layer23/src/mobile/vty_interface.c index 4cc2209..ecefc89 100644 --- a/src/host/layer23/src/mobile/vty_interface.c +++ b/src/host/layer23/src/mobile/vty_interface.c @@ -835,7 +835,7 @@ DEFUN(network_search, network_search_cmd, "network search MS_NAME", DEFUN(cfg_gps_enable, cfg_gps_enable_cmd, "gps enable", "GPS receiver") { - if (gps_open()) { + if (osmo_gps_open()) { gps.enable = 1; vty_out(vty, "Failed to open GPS device!%s", VTY_NEWLINE); return CMD_WARNING; @@ -849,7 +849,7 @@ DEFUN(cfg_no_gps_enable, cfg_no_gps_enable_cmd, "no gps enable", NO_STR "Disable GPS receiver") { if (gps.enable) - gps_close(); + osmo_gps_close(); gps.enable = 0; return CMD_SUCCESS; @@ -862,8 +862,8 @@ DEFUN(cfg_gps_device, cfg_gps_device_cmd, "gps device DEVICE", strncpy(gps.device, argv[0], sizeof(gps.device)); gps.device[sizeof(gps.device) - 1] = '\0'; if (gps.enable) { - gps_close(); - if (gps_open()) { + osmo_gps_close(); + if (osmo_gps_open()) { vty_out(vty, "Failed to open GPS device!%s", VTY_NEWLINE); return CMD_WARNING; @@ -882,8 +882,8 @@ DEFUN(cfg_gps_baud, cfg_gps_baud_cmd, "gps baudrate " else gps.baud = atoi(argv[0]); if (gps.enable) { - gps_close(); - if (gps_open()) { + osmo_gps_close(); + if (osmo_gps_open()) { gps.enable = 0; vty_out(vty, "Failed to open GPS device!%s", VTY_NEWLINE); -- 1.7.4 --------------010406050303050102020702 Content-Type: text/x-patch; name="0002-Added-gpsd-support.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Added-gpsd-support.patch" From dario.lombardo at libero.it Thu Feb 10 13:24:53 2011 From: dario.lombardo at libero.it (Dario Lombardo) Date: Thu, 10 Feb 2011 14:24:53 +0100 Subject: [PATCH] Added gpsd support. Message-ID: --- src/host/layer23/configure.ac | 1 + src/host/layer23/include/osmocom/bb/common/gps.h | 6 ++ src/host/layer23/src/common/gps.c | 106 +++++++++++++++++++++- src/host/layer23/src/misc/app_cell_log.c | 32 ++++++- src/host/layer23/src/mobile/vty_interface.c | 41 +++++++++ 5 files changed, 182 insertions(+), 4 deletions(-) diff --git a/src/host/layer23/configure.ac b/src/host/layer23/configure.ac index 1be98ee..e1c718e 100644 --- a/src/host/layer23/configure.ac +++ b/src/host/layer23/configure.ac @@ -15,6 +15,7 @@ AC_PROG_RANLIB dnl checks for libraries PKG_CHECK_MODULES(LIBOSMOCORE, libosmocore) PKG_CHECK_MODULES(LIBOSMOVTY, libosmovty) +AC_CHECK_LIB(gps, gps_open, CFLAGS+=" -D_USE_GPSD" LDFLAGS+=" -lgps",,) dnl checks for header files AC_HEADER_STDC diff --git a/src/host/layer23/include/osmocom/bb/common/gps.h b/src/host/layer23/include/osmocom/bb/common/gps.h index 467cee5..b7500db 100644 --- a/src/host/layer23/include/osmocom/bb/common/gps.h +++ b/src/host/layer23/include/osmocom/bb/common/gps.h @@ -22,8 +22,14 @@ struct osmo_gps { /* GPS device */ uint8_t enable; + +#ifdef _USE_GPSD + char gpsd_host[32]; + char gpsd_port[6]; +#else char device[32]; uint32_t baud; +#endif /* current data */ uint8_t valid; /* we have a fix */ diff --git a/src/host/layer23/src/common/gps.c b/src/host/layer23/src/common/gps.c index dfca3b2..55dd239 100644 --- a/src/host/layer23/src/common/gps.c +++ b/src/host/layer23/src/common/gps.c @@ -27,6 +27,10 @@ #include #include +#ifdef _USE_GPSD +#include +#endif + #include #include @@ -35,15 +39,111 @@ struct osmo_gps gps = { 0, +#ifdef _USE_GPSD + "localhost", + "2947", +#else "/dev/ttyACM0", 0, - +#endif 0, 0, - 0,0, + 0,0 }; static struct bsc_fd gps_bfd; + +#ifdef _USE_GPSD + +static struct gps_data_t* gdata; + +int osmo_gps_cb(struct bsc_fd *bfd, unsigned int what) +{ + struct tm *tm; + unsigned diff = 0; + + gps.valid = 0; + + /* gps is offline */ + if (gdata->online) + goto gps_not_ready; + + /* gps has no data */ + if (gps_waiting(gdata)) + goto gps_not_ready; + + /* polling returned an error */ + if (gps_poll(gdata)) + goto gps_not_ready; + + /* data are valid */ + if (gdata->set & LATLON_SET) { + gps.valid = 1; + gps.gmt = gdata->fix.time; + tm = localtime(&gps.gmt); + diff = time(NULL) - gps.gmt; + gps.latitude = gdata->fix.latitude; + gps.longitude = gdata->fix.longitude; + + LOGP(DGPS, LOGL_INFO, " time=%02d:%02d:%02d %04d-%02d-%02d, " + "diff-to-host=%d, latitude=%do%.4f, longitude=%do%.4f\n", + tm->tm_hour, tm->tm_min, tm->tm_sec, tm->tm_year + 1900, + tm->tm_mday, tm->tm_mon + 1, diff, + (int)gps.latitude, + (gps.latitude - ((int)gps.latitude)) * 60.0, + (int)gps.longitude, + (gps.longitude - ((int)gps.longitude)) * 60.0); + } + + return 0; + +gps_not_ready: + LOGP(DGPS, LOGL_DEBUG, "gps is offline"); + return -1; +} + +int osmo_gps_open(void) +{ + LOGP(DGPS, LOGL_INFO, "Connecting to gpsd at '%s:%s'\n", gps.gpsd_host, gps.gpsd_port); + + gps_bfd.data = NULL; + gps_bfd.when = BSC_FD_READ; + gps_bfd.cb = osmo_gps_cb; + + gdata = gps_open(gps.gpsd_host, gps.gpsd_port); + if (gdata == NULL) { + LOGP(DGPS, LOGL_ERROR, "Can't connect to gpsd\n"); + return -1; + } + gps_bfd.fd = gdata->gps_fd; + if (gps_bfd.fd < 0) + return gps_bfd.fd; + + if (gps_stream(gdata, WATCH_ENABLE, NULL) == -1) { + LOGP(DGPS, LOGL_ERROR, "Error in gps_stream()\n"); + return -1; + } + + bsc_register_fd(&gps_bfd); + + return 0; +} + +void osmo_gps_close(void) +{ + if (gps_bfd.fd <= 0) + return; + + LOGP(DGPS, LOGL_INFO, "Disconnecting from gpsd\n"); + + bsc_unregister_fd(&gps_bfd); + + gps_close(gdata); + gps_bfd.fd = -1; /* -1 or 0 indicates: 'close' */ +} + +#else + static struct termios gps_termios, gps_old_termios; static int osmo_gps_line(char *line) @@ -243,6 +343,8 @@ void osmo_gps_close(void) gps_bfd.fd = -1; /* -1 or 0 indicates: 'close' */ } +#endif + void osmo_gps_init(void) { memset(&gps_bfd, 0, sizeof(gps_bfd)); diff --git a/src/host/layer23/src/misc/app_cell_log.c b/src/host/layer23/src/misc/app_cell_log.c index 0d61226..7a2c67a 100644 --- a/src/host/layer23/src/misc/app_cell_log.c +++ b/src/host/layer23/src/misc/app_cell_log.c @@ -92,8 +92,13 @@ static int l23_getopt_options(struct option **options) {"logfile", 1, 0, 'l'}, {"rach", 1, 0, 'r'}, {"no-rach", 1, 0, 'n'}, +#ifdef _USE_GPSD + {"gpsd-host", 1, 0, 'g'}, + {"gpsd-port", 1, 0, 'p'} +#else {"gps", 1, 0, 'g'}, {"baud", 1, 0, 'b'} +#endif }; *options = opts; @@ -103,11 +108,16 @@ static int l23_getopt_options(struct option **options) static int l23_cfg_print_help() { printf("\nApplication specific\n"); - printf(" -l --logfile LOGFILE Logfile for the cell log.\n"); + printf(" -l --logfile LOGFILE Logfile for the cell log.\n"); printf(" -r --rach RACH Nr. of RACH bursts to send.\n"); printf(" -n --no-rach Send no rach bursts.\n"); +#ifdef _USE_GPSD + printf(" -g --gpsd-host HOST 127.0.0.1. gpsd host.\n"); + printf(" -p --port PORT 2947. gpsd port\n"); +#else printf(" -g --gps DEVICE /dev/ttyACM0. GPS device.\n"); printf(" -b --baud BAUDRAT The baud rate of the GPS device\n"); +#endif return 0; } @@ -123,6 +133,20 @@ static int l23_cfg_handle(int c, const char *optarg) case 'n': RACH_MAX = 0; break; +#ifdef _USE_GPSD + case 'g': + snprintf(gps.gpsd_host, ARRAY_SIZE(gps.gpsd_host), "%s", optarg); + /* force string terminator */ + gps.gpsd_host[ARRAY_SIZE(gps.gpsd_host) - 1] = '\0'; + LOGP(DGPS, LOGL_INFO, "Using gpsd host %s\n", gps.gpsd_host); + break; + case 'p': + snprintf(gps.gpsd_port, ARRAY_SIZE(gps.gpsd_port), "%s", optarg); + /* force string terminator */ + gps.gpsd_port[ARRAY_SIZE(gps.gpsd_port) - 1] = '\0'; + LOGP(DGPS, LOGL_INFO, "Using gpsd port %s\n", gps.gpsd_port); + break; +#else case 'g': snprintf(gps.device, ARRAY_SIZE(gps.device), "%s", optarg); /* force string terminator */ @@ -133,14 +157,18 @@ static int l23_cfg_handle(int c, const char *optarg) gps.baud = atoi(optarg); LOGP(DGPS, LOGL_INFO, "Setting GPS baudrate to %u\n", gps.baud); break; +#endif } - return 0; } static struct l23_app_info info = { .copyright = "Copyright (C) 2010 Andreas Eversberg\n", +#ifdef _USE_GPSD + .getopt_string = "l:r:ng:p:", +#else .getopt_string = "l:r:ng:b:", +#endif .cfg_supported = l23_cfg_supported, .cfg_getopt_opt = l23_getopt_options, .cfg_handle_opt = l23_cfg_handle, diff --git a/src/host/layer23/src/mobile/vty_interface.c b/src/host/layer23/src/mobile/vty_interface.c index ecefc89..7888f01 100644 --- a/src/host/layer23/src/mobile/vty_interface.c +++ b/src/host/layer23/src/mobile/vty_interface.c @@ -855,6 +855,35 @@ DEFUN(cfg_no_gps_enable, cfg_no_gps_enable_cmd, "no gps enable", return CMD_SUCCESS; } +#ifdef _USE_GPSD +DEFUN(cfg_gps_host, cfg_gps_host_cmd, "gps host HOST:PORT", + "GPS receiver\nSelect gpsd host and port\n" + "IP and port (optional) of the host running gpsd") +{ + char* colon = strstr(argv[0], ":"); + if (colon != NULL) { + memcpy(gps.gpsd_host, argv[0], colon - argv[0] - 1); + gps.gpsd_host[colon - argv[0]] = '\0'; + memcpy(gps.gpsd_port, colon, strlen(colon)); + gps.gpsd_port[strlen(colon)] = '\0'; + } else { + snprintf(gps.gpsd_host, ARRAY_SIZE(gps.gpsd_host), "%s", argv[0]); + gps.gpsd_host[ARRAY_SIZE(gps.gpsd_host) - 1] = '\0'; + snprintf(gps.gpsd_port, ARRAY_SIZE(gps.gpsd_port), "2947"); + gps.gpsd_port[ARRAY_SIZE(gps.gpsd_port) - 1] = '\0'; + } + if (gps.enable) { + osmo_gps_close(); + if (osmo_gps_open()) { + vty_out(vty, "Failed to connect to gpsd host!%s", + VTY_NEWLINE); + return CMD_WARNING; + } + } + + return CMD_SUCCESS; +} +#else DEFUN(cfg_gps_device, cfg_gps_device_cmd, "gps device DEVICE", "GPS receiver\nSelect serial device\n" "Full path of serial device including /dev/") @@ -872,7 +901,9 @@ DEFUN(cfg_gps_device, cfg_gps_device_cmd, "gps device DEVICE", return CMD_SUCCESS; } +#endif +#ifndef _USE_GPSD DEFUN(cfg_gps_baud, cfg_gps_baud_cmd, "gps baudrate " "(default|4800|""9600|19200|38400|57600|115200)", "GPS receiver\nSelect baud rate\nDefault, don't modify\n\n\n\n\n\n") @@ -893,6 +924,7 @@ DEFUN(cfg_gps_baud, cfg_gps_baud_cmd, "gps baudrate " return CMD_SUCCESS; } +#endif /* per MS config */ DEFUN(cfg_ms, cfg_ms_cmd, "ms MS_NAME", @@ -1172,11 +1204,16 @@ static int config_write(struct vty *vty) { struct osmocom_ms *ms; +#ifdef _USE_GPSD + vty_out(vty, "gpsd host %s%s", gps.gpsd_host, VTY_NEWLINE); + vty_out(vty, "gpsd port %s%s", gps.gpsd_port, VTY_NEWLINE); +#else vty_out(vty, "gps device %s%s", gps.device, VTY_NEWLINE); if (gps.baud) vty_out(vty, "gps baudrate %d%s", gps.baud, VTY_NEWLINE); else vty_out(vty, "gps baudrate default%s", VTY_NEWLINE); +#endif vty_out(vty, "%sgps enable%s", (gps.enable) ? "" : "no ", VTY_NEWLINE); vty_out(vty, "!%s", VTY_NEWLINE); @@ -2268,8 +2305,12 @@ int ms_vty_init(void) install_element(ENABLE_NODE, &call_retr_cmd); install_element(ENABLE_NODE, &call_dtmf_cmd); +#ifdef _USE_GPSD + install_element(CONFIG_NODE, &cfg_gps_host_cmd); +#else install_element(CONFIG_NODE, &cfg_gps_device_cmd); install_element(CONFIG_NODE, &cfg_gps_baud_cmd); +#endif install_element(CONFIG_NODE, &cfg_gps_enable_cmd); install_element(CONFIG_NODE, &cfg_no_gps_enable_cmd); -- 1.7.4 --------------010406050303050102020702-- From dario.lombardo at libero.it Tue Feb 15 16:37:48 2011 From: dario.lombardo at libero.it (Dario Lombardo) Date: Tue, 15 Feb 2011 17:37:48 +0100 Subject: gpsd support In-Reply-To: <4D53E857.4010905@libero.it> References: <4D52A7DC.9050603@libero.it> <20110209191237.GR5246@prithivi.gnumonks.org> <4D53A4A2.5060000@libero.it> <4D53E857.4010905@libero.it> Message-ID: Hi guys Any news this side? Are patches ok? Are you planning to merge them? If not, tell me what's wrong so I can change it. Bye Dario. On Thu, Feb 10, 2011 at 2:29 PM, Dario Lombardo wrote: > These are the 2 patches for renaming functions and gpsd support throught > conditional compilation. > Dario. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From laforge at gnumonks.org Tue Feb 15 18:22:00 2011 From: laforge at gnumonks.org (Harald Welte) Date: Tue, 15 Feb 2011 19:22:00 +0100 Subject: gpsd support In-Reply-To: References: <4D52A7DC.9050603@libero.it> <20110209191237.GR5246@prithivi.gnumonks.org> <4D53A4A2.5060000@libero.it> <4D53E857.4010905@libero.it> Message-ID: <20110215182200.GB25856@prithivi.gnumonks.org> On Tue, Feb 15, 2011 at 05:37:48PM +0100, Dario Lombardo wrote: > Hi guys > Any news this side? Are patches ok? Are you planning to merge them? If not, > tell me what's wrong so I can change it. It is customary for the original author to decide what patches to apply or not.. Andreas? -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From laforge at gnumonks.org Wed Feb 16 14:13:50 2011 From: laforge at gnumonks.org (Harald Welte) Date: Wed, 16 Feb 2011 15:13:50 +0100 Subject: gpsd support In-Reply-To: References: <4D52A7DC.9050603@libero.it> <20110209191237.GR5246@prithivi.gnumonks.org> <4D53A4A2.5060000@libero.it> <4D53E857.4010905@libero.it> Message-ID: <20110216141350.GJ25856@prithivi.gnumonks.org> On Tue, Feb 15, 2011 at 05:37:48PM +0100, Dario Lombardo wrote: > Hi guys > Any news this side? Are patches ok? Are you planning to merge them? If not, > tell me what's wrong so I can change it. Andreas said he is OK with applying them, so I will do that. However, if I read your code correctly, it still seems to me that there is a fixed compile time decision if gpsd or built-in gps support is to be used. I think it would be better to keep it a runtime decision, i.e. 1) if gpsd headers/library available during compilation, build support for _both_ gpsd and built-in gps into the program, 2) if they are not available, only include the built-in gps support. The decision which method to use should be a config file option. Please make sure that a config file configured for built-in gps support will work with both versions of the program. A config file requesting the use of gpsd support should make the program abort if it was compiled without gpsd support included. So I will apply your patch now, but I would really appreciate if you could improve it the way I described in an incremental patch at some later point. Thanks, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From Andreas.Eversberg at versatel.de Wed Feb 16 07:07:30 2011 From: Andreas.Eversberg at versatel.de (Andreas.Eversberg) Date: Wed, 16 Feb 2011 08:07:30 +0100 Subject: AW: gpsd support Message-ID: On Tue, Feb 15, 2011 at 05:37:48PM +0100, Dario Lombardo wrote: > Hi guys > Any news this side? Are patches ok? Are you planning to merge them? If not, > tell me what's wrong so I can change it. hi dario, sorry, but i did not follow this list the last days. just apply the patch. it seems ok to me. best regards, andreas From b.alecu at yahoo.com Fri Feb 11 16:12:25 2011 From: b.alecu at yahoo.com (Bogdan Alecu) Date: Fri, 11 Feb 2011 08:12:25 -0800 (PST) Subject: GsmMap glocation sources Message-ID: <12524.24053.qm@web46211.mail.sp1.yahoo.com> Hi all, Sorry for the delay, here are the sources for glocation program I made which uses Google API to get your location. ____________________________________________________________________________________ Need Mail bonding? Go to the Yahoo! Mail Q&A for great tips from Yahoo! Answers users. http://answers.yahoo.com/dir/?link=list&sid=396546091 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: glocation.rar Type: application/x-rar-compressed Size: 21963 bytes Desc: not available URL: From paul at kristianpaul.org Fri Feb 11 17:10:56 2011 From: paul at kristianpaul.org (Cristian Paul =?iso-8859-1?Q?Pe=F1aranda?= Rojas) Date: Fri, 11 Feb 2011 12:10:56 -0500 Subject: GsmMap glocation sources In-Reply-To: <12524.24053.qm@web46211.mail.sp1.yahoo.com> References: <12524.24053.qm@web46211.mail.sp1.yahoo.com> Message-ID: <20110211171056.GG18208@micro.kristianpaul.org> Can you please use a open format to compress the file? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From edrocoyote at yahoo.es Mon Feb 14 01:12:18 2011 From: edrocoyote at yahoo.es (Pedro Collado) Date: Mon, 14 Feb 2011 02:12:18 +0100 Subject: a small petition References: <12524.24053.qm@web46211.mail.sp1.yahoo.com> <20110211171056.GG18208@micro.kristianpaul.org> Message-ID: <18633E5D8C3647C88407A89CA3E1E7DD@CentroSalud> I want that somebody sent me the result of the command dpkg -l >> dpkgrequired.txt and it attaches me dpkgrequired.txt thank you From 775725965 at qq.com Sat Feb 12 04:22:35 2011 From: 775725965 at qq.com (=?gbk?B?wvPM78rYzfs=?=) Date: Sat, 12 Feb 2011 12:22:35 +0800 Subject: motorola c375 to do Message-ID: who know the motorola can to do is it have fireware? -------------- next part -------------- An HTML attachment was scrubbed... URL: From mad at auth.se Sun Feb 13 19:55:45 2011 From: mad at auth.se (Mad) Date: Sun, 13 Feb 2011 20:55:45 +0100 Subject: Pirelli DP-L10 support for =?UTF-8?Q?burst=5Find?= Message-ID: Hi Sylvain, hi Steve, hi list! I did some kind of backport of Pirelli DP-L10 support for the burst_ind branch, patch attached. Remember that after applying you still have to swap the UARTs as mentioned in the wiki to maintain compatibility with the usual configuration in compal phones. The convenient thing with using the Pirelli with burst_ind is that it works out-of-the-box at high serial speed using its standard usb cable (without 2.5 jack to serial to ftdi-usb constructions). But there is one issue I came across with layer23, after a short time of normal operation when returning from DCH to CCH it just gets stuck. The FBSB request returns 255 as result so I guess the fw was not able to resyncronize. When a new request is made by restarting layer23, it works again for some time. Perhaps it has something to do with the used calibration values like SYSTEM_INHERENT_GAIN for the gain control etc. which could be different with the Pirelli layout? BTW, Sylvain, will there be an integration of burst_ind functionality into the master branch at some time, do you have some plan for this? Regards, Mad -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-fw-layer1-Ported-necessary-files-and-changes-from-ma.patch Type: application/octet-stream Size: 14704 bytes Desc: not available URL: From mforce2 at gmail.com Sun Feb 13 21:05:03 2011 From: mforce2 at gmail.com (Marius Cirsta) Date: Sun, 13 Feb 2011 23:05:03 +0200 Subject: mt6516 Message-ID: Hi Does anyone have any info on Mediatek MT6516 ? I'd like to take a look at a datasheet if possible and I also know Android had been ported to it. Any chance of some open source code being released by Mediatek ? Thanks. From andre at ac.nl.eu.org Mon Feb 14 09:19:29 2011 From: andre at ac.nl.eu.org (=?ISO-8859-1?Q?Andr=E9?=) Date: Mon, 14 Feb 2011 10:19:29 +0100 Subject: mt6516 / Android / GPL violation In-Reply-To: References: Message-ID: <4D58F3A1.4040400@ac.nl.eu.org> Hi Marius, To my best knowledge, Mediatek's SDK for MT6516 is based around Android. Therefore, I guess, virtually all phones with this chip will run Android as shipped from factory, and it turn, that means, that good chunk of code is GPL. In theory, this means, that getting source code is enforceable. Anybody familiar enough with http://gpl-violations.org/ to submit this case there? Regards, Andr?. On 13/02/11 22:05, Marius Cirsta wrote: > Hi > > Does anyone have any info on Mediatek MT6516 ? I'd like to take a look > at a datasheet if possible and I also know Android had been ported to > it. Any chance of some open source code being released by Mediatek ? > > Thanks. > From laforge at gnumonks.org Mon Feb 14 14:06:50 2011 From: laforge at gnumonks.org (Harald Welte) Date: Mon, 14 Feb 2011 15:06:50 +0100 Subject: mt6516 / Android / GPL violation In-Reply-To: <4D58F3A1.4040400@ac.nl.eu.org> References: <4D58F3A1.4040400@ac.nl.eu.org> Message-ID: <20110214140650.GK5246@prithivi.gnumonks.org> Hi Andre, On Mon, Feb 14, 2011 at 10:19:29AM +0100, Andr? wrote: > To my best knowledge, Mediatek's SDK for MT6516 is based around > Android. Therefore, I guess, virtually all phones with this chip > will run Android as shipped from factory, and it turn, that means, > that good chunk of code is GPL. In theory, this means, that getting > source code is enforceable. Anybody familiar enough with > http://gpl-violations.org/ to submit this case there? *hrm* I happen to have started both OsmocomBB and gpl-violations.org ;) But please, before running around and pointing fingers at companies: Do you have any evidence that Mediatek is in breach of the GPL? I don't think so. MTK is not selling any phones. They are merely selling the chipset to phone manufacturers. If MTK has gone for '3a)' of GPLv2, then they have provided the complete corresponding source code to the phone manufacturers. _if_ that is the case, they have no obligation to provide any source code to any 3rd party. If you buy a MTK chipsets + Linux kernel based phone, it is the phone manufacturer / importer / distributor who needs to ensure GPL compliance of the full device/product. Please keep further discussion on MTKs GPL compliance off this list. This is a technical list on OsmocomBB development. If you actually found some GPL violation in a product and have evidence, please report it to license-violation at gpl-violations.org Regards, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From azet at azet.org Mon Feb 14 07:05:04 2011 From: azet at azet.org (Aaron Zauner) Date: Mon, 14 Feb 2011 08:05:04 +0100 Subject: suggesting new mailing lists for osmocombb Message-ID: hi, as there has been much spam ongoing and countless discussions of build-problems from users who didnt read the (not quite so good) documentation. i am suggesting a new mailing list for new- comers, buildproblems and so on. i am a bit frustrated over reading countless threads that have nothing to do with actual development. just a suggestion. so long azet -- "I have no certainties, at most probabilities." -- Renato Caccioppoli -------------- next part -------------- An HTML attachment was scrubbed... URL: From azet at azet.org Mon Feb 14 07:06:49 2011 From: azet at azet.org (Aaron Zauner) Date: Mon, 14 Feb 2011 08:06:49 +0100 Subject: suggesting new mailing lists for osmocombb In-Reply-To: References: Message-ID: also: is there a way to stop the chinese spam? that almost seems to be randomly generated.. :) -- "I have no certainties, at most probabilities." -- Renato Caccioppoli -------------- next part -------------- An HTML attachment was scrubbed... URL: From wolfram at the-dreams.de Mon Feb 14 07:32:59 2011 From: wolfram at the-dreams.de (Wolfram Sang) Date: Mon, 14 Feb 2011 08:32:59 +0100 Subject: suggesting new mailing lists for osmocombb In-Reply-To: References: Message-ID: <4D58DAAB.4040000@the-dreams.de> > who didnt read the (not quite so good) documentation. i am suggesting a > new mailing list for new- Cough, ahem, looks like your mail-archive-fu could be improved as well ;) http://lists.osmocom.org/pipermail/baseband-devel/2011-January/001036.html Regards, Wolfram From edrocoyote at yahoo.es Tue Feb 15 00:31:03 2011 From: edrocoyote at yahoo.es (Pedro Collado) Date: Tue, 15 Feb 2011 01:31:03 +0100 Subject: suggesting new mailing lists for osmocombb References: Message-ID: <2F1EEB43BFA34E6A90BD9FC267E5700E@CentroSalud> serious convenient that somebody put in the web the result of ago dpkg -l I try to compile for 3 weeks: IMPOSSIBLE I proved Debian 5.08 6.0 Ubuntu 10.10 Arch etc thank you ----- Original Message ----- From: "Aaron Zauner" To: Sent: Monday, February 14, 2011 8:05 AM Subject: suggesting new mailing lists for osmocombb > hi, > > as there has been much spam ongoing and countless discussions of > build-problems from users > who didnt read the (not quite so good) documentation. i am suggesting a > new > mailing list for new- > comers, buildproblems and so on. i am a bit frustrated over reading > countless threads that have > nothing to do with actual development. > > just a suggestion. > > so long > azet > -- > "I have no certainties, at most probabilities." -- Renato Caccioppoli > From azet at azet.org Tue Feb 15 00:39:30 2011 From: azet at azet.org (Aaron Zauner) Date: Tue, 15 Feb 2011 01:39:30 +0100 Subject: suggesting new mailing lists for osmocombb In-Reply-To: <2F1EEB43BFA34E6A90BD9FC267E5700E@CentroSalud> References: <2F1EEB43BFA34E6A90BD9FC267E5700E@CentroSalud> Message-ID: i hab no problem compiling the source after reading the documentation carefully and the content of the --help parameters of the various programs. also: the distribution should not matter. this is a perfect example, by the way. and, i've got the mail about the newcomer list, is there a posibility to moderate/filter the mailing list. after the 27c3 talk about wideband gsm sniffing, it seems traffic got quite up a bit and people who have no idea of what they are doing are trying to "reverse engineer" the presented python scripts. maybe just a feeling, but i got interested in both the development, and of course a bit because of the sniffing talk, but developing an GSM stack on cheap cell phones is just a great idea, respect to the developers, by the way for the code so far. so long azet On Tue, Feb 15, 2011 at 1:31 AM, Pedro Collado wrote: > > serious convenient that somebody put in the web the result of ago dpkg -l > I try to compile for 3 weeks: IMPOSSIBLE > I proved Debian 5.08 6.0 Ubuntu 10.10 Arch etc > thank you > > ----- Original Message ----- From: "Aaron Zauner" > To: > Sent: Monday, February 14, 2011 8:05 AM > Subject: suggesting new mailing lists for osmocombb > > >> hi, >> >> as there has been much spam ongoing and countless discussions of >> build-problems from users >> who didnt read the (not quite so good) documentation. i am suggesting a new >> mailing list for new- >> comers, buildproblems and so on. i am a bit frustrated over reading >> countless threads that have >> nothing to do with actual development. >> >> just a suggestion. >> >> so long >> azet >> -- >> "I have no certainties, at most probabilities." -- Renato Caccioppoli >> > > -- "I have no certainties, at most probabilities." -- Renato Caccioppoli From steve at steve-m.de Tue Feb 15 00:49:59 2011 From: steve at steve-m.de (Steve Markgraf) Date: Tue, 15 Feb 2011 01:49:59 +0100 Subject: suggesting new mailing lists for osmocombb In-Reply-To: <2F1EEB43BFA34E6A90BD9FC267E5700E@CentroSalud> References: <2F1EEB43BFA34E6A90BD9FC267E5700E@CentroSalud> Message-ID: <4D59CDB7.10408@steve-m.de> Hi, On 15.02.2011 01:31, Pedro Collado wrote: > serious convenient that somebody put in the web the result of ago dpkg -l > I try to compile for 3 weeks: IMPOSSIBLE > I proved Debian 5.08 6.0 Ubuntu 10.10 Arch etc First of all: _don't_ _hijack_ other threads! Did you even bother to read the frontpage of the wiki, and thus PreliminaryRequirements/ GettingStarted? And why should someone post a list of all installed packages, if all packages you need to compile osmocomBB are listed in the wiki? Regards, Steve From squalyl at gmail.com Tue Feb 15 07:10:42 2011 From: squalyl at gmail.com (=?UTF-8?Q?S=C3=A9bastien_Lorquet?=) Date: Tue, 15 Feb 2011 08:10:42 +0100 Subject: suggesting new mailing lists for osmocombb In-Reply-To: <4D59CDB7.10408@steve-m.de> References: <2F1EEB43BFA34E6A90BD9FC267E5700E@CentroSalud> <4D59CDB7.10408@steve-m.de> Message-ID: Well.. Even if, as Harald said, the list's volume is still low and we're free not to answer to newcomers, that's still a great temptation. And on top of that, if "useful" threads get hijacked... every time I see new conversations in this gmail label, I ask myself whether this is a newcomer trying to compile the wrong git branch, or a real information about osmocom-bb. Any feelings about that? Sebastien On Tue, Feb 15, 2011 at 1:49 AM, Steve Markgraf wrote: > Hi, > > > On 15.02.2011 01:31, Pedro Collado wrote: > >> serious convenient that somebody put in the web the result of ago dpkg -l >> I try to compile for 3 weeks: IMPOSSIBLE >> I proved Debian 5.08 6.0 Ubuntu 10.10 Arch etc >> > > First of all: _don't_ _hijack_ other threads! Did you even bother to > read the frontpage of the wiki, and thus PreliminaryRequirements/ > GettingStarted? > > And why should someone post a list of all installed packages, if all > packages you need to compile osmocomBB are listed in the wiki? > > Regards, > Steve > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From 246tnt at gmail.com Tue Feb 15 07:45:50 2011 From: 246tnt at gmail.com (Sylvain Munaut) Date: Tue, 15 Feb 2011 08:45:50 +0100 Subject: suggesting new mailing lists for osmocombb In-Reply-To: References: <2F1EEB43BFA34E6A90BD9FC267E5700E@CentroSalud> <4D59CDB7.10408@steve-m.de> Message-ID: Hi, > Any feelings about that? Well, you're making a few assumptions ... 1) That people that apparently can't read the wiki would still figure out to post only in the right list ... (at worse they would cross post in both ...) 2) Even if they posted there at first, people subscribed to that 'user' list would most often have no clue and they would end up re-posting in the dev list anyway ... Cheers, Sylvain From squalyl at gmail.com Tue Feb 15 08:08:16 2011 From: squalyl at gmail.com (=?UTF-8?Q?S=C3=A9bastien_Lorquet?=) Date: Tue, 15 Feb 2011 09:08:16 +0100 Subject: suggesting new mailing lists for osmocombb In-Reply-To: References: <2F1EEB43BFA34E6A90BD9FC267E5700E@CentroSalud> <4D59CDB7.10408@steve-m.de> Message-ID: Hi, that's two good points, I agree :-( Sebastien On Tue, Feb 15, 2011 at 8:45 AM, Sylvain Munaut <246tnt at gmail.com> wrote: > Hi, > > > Any feelings about that? > > Well, you're making a few assumptions ... > > 1) That people that apparently can't read the wiki would still figure > out to post only in the right list ... (at worse they would cross post > in both ...) > 2) Even if they posted there at first, people subscribed to that > 'user' list would most often have no clue and they would end up > re-posting in the dev list anyway ... > > Cheers, > > Sylvain > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fritsch+osmocom-baseband at in.tum.de Tue Feb 15 08:01:19 2011 From: fritsch+osmocom-baseband at in.tum.de (Hagen Fritsch) Date: Tue, 15 Feb 2011 09:01:19 +0100 Subject: suggesting new mailing lists for osmocombb In-Reply-To: References: <2F1EEB43BFA34E6A90BD9FC267E5700E@CentroSalud> <4D59CDB7.10408@steve-m.de> Message-ID: <4D5A32CF.8060104@in.tum.de> Personally, I think a web-based forum is more appropriate for user-discussions such as build problems or supported hardware. It also facilitates searching, information grouping and adminstration (moving threads) and makes spam-control easier. (+ one doesn't have to subscribe just to be up-to-date). That was just an idea, but then again I don?t really want to start a discussion on mailinglist vs forums. Therefore a summary of arguments is found for example here: http://www.freelock.com/blog/john-locke/2010-03/mailing-list-or-forum-theory Regards, Hagen On 15.02.2011 08:10, S?bastien Lorquet wrote: > Well.. > > Even if, as Harald said, the list's volume is still low and we're free > not to answer to newcomers, that's still a great temptation. > And on top of that, if "useful" threads get hijacked... > > every time I see new conversations in this gmail label, I ask myself > whether this is a newcomer trying to compile the wrong git branch, or a > real information about osmocom-bb. > > Any feelings about that? > > Sebastien From wolfram at the-dreams.de Tue Feb 15 07:38:06 2011 From: wolfram at the-dreams.de (Wolfram Sang) Date: Tue, 15 Feb 2011 08:38:06 +0100 Subject: suggesting new mailing lists for osmocombb In-Reply-To: <2F1EEB43BFA34E6A90BD9FC267E5700E@CentroSalud> References: <2F1EEB43BFA34E6A90BD9FC267E5700E@CentroSalud> Message-ID: <4D5A2D5E.40300@the-dreams.de> > serious convenient that somebody put in the web the result of ago dpkg -l No. > I try to compile for 3 weeks: IMPOSSIBLE Must be something on your side... > I proved Debian 5.08 6.0 Ubuntu 10.10 Arch etc ...because I already wrote you when you asked privately that it works fine with Debian Squeeze (at least). So, go on debugging, the list archive is full of examples what other people had problems with. Wolfram From azet at azet.org Tue Feb 15 22:44:41 2011 From: azet at azet.org (Aaron Zauner) Date: Tue, 15 Feb 2011 23:44:41 +0100 Subject: suggesting new mailing lists for osmocombb In-Reply-To: <4D5AE5D1.7010402@c-base.org> References: <4D5AE5D1.7010402@c-base.org> Message-ID: hi, its probably best if you post this on the public mailing list, not directly to me, as i am not that involved with the project (this reply is CC to the baseband-devel btw. - so that you dont have to remail it, and everything is in context :)). so long! azet On Tue, Feb 15, 2011 at 9:45 PM, Brian Wiborg wrote: > On 02/14/2011 08:05 AM, Aaron Zauner wrote: >> >> hi, >> >> as there has been much spam ongoing and countless discussions of >> build-problems from users >> who didnt read the (not quite so good) documentation. i am suggesting a >> new mailing list for new- >> comers, buildproblems and so on. i am a bit frustrated over reading >> countless threads that have >> nothing to do with actual development. >> >> just a suggestion. >> >> so long >> azet >> -- >> "I have no certainties, at most probabilities." -- Renato Caccioppoli > > hi aaron, > > to make it short: > have you folks considered just moving the noise to irc? I'd be really > interested maintaining and developing such a #channel and help the community > collaboratively grow. who would this best be discussed with? > > best regards > brian > -- "I have no certainties, at most probabilities." -- Renato Caccioppoli From jtd1959 at gmail.com Mon Feb 14 08:44:59 2011 From: jtd1959 at gmail.com (J T Dsouza) Date: Mon, 14 Feb 2011 14:14:59 +0530 Subject: MTK6325 Message-ID: I have three of PK168+ Mediatek 6325. Is it possible to use these? -------------- next part -------------- An HTML attachment was scrubbed... URL: From laforge at gnumonks.org Mon Feb 14 13:29:36 2011 From: laforge at gnumonks.org (Harald Welte) Date: Mon, 14 Feb 2011 14:29:36 +0100 Subject: MTK6325 In-Reply-To: References: Message-ID: <20110214132936.GJ5246@prithivi.gnumonks.org> On Mon, Feb 14, 2011 at 02:14:59PM +0530, J T Dsouza wrote: > I have three of PK168+ Mediatek 6325. Is it possible to use these? you fail to mention to use them _for what_ ? -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From 775725965 at qq.com Wed Feb 16 03:36:36 2011 From: 775725965 at qq.com (=?gbk?B?wvPM78rYzfs=?=) Date: Wed, 16 Feb 2011 11:36:36 +0800 Subject: who can to do motorola c375 use osmocom Message-ID: hi every one who can to do motorola c375 use osmocom please call me thinks -------------- next part -------------- An HTML attachment was scrubbed... URL: From mattjevans at btinternet.com Wed Feb 16 21:19:44 2011 From: mattjevans at btinternet.com (MATTHEW EVANS) Date: Wed, 16 Feb 2011 21:19:44 +0000 (GMT) Subject: Extract Kc from Phone? Message-ID: <612233.71305.qm@web86606.mail.ird.yahoo.com> Hi all, Does anyone have any suggestions with regard to models of phone in which it is easy to view the current Kc? I have a Motorola C115, Nokia 3310/6630, Android Desire, iPhone etc. I can get every everything from the in built field test modes, however I really want to get the current session key so that I can verify/analyse my captured bursts. Thanks, Matt. From seppel18 at hotmail.com Wed Feb 16 22:29:07 2011 From: seppel18 at hotmail.com (Sebastian ---) Date: Wed, 16 Feb 2011 23:29:07 +0100 Subject: Extract Kc from Phone? In-Reply-To: <612233.71305.qm@web86606.mail.ird.yahoo.com> References: <612233.71305.qm@web86606.mail.ird.yahoo.com> Message-ID: I use smartcard reader for this. I recommend http://nobbi.com/download/SIMspyII.zip for PC/SC readers (Towitoko) or http://www.endorasoft.es/download/xsim.zip for smartmouse / phoenix based readers. You should find PC/SC Reader at most Computer-Shops. Remove the Batterie from your phone, and read Kc from Sim-Card (Don't Switch off Phone or Kc will be deleted from SIM) > Date: Wed, 16 Feb 2011 21:19:44 +0000 > From: mattjevans at btinternet.com > Subject: Extract Kc from Phone? > To: baseband-devel at lists.osmocom.org > > Hi all, > > Does anyone have any suggestions with regard to models of phone in which it is > easy to view the current Kc? I have a Motorola C115, Nokia 3310/6630, Android > Desire, iPhone etc. I can get every everything from the in built field test > modes, however I really want to get the current session key so that I can > verify/analyse my captured bursts. > > Thanks, > > Matt. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dario.lombardo at libero.it Wed Feb 16 23:31:03 2011 From: dario.lombardo at libero.it (Dario Lombardo) Date: Thu, 17 Feb 2011 00:31:03 +0100 Subject: Extract Kc from Phone? In-Reply-To: References: <612233.71305.qm@web86606.mail.ird.yahoo.com> Message-ID: On Wed, Feb 16, 2011 at 11:29 PM, Sebastian --- wrote: > > I recommend http://nobbi.com/download/SIMspyII.zip for PC/SC readers > (Towitoko) or http://www.endorasoft.es/download/xsim.zip for smartmouse / > phoenix based readers. > How do they do that? As far as I know Kc shouldn't be extracted (except from very old cards). I would be better to know to have an open source sw that allow us to understand... Another way is to use the "mobile" app from sylvain/testing. It associates with the network and makes calls. If I am not wrong it shows you the Kc, so it would be useful for the original poster. Ciao. Dario. -------------- next part -------------- An HTML attachment was scrubbed... URL: From zero-kelvin at gmx.de Thu Feb 17 00:02:21 2011 From: zero-kelvin at gmx.de (dexter) Date: Thu, 17 Feb 2011 01:02:21 +0100 Subject: Extract Kc from Phone? In-Reply-To: References: <612233.71305.qm@web86606.mail.ird.yahoo.com> Message-ID: <4D5C658D.1070500@gmx.de> Hi folks. > > How do they do that? As far as I know Kc shouldn't be extracted (except from > very old cards). I would be better to know to have an open source sw that > allow us to understand... > The Kc is only the session key. The Ki is the key that you can not extract. I had a similar problem some time ago. I wanted to get the current kc in realtime. My solution was to sniff the kc from the data stream between sim and phone. The kc occurs in 2 ways: 1. When RUN-GSM-ALGORITHM is executed and when the phone stores the Kc back on the simcard. You can download the sourcecode, layouts for my approach at: http://www.runningserver.com/software/chipcardlab.tar The hardest task is to sniff the data because the baudrate of the communication is not a standard baudrate. You can also try to get simtrace (http://bb.osmocom.org/trac/wiki/SIMtrace) running. I did not test it yet but i think it can achieve the same. You could also find a phone where you can read the Kc by sending APDUs through AT-Commands. Some Blackberrys have a netmonitor mode that can display the Kc. regards. Philipp From mad at auth.se Thu Feb 17 14:31:34 2011 From: mad at auth.se (Mad) Date: Thu, 17 Feb 2011 15:31:34 +0100 Subject: Extract Kc from =?UTF-8?Q?Phone=3F?= In-Reply-To: <612233.71305.qm@web86606.mail.ird.yahoo.com> References: <612233.71305.qm@web86606.mail.ird.yahoo.com> Message-ID: <189887e07e06531f794f71d16e4c8d08@auth.se> On Wed, 16 Feb 2011 21:19:44 +0000 (GMT), MATTHEW EVANS wrote: > Does anyone have any suggestions with regard to models of phone in > which it is > easy to view the current Kc? I have a Motorola C115, Nokia 3310/6630, > Android > Desire, iPhone etc. I can get every everything from the in built > field test > modes, however I really want to get the current session key so that I > can > verify/analyse my captured bursts. > If you have a phone with access to the AT command interface via cable or bluetooth you can use the +crsm command to read the kc file from the sim while the phone is operating. Try at+crsm=? to check if your phone supports this command, if it returns an error, it doesn't. at+crsm=176,28448,0,0,8 reads the Kc file from sim and returns a 9 octet hex string of which the first 8 ones are the actual Kc. I'm not sure which of your phones supports this, c115 and 3310 surely don't, iphone maybe depending on version, not sure, just test your phone zoo. BTW, most old Siemens phones support this. Regards, Mad From mad at auth.se Thu Feb 17 14:36:25 2011 From: mad at auth.se (Mad) Date: Thu, 17 Feb 2011 15:36:25 +0100 Subject: Extract Kc from =?UTF-8?Q?Phone=3F?= In-Reply-To: <612233.71305.qm@web86606.mail.ird.yahoo.com> References: <612233.71305.qm@web86606.mail.ird.yahoo.com> Message-ID: <11528fbde8e1b7f5521ca34d871b4daf@auth.se> Forgot to mention a second method to extract kc from a running phone, using Nokias with netmonitor display 52. Again, only some phones have this specific display in their netmon, 3310 I've seen don't. Sim card phonebook entry no 34 has to contain the hex file number (6F20) and after running display 52 phonebook entry 35 should contain the file content. Better check the usual netmon docs for further instructions. Regards, Mad From ste7an at gmail.com Fri Feb 18 21:07:25 2011 From: ste7an at gmail.com (ste7an) Date: Fri, 18 Feb 2011 22:07:25 +0100 Subject: Extract Kc from Phone? In-Reply-To: <11528fbde8e1b7f5521ca34d871b4daf@auth.se> References: <612233.71305.qm@web86606.mail.ird.yahoo.com> <11528fbde8e1b7f5521ca34d871b4daf@auth.se> Message-ID: For those having a Blackberry (I tried it for a Blackberry Torch and it really works:) the following link http://www.zibri.org/2009/08/hidden-things-are-usually-best.html enables Engineering mode. Follow the instructions and instead of the Help screen the engineering screen is displayed. Under Utilities there is a SIM monitor allowing to display SIM_Kc or USIM_Kc depinding on the type of SIM you use. There is an impressive set of tools and different monitor functions ranging from neigbour cells, System Information messages to Wifi and security related settings. Regards, Stefan -------------- next part -------------- An HTML attachment was scrubbed... URL: From mattjevans at btinternet.com Tue Feb 22 12:26:24 2011 From: mattjevans at btinternet.com (MATTHEW EVANS) Date: Tue, 22 Feb 2011 12:26:24 +0000 (GMT) Subject: Extract Kc from Phone? In-Reply-To: <11528fbde8e1b7f5521ca34d871b4daf@auth.se> References: <612233.71305.qm@web86606.mail.ird.yahoo.com> <11528fbde8e1b7f5521ca34d871b4daf@auth.se> Message-ID: <735875.90133.qm@web86608.mail.ird.yahoo.com> Thanks for the advice all. I purchased a cheap sim reader and used xsim to retrieve the Kc. Funny thing is the 3310 doesn't seem to delete the Kc file if I power down normally. Even funnier is the fact that the Kc doesn't change even after power cycle! I guess the Kc change policy must be specific to the operator. It will be interesting to see how often it gets changed! Probably not that often :). Matt. From laforge at gnumonks.org Tue Feb 22 18:35:11 2011 From: laforge at gnumonks.org (Harald Welte) Date: Tue, 22 Feb 2011 13:35:11 -0500 Subject: Extract Kc from Phone? In-Reply-To: <735875.90133.qm@web86608.mail.ird.yahoo.com> References: <612233.71305.qm@web86606.mail.ird.yahoo.com> <11528fbde8e1b7f5521ca34d871b4daf@auth.se> <735875.90133.qm@web86608.mail.ird.yahoo.com> Message-ID: <4D6401DF.2000606@gnumonks.org> On 02/22/2011 07:26 AM, MATTHEW EVANS wrote: > Thanks for the advice all. I purchased a cheap sim reader and used xsim to > retrieve the Kc. Funny thing is the 3310 doesn't seem to delete the Kc file if I > power down normally. Even funnier is the fact that the Kc doesn't change even > after power cycle! Of course, this is how GSM is specified. No suprise here > I guess the Kc change policy must be specific to the > operator. Of course, it is pure operator policy. Regards, Harald From Marcin.Mielczarczyk at tieto.com Thu Feb 17 14:23:09 2011 From: Marcin.Mielczarczyk at tieto.com (Marcin.Mielczarczyk at tieto.com) Date: Thu, 17 Feb 2011 16:23:09 +0200 Subject: Mediatek MT6235 status (Sciphone G2) Message-ID: <8716C48654180249A0941A44457B90751466D32B14@EXMB02.eu.tieto.com> Hi list, After some break finally I managed to describe and commit all changes made to MT6235 Linux port during last one and the half month. Currently I got full Angstrom Linux distribution running with UI. Now you can run everything what I'm writing below without changing Sciphone's original firmware. Just use osmocon to load U-Boot to RAM and SD card which has rootfs (with Linux kernel placed in /boot/uImage). For the beginning I chose OPIE, which runs on both versions of Sciphone - with 32MB and 64MB of RAM. OPIE is based on Qtopia which is lightweight and runs pretty fast on MT6235. When you run OPIE on Sciphone G2 it works as full blown PDA. In OPIE there is no telephony support. I also ran X window server with blackbox and matchbox window managers. It runs fine with this difference that sometimes I got oops messages concerning memory on phones with 32MB of RAM . I'll investigate it in the future. Next step is running SHR and Android (probably only on 64MB versions). Android will be working very slow, but from marketing point of view "Android" is magic word so I guess it'll bring more interest into project. For building Linux distributions I chose OpenEmbedded where you can build a lot of Linux variations. To be able to do this I prepared patch which adds Sciphone G2 target and adds U-Boot and Linux kernel repositories from OsmocomBB project. All details regarding OE are described on wiki: http://bb.osmocom.org/trac/wiki/SciphoneDreamG2 With above patches you're able now to build Linux distribution with any configuration by yourself (Angtrom, SHR, QTE, OPIE, GPE, etc.). Video presenting how Angstrom Linux with OPIE is running on Sciphone G2 is placed under following link: http://www.youtube.com/watch?v=-_guRruQi0I As you can see, there is already new OsmocomBB logo. When it's on white background, it means that U-Boot is running, when it's on black background it menas that Linux is starting up. On above video I used phone (32MB of RAM) which has only U-Boot flashed, everything else is running from SD card. Unfortunatelly OPIE has a lot of elements on boarders of screen (scrolling, application close, etc.) and Sciphone's touchscreen has pretty bad quality and it doesn't work well. You have to be patient while operating it. In the middle of screen it works pretty well. I'm going to improve touchscreen driver, so hopefully it'll work better. I prepared ready to load images from above presentation for people who want to try it out without building: http://downloads.qi-hardware.com/people/marcin/sciphone_g2_mt6235/images/ Below is short status what's going on now in Linux work. Peripherals which are already running under Linux: 1) GPIO 2) clocks 3) timers 4) SD card 5) LCD frame buffer 6) touch screen 7) keypad 8) NAND - not yet finished under Linux as I had no motivation to finish it (it fully runs under U-Boot) 9) RTC - not yet integrated 10) U-Boot has been rebased to newest version and commit history was cleaned - preparations for mainlining of Sciphone G2 port Topics on which we're working now: 1) rebase Sicphone's kernel to newest version 2) USB 3) Audio - needs to know how DSP is working 4) Android porting I hope above software will also run on your devices. BR, Marcin -------------- next part -------------- An HTML attachment was scrubbed... URL: From kevin.granade at gmail.com Thu Feb 17 14:57:40 2011 From: kevin.granade at gmail.com (kevin granade) Date: Thu, 17 Feb 2011 08:57:40 -0600 Subject: Mediatek MT6235 status (Sciphone G2) In-Reply-To: <8716C48654180249A0941A44457B90751466D32B14@EXMB02.eu.tieto.com> References: <8716C48654180249A0941A44457B90751466D32B14@EXMB02.eu.tieto.com> Message-ID: First I'd like to just say it's awesome that you are doing this, I've been following the various efforts to get open software on phones, and your progress is heartening. > > Unfortunatelly OPIE has a lot of elements on boarders of screen (scrolling, > application close, etc.) and Sciphone's touchscreen has pretty bad quality > and it doesn't work well. You have to be patient while operating it. In the > middle of screen it works pretty well. I'm going to improve touchscreen > driver, so hopefully it'll work better. > One thing you might want to look into is translating the touchscreen interface into a touchpad interface. I use this setup when using VNC to connect to a desktop system remotely from my phone, and having the absolute events translated to relative events seems to be the most usable option for interacting with the tiny desktop elements. Thanks, Kevin > > BR, > Marcin > From stefan at datenfreihafen.org Thu Feb 17 15:12:05 2011 From: stefan at datenfreihafen.org (Stefan Schmidt) Date: Thu, 17 Feb 2011 16:12:05 +0100 Subject: Mediatek MT6235 status (Sciphone G2) In-Reply-To: <8716C48654180249A0941A44457B90751466D32B14@EXMB02.eu.tieto.com> References: <8716C48654180249A0941A44457B90751466D32B14@EXMB02.eu.tieto.com> Message-ID: <20110217151205.GV14931@excalibur.local> Hello. On Thu, 2011-02-17 at 16:23, Marcin.Mielczarczyk at tieto.com wrote: > > After some break finally I managed to describe and commit all changes made to MT6235 Linux port during last one and the half month. > Currently I got full Angstrom Linux distribution running with UI. > Now you can run everything what I'm writing below without changing Sciphone's original firmware. Just use osmocon to load U-Boot to RAM and SD card which has rootfs (with Linux kernel placed in /boot/uImage). Nice progress. :) > For building Linux distributions I chose OpenEmbedded where you can build a lot of Linux variations. > To be able to do this I prepared patch which adds Sciphone G2 target and adds U-Boot and Linux kernel repositories from OsmocomBB project. > All details regarding OE are described on wiki: > > http://bb.osmocom.org/trac/wiki/SciphoneDreamG2 Are you planning to change the OE patch soon or would you like to get it into the OE tree? If you are fine with its current state I could review it for you and push it when it is ready. (Well, Holger could do it as well but I think he is busy enough :)) regards Stefan Schmidt From Marcin.Mielczarczyk at tieto.com Fri Feb 18 07:56:06 2011 From: Marcin.Mielczarczyk at tieto.com (Marcin.Mielczarczyk at tieto.com) Date: Fri, 18 Feb 2011 09:56:06 +0200 Subject: Mediatek MT6235 status (Sciphone G2) In-Reply-To: <20110217151205.GV14931@excalibur.local> References: <8716C48654180249A0941A44457B90751466D32B14@EXMB02.eu.tieto.com> <20110217151205.GV14931@excalibur.local> Message-ID: <8716C48654180249A0941A44457B9075146AA79BE0@EXMB02.eu.tieto.com> Hi Stefan, > Are you planning to change the OE patch soon or would you like to get it into the OE tree? If you are fine with its > current state I could review it for you and push it when it is ready. (Well, Holger could do it as well but > I think he is busy enough :)) For initial support of Sciphone G2 this patch is sufficient and I don't plan to change anything at the moment. Probably while building new features there will be need to add new options, but then I can create incremental patches. In this case I'm definitely fine to get this patch in OE tree. You can only change PV variable in "linux-mtk_git.bb" recipe to 2.6.37 wich will be available on OsmocomBB repository today. Thank you for support. BR, Marcin From stefan at datenfreihafen.org Fri Feb 18 08:11:56 2011 From: stefan at datenfreihafen.org (Stefan Schmidt) Date: Fri, 18 Feb 2011 09:11:56 +0100 Subject: Mediatek MT6235 status (Sciphone G2) In-Reply-To: <8716C48654180249A0941A44457B9075146AA79BE0@EXMB02.eu.tieto.com> References: <8716C48654180249A0941A44457B90751466D32B14@EXMB02.eu.tieto.com> <20110217151205.GV14931@excalibur.local> <8716C48654180249A0941A44457B9075146AA79BE0@EXMB02.eu.tieto.com> Message-ID: <20110218081156.GX14931@excalibur.local> Hello. On Fri, 2011-02-18 at 09:56, Marcin.Mielczarczyk at tieto.com wrote: > > > Are you planning to change the OE patch soon or would you like to get it into the OE tree? If you are fine with its > > current state I could review it for you and push it when it is ready. (Well, Holger could do it as well but > > I think he is busy enough :)) > > For initial support of Sciphone G2 this patch is sufficient and I don't plan to change anything at the moment. Good. > Probably while building new features there will be need to add new options, but then I can create incremental patches. Indeed. Thats easy enough. > In this case I'm definitely fine to get this patch in OE tree. You can only change PV variable in "linux-mtk_git.bb" recipe to 2.6.37 wich will be available on OsmocomBB repository today. Great. I will do some review and testing tomorrow to get the patch in. > Thank you for support. No problem. regards Stefan Schmidt From andre at ac.nl.eu.org Thu Feb 17 15:42:58 2011 From: andre at ac.nl.eu.org (=?UTF-8?B?QW5kcsOpIMSMZXJuw6Jr?=) Date: Thu, 17 Feb 2011 16:42:58 +0100 Subject: Mediatek MT6235 status (Sciphone G2) In-Reply-To: <8716C48654180249A0941A44457B90751466D32B14@EXMB02.eu.tieto.com> References: <8716C48654180249A0941A44457B90751466D32B14@EXMB02.eu.tieto.com> Message-ID: <4D5D4202.3070601@ac.nl.eu.org> Coincidently, I had rebased Marcin's kernel to 2.6.37. You can find it under "target/linux/mt623x" of this OpenWRT port: http://ac.nl.eu.org/mt623x/ Regards, Andr? On 17/02/11 15:23, Marcin.Mielczarczyk at tieto.com wrote: > 1) rebase Sicphone's kernel to newest version > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Marcin.Mielczarczyk at tieto.com Fri Feb 18 07:59:09 2011 From: Marcin.Mielczarczyk at tieto.com (Marcin.Mielczarczyk at tieto.com) Date: Fri, 18 Feb 2011 09:59:09 +0200 Subject: Mediatek MT6235 status (Sciphone G2) In-Reply-To: <4D5D4202.3070601@ac.nl.eu.org> References: <8716C48654180249A0941A44457B90751466D32B14@EXMB02.eu.tieto.com> <4D5D4202.3070601@ac.nl.eu.org> Message-ID: <8716C48654180249A0941A44457B9075146AA79BEE@EXMB02.eu.tieto.com> > Coincidently, I had rebased Marcin's kernel to 2.6.37. You can find it under "target/linux/mt623x" of this > OpenWRT port: http://ac.nl.eu.org/mt623x/ Thanks for information. Wolfram Sang have written me already that he also rebased Sciphone G2 kernel to newest one without issues, so I don't expect problems here. Today I'll commit rebased kernel to OsmocomBB repository. BR, Marcin From wolfram at the-dreams.de Fri Feb 18 13:40:14 2011 From: wolfram at the-dreams.de (Wolfram Sang) Date: Fri, 18 Feb 2011 14:40:14 +0100 Subject: Mediatek MT6235 status (Sciphone G2) In-Reply-To: <8716C48654180249A0941A44457B9075146AA79BEE@EXMB02.eu.tieto.com> References: <8716C48654180249A0941A44457B90751466D32B14@EXMB02.eu.tieto.com> <4D5D4202.3070601@ac.nl.eu.org> <8716C48654180249A0941A44457B9075146AA79BEE@EXMB02.eu.tieto.com> Message-ID: <4D5E76BE.4000309@the-dreams.de> Hi Marcin, awesome work again! One comment: > Today I'll commit rebased kernel to OsmocomBB repository. Please don't rebase against linux-next again. Latest tag should be fine (2.6.38-rc5 as of now); Russell has a devel-branch you can check your patches against shortly before sending them (when they are ready). Regards, Wolfram From sweisman at pobox.com Fri Feb 18 09:40:44 2011 From: sweisman at pobox.com (Scott Weisman) Date: Fri, 18 Feb 2011 11:40:44 +0200 Subject: Mediatek MT6235 status (Sciphone G2) In-Reply-To: <8716C48654180249A0941A44457B90751466D32B14@EXMB02.eu.tieto.com> References: <8716C48654180249A0941A44457B90751466D32B14@EXMB02.eu.tieto.com> Message-ID: This is a very nice effort. I have an HTC Kaiser running FroYo, and I would like to add some observations based on this phone, which is more capable in every respect than the G2. The Kaiser is just barely adequate. While the G2 can run Linux, and by extension, Android, it's just too underpowered to make it usable, IMHO. I haven't seen Android on more modern hardware, but I imagine it would be similar in responsiveness to the iPhone 4, which is VERY smooth. It's too bad that there doesn't seem to be any alternative that is responsive enough on lighter, but still capable, hardware like this. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mforce2 at gmail.com Fri Feb 18 10:17:51 2011 From: mforce2 at gmail.com (Marius Cirsta) Date: Fri, 18 Feb 2011 03:17:51 -0700 Subject: Mediatek MT6235 status (Sciphone G2) In-Reply-To: References: <8716C48654180249A0941A44457B90751466D32B14@EXMB02.eu.tieto.com> Message-ID: There isn't any good open source alternative to run on this but one could be crafted I guess. There's Meego which has a Qt interface that could be slimmed down and should run on Qt on the framebuffer and there's also some open source Qt stuff for Symbian that might be portable to Linux. This is just an idea but I'm planning on investigating this as it certainly sounds better to me than Android. I like Qt and C++ better and it's better option for such a low end configuration anyway. P.S. : Sorry for the offlist response , damn gmail - Hide quoted text - On Fri, Feb 18, 2011 at 2:40 AM, Scott Weisman wrote: > This is a very nice effort. I have an HTC Kaiser running FroYo, and I would > like to add some observations based on this phone, which is more capable in > every respect than the G2. The Kaiser is just barely adequate. While the G2 > can run Linux, and by extension, Android, it's just too underpowered to make > it usable, IMHO. I haven't seen Android on more modern hardware, but I > imagine it would be similar in responsiveness to the iPhone 4, which is VERY > smooth. It's too bad that there doesn't seem to be any alternative that is > responsive enough on lighter, but still capable, hardware like this. > > > From laforge at gnumonks.org Fri Feb 18 10:32:03 2011 From: laforge at gnumonks.org (Harald Welte) Date: Fri, 18 Feb 2011 11:32:03 +0100 Subject: Mediatek MT6235 status (Sciphone G2) In-Reply-To: References: <8716C48654180249A0941A44457B90751466D32B14@EXMB02.eu.tieto.com> Message-ID: <20110218103203.GZ1002@prithivi.gnumonks.org> Guys, this is a mailinglist about runnign custom Free Software on the _Baseband_ processor of a telephone. Please keep it on-topic. This is not a discussion forum for the various official or unofficial Linux ports to application processors in phones (like htc-linux, iphone-linux, Openmoko, OpenEZX, etc.) Thanks. -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From sweisman at pobox.com Fri Feb 18 10:50:37 2011 From: sweisman at pobox.com (Scott Weisman) Date: Fri, 18 Feb 2011 12:50:37 +0200 Subject: Mediatek MT6235 status (Sciphone G2) In-Reply-To: <20110218103203.GZ1002@prithivi.gnumonks.org> References: <8716C48654180249A0941A44457B90751466D32B14@EXMB02.eu.tieto.com> <20110218103203.GZ1002@prithivi.gnumonks.org> Message-ID: Maybe it's more blue sky than current focus, but these goals are on the wiki page (http://bb.osmocom.org/trac/wiki/MasterPlan) as long term goals: - Port some minimalistic RTOS that already supports ARM7TDMI well to the Calypso - Attempt to move L2 from PC into the phone - Attempt to move l3 from PC into the phone Maybe the page needs to be updated if the above are no longer goals of the project. Scott On Fri, Feb 18, 2011 at 12:32 PM, Harald Welte wrote: > Guys, > > this is a mailinglist about runnign custom Free Software on the _Baseband_ > processor of a telephone. > > Please keep it on-topic. This is not a discussion forum for the various > official or unofficial Linux ports to application processors in phones > (like htc-linux, iphone-linux, Openmoko, OpenEZX, etc.) > > Thanks. > > -- > - Harald Welte > http://laforge.gnumonks.org/ > > ============================================================================ > "Privacy in residential applications is a desirable marketing option." > (ETSI EN 300 175-7 Ch. A6) > -------------- next part -------------- An HTML attachment was scrubbed... URL: From laforge at gnumonks.org Fri Feb 18 12:19:07 2011 From: laforge at gnumonks.org (Harald Welte) Date: Fri, 18 Feb 2011 13:19:07 +0100 Subject: Mediatek MT6235 status (Sciphone G2) In-Reply-To: References: <8716C48654180249A0941A44457B90751466D32B14@EXMB02.eu.tieto.com> <20110218103203.GZ1002@prithivi.gnumonks.org> Message-ID: <20110218121907.GE1002@prithivi.gnumonks.org> On Fri, Feb 18, 2011 at 12:50:37PM +0200, Scott Weisman wrote: > Maybe it's more blue sky than current focus, but these goals are on the wiki > page (http://bb.osmocom.org/trac/wiki/MasterPlan) as long term goals: > > - Port some minimalistic RTOS that already supports ARM7TDMI well to the > Calypso > - Attempt to move L2 from PC into the phone > - Attempt to move l3 from PC into the phone > > Maybe the page needs to be updated if the above are no longer goals of the > project. I don't understand your comment. The ARM7TDMI that we are talking about is the _baseband_ processor. The long-term goals still exist as they stand in the wiki. What has been discussed previously on this thread (and triggered my response) was running Linux on HTC phones and the like. That was about the _applicaiton_ processor. Marcin's work is different, as we are talking about a port of Linux to the (in this case ARM926EJS) _baseband_ processor of a phone. Regards, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From sweisman at pobox.com Fri Feb 18 13:42:59 2011 From: sweisman at pobox.com (Scott Weisman) Date: Fri, 18 Feb 2011 15:42:59 +0200 Subject: Mediatek MT6235 status (Sciphone G2) In-Reply-To: <20110218121907.GE1002@prithivi.gnumonks.org> References: <8716C48654180249A0941A44457B90751466D32B14@EXMB02.eu.tieto.com> <20110218103203.GZ1002@prithivi.gnumonks.org> <20110218121907.GE1002@prithivi.gnumonks.org> Message-ID: I have to apologize, because I think I am missing something here. Does the G2, or any of the phones that OsmocomBB currently supports, have more than one ARM CPU? I vaguely recall reading an email on this list that one of the ways the G2 was able to keep costs down was not have separate baseband and app CPUs. Plus, all the wiki pages I've read, seem to indicate not. I don't understand your comment. The ARM7TDMI that we are talking about is > the _baseband_ processor. The long-term goals still exist as they stand in > the wiki. > > What has been discussed previously on this thread (and triggered my > response) > was running Linux on HTC phones and the like. That was about the > _applicaiton_ > processor. > > Marcin's work is different, as we are talking about a port of Linux to the > (in > this case ARM926EJS) _baseband_ processor of a phone. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mforce2 at gmail.com Fri Feb 18 14:27:59 2011 From: mforce2 at gmail.com (Marius Cirsta) Date: Fri, 18 Feb 2011 07:27:59 -0700 Subject: Mediatek MT6235 status (Sciphone G2) In-Reply-To: References: <8716C48654180249A0941A44457B90751466D32B14@EXMB02.eu.tieto.com> <20110218103203.GZ1002@prithivi.gnumonks.org> <20110218121907.GE1002@prithivi.gnumonks.org> Message-ID: From what I understand MT6235 has just one ARM926EJS processor and a DSP. This probably means that the it runs both the application and the GSM stack on a single CPU , right ? I read in an article about Symbian that it's able to do this because it's a realtime OS but to my knowledge Linux is not ( hence the GSM stack runs on a second processor in Android phones ). Now I also know there's a realtime Linux kernel but the question is would it be possible to run both the application and GSM stack together on the MT6235 under Linux. Please excuse my question if they're newbish. Thanks. On Fri, Feb 18, 2011 at 6:42 AM, Scott Weisman wrote: > I have to apologize, because I think I am missing something here. Does the > G2, or any of the phones that OsmocomBB currently supports, have more than > one ARM CPU? I vaguely recall reading an email on this list that one of the > ways the G2 was able to keep costs down was not have separate baseband and > app CPUs. Plus, all the wiki pages I've read, seem to indicate not. >> >> I don't understand your comment. ?The ARM7TDMI that we are talking about >> is >> the _baseband_ processor. ?The long-term goals still exist as they stand >> in >> the wiki. >> >> What has been discussed previously on this thread (and triggered my >> response) >> was running Linux on HTC phones and the like. ?That was about the >> _applicaiton_ >> processor. >> >> Marcin's work is different, as we are talking about a port of Linux to the >> (in >> this case ARM926EJS) _baseband_ processor of a phone. >> > From drasko.draskovic at gmail.com Fri Feb 18 14:52:53 2011 From: drasko.draskovic at gmail.com (Drasko DRASKOVIC) Date: Fri, 18 Feb 2011 15:52:53 +0100 Subject: Mediatek MT6235 status (Sciphone G2) In-Reply-To: References: <8716C48654180249A0941A44457B90751466D32B14@EXMB02.eu.tieto.com> <20110218103203.GZ1002@prithivi.gnumonks.org> <20110218121907.GE1002@prithivi.gnumonks.org> Message-ID: On Fri, Feb 18, 2011 at 3:27 PM, Marius Cirsta wrote: > ?From what I understand MT6235 has just one ARM926EJS processor and a > DSP. ?This probably means that the it runs both the application and > the GSM stack on a single CPU , right ? > ?I read in an article about Symbian that it's able to do this because > it's a realtime OS but to my knowledge Linux is not ( hence the GSM > stack runs on a second processor in Android phones ). Now I also know > there's a realtime Linux kernel but the question is would it be > possible to run both the application and GSM stack together on the > MT6235 under Linux. > ?Please excuse my question if they're newbish. Under Linux probably not, under RT Linux maybe. Depends on the amount of work done by DSP, CPU load by applications etc... Nothing prevents you to implement stack and applications handling on the single CPU except performance limitations (but you should have in mind memory isolation, security issues, etc). As a matter of fact, what becomes more and more attractive now days are L4 hypervisors, which could separate BB and APP system in the separate containers, running on the same CPU. BR, Drasko BR, Drasko From laforge at gnumonks.org Fri Feb 18 17:57:23 2011 From: laforge at gnumonks.org (Harald Welte) Date: Fri, 18 Feb 2011 18:57:23 +0100 Subject: Mediatek MT6235 status (Sciphone G2) In-Reply-To: References: <8716C48654180249A0941A44457B90751466D32B14@EXMB02.eu.tieto.com> <20110218103203.GZ1002@prithivi.gnumonks.org> <20110218121907.GE1002@prithivi.gnumonks.org> Message-ID: <20110218175723.GL1002@prithivi.gnumonks.org> Hi, On Fri, Feb 18, 2011 at 03:52:53PM +0100, Drasko DRASKOVIC wrote: > As a matter of fact, what becomes more and more attractive now days > are L4 hypervisors, which could separate BB and APP system in the > separate containers, running on the same CPU. The only reason why commercial companies (most notably ST-Ericsson) with proprietary GSM stacks use this is to make sure they don't have to release any of their proprietary code under GPL. There is absolutely no technical reason why you cannot do a GSM L1 inside the regular Linux kernel. You just have to do it in a GPL-compatible way :) -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From drasko.draskovic at gmail.com Fri Feb 18 20:04:59 2011 From: drasko.draskovic at gmail.com (Drasko DRASKOVIC) Date: Fri, 18 Feb 2011 21:04:59 +0100 Subject: Mediatek MT6235 status (Sciphone G2) In-Reply-To: <20110218175723.GL1002@prithivi.gnumonks.org> References: <8716C48654180249A0941A44457B90751466D32B14@EXMB02.eu.tieto.com> <20110218103203.GZ1002@prithivi.gnumonks.org> <20110218121907.GE1002@prithivi.gnumonks.org> <20110218175723.GL1002@prithivi.gnumonks.org> Message-ID: On Fri, Feb 18, 2011 at 6:57 PM, Harald Welte wrote: > Hi, > > On Fri, Feb 18, 2011 at 03:52:53PM +0100, Drasko DRASKOVIC wrote: > >> As a matter of fact, what becomes more and more attractive now days >> are L4 hypervisors, which could separate BB and APP system in the >> separate containers, running on the same CPU. > > The only reason why commercial companies (most notably ST-Ericsson) with > proprietary GSM stacks use this is to make sure they don't have to release any > of their proprietary code under GPL. There is always a way to insert your PS code in some FOSS system and keep it closed. You can use any BSD licensed system. Apparently with L23 you can do this with Linux, since you are in the userspace, so you do not have to link with GPL'd kernel. L1 can be a baremetal app running side by side with your kernel. I would not say that L4 is used only to close code. It gives you opportunity to clearly separate several systems running on the same core, and have them communicate between themselves in a standardized and secure way. It can also serve as a powerful HAL and can come into play with security requirements. I think we'll be looking a lot of into this in the future... but that's just my $0.2. BR, Drasko From laforge at gnumonks.org Fri Feb 18 17:55:12 2011 From: laforge at gnumonks.org (Harald Welte) Date: Fri, 18 Feb 2011 18:55:12 +0100 Subject: Mediatek MT6235 status (Sciphone G2) In-Reply-To: References: <8716C48654180249A0941A44457B90751466D32B14@EXMB02.eu.tieto.com> <20110218103203.GZ1002@prithivi.gnumonks.org> <20110218121907.GE1002@prithivi.gnumonks.org> Message-ID: <20110218175512.GK1002@prithivi.gnumonks.org> On Fri, Feb 18, 2011 at 07:27:59AM -0700, Marius Cirsta wrote: > From what I understand MT6235 has just one ARM926EJS processor and a > DSP. This probably means that the it runs both the application and > the GSM stack on a single CPU , right ? It's actually 2 DSP cores. But yes, your last statement is correct. > I read in an article about Symbian that it's able to do this because > it's a realtime OS but to my knowledge Linux is not ( hence the GSM > stack runs on a second processor in Android phones ). Now I also know > there's a realtime Linux kernel but the question is would it be > possible to run both the application and GSM stack together on the > MT6235 under Linux. Don't believe marketing crap by any company (or the Symbian foundation) ;) Layer 2 and Layer 3 of GSM have no realtime requirements, it's only the L1 that has. Running L1 inside the kernel in IRQ priority should solve all those problems. If not, we can still use the FIQ to pre-empt all the other IRQs in the kernel. Layer2 + Layer3 then run as regular userspace programs on top of the kernel. The entire' "realtime vs. non-realtime" debate often seems nothing but a religious and/or marketing war. Regards, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From mforce2 at gmail.com Fri Feb 18 18:54:46 2011 From: mforce2 at gmail.com (Marius Cirsta) Date: Fri, 18 Feb 2011 20:54:46 +0200 Subject: Mediatek MT6235 status (Sciphone G2) In-Reply-To: <20110218175512.GK1002@prithivi.gnumonks.org> References: <8716C48654180249A0941A44457B90751466D32B14@EXMB02.eu.tieto.com> <20110218103203.GZ1002@prithivi.gnumonks.org> <20110218121907.GE1002@prithivi.gnumonks.org> <20110218175512.GK1002@prithivi.gnumonks.org> Message-ID: On Fri, Feb 18, 2011 at 7:55 PM, Harald Welte wrote: > On Fri, Feb 18, 2011 at 07:27:59AM -0700, Marius Cirsta wrote: >> ?From what I understand MT6235 has just one ARM926EJS processor and a >> DSP. ?This probably means that the it runs both the application and >> the GSM stack on a single CPU , right ? > > It's actually 2 DSP cores. ?But yes, your last statement is correct. > Didn't read the datasheet that well it seems. >> ?I read in an article about Symbian that it's able to do this because >> it's a realtime OS but to my knowledge Linux is not ( hence the GSM >> stack runs on a second processor in Android phones ). Now I also know >> there's a realtime Linux kernel but the question is would it be >> possible to run both the application and GSM stack together on the >> MT6235 under Linux. > > Don't believe marketing crap by any company (or the Symbian foundation) ;) > I usually don't but since I have only basic knowledge in telecom I thought what they said was true and it did acutally make sense. > Layer 2 and Layer 3 of GSM have no realtime requirements, it's only the L1 > that has. ?Running L1 inside the kernel in IRQ priority should solve all those > problems. ?If not, we can still use the FIQ to pre-empt all the other IRQs > in the kernel. > > Layer2 + Layer3 then run as regular userspace programs on top of the kernel. > > The entire' "realtime vs. non-realtime" debate often seems nothing but > a religious and/or marketing war. > Thanks for these clarifications , it answers my question. I do have another one though , out of curiosity. Why do most if not all Android phone have a separate core for running the GSM stack ? Even MT6516 has a dedicated ARM 7 core. I cand think of the advantages being isolation of the GSM stack and keeping it hidden and proprietary but until now I thought it was a must. > Regards, > ? ? ? ?Harald > -- > - Harald Welte ? ? ? ? ? http://laforge.gnumonks.org/ > ============================================================================ > "Privacy in residential applications is a desirable marketing option." > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?(ETSI EN 300 175-7 Ch. A6) > From drasko.draskovic at gmail.com Fri Feb 18 19:56:50 2011 From: drasko.draskovic at gmail.com (Drasko DRASKOVIC) Date: Fri, 18 Feb 2011 20:56:50 +0100 Subject: Mediatek MT6235 status (Sciphone G2) In-Reply-To: References: <8716C48654180249A0941A44457B90751466D32B14@EXMB02.eu.tieto.com> <20110218103203.GZ1002@prithivi.gnumonks.org> <20110218121907.GE1002@prithivi.gnumonks.org> <20110218175512.GK1002@prithivi.gnumonks.org> Message-ID: On Fri, Feb 18, 2011 at 7:54 PM, Marius Cirsta wrote: > Thanks for these clarifications , it answers my question. I do have > another one though , out of curiosity. Why do most if not all Android > phone have a separate core for running the GSM stack ? Even MT6516 has > a dedicated ARM 7 core. I cand think of the advantages being isolation > of the GSM stack and keeping it hidden and proprietary but until now I > thought it was a must. As I said, it is mostly performance issue. From laforge at gnumonks.org Fri Feb 18 10:22:06 2011 From: laforge at gnumonks.org (Harald Welte) Date: Fri, 18 Feb 2011 11:22:06 +0100 Subject: Mediatek MT6235 status (Sciphone G2) In-Reply-To: <8716C48654180249A0941A44457B90751466D32B14@EXMB02.eu.tieto.com> References: <8716C48654180249A0941A44457B90751466D32B14@EXMB02.eu.tieto.com> Message-ID: <20110218102206.GW1002@prithivi.gnumonks.org> Marcin, I can only second the other people who have commented: Congratulations on your great work! It's good to see that you have still been on track. I was already starting to wonder after the comparatively long period of silence. Unfortunately I still haven't had much time to work on the GSM side of the MTK chipset - though I've spent some 2 days and think I have a farily good understanding of the architecture and the required drivers for the analog/RF side. The biggest unknown part so far is the ARM/DSP shared memory interface, and the "API" (rather an ABI) that is used to exchange information on it. I have done some initial research, but given my high workload with other (interesting + paid) GSM protocol R&D related work, I still cannot make any promises when we'll actually see some progress here. If anyone else feels interested to dive into it, feel free to do so. Especially the RF transceiver driver, TDMA timer driver, etc. should all be possible to develop right now based on the documentation that is available. Those of you with a Racal 6103 or similar device should also be able to take measurements and test the drivers, i.e. whether it tunes to the right Tx frequency, whether the TDMA timer are firing at the right point in time (power ramp up/ramp down, ...) Regards, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From Marcin.Mielczarczyk at tieto.com Fri Feb 18 10:46:23 2011 From: Marcin.Mielczarczyk at tieto.com (Marcin.Mielczarczyk at tieto.com) Date: Fri, 18 Feb 2011 12:46:23 +0200 Subject: Mediatek MT6235 status (Sciphone G2) In-Reply-To: <20110218102206.GW1002@prithivi.gnumonks.org> References: <8716C48654180249A0941A44457B90751466D32B14@EXMB02.eu.tieto.com> <20110218102206.GW1002@prithivi.gnumonks.org> Message-ID: <8716C48654180249A0941A44457B9075146AA79D9E@EXMB02.eu.tieto.com> > The biggest unknown part so far is the ARM/DSP shared memory interface, and the "API" (rather an ABI) that is used to exchange information on it. I agree, as I have the same problem here to run audio. > I have done some initial research, but given my high workload with other (interesting + paid) GSM protocol R&D related work, > I still cannot make any promises when we'll actually see some progress here. No problem. > If anyone else feels interested to dive into it, feel free to do so. > Especially the RF transceiver driver, TDMA timer driver, etc. should all be possible to develop right now based on the documentation that is available. I'm gonna dive into this topic. That's something where I don't have experience so it'll take me some time to understand it, but it's worth effort. As I mentioned some time ago I had adventure with L2/3 development and I'm gonna refresh my knowledge. I'm also eager to try something new, so I'll be satisfied stepping down into RF part. BR, Marcin From laforge at gnumonks.org Fri Feb 18 12:23:04 2011 From: laforge at gnumonks.org (Harald Welte) Date: Fri, 18 Feb 2011 13:23:04 +0100 Subject: Mediatek MT6235 status (Sciphone G2) In-Reply-To: <8716C48654180249A0941A44457B9075146AA79D9E@EXMB02.eu.tieto.com> References: <8716C48654180249A0941A44457B90751466D32B14@EXMB02.eu.tieto.com> <20110218102206.GW1002@prithivi.gnumonks.org> <8716C48654180249A0941A44457B9075146AA79D9E@EXMB02.eu.tieto.com> Message-ID: <20110218122304.GF1002@prithivi.gnumonks.org> Marcin, On Fri, Feb 18, 2011 at 12:46:23PM +0200, Marcin.Mielczarczyk at tieto.com wrote: > > If anyone else feels interested to dive into it, feel free to do so. > > Especially the RF transceiver driver, TDMA timer driver, etc. should all be > > possible to develop right now based on the documentation that is available. > > I'm gonna dive into this topic. > That's something where I don't have experience so it'll take me some time to > understand it, but it's worth effort. I'm happy to hear this. The problem sort-of is: Do you have the kind of measurement equipment to facilitate that kind of development? In order to e.g. test the VCO/PLL / Transmit code, you would have to have something like a spectrum analyzer or a scope that can go up to at least the GSM900, preferrably up into 1800/1900 MHz. If you want to test the receive side, something like a GSM signal generator (HP 8922, Racal 6103, R&S CMD 55) would be great, as they can transmit a well-known bit pattern (all-1, all-0, 101010101010 and the like) on a configured ARFCN, then configure the RF Transceiver (MT61400 and you can watch the analog baseband signal on an oscilloscope and determine if it mathes the expected singal. Regards, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From Marcin.Mielczarczyk at tieto.com Fri Feb 18 12:46:49 2011 From: Marcin.Mielczarczyk at tieto.com (Marcin.Mielczarczyk at tieto.com) Date: Fri, 18 Feb 2011 14:46:49 +0200 Subject: Mediatek MT6235 status (Sciphone G2) In-Reply-To: <20110218122304.GF1002@prithivi.gnumonks.org> References: <8716C48654180249A0941A44457B90751466D32B14@EXMB02.eu.tieto.com> <20110218102206.GW1002@prithivi.gnumonks.org> <8716C48654180249A0941A44457B9075146AA79D9E@EXMB02.eu.tieto.com> <20110218122304.GF1002@prithivi.gnumonks.org> Message-ID: <8716C48654180249A0941A44457B9075146AA79E63@EXMB02.eu.tieto.com> > I'm happy to hear this. The problem sort-of is: Do you have the kind of measurement equipment to facilitate that kind of development? > In order to e.g. test the VCO/PLL / Transmit code, you would have to have something like a spectrum analyzer or a scope that can go up to > at least the GSM900, preferrably up into 1800/1900 MHz. > > If you want to test the receive side, something like a GSM signal generator (HP 8922, Racal 6103, R&S CMD 55) would be great, > as they can transmit a well-known bit pattern (all-1, all-0, 101010101010 and the like) on a configured ARFCN, then configure the RF Transceiver > (MT61400 and you can watch the analog baseband signal on an oscilloscope and determine if it mathes the expected singal. I have access to such equipment. I have access to Agilent Spectrum Analyzer E4405B (9kHz - 13.2GHz) and Rohde&Schwarz CMU200 (Universal Radio Communication Tester, it also has spectrum analyzer). In this case there're no obstacles to start, only matter of time available for this project. BR, Marcin From dario.lombardo at libero.it Thu Feb 17 16:33:57 2011 From: dario.lombardo at libero.it (Dario Lombardo) Date: Thu, 17 Feb 2011 17:33:57 +0100 Subject: Fwd: gpsd support In-Reply-To: References: Message-ID: Andreas said he is OK with applying them, so I will do that. > > OK :) > However, if I read your code correctly, it still seems to me that there is > a fixed compile time decision if gpsd or built-in gps support is to be > used. > > I think it would be better to keep it a runtime decision, i.e. > > 1) if gpsd headers/library available during compilation, > build support for _both_ gpsd and built-in gps into the program, > 2) if they are not available, only include the built-in gps support. > > That's easy to do. I can maintain the original gps interface, so old code doesn't need to be fixed, and choose the support to use from an internal state. > The decision which method to use should be a config file option. Please > make > sure that a config file configured for built-in gps support will work with > both > versions of the program. > > A config file requesting the use of gpsd support should make the program > abort if it was compiled without gpsd support included. > > Not sure to agree. Execs from layer23/misc don't rely on config files. Probably that's due to the low number of switches used. I think that, even if cell_log options are increased, we can still use cmd switches. Do you agree? Ciao Dario. -------------- next part -------------- An HTML attachment was scrubbed... URL: From laforge at gnumonks.org Thu Feb 17 17:08:42 2011 From: laforge at gnumonks.org (Harald Welte) Date: Thu, 17 Feb 2011 18:08:42 +0100 Subject: Fwd: gpsd support In-Reply-To: References: Message-ID: <20110217170842.GH1002@prithivi.gnumonks.org> Hi Dario, On Thu, Feb 17, 2011 at 05:33:57PM +0100, Dario Lombardo wrote: > That's easy to do. I can maintain the original gps interface, so old code > doesn't need to be fixed, and choose the support to use from an internal > state. Great. > > A config file requesting the use of gpsd support should make the program > > abort if it was compiled without gpsd support included. > Not sure to agree. Execs from layer23/misc don't rely on config files. > Probably that's due to the low number of switches used. I think that, even > if cell_log options are increased, we can still use cmd switches. Do you > agree? Yes, I agree with you. No need for introducing a config file. -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From dario.lombardo at libero.it Tue Feb 22 09:04:17 2011 From: dario.lombardo at libero.it (Dario Lombardo) Date: Tue, 22 Feb 2011 10:04:17 +0100 Subject: Fwd: gpsd support In-Reply-To: <20110217170842.GH1002@prithivi.gnumonks.org> References: <20110217170842.GH1002@prithivi.gnumonks.org> Message-ID: <4D637C11.2060307@libero.it> On 02/17/2011 06:08 PM, Harald Welte wrote: > Yes, I agree with you. No need for introducing a config file. > I have written the new code that supports gps selection at runtime through cmdline switches. Send me any comment you have :). Have a nice day!! Dario. From dario.lombardo at libero.it Mon Feb 21 17:30:24 2011 From: dario.lombardo at libero.it (Dario Lombardo) Date: Mon, 21 Feb 2011 18:30:24 +0100 Subject: [PATCH] Added run-time selection of the gps device. Message-ID: --- src/host/layer23/configure.ac | 2 +- src/host/layer23/include/osmocom/bb/common/gps.h | 13 ++++- src/host/layer23/src/common/gps.c | 64 ++++++++++++++++------ src/host/layer23/src/misc/app_cell_log.c | 48 ++++++++++------- src/host/layer23/src/mobile/vty_interface.c | 20 +++---- 5 files changed, 95 insertions(+), 52 deletions(-) diff --git a/src/host/layer23/configure.ac b/src/host/layer23/configure.ac index e1c718e..92ec30f 100644 --- a/src/host/layer23/configure.ac +++ b/src/host/layer23/configure.ac @@ -15,7 +15,7 @@ AC_PROG_RANLIB dnl checks for libraries PKG_CHECK_MODULES(LIBOSMOCORE, libosmocore) PKG_CHECK_MODULES(LIBOSMOVTY, libosmovty) -AC_CHECK_LIB(gps, gps_open, CFLAGS+=" -D_USE_GPSD" LDFLAGS+=" -lgps",,) +AC_CHECK_LIB(gps, gps_open, CFLAGS+=" -D_HAVE_GPSD" LDFLAGS+=" -lgps",,) dnl checks for header files AC_HEADER_STDC diff --git a/src/host/layer23/include/osmocom/bb/common/gps.h b/src/host/layer23/include/osmocom/bb/common/gps.h index b7500db..8096dd8 100644 --- a/src/host/layer23/include/osmocom/bb/common/gps.h +++ b/src/host/layer23/include/osmocom/bb/common/gps.h @@ -19,17 +19,24 @@ * */ +enum { + GPS_TYPE_UNDEF, + GPS_TYPE_GPSD, + GPS_TYPE_SERIAL +}; + struct osmo_gps { /* GPS device */ uint8_t enable; + uint8_t gps_type; -#ifdef _USE_GPSD +#ifdef _HAVE_GPSD char gpsd_host[32]; char gpsd_port[6]; -#else +#endif + char device[32]; uint32_t baud; -#endif /* current data */ uint8_t valid; /* we have a fix */ diff --git a/src/host/layer23/src/common/gps.c b/src/host/layer23/src/common/gps.c index 55dd239..24d6c51 100644 --- a/src/host/layer23/src/common/gps.c +++ b/src/host/layer23/src/common/gps.c @@ -26,8 +26,9 @@ #include #include #include +#include -#ifdef _USE_GPSD +#ifdef _HAVE_GPSD #include #endif @@ -39,13 +40,13 @@ struct osmo_gps gps = { 0, -#ifdef _USE_GPSD + GPS_TYPE_UNDEF, +#ifdef _HAVE_GPSD "localhost", "2947", -#else +#endif "/dev/ttyACM0", 0, -#endif 0, 0, 0,0 @@ -53,11 +54,11 @@ struct osmo_gps gps = { static struct bsc_fd gps_bfd; -#ifdef _USE_GPSD +#ifdef _HAVE_GPSD static struct gps_data_t* gdata; -int osmo_gps_cb(struct bsc_fd *bfd, unsigned int what) +int osmo_gpsd_cb(struct bsc_fd *bfd, unsigned int what) { struct tm *tm; unsigned diff = 0; @@ -102,13 +103,13 @@ gps_not_ready: return -1; } -int osmo_gps_open(void) +int osmo_gpsd_open(void) { LOGP(DGPS, LOGL_INFO, "Connecting to gpsd at '%s:%s'\n", gps.gpsd_host, gps.gpsd_port); gps_bfd.data = NULL; gps_bfd.when = BSC_FD_READ; - gps_bfd.cb = osmo_gps_cb; + gps_bfd.cb = osmo_gpsd_cb; gdata = gps_open(gps.gpsd_host, gps.gpsd_port); if (gdata == NULL) { @@ -129,7 +130,7 @@ int osmo_gps_open(void) return 0; } -void osmo_gps_close(void) +void osmo_gpsd_close(void) { if (gps_bfd.fd <= 0) return; @@ -142,11 +143,11 @@ void osmo_gps_close(void) gps_bfd.fd = -1; /* -1 or 0 indicates: 'close' */ } -#else +#endif static struct termios gps_termios, gps_old_termios; -static int osmo_gps_line(char *line) +static int osmo_serialgps_line(char *line) { time_t gps_now, host_now; struct tm *tm; @@ -241,7 +242,7 @@ static int nmea_checksum(char *line) return (strtoul(line+1, NULL, 16) == checksum); } -int osmo_gps_cb(struct bsc_fd *bfd, unsigned int what) +int osmo_serialgps_cb(struct bsc_fd *bfd, unsigned int what) { char buff[128]; static char line[128]; @@ -265,7 +266,7 @@ int osmo_gps_cb(struct bsc_fd *bfd, unsigned int what) if (!nmea_checksum(line)) fprintf(stderr, "NMEA checksum error\n"); else - osmo_gps_line(line); + osmo_serialgps_line(line); continue; } line[lpos++] = buff[i++]; @@ -276,7 +277,7 @@ int osmo_gps_cb(struct bsc_fd *bfd, unsigned int what) return 0; } -int osmo_gps_open(void) +int osmo_serialgps_open(void) { int baud = 0; @@ -287,7 +288,7 @@ int osmo_gps_open(void) gps_bfd.data = NULL; gps_bfd.when = BSC_FD_READ; - gps_bfd.cb = osmo_gps_cb; + gps_bfd.cb = osmo_serialgps_cb; gps_bfd.fd = open(gps.device, O_RDONLY); if (gps_bfd.fd < 0) return gps_bfd.fd; @@ -327,7 +328,7 @@ int osmo_gps_open(void) return 0; } -void osmo_gps_close(void) +void osmo_serialgps_close(void) { if (gps_bfd.fd <= 0) return; @@ -343,11 +344,38 @@ void osmo_gps_close(void) gps_bfd.fd = -1; /* -1 or 0 indicates: 'close' */ } -#endif - void osmo_gps_init(void) { memset(&gps_bfd, 0, sizeof(gps_bfd)); } +int osmo_gps_open(void) +{ + switch (gps.gps_type) { +#ifdef _HAVE_GPSD + case GPS_TYPE_GPSD: + return osmo_gpsd_open(); +#endif + case GPS_TYPE_SERIAL: + return osmo_serialgps_open(); + + default: + return 0; + } +} + +void osmo_gps_close(void) +{ + switch (gps.gps_type) { +#ifdef _HAVE_GPSD + case GPS_TYPE_GPSD: + return osmo_gpsd_close(); +#endif + case GPS_TYPE_SERIAL: + return osmo_serialgps_close(); + + default: + return; + } +} diff --git a/src/host/layer23/src/misc/app_cell_log.c b/src/host/layer23/src/misc/app_cell_log.c index 7a2c67a..40aac5a 100644 --- a/src/host/layer23/src/misc/app_cell_log.c +++ b/src/host/layer23/src/misc/app_cell_log.c @@ -92,13 +92,12 @@ static int l23_getopt_options(struct option **options) {"logfile", 1, 0, 'l'}, {"rach", 1, 0, 'r'}, {"no-rach", 1, 0, 'n'}, -#ifdef _USE_GPSD +#ifdef _HAVE_GPSD {"gpsd-host", 1, 0, 'g'}, - {"gpsd-port", 1, 0, 'p'} -#else + {"gpsd-port", 1, 0, 'p'}, +#endif {"gps", 1, 0, 'g'}, {"baud", 1, 0, 'b'} -#endif }; *options = opts; @@ -109,15 +108,15 @@ static int l23_cfg_print_help() { printf("\nApplication specific\n"); printf(" -l --logfile LOGFILE Logfile for the cell log.\n"); - printf(" -r --rach RACH Nr. of RACH bursts to send.\n"); - printf(" -n --no-rach Send no rach bursts.\n"); -#ifdef _USE_GPSD + printf(" -r --rach RACH Nr. of RACH bursts to send.\n"); + printf(" -n --no-rach Send no rach bursts.\n"); +#ifdef _HAVE_GPSD printf(" -g --gpsd-host HOST 127.0.0.1. gpsd host.\n"); - printf(" -p --port PORT 2947. gpsd port\n"); -#else - printf(" -g --gps DEVICE /dev/ttyACM0. GPS device.\n"); - printf(" -b --baud BAUDRAT The baud rate of the GPS device\n"); + printf(" -p --port PORT 2947. gpsd port\n"); #endif + printf(" -f --gps DEVICE /dev/ttyACM0. GPS serial device.\n"); + printf(" -b --baud BAUDRAT The baud rate of the GPS device\n"); + return 0; } @@ -133,41 +132,52 @@ static int l23_cfg_handle(int c, const char *optarg) case 'n': RACH_MAX = 0; break; -#ifdef _USE_GPSD +#ifdef _HAVE_GPSD case 'g': snprintf(gps.gpsd_host, ARRAY_SIZE(gps.gpsd_host), "%s", optarg); /* force string terminator */ gps.gpsd_host[ARRAY_SIZE(gps.gpsd_host) - 1] = '\0'; + if (gps.gps_type != GPS_TYPE_UNDEF) + goto cmd_line_error; + gps.gps_type = GPS_TYPE_GPSD; LOGP(DGPS, LOGL_INFO, "Using gpsd host %s\n", gps.gpsd_host); break; case 'p': snprintf(gps.gpsd_port, ARRAY_SIZE(gps.gpsd_port), "%s", optarg); /* force string terminator */ gps.gpsd_port[ARRAY_SIZE(gps.gpsd_port) - 1] = '\0'; + gps.gps_type = GPS_TYPE_GPSD; LOGP(DGPS, LOGL_INFO, "Using gpsd port %s\n", gps.gpsd_port); break; -#else - case 'g': +#endif + case 'f': snprintf(gps.device, ARRAY_SIZE(gps.device), "%s", optarg); /* force string terminator */ gps.device[ARRAY_SIZE(gps.device) - 1] = '\0'; - LOGP(DGPS, LOGL_INFO, "Using GPS device %s\n", gps.device); + if (gps.gps_type != GPS_TYPE_UNDEF) + goto cmd_line_error; + gps.gps_type = GPS_TYPE_SERIAL; + LOGP(DGPS, LOGL_INFO, "Using GPS serial device %s\n", gps.device); break; case 'b': gps.baud = atoi(optarg); + gps.gps_type = GPS_TYPE_SERIAL; LOGP(DGPS, LOGL_INFO, "Setting GPS baudrate to %u\n", gps.baud); break; -#endif } return 0; + +cmd_line_error: + printf("\nYou can't specify both gpsd and serial gps!!\n\n"); + exit(1); } static struct l23_app_info info = { .copyright = "Copyright (C) 2010 Andreas Eversberg\n", -#ifdef _USE_GPSD - .getopt_string = "l:r:ng:p:", +#ifdef _HAVE_GPSD + .getopt_string = "l:r:nf:b:g:p:", #else - .getopt_string = "l:r:ng:b:", + .getopt_string = "l:r:nf:b:", #endif .cfg_supported = l23_cfg_supported, .cfg_getopt_opt = l23_getopt_options, diff --git a/src/host/layer23/src/mobile/vty_interface.c b/src/host/layer23/src/mobile/vty_interface.c index 7888f01..fadc152 100644 --- a/src/host/layer23/src/mobile/vty_interface.c +++ b/src/host/layer23/src/mobile/vty_interface.c @@ -855,7 +855,7 @@ DEFUN(cfg_no_gps_enable, cfg_no_gps_enable_cmd, "no gps enable", return CMD_SUCCESS; } -#ifdef _USE_GPSD +#ifdef _HAVE_GPSD DEFUN(cfg_gps_host, cfg_gps_host_cmd, "gps host HOST:PORT", "GPS receiver\nSelect gpsd host and port\n" "IP and port (optional) of the host running gpsd") @@ -872,6 +872,7 @@ DEFUN(cfg_gps_host, cfg_gps_host_cmd, "gps host HOST:PORT", snprintf(gps.gpsd_port, ARRAY_SIZE(gps.gpsd_port), "2947"); gps.gpsd_port[ARRAY_SIZE(gps.gpsd_port) - 1] = '\0'; } + gps.gps_type = GPS_TYPE_GPSD; if (gps.enable) { osmo_gps_close(); if (osmo_gps_open()) { @@ -883,13 +884,15 @@ DEFUN(cfg_gps_host, cfg_gps_host_cmd, "gps host HOST:PORT", return CMD_SUCCESS; } -#else +#endif + DEFUN(cfg_gps_device, cfg_gps_device_cmd, "gps device DEVICE", "GPS receiver\nSelect serial device\n" "Full path of serial device including /dev/") { strncpy(gps.device, argv[0], sizeof(gps.device)); gps.device[sizeof(gps.device) - 1] = '\0'; + gps.gps_type = GPS_TYPE_SERIAL; if (gps.enable) { osmo_gps_close(); if (osmo_gps_open()) { @@ -901,9 +904,7 @@ DEFUN(cfg_gps_device, cfg_gps_device_cmd, "gps device DEVICE", return CMD_SUCCESS; } -#endif -#ifndef _USE_GPSD DEFUN(cfg_gps_baud, cfg_gps_baud_cmd, "gps baudrate " "(default|4800|""9600|19200|38400|57600|115200)", "GPS receiver\nSelect baud rate\nDefault, don't modify\n\n\n\n\n\n") @@ -924,7 +925,6 @@ DEFUN(cfg_gps_baud, cfg_gps_baud_cmd, "gps baudrate " return CMD_SUCCESS; } -#endif /* per MS config */ DEFUN(cfg_ms, cfg_ms_cmd, "ms MS_NAME", @@ -1204,16 +1204,15 @@ static int config_write(struct vty *vty) { struct osmocom_ms *ms; -#ifdef _USE_GPSD +#ifdef _HAVE_GPSD vty_out(vty, "gpsd host %s%s", gps.gpsd_host, VTY_NEWLINE); vty_out(vty, "gpsd port %s%s", gps.gpsd_port, VTY_NEWLINE); -#else +#endif vty_out(vty, "gps device %s%s", gps.device, VTY_NEWLINE); if (gps.baud) vty_out(vty, "gps baudrate %d%s", gps.baud, VTY_NEWLINE); else vty_out(vty, "gps baudrate default%s", VTY_NEWLINE); -#endif vty_out(vty, "%sgps enable%s", (gps.enable) ? "" : "no ", VTY_NEWLINE); vty_out(vty, "!%s", VTY_NEWLINE); @@ -2305,12 +2304,11 @@ int ms_vty_init(void) install_element(ENABLE_NODE, &call_retr_cmd); install_element(ENABLE_NODE, &call_dtmf_cmd); -#ifdef _USE_GPSD +#ifdef _HAVE_GPSD install_element(CONFIG_NODE, &cfg_gps_host_cmd); -#else +#endif install_element(CONFIG_NODE, &cfg_gps_device_cmd); install_element(CONFIG_NODE, &cfg_gps_baud_cmd); -#endif install_element(CONFIG_NODE, &cfg_gps_enable_cmd); install_element(CONFIG_NODE, &cfg_no_gps_enable_cmd); -- 1.7.4 --------------070003050405000809030404-- From peter at stuge.se Tue Feb 22 13:58:57 2011 From: peter at stuge.se (Peter Stuge) Date: Tue, 22 Feb 2011 14:58:57 +0100 Subject: Fwd: gpsd support In-Reply-To: <4D637C11.2060307@libero.it> References: <20110217170842.GH1002@prithivi.gnumonks.org> <4D637C11.2060307@libero.it> Message-ID: <20110222135857.5874.qmail@stuge.se> Dario Lombardo wrote: > +++ b/src/host/layer23/src/common/gps.c .. > @@ -343,11 +344,38 @@ void osmo_gps_close(void) > gps_bfd.fd = -1; /* -1 or 0 indicates: 'close' */ > } > > -#endif > - > void osmo_gps_init(void) > { > memset(&gps_bfd, 0, sizeof(gps_bfd)); > } > > +int osmo_gps_open(void) > +{ > + switch (gps.gps_type) { > +#ifdef _HAVE_GPSD > + case GPS_TYPE_GPSD: > + return osmo_gpsd_open(); > +#endif > + case GPS_TYPE_SERIAL: > + return osmo_serialgps_open(); > + > + default: > + return 0; > + } > +} Maybe the program should accept the gpsd options also when not compiled with support, and throw an error here? Benefit would be better consistency. > +++ b/src/host/layer23/src/misc/app_cell_log.c .. > static struct l23_app_info info = { > .copyright = "Copyright (C) 2010 Andreas Eversberg\n", > -#ifdef _USE_GPSD > - .getopt_string = "l:r:ng:p:", > +#ifdef _HAVE_GPSD > + .getopt_string = "l:r:nf:b:g:p:", > #else > - .getopt_string = "l:r:ng:b:", > + .getopt_string = "l:r:nf:b:", > #endif This part *so* can not scale. Maybe use something like this.. .getopt_string = "l:r:nf:b" \ #ifdef _HAVE_GPSD "g:p:" \ #endif "", > +++ b/src/host/layer23/src/mobile/vty_interface.c > @@ -855,7 +855,7 @@ DEFUN(cfg_no_gps_enable, cfg_no_gps_enable_cmd, "no gps enable", > return CMD_SUCCESS; > } > > -#ifdef _USE_GPSD > +#ifdef _HAVE_GPSD > DEFUN(cfg_gps_host, cfg_gps_host_cmd, "gps host HOST:PORT", ..but again, maybe consider always having the options and commands be supported, and failing in some other way than invalid option/command without _HAVE_GPSD. //Peter From dario.lombardo at libero.it Thu Feb 24 09:35:34 2011 From: dario.lombardo at libero.it (Dario Lombardo) Date: Thu, 24 Feb 2011 10:35:34 +0100 Subject: Fwd: gpsd support In-Reply-To: <20110222135857.5874.qmail@stuge.se> References: <20110217170842.GH1002@prithivi.gnumonks.org> <4D637C11.2060307@libero.it> <20110222135857.5874.qmail@stuge.se> Message-ID: <4D662666.4060006@libero.it> Hi guys Thanks to Martin Hauke help I have added a gpsv3 support, that allows the previous support to work with gpsd-2.39 and gpsd-2.95. To Peter: I have added your suggestion about the ".getopt_string", but not the suggestion about the runtime error, because I didn't find any smart way to do that. May be next step :). Please take a look at the attached patch. Bye Dario. From dario.lombardo at libero.it Thu Feb 24 09:16:33 2011 From: dario.lombardo at libero.it (Dario Lombardo) Date: Thu, 24 Feb 2011 10:16:33 +0100 Subject: [PATCH] Added cmd-line selection of gps device. Message-ID: --- src/host/layer23/configure.ac | 3 +- src/host/layer23/include/osmocom/bb/common/gps.h | 15 ++- src/host/layer23/src/common/gps.c | 128 ++++++++++++++-------- src/host/layer23/src/misc/app_cell_log.c | 70 +++++++----- src/host/layer23/src/misc/cell_log.c | 28 +++--- src/host/layer23/src/mobile/vty_interface.c | 72 ++++++------ 6 files changed, 186 insertions(+), 130 deletions(-) diff --git a/src/host/layer23/configure.ac b/src/host/layer23/configure.ac index e1c718e..c797e29 100644 --- a/src/host/layer23/configure.ac +++ b/src/host/layer23/configure.ac @@ -15,7 +15,8 @@ AC_PROG_RANLIB dnl checks for libraries PKG_CHECK_MODULES(LIBOSMOCORE, libosmocore) PKG_CHECK_MODULES(LIBOSMOVTY, libosmovty) -AC_CHECK_LIB(gps, gps_open, CFLAGS+=" -D_USE_GPSD" LDFLAGS+=" -lgps",,) +AC_CHECK_LIB(gps, gps_open, CFLAGS+=" -D_HAVE_GPSD" LDFLAGS+=" -lgps",,) +AC_CHECK_LIB(gps, gps_stream, CFLAGS+=" -D_HAVE_GPSD_V3",,) dnl checks for header files AC_HEADER_STDC diff --git a/src/host/layer23/include/osmocom/bb/common/gps.h b/src/host/layer23/include/osmocom/bb/common/gps.h index b7500db..58c0c53 100644 --- a/src/host/layer23/include/osmocom/bb/common/gps.h +++ b/src/host/layer23/include/osmocom/bb/common/gps.h @@ -19,17 +19,24 @@ * */ +enum { + GPS_TYPE_UNDEF, + GPS_TYPE_GPSD, + GPS_TYPE_SERIAL +}; + struct osmo_gps { /* GPS device */ uint8_t enable; + uint8_t gps_type; -#ifdef _USE_GPSD +#ifdef _HAVE_GPSD char gpsd_host[32]; char gpsd_port[6]; -#else +#endif + char device[32]; uint32_t baud; -#endif /* current data */ uint8_t valid; /* we have a fix */ @@ -37,7 +44,7 @@ struct osmo_gps { double latitude, longitude; }; -extern struct osmo_gps gps; +extern struct osmo_gps g; int osmo_gps_open(void); void osmo_gps_close(void); diff --git a/src/host/layer23/src/common/gps.c b/src/host/layer23/src/common/gps.c index 55dd239..f858270 100644 --- a/src/host/layer23/src/common/gps.c +++ b/src/host/layer23/src/common/gps.c @@ -26,8 +26,9 @@ #include #include #include +#include -#ifdef _USE_GPSD +#ifdef _HAVE_GPSD #include #endif @@ -37,15 +38,15 @@ #include #include -struct osmo_gps gps = { +struct osmo_gps g = { 0, -#ifdef _USE_GPSD + GPS_TYPE_UNDEF, +#ifdef _HAVE_GPSD "localhost", "2947", -#else +#endif "/dev/ttyACM0", 0, -#endif 0, 0, 0,0 @@ -53,16 +54,16 @@ struct osmo_gps gps = { static struct bsc_fd gps_bfd; -#ifdef _USE_GPSD +#ifdef _HAVE_GPSD static struct gps_data_t* gdata; -int osmo_gps_cb(struct bsc_fd *bfd, unsigned int what) +int osmo_gpsd_cb(struct bsc_fd *bfd, unsigned int what) { struct tm *tm; unsigned diff = 0; - gps.valid = 0; + g.valid = 0; /* gps is offline */ if (gdata->online) @@ -78,21 +79,21 @@ int osmo_gps_cb(struct bsc_fd *bfd, unsigned int what) /* data are valid */ if (gdata->set & LATLON_SET) { - gps.valid = 1; - gps.gmt = gdata->fix.time; - tm = localtime(&gps.gmt); - diff = time(NULL) - gps.gmt; - gps.latitude = gdata->fix.latitude; - gps.longitude = gdata->fix.longitude; + g.valid = 1; + g.gmt = gdata->fix.time; + tm = localtime(&g.gmt); + diff = time(NULL) - g.gmt; + g.latitude = gdata->fix.latitude; + g.longitude = gdata->fix.longitude; LOGP(DGPS, LOGL_INFO, " time=%02d:%02d:%02d %04d-%02d-%02d, " "diff-to-host=%d, latitude=%do%.4f, longitude=%do%.4f\n", tm->tm_hour, tm->tm_min, tm->tm_sec, tm->tm_year + 1900, tm->tm_mday, tm->tm_mon + 1, diff, - (int)gps.latitude, - (gps.latitude - ((int)gps.latitude)) * 60.0, - (int)gps.longitude, - (gps.longitude - ((int)gps.longitude)) * 60.0); + (int)g.latitude, + (g.latitude - ((int)g.latitude)) * 60.0, + (int)g.longitude, + (g.longitude - ((int)g.longitude)) * 60.0); } return 0; @@ -102,15 +103,15 @@ gps_not_ready: return -1; } -int osmo_gps_open(void) +int osmo_gpsd_open(void) { - LOGP(DGPS, LOGL_INFO, "Connecting to gpsd at '%s:%s'\n", gps.gpsd_host, gps.gpsd_port); + LOGP(DGPS, LOGL_INFO, "Connecting to gpsd at '%s:%s'\n", g.gpsd_host, g.gpsd_port); gps_bfd.data = NULL; gps_bfd.when = BSC_FD_READ; - gps_bfd.cb = osmo_gps_cb; + gps_bfd.cb = osmo_gpsd_cb; - gdata = gps_open(gps.gpsd_host, gps.gpsd_port); + gdata = gps_open(g.gpsd_host, g.gpsd_port); if (gdata == NULL) { LOGP(DGPS, LOGL_ERROR, "Can't connect to gpsd\n"); return -1; @@ -119,6 +120,18 @@ int osmo_gps_open(void) if (gps_bfd.fd < 0) return gps_bfd.fd; +#ifdef _HAVE_GPSD_V3 + if (gps_stream(gdata, WATCH_ENABLE, NULL) == -1) { + LOGP(DGPS, LOGL_ERROR, "Error in gps_stream()\n"); + return -1; + } +#else + if (gps_query(gdata, "o")) { + LOGP(DGPS, LOGL_ERROR, "Error in gps_query()\n"); + return -1; + } +#endif + if (gps_stream(gdata, WATCH_ENABLE, NULL) == -1) { LOGP(DGPS, LOGL_ERROR, "Error in gps_stream()\n"); return -1; @@ -129,7 +142,7 @@ int osmo_gps_open(void) return 0; } -void osmo_gps_close(void) +void osmo_gpsd_close(void) { if (gps_bfd.fd <= 0) return; @@ -142,11 +155,11 @@ void osmo_gps_close(void) gps_bfd.fd = -1; /* -1 or 0 indicates: 'close' */ } -#else +#endif static struct termios gps_termios, gps_old_termios; -static int osmo_gps_line(char *line) +static int osmo_serialgps_line(char *line) { time_t gps_now, host_now; struct tm *tm; @@ -164,10 +177,10 @@ static int osmo_gps_line(char *line) /* valid position */ if (line[36] != 'A') { LOGP(DGPS, LOGL_INFO, "%s (invalid)\n", line); - gps.valid = 0; + g.valid = 0; return 0; } - gps.valid = 1; + g.valid = 1; /* time stamp */ gps_now = line[30] - '0'; @@ -185,7 +198,7 @@ static int osmo_gps_line(char *line) diff -= 86400; /* apply the "date" part to the GPS time */ gps_now = host_now - diff; - gps.gmt = gps_now; + g.gmt = gps_now; tm = localtime(&gps_now); /* position */ @@ -199,7 +212,7 @@ static int osmo_gps_line(char *line) latitude += (double)(line[8] - '0') / 600000.0; if (line[10] == 'S') latitude = 0.0 - latitude; - gps.latitude = latitude; + g.latitude = latitude; longitude = (double)(line[12] - '0') * 100.0; longitude += (double)(line[13] - '0') * 10.0; longitude += (double)(line[14] - '0'); @@ -211,17 +224,17 @@ static int osmo_gps_line(char *line) longitude += (double)(line[21] - '0') / 600000.0; if (line[23] == 'W') longitude = 360.0 - longitude; - gps.longitude = longitude; + g.longitude = longitude; LOGP(DGPS, LOGL_DEBUG, "%s\n", line); LOGP(DGPS, LOGL_INFO, " time=%02d:%02d:%02d %04d-%02d-%02d, " "diff-to-host=%d, latitude=%do%.4f, longitude=%do%.4f\n", tm->tm_hour, tm->tm_min, tm->tm_sec, tm->tm_year + 1900, tm->tm_mday, tm->tm_mon + 1, diff, - (int)gps.latitude, - (gps.latitude - ((int)gps.latitude)) * 60.0, - (int)gps.longitude, - (gps.longitude - ((int)gps.longitude)) * 60.0); + (int)g.latitude, + (g.latitude - ((int)g.latitude)) * 60.0, + (int)g.longitude, + (g.longitude - ((int)g.longitude)) * 60.0); return 0; } @@ -241,7 +254,7 @@ static int nmea_checksum(char *line) return (strtoul(line+1, NULL, 16) == checksum); } -int osmo_gps_cb(struct bsc_fd *bfd, unsigned int what) +int osmo_serialgps_cb(struct bsc_fd *bfd, unsigned int what) { char buff[128]; static char line[128]; @@ -265,7 +278,7 @@ int osmo_gps_cb(struct bsc_fd *bfd, unsigned int what) if (!nmea_checksum(line)) fprintf(stderr, "NMEA checksum error\n"); else - osmo_gps_line(line); + osmo_serialgps_line(line); continue; } line[lpos++] = buff[i++]; @@ -276,23 +289,23 @@ int osmo_gps_cb(struct bsc_fd *bfd, unsigned int what) return 0; } -int osmo_gps_open(void) +int osmo_serialgps_open(void) { int baud = 0; if (gps_bfd.fd > 0) return 0; - LOGP(DGPS, LOGL_INFO, "Open GPS device '%s'\n", gps.device); + LOGP(DGPS, LOGL_INFO, "Open GPS device '%s'\n", g.device); gps_bfd.data = NULL; gps_bfd.when = BSC_FD_READ; - gps_bfd.cb = osmo_gps_cb; - gps_bfd.fd = open(gps.device, O_RDONLY); + gps_bfd.cb = osmo_serialgps_cb; + gps_bfd.fd = open(g.device, O_RDONLY); if (gps_bfd.fd < 0) return gps_bfd.fd; - switch (gps.baud) { + switch (g.baud) { case 4800: baud = B4800; break; case 9600: @@ -327,7 +340,7 @@ int osmo_gps_open(void) return 0; } -void osmo_gps_close(void) +void osmo_serialgps_close(void) { if (gps_bfd.fd <= 0) return; @@ -343,11 +356,38 @@ void osmo_gps_close(void) gps_bfd.fd = -1; /* -1 or 0 indicates: 'close' */ } -#endif - void osmo_gps_init(void) { memset(&gps_bfd, 0, sizeof(gps_bfd)); } +int osmo_gps_open(void) +{ + switch (g.gps_type) { +#ifdef _HAVE_GPSD + case GPS_TYPE_GPSD: + return osmo_gpsd_open(); +#endif + case GPS_TYPE_SERIAL: + return osmo_serialgps_open(); + + default: + return 0; + } +} + +void osmo_gps_close(void) +{ + switch (g.gps_type) { +#ifdef _HAVE_GPSD + case GPS_TYPE_GPSD: + return osmo_gpsd_close(); +#endif + case GPS_TYPE_SERIAL: + return osmo_serialgps_close(); + + default: + return; + } +} diff --git a/src/host/layer23/src/misc/app_cell_log.c b/src/host/layer23/src/misc/app_cell_log.c index 7a2c67a..7030abf 100644 --- a/src/host/layer23/src/misc/app_cell_log.c +++ b/src/host/layer23/src/misc/app_cell_log.c @@ -92,13 +92,12 @@ static int l23_getopt_options(struct option **options) {"logfile", 1, 0, 'l'}, {"rach", 1, 0, 'r'}, {"no-rach", 1, 0, 'n'}, -#ifdef _USE_GPSD +#ifdef _HAVE_GPSD {"gpsd-host", 1, 0, 'g'}, - {"gpsd-port", 1, 0, 'p'} -#else + {"gpsd-port", 1, 0, 'p'}, +#endif {"gps", 1, 0, 'g'}, {"baud", 1, 0, 'b'} -#endif }; *options = opts; @@ -109,15 +108,15 @@ static int l23_cfg_print_help() { printf("\nApplication specific\n"); printf(" -l --logfile LOGFILE Logfile for the cell log.\n"); - printf(" -r --rach RACH Nr. of RACH bursts to send.\n"); - printf(" -n --no-rach Send no rach bursts.\n"); -#ifdef _USE_GPSD + printf(" -r --rach RACH Nr. of RACH bursts to send.\n"); + printf(" -n --no-rach Send no rach bursts.\n"); +#ifdef _HAVE_GPSD printf(" -g --gpsd-host HOST 127.0.0.1. gpsd host.\n"); - printf(" -p --port PORT 2947. gpsd port\n"); -#else - printf(" -g --gps DEVICE /dev/ttyACM0. GPS device.\n"); - printf(" -b --baud BAUDRAT The baud rate of the GPS device\n"); + printf(" -p --port PORT 2947. gpsd port\n"); #endif + printf(" -f --gps DEVICE /dev/ttyACM0. GPS serial device.\n"); + printf(" -b --baud BAUDRAT The baud rate of the GPS device\n"); + return 0; } @@ -133,42 +132,53 @@ static int l23_cfg_handle(int c, const char *optarg) case 'n': RACH_MAX = 0; break; -#ifdef _USE_GPSD +#ifdef _HAVE_GPSD case 'g': - snprintf(gps.gpsd_host, ARRAY_SIZE(gps.gpsd_host), "%s", optarg); + snprintf(g.gpsd_host, ARRAY_SIZE(g.gpsd_host), "%s", optarg); /* force string terminator */ - gps.gpsd_host[ARRAY_SIZE(gps.gpsd_host) - 1] = '\0'; - LOGP(DGPS, LOGL_INFO, "Using gpsd host %s\n", gps.gpsd_host); + g.gpsd_host[ARRAY_SIZE(g.gpsd_host) - 1] = '\0'; + if (g.gps_type != GPS_TYPE_UNDEF) + goto cmd_line_error; + g.gps_type = GPS_TYPE_GPSD; + LOGP(DGPS, LOGL_INFO, "Using gpsd host %s\n", g.gpsd_host); break; case 'p': - snprintf(gps.gpsd_port, ARRAY_SIZE(gps.gpsd_port), "%s", optarg); + snprintf(g.gpsd_port, ARRAY_SIZE(g.gpsd_port), "%s", optarg); /* force string terminator */ - gps.gpsd_port[ARRAY_SIZE(gps.gpsd_port) - 1] = '\0'; - LOGP(DGPS, LOGL_INFO, "Using gpsd port %s\n", gps.gpsd_port); + g.gpsd_port[ARRAY_SIZE(g.gpsd_port) - 1] = '\0'; + g.gps_type = GPS_TYPE_GPSD; + LOGP(DGPS, LOGL_INFO, "Using gpsd port %s\n", g.gpsd_port); break; -#else - case 'g': - snprintf(gps.device, ARRAY_SIZE(gps.device), "%s", optarg); +#endif + case 'f': + snprintf(g.device, ARRAY_SIZE(g.device), "%s", optarg); /* force string terminator */ - gps.device[ARRAY_SIZE(gps.device) - 1] = '\0'; - LOGP(DGPS, LOGL_INFO, "Using GPS device %s\n", gps.device); + g.device[ARRAY_SIZE(g.device) - 1] = '\0'; + if (g.gps_type != GPS_TYPE_UNDEF) + goto cmd_line_error; + g.gps_type = GPS_TYPE_SERIAL; + LOGP(DGPS, LOGL_INFO, "Using GPS serial device %s\n", g.device); break; case 'b': - gps.baud = atoi(optarg); - LOGP(DGPS, LOGL_INFO, "Setting GPS baudrate to %u\n", gps.baud); + g.baud = atoi(optarg); + g.gps_type = GPS_TYPE_SERIAL; + LOGP(DGPS, LOGL_INFO, "Setting GPS baudrate to %u\n", g.baud); break; -#endif } return 0; + +cmd_line_error: + printf("\nYou can't specify both gpsd and serial gps!!\n\n"); + exit(1); } static struct l23_app_info info = { .copyright = "Copyright (C) 2010 Andreas Eversberg\n", -#ifdef _USE_GPSD - .getopt_string = "l:r:ng:p:", -#else - .getopt_string = "l:r:ng:b:", + .getopt_string = +#ifdef _HAVE_GPSD + "g:p:" #endif + "l:r:nf:b:", .cfg_supported = l23_cfg_supported, .cfg_getopt_opt = l23_getopt_options, .cfg_handle_opt = l23_cfg_handle, diff --git a/src/host/layer23/src/misc/cell_log.c b/src/host/layer23/src/misc/cell_log.c index a0f9769..7de2c40 100644 --- a/src/host/layer23/src/misc/cell_log.c +++ b/src/host/layer23/src/misc/cell_log.c @@ -119,17 +119,17 @@ static void start_pm(void); static void log_gps(void) { - if (!gps.enable || !gps.valid) + if (!g.enable || !g.valid) return; - LOGFILE("position %.8f %.8f\n", gps.longitude, gps.latitude); + LOGFILE("position %.8f %.8f\n", g.longitude, g.latitude); } static void log_time(void) { time_t now; - if (gps.enable && gps.valid) - now = gps.gmt; + if (g.enable && g.valid) + now = g.gmt; else time(&now); LOGFILE("time %lu\n", now); @@ -317,15 +317,15 @@ static void start_sync(void) } } /* if GPS becomes valid, like after exitting a tunnel */ - if (!pm_gps_valid && gps.valid) { + if (!pm_gps_valid && g.valid) { pm_gps_valid = 1; - geo2space(&pm_gps_x, &pm_gps_y, &pm_gps_z, gps.longitude, - gps.latitude); + geo2space(&pm_gps_x, &pm_gps_y, &pm_gps_z, g.longitude, + g.latitude); } - if (pm_gps_valid && gps.valid) { + if (pm_gps_valid && g.valid) { double x, y, z; - geo2space(&x, &y, &z, gps.longitude, gps.latitude); + geo2space(&x, &y, &z, g.longitude, g.latitude); dist = distinspace(pm_gps_x, pm_gps_y, pm_gps_z, x, y, z); sprintf(dist_str, " dist %d", (int)dist); } @@ -357,10 +357,10 @@ static void start_pm(void) if (from == 0 && to == 0) { LOGP(DSUM, LOGL_INFO, "Measurement done\n"); - pm_gps_valid = gps.enable && gps.valid; + pm_gps_valid = g.enable && g.valid; if (pm_gps_valid) geo2space(&pm_gps_x, &pm_gps_y, &pm_gps_z, - gps.longitude, gps.latitude); + g.longitude, g.latitude); log_pm(); start_sync(); return; @@ -786,10 +786,10 @@ int scan_init(struct osmocom_ms *_ms) register_signal_handler(SS_L1CTL, &signal_cb, NULL); memset(&timer, 0, sizeof(timer)); osmol2_register_handler(ms, &rcv_rsl); - gps.enable = 1; + g.enable = 1; osmo_gps_init(); if (osmo_gps_open()) - gps.enable = 0; + g.enable = 0; if (!strcmp(logname, "-")) logfp = stdout; @@ -808,7 +808,7 @@ int scan_init(struct osmocom_ms *_ms) int scan_exit(void) { LOGP(DSUM, LOGL_INFO, "Scanner exit\n"); - if (gps.valid) + if (g.valid) osmo_gps_close(); if (logfp) fclose(logfp); diff --git a/src/host/layer23/src/mobile/vty_interface.c b/src/host/layer23/src/mobile/vty_interface.c index 7888f01..b93248d 100644 --- a/src/host/layer23/src/mobile/vty_interface.c +++ b/src/host/layer23/src/mobile/vty_interface.c @@ -836,11 +836,11 @@ DEFUN(cfg_gps_enable, cfg_gps_enable_cmd, "gps enable", "GPS receiver") { if (osmo_gps_open()) { - gps.enable = 1; + g.enable = 1; vty_out(vty, "Failed to open GPS device!%s", VTY_NEWLINE); return CMD_WARNING; } - gps.enable = 1; + g.enable = 1; return CMD_SUCCESS; } @@ -848,31 +848,32 @@ DEFUN(cfg_gps_enable, cfg_gps_enable_cmd, "gps enable", DEFUN(cfg_no_gps_enable, cfg_no_gps_enable_cmd, "no gps enable", NO_STR "Disable GPS receiver") { - if (gps.enable) + if (g.enable) osmo_gps_close(); - gps.enable = 0; + g.enable = 0; return CMD_SUCCESS; } -#ifdef _USE_GPSD +#ifdef _HAVE_GPSD DEFUN(cfg_gps_host, cfg_gps_host_cmd, "gps host HOST:PORT", "GPS receiver\nSelect gpsd host and port\n" "IP and port (optional) of the host running gpsd") { char* colon = strstr(argv[0], ":"); if (colon != NULL) { - memcpy(gps.gpsd_host, argv[0], colon - argv[0] - 1); - gps.gpsd_host[colon - argv[0]] = '\0'; - memcpy(gps.gpsd_port, colon, strlen(colon)); - gps.gpsd_port[strlen(colon)] = '\0'; + memcpy(g.gpsd_host, argv[0], colon - argv[0] - 1); + g.gpsd_host[colon - argv[0]] = '\0'; + memcpy(g.gpsd_port, colon, strlen(colon)); + g.gpsd_port[strlen(colon)] = '\0'; } else { - snprintf(gps.gpsd_host, ARRAY_SIZE(gps.gpsd_host), "%s", argv[0]); - gps.gpsd_host[ARRAY_SIZE(gps.gpsd_host) - 1] = '\0'; - snprintf(gps.gpsd_port, ARRAY_SIZE(gps.gpsd_port), "2947"); - gps.gpsd_port[ARRAY_SIZE(gps.gpsd_port) - 1] = '\0'; + snprintf(g.gpsd_host, ARRAY_SIZE(g.gpsd_host), "%s", argv[0]); + g.gpsd_host[ARRAY_SIZE(g.gpsd_host) - 1] = '\0'; + snprintf(g.gpsd_port, ARRAY_SIZE(g.gpsd_port), "2947"); + g.gpsd_port[ARRAY_SIZE(g.gpsd_port) - 1] = '\0'; } - if (gps.enable) { + g.gps_type = GPS_TYPE_GPSD; + if (g.enable) { osmo_gps_close(); if (osmo_gps_open()) { vty_out(vty, "Failed to connect to gpsd host!%s", @@ -883,14 +884,16 @@ DEFUN(cfg_gps_host, cfg_gps_host_cmd, "gps host HOST:PORT", return CMD_SUCCESS; } -#else +#endif + DEFUN(cfg_gps_device, cfg_gps_device_cmd, "gps device DEVICE", "GPS receiver\nSelect serial device\n" "Full path of serial device including /dev/") { - strncpy(gps.device, argv[0], sizeof(gps.device)); - gps.device[sizeof(gps.device) - 1] = '\0'; - if (gps.enable) { + strncpy(g.device, argv[0], sizeof(g.device)); + g.device[sizeof(g.device) - 1] = '\0'; + g.gps_type = GPS_TYPE_SERIAL; + if (g.enable) { osmo_gps_close(); if (osmo_gps_open()) { vty_out(vty, "Failed to open GPS device!%s", @@ -901,21 +904,19 @@ DEFUN(cfg_gps_device, cfg_gps_device_cmd, "gps device DEVICE", return CMD_SUCCESS; } -#endif -#ifndef _USE_GPSD DEFUN(cfg_gps_baud, cfg_gps_baud_cmd, "gps baudrate " "(default|4800|""9600|19200|38400|57600|115200)", "GPS receiver\nSelect baud rate\nDefault, don't modify\n\n\n\n\n\n") { if (argv[0][0] == 'd') - gps.baud = 0; + g.baud = 0; else - gps.baud = atoi(argv[0]); - if (gps.enable) { + g.baud = atoi(argv[0]); + if (g.enable) { osmo_gps_close(); if (osmo_gps_open()) { - gps.enable = 0; + g.enable = 0; vty_out(vty, "Failed to open GPS device!%s", VTY_NEWLINE); return CMD_WARNING; @@ -924,7 +925,6 @@ DEFUN(cfg_gps_baud, cfg_gps_baud_cmd, "gps baudrate " return CMD_SUCCESS; } -#endif /* per MS config */ DEFUN(cfg_ms, cfg_ms_cmd, "ms MS_NAME", @@ -1204,17 +1204,16 @@ static int config_write(struct vty *vty) { struct osmocom_ms *ms; -#ifdef _USE_GPSD - vty_out(vty, "gpsd host %s%s", gps.gpsd_host, VTY_NEWLINE); - vty_out(vty, "gpsd port %s%s", gps.gpsd_port, VTY_NEWLINE); -#else - vty_out(vty, "gps device %s%s", gps.device, VTY_NEWLINE); - if (gps.baud) - vty_out(vty, "gps baudrate %d%s", gps.baud, VTY_NEWLINE); +#ifdef _HAVE_GPSD + vty_out(vty, "gpsd host %s%s", g.gpsd_host, VTY_NEWLINE); + vty_out(vty, "gpsd port %s%s", g.gpsd_port, VTY_NEWLINE); +#endif + vty_out(vty, "gps device %s%s", g.device, VTY_NEWLINE); + if (g.baud) + vty_out(vty, "gps baudrate %d%s", g.baud, VTY_NEWLINE); else vty_out(vty, "gps baudrate default%s", VTY_NEWLINE); -#endif - vty_out(vty, "%sgps enable%s", (gps.enable) ? "" : "no ", VTY_NEWLINE); + vty_out(vty, "%sgps enable%s", (g.enable) ? "" : "no ", VTY_NEWLINE); vty_out(vty, "!%s", VTY_NEWLINE); llist_for_each_entry(ms, &ms_list, entity) @@ -2305,12 +2304,11 @@ int ms_vty_init(void) install_element(ENABLE_NODE, &call_retr_cmd); install_element(ENABLE_NODE, &call_dtmf_cmd); -#ifdef _USE_GPSD +#ifdef _HAVE_GPSD install_element(CONFIG_NODE, &cfg_gps_host_cmd); -#else +#endif install_element(CONFIG_NODE, &cfg_gps_device_cmd); install_element(CONFIG_NODE, &cfg_gps_baud_cmd); -#endif install_element(CONFIG_NODE, &cfg_gps_enable_cmd); install_element(CONFIG_NODE, &cfg_no_gps_enable_cmd); -- 1.7.4 --------------020806060709070700080703-- From dario.lombardo at libero.it Thu Feb 24 09:16:33 2011 From: dario.lombardo at libero.it (Dario Lombardo) Date: Thu, 24 Feb 2011 10:16:33 +0100 Subject: [PATCH 1/2] Added cmd-line selection of gps device. Message-ID: --- src/host/layer23/configure.ac | 3 +- src/host/layer23/include/osmocom/bb/common/gps.h | 15 ++- src/host/layer23/src/common/gps.c | 128 ++++++++++++++-------- src/host/layer23/src/misc/app_cell_log.c | 70 +++++++----- src/host/layer23/src/misc/cell_log.c | 28 +++--- src/host/layer23/src/mobile/vty_interface.c | 72 ++++++------ 6 files changed, 186 insertions(+), 130 deletions(-) diff --git a/src/host/layer23/configure.ac b/src/host/layer23/configure.ac index e1c718e..c797e29 100644 --- a/src/host/layer23/configure.ac +++ b/src/host/layer23/configure.ac @@ -15,7 +15,8 @@ AC_PROG_RANLIB dnl checks for libraries PKG_CHECK_MODULES(LIBOSMOCORE, libosmocore) PKG_CHECK_MODULES(LIBOSMOVTY, libosmovty) -AC_CHECK_LIB(gps, gps_open, CFLAGS+=" -D_USE_GPSD" LDFLAGS+=" -lgps",,) +AC_CHECK_LIB(gps, gps_open, CFLAGS+=" -D_HAVE_GPSD" LDFLAGS+=" -lgps",,) +AC_CHECK_LIB(gps, gps_stream, CFLAGS+=" -D_HAVE_GPSD_V3",,) dnl checks for header files AC_HEADER_STDC diff --git a/src/host/layer23/include/osmocom/bb/common/gps.h b/src/host/layer23/include/osmocom/bb/common/gps.h index b7500db..58c0c53 100644 --- a/src/host/layer23/include/osmocom/bb/common/gps.h +++ b/src/host/layer23/include/osmocom/bb/common/gps.h @@ -19,17 +19,24 @@ * */ +enum { + GPS_TYPE_UNDEF, + GPS_TYPE_GPSD, + GPS_TYPE_SERIAL +}; + struct osmo_gps { /* GPS device */ uint8_t enable; + uint8_t gps_type; -#ifdef _USE_GPSD +#ifdef _HAVE_GPSD char gpsd_host[32]; char gpsd_port[6]; -#else +#endif + char device[32]; uint32_t baud; -#endif /* current data */ uint8_t valid; /* we have a fix */ @@ -37,7 +44,7 @@ struct osmo_gps { double latitude, longitude; }; -extern struct osmo_gps gps; +extern struct osmo_gps g; int osmo_gps_open(void); void osmo_gps_close(void); diff --git a/src/host/layer23/src/common/gps.c b/src/host/layer23/src/common/gps.c index 55dd239..f858270 100644 --- a/src/host/layer23/src/common/gps.c +++ b/src/host/layer23/src/common/gps.c @@ -26,8 +26,9 @@ #include #include #include +#include -#ifdef _USE_GPSD +#ifdef _HAVE_GPSD #include #endif @@ -37,15 +38,15 @@ #include #include -struct osmo_gps gps = { +struct osmo_gps g = { 0, -#ifdef _USE_GPSD + GPS_TYPE_UNDEF, +#ifdef _HAVE_GPSD "localhost", "2947", -#else +#endif "/dev/ttyACM0", 0, -#endif 0, 0, 0,0 @@ -53,16 +54,16 @@ struct osmo_gps gps = { static struct bsc_fd gps_bfd; -#ifdef _USE_GPSD +#ifdef _HAVE_GPSD static struct gps_data_t* gdata; -int osmo_gps_cb(struct bsc_fd *bfd, unsigned int what) +int osmo_gpsd_cb(struct bsc_fd *bfd, unsigned int what) { struct tm *tm; unsigned diff = 0; - gps.valid = 0; + g.valid = 0; /* gps is offline */ if (gdata->online) @@ -78,21 +79,21 @@ int osmo_gps_cb(struct bsc_fd *bfd, unsigned int what) /* data are valid */ if (gdata->set & LATLON_SET) { - gps.valid = 1; - gps.gmt = gdata->fix.time; - tm = localtime(&gps.gmt); - diff = time(NULL) - gps.gmt; - gps.latitude = gdata->fix.latitude; - gps.longitude = gdata->fix.longitude; + g.valid = 1; + g.gmt = gdata->fix.time; + tm = localtime(&g.gmt); + diff = time(NULL) - g.gmt; + g.latitude = gdata->fix.latitude; + g.longitude = gdata->fix.longitude; LOGP(DGPS, LOGL_INFO, " time=%02d:%02d:%02d %04d-%02d-%02d, " "diff-to-host=%d, latitude=%do%.4f, longitude=%do%.4f\n", tm->tm_hour, tm->tm_min, tm->tm_sec, tm->tm_year + 1900, tm->tm_mday, tm->tm_mon + 1, diff, - (int)gps.latitude, - (gps.latitude - ((int)gps.latitude)) * 60.0, - (int)gps.longitude, - (gps.longitude - ((int)gps.longitude)) * 60.0); + (int)g.latitude, + (g.latitude - ((int)g.latitude)) * 60.0, + (int)g.longitude, + (g.longitude - ((int)g.longitude)) * 60.0); } return 0; @@ -102,15 +103,15 @@ gps_not_ready: return -1; } -int osmo_gps_open(void) +int osmo_gpsd_open(void) { - LOGP(DGPS, LOGL_INFO, "Connecting to gpsd at '%s:%s'\n", gps.gpsd_host, gps.gpsd_port); + LOGP(DGPS, LOGL_INFO, "Connecting to gpsd at '%s:%s'\n", g.gpsd_host, g.gpsd_port); gps_bfd.data = NULL; gps_bfd.when = BSC_FD_READ; - gps_bfd.cb = osmo_gps_cb; + gps_bfd.cb = osmo_gpsd_cb; - gdata = gps_open(gps.gpsd_host, gps.gpsd_port); + gdata = gps_open(g.gpsd_host, g.gpsd_port); if (gdata == NULL) { LOGP(DGPS, LOGL_ERROR, "Can't connect to gpsd\n"); return -1; @@ -119,6 +120,18 @@ int osmo_gps_open(void) if (gps_bfd.fd < 0) return gps_bfd.fd; +#ifdef _HAVE_GPSD_V3 + if (gps_stream(gdata, WATCH_ENABLE, NULL) == -1) { + LOGP(DGPS, LOGL_ERROR, "Error in gps_stream()\n"); + return -1; + } +#else + if (gps_query(gdata, "o")) { + LOGP(DGPS, LOGL_ERROR, "Error in gps_query()\n"); + return -1; + } +#endif + if (gps_stream(gdata, WATCH_ENABLE, NULL) == -1) { LOGP(DGPS, LOGL_ERROR, "Error in gps_stream()\n"); return -1; @@ -129,7 +142,7 @@ int osmo_gps_open(void) return 0; } -void osmo_gps_close(void) +void osmo_gpsd_close(void) { if (gps_bfd.fd <= 0) return; @@ -142,11 +155,11 @@ void osmo_gps_close(void) gps_bfd.fd = -1; /* -1 or 0 indicates: 'close' */ } -#else +#endif static struct termios gps_termios, gps_old_termios; -static int osmo_gps_line(char *line) +static int osmo_serialgps_line(char *line) { time_t gps_now, host_now; struct tm *tm; @@ -164,10 +177,10 @@ static int osmo_gps_line(char *line) /* valid position */ if (line[36] != 'A') { LOGP(DGPS, LOGL_INFO, "%s (invalid)\n", line); - gps.valid = 0; + g.valid = 0; return 0; } - gps.valid = 1; + g.valid = 1; /* time stamp */ gps_now = line[30] - '0'; @@ -185,7 +198,7 @@ static int osmo_gps_line(char *line) diff -= 86400; /* apply the "date" part to the GPS time */ gps_now = host_now - diff; - gps.gmt = gps_now; + g.gmt = gps_now; tm = localtime(&gps_now); /* position */ @@ -199,7 +212,7 @@ static int osmo_gps_line(char *line) latitude += (double)(line[8] - '0') / 600000.0; if (line[10] == 'S') latitude = 0.0 - latitude; - gps.latitude = latitude; + g.latitude = latitude; longitude = (double)(line[12] - '0') * 100.0; longitude += (double)(line[13] - '0') * 10.0; longitude += (double)(line[14] - '0'); @@ -211,17 +224,17 @@ static int osmo_gps_line(char *line) longitude += (double)(line[21] - '0') / 600000.0; if (line[23] == 'W') longitude = 360.0 - longitude; - gps.longitude = longitude; + g.longitude = longitude; LOGP(DGPS, LOGL_DEBUG, "%s\n", line); LOGP(DGPS, LOGL_INFO, " time=%02d:%02d:%02d %04d-%02d-%02d, " "diff-to-host=%d, latitude=%do%.4f, longitude=%do%.4f\n", tm->tm_hour, tm->tm_min, tm->tm_sec, tm->tm_year + 1900, tm->tm_mday, tm->tm_mon + 1, diff, - (int)gps.latitude, - (gps.latitude - ((int)gps.latitude)) * 60.0, - (int)gps.longitude, - (gps.longitude - ((int)gps.longitude)) * 60.0); + (int)g.latitude, + (g.latitude - ((int)g.latitude)) * 60.0, + (int)g.longitude, + (g.longitude - ((int)g.longitude)) * 60.0); return 0; } @@ -241,7 +254,7 @@ static int nmea_checksum(char *line) return (strtoul(line+1, NULL, 16) == checksum); } -int osmo_gps_cb(struct bsc_fd *bfd, unsigned int what) +int osmo_serialgps_cb(struct bsc_fd *bfd, unsigned int what) { char buff[128]; static char line[128]; @@ -265,7 +278,7 @@ int osmo_gps_cb(struct bsc_fd *bfd, unsigned int what) if (!nmea_checksum(line)) fprintf(stderr, "NMEA checksum error\n"); else - osmo_gps_line(line); + osmo_serialgps_line(line); continue; } line[lpos++] = buff[i++]; @@ -276,23 +289,23 @@ int osmo_gps_cb(struct bsc_fd *bfd, unsigned int what) return 0; } -int osmo_gps_open(void) +int osmo_serialgps_open(void) { int baud = 0; if (gps_bfd.fd > 0) return 0; - LOGP(DGPS, LOGL_INFO, "Open GPS device '%s'\n", gps.device); + LOGP(DGPS, LOGL_INFO, "Open GPS device '%s'\n", g.device); gps_bfd.data = NULL; gps_bfd.when = BSC_FD_READ; - gps_bfd.cb = osmo_gps_cb; - gps_bfd.fd = open(gps.device, O_RDONLY); + gps_bfd.cb = osmo_serialgps_cb; + gps_bfd.fd = open(g.device, O_RDONLY); if (gps_bfd.fd < 0) return gps_bfd.fd; - switch (gps.baud) { + switch (g.baud) { case 4800: baud = B4800; break; case 9600: @@ -327,7 +340,7 @@ int osmo_gps_open(void) return 0; } -void osmo_gps_close(void) +void osmo_serialgps_close(void) { if (gps_bfd.fd <= 0) return; @@ -343,11 +356,38 @@ void osmo_gps_close(void) gps_bfd.fd = -1; /* -1 or 0 indicates: 'close' */ } -#endif - void osmo_gps_init(void) { memset(&gps_bfd, 0, sizeof(gps_bfd)); } +int osmo_gps_open(void) +{ + switch (g.gps_type) { +#ifdef _HAVE_GPSD + case GPS_TYPE_GPSD: + return osmo_gpsd_open(); +#endif + case GPS_TYPE_SERIAL: + return osmo_serialgps_open(); + + default: + return 0; + } +} + +void osmo_gps_close(void) +{ + switch (g.gps_type) { +#ifdef _HAVE_GPSD + case GPS_TYPE_GPSD: + return osmo_gpsd_close(); +#endif + case GPS_TYPE_SERIAL: + return osmo_serialgps_close(); + + default: + return; + } +} diff --git a/src/host/layer23/src/misc/app_cell_log.c b/src/host/layer23/src/misc/app_cell_log.c index 7a2c67a..7030abf 100644 --- a/src/host/layer23/src/misc/app_cell_log.c +++ b/src/host/layer23/src/misc/app_cell_log.c @@ -92,13 +92,12 @@ static int l23_getopt_options(struct option **options) {"logfile", 1, 0, 'l'}, {"rach", 1, 0, 'r'}, {"no-rach", 1, 0, 'n'}, -#ifdef _USE_GPSD +#ifdef _HAVE_GPSD {"gpsd-host", 1, 0, 'g'}, - {"gpsd-port", 1, 0, 'p'} -#else + {"gpsd-port", 1, 0, 'p'}, +#endif {"gps", 1, 0, 'g'}, {"baud", 1, 0, 'b'} -#endif }; *options = opts; @@ -109,15 +108,15 @@ static int l23_cfg_print_help() { printf("\nApplication specific\n"); printf(" -l --logfile LOGFILE Logfile for the cell log.\n"); - printf(" -r --rach RACH Nr. of RACH bursts to send.\n"); - printf(" -n --no-rach Send no rach bursts.\n"); -#ifdef _USE_GPSD + printf(" -r --rach RACH Nr. of RACH bursts to send.\n"); + printf(" -n --no-rach Send no rach bursts.\n"); +#ifdef _HAVE_GPSD printf(" -g --gpsd-host HOST 127.0.0.1. gpsd host.\n"); - printf(" -p --port PORT 2947. gpsd port\n"); -#else - printf(" -g --gps DEVICE /dev/ttyACM0. GPS device.\n"); - printf(" -b --baud BAUDRAT The baud rate of the GPS device\n"); + printf(" -p --port PORT 2947. gpsd port\n"); #endif + printf(" -f --gps DEVICE /dev/ttyACM0. GPS serial device.\n"); + printf(" -b --baud BAUDRAT The baud rate of the GPS device\n"); + return 0; } @@ -133,42 +132,53 @@ static int l23_cfg_handle(int c, const char *optarg) case 'n': RACH_MAX = 0; break; -#ifdef _USE_GPSD +#ifdef _HAVE_GPSD case 'g': - snprintf(gps.gpsd_host, ARRAY_SIZE(gps.gpsd_host), "%s", optarg); + snprintf(g.gpsd_host, ARRAY_SIZE(g.gpsd_host), "%s", optarg); /* force string terminator */ - gps.gpsd_host[ARRAY_SIZE(gps.gpsd_host) - 1] = '\0'; - LOGP(DGPS, LOGL_INFO, "Using gpsd host %s\n", gps.gpsd_host); + g.gpsd_host[ARRAY_SIZE(g.gpsd_host) - 1] = '\0'; + if (g.gps_type != GPS_TYPE_UNDEF) + goto cmd_line_error; + g.gps_type = GPS_TYPE_GPSD; + LOGP(DGPS, LOGL_INFO, "Using gpsd host %s\n", g.gpsd_host); break; case 'p': - snprintf(gps.gpsd_port, ARRAY_SIZE(gps.gpsd_port), "%s", optarg); + snprintf(g.gpsd_port, ARRAY_SIZE(g.gpsd_port), "%s", optarg); /* force string terminator */ - gps.gpsd_port[ARRAY_SIZE(gps.gpsd_port) - 1] = '\0'; - LOGP(DGPS, LOGL_INFO, "Using gpsd port %s\n", gps.gpsd_port); + g.gpsd_port[ARRAY_SIZE(g.gpsd_port) - 1] = '\0'; + g.gps_type = GPS_TYPE_GPSD; + LOGP(DGPS, LOGL_INFO, "Using gpsd port %s\n", g.gpsd_port); break; -#else - case 'g': - snprintf(gps.device, ARRAY_SIZE(gps.device), "%s", optarg); +#endif + case 'f': + snprintf(g.device, ARRAY_SIZE(g.device), "%s", optarg); /* force string terminator */ - gps.device[ARRAY_SIZE(gps.device) - 1] = '\0'; - LOGP(DGPS, LOGL_INFO, "Using GPS device %s\n", gps.device); + g.device[ARRAY_SIZE(g.device) - 1] = '\0'; + if (g.gps_type != GPS_TYPE_UNDEF) + goto cmd_line_error; + g.gps_type = GPS_TYPE_SERIAL; + LOGP(DGPS, LOGL_INFO, "Using GPS serial device %s\n", g.device); break; case 'b': - gps.baud = atoi(optarg); - LOGP(DGPS, LOGL_INFO, "Setting GPS baudrate to %u\n", gps.baud); + g.baud = atoi(optarg); + g.gps_type = GPS_TYPE_SERIAL; + LOGP(DGPS, LOGL_INFO, "Setting GPS baudrate to %u\n", g.baud); break; -#endif } return 0; + +cmd_line_error: + printf("\nYou can't specify both gpsd and serial gps!!\n\n"); + exit(1); } static struct l23_app_info info = { .copyright = "Copyright (C) 2010 Andreas Eversberg\n", -#ifdef _USE_GPSD - .getopt_string = "l:r:ng:p:", -#else - .getopt_string = "l:r:ng:b:", + .getopt_string = +#ifdef _HAVE_GPSD + "g:p:" #endif + "l:r:nf:b:", .cfg_supported = l23_cfg_supported, .cfg_getopt_opt = l23_getopt_options, .cfg_handle_opt = l23_cfg_handle, diff --git a/src/host/layer23/src/misc/cell_log.c b/src/host/layer23/src/misc/cell_log.c index a0f9769..7de2c40 100644 --- a/src/host/layer23/src/misc/cell_log.c +++ b/src/host/layer23/src/misc/cell_log.c @@ -119,17 +119,17 @@ static void start_pm(void); static void log_gps(void) { - if (!gps.enable || !gps.valid) + if (!g.enable || !g.valid) return; - LOGFILE("position %.8f %.8f\n", gps.longitude, gps.latitude); + LOGFILE("position %.8f %.8f\n", g.longitude, g.latitude); } static void log_time(void) { time_t now; - if (gps.enable && gps.valid) - now = gps.gmt; + if (g.enable && g.valid) + now = g.gmt; else time(&now); LOGFILE("time %lu\n", now); @@ -317,15 +317,15 @@ static void start_sync(void) } } /* if GPS becomes valid, like after exitting a tunnel */ - if (!pm_gps_valid && gps.valid) { + if (!pm_gps_valid && g.valid) { pm_gps_valid = 1; - geo2space(&pm_gps_x, &pm_gps_y, &pm_gps_z, gps.longitude, - gps.latitude); + geo2space(&pm_gps_x, &pm_gps_y, &pm_gps_z, g.longitude, + g.latitude); } - if (pm_gps_valid && gps.valid) { + if (pm_gps_valid && g.valid) { double x, y, z; - geo2space(&x, &y, &z, gps.longitude, gps.latitude); + geo2space(&x, &y, &z, g.longitude, g.latitude); dist = distinspace(pm_gps_x, pm_gps_y, pm_gps_z, x, y, z); sprintf(dist_str, " dist %d", (int)dist); } @@ -357,10 +357,10 @@ static void start_pm(void) if (from == 0 && to == 0) { LOGP(DSUM, LOGL_INFO, "Measurement done\n"); - pm_gps_valid = gps.enable && gps.valid; + pm_gps_valid = g.enable && g.valid; if (pm_gps_valid) geo2space(&pm_gps_x, &pm_gps_y, &pm_gps_z, - gps.longitude, gps.latitude); + g.longitude, g.latitude); log_pm(); start_sync(); return; @@ -786,10 +786,10 @@ int scan_init(struct osmocom_ms *_ms) register_signal_handler(SS_L1CTL, &signal_cb, NULL); memset(&timer, 0, sizeof(timer)); osmol2_register_handler(ms, &rcv_rsl); - gps.enable = 1; + g.enable = 1; osmo_gps_init(); if (osmo_gps_open()) - gps.enable = 0; + g.enable = 0; if (!strcmp(logname, "-")) logfp = stdout; @@ -808,7 +808,7 @@ int scan_init(struct osmocom_ms *_ms) int scan_exit(void) { LOGP(DSUM, LOGL_INFO, "Scanner exit\n"); - if (gps.valid) + if (g.valid) osmo_gps_close(); if (logfp) fclose(logfp); diff --git a/src/host/layer23/src/mobile/vty_interface.c b/src/host/layer23/src/mobile/vty_interface.c index 7888f01..b93248d 100644 --- a/src/host/layer23/src/mobile/vty_interface.c +++ b/src/host/layer23/src/mobile/vty_interface.c @@ -836,11 +836,11 @@ DEFUN(cfg_gps_enable, cfg_gps_enable_cmd, "gps enable", "GPS receiver") { if (osmo_gps_open()) { - gps.enable = 1; + g.enable = 1; vty_out(vty, "Failed to open GPS device!%s", VTY_NEWLINE); return CMD_WARNING; } - gps.enable = 1; + g.enable = 1; return CMD_SUCCESS; } @@ -848,31 +848,32 @@ DEFUN(cfg_gps_enable, cfg_gps_enable_cmd, "gps enable", DEFUN(cfg_no_gps_enable, cfg_no_gps_enable_cmd, "no gps enable", NO_STR "Disable GPS receiver") { - if (gps.enable) + if (g.enable) osmo_gps_close(); - gps.enable = 0; + g.enable = 0; return CMD_SUCCESS; } -#ifdef _USE_GPSD +#ifdef _HAVE_GPSD DEFUN(cfg_gps_host, cfg_gps_host_cmd, "gps host HOST:PORT", "GPS receiver\nSelect gpsd host and port\n" "IP and port (optional) of the host running gpsd") { char* colon = strstr(argv[0], ":"); if (colon != NULL) { - memcpy(gps.gpsd_host, argv[0], colon - argv[0] - 1); - gps.gpsd_host[colon - argv[0]] = '\0'; - memcpy(gps.gpsd_port, colon, strlen(colon)); - gps.gpsd_port[strlen(colon)] = '\0'; + memcpy(g.gpsd_host, argv[0], colon - argv[0] - 1); + g.gpsd_host[colon - argv[0]] = '\0'; + memcpy(g.gpsd_port, colon, strlen(colon)); + g.gpsd_port[strlen(colon)] = '\0'; } else { - snprintf(gps.gpsd_host, ARRAY_SIZE(gps.gpsd_host), "%s", argv[0]); - gps.gpsd_host[ARRAY_SIZE(gps.gpsd_host) - 1] = '\0'; - snprintf(gps.gpsd_port, ARRAY_SIZE(gps.gpsd_port), "2947"); - gps.gpsd_port[ARRAY_SIZE(gps.gpsd_port) - 1] = '\0'; + snprintf(g.gpsd_host, ARRAY_SIZE(g.gpsd_host), "%s", argv[0]); + g.gpsd_host[ARRAY_SIZE(g.gpsd_host) - 1] = '\0'; + snprintf(g.gpsd_port, ARRAY_SIZE(g.gpsd_port), "2947"); + g.gpsd_port[ARRAY_SIZE(g.gpsd_port) - 1] = '\0'; } - if (gps.enable) { + g.gps_type = GPS_TYPE_GPSD; + if (g.enable) { osmo_gps_close(); if (osmo_gps_open()) { vty_out(vty, "Failed to connect to gpsd host!%s", @@ -883,14 +884,16 @@ DEFUN(cfg_gps_host, cfg_gps_host_cmd, "gps host HOST:PORT", return CMD_SUCCESS; } -#else +#endif + DEFUN(cfg_gps_device, cfg_gps_device_cmd, "gps device DEVICE", "GPS receiver\nSelect serial device\n" "Full path of serial device including /dev/") { - strncpy(gps.device, argv[0], sizeof(gps.device)); - gps.device[sizeof(gps.device) - 1] = '\0'; - if (gps.enable) { + strncpy(g.device, argv[0], sizeof(g.device)); + g.device[sizeof(g.device) - 1] = '\0'; + g.gps_type = GPS_TYPE_SERIAL; + if (g.enable) { osmo_gps_close(); if (osmo_gps_open()) { vty_out(vty, "Failed to open GPS device!%s", @@ -901,21 +904,19 @@ DEFUN(cfg_gps_device, cfg_gps_device_cmd, "gps device DEVICE", return CMD_SUCCESS; } -#endif -#ifndef _USE_GPSD DEFUN(cfg_gps_baud, cfg_gps_baud_cmd, "gps baudrate " "(default|4800|""9600|19200|38400|57600|115200)", "GPS receiver\nSelect baud rate\nDefault, don't modify\n\n\n\n\n\n") { if (argv[0][0] == 'd') - gps.baud = 0; + g.baud = 0; else - gps.baud = atoi(argv[0]); - if (gps.enable) { + g.baud = atoi(argv[0]); + if (g.enable) { osmo_gps_close(); if (osmo_gps_open()) { - gps.enable = 0; + g.enable = 0; vty_out(vty, "Failed to open GPS device!%s", VTY_NEWLINE); return CMD_WARNING; @@ -924,7 +925,6 @@ DEFUN(cfg_gps_baud, cfg_gps_baud_cmd, "gps baudrate " return CMD_SUCCESS; } -#endif /* per MS config */ DEFUN(cfg_ms, cfg_ms_cmd, "ms MS_NAME", @@ -1204,17 +1204,16 @@ static int config_write(struct vty *vty) { struct osmocom_ms *ms; -#ifdef _USE_GPSD - vty_out(vty, "gpsd host %s%s", gps.gpsd_host, VTY_NEWLINE); - vty_out(vty, "gpsd port %s%s", gps.gpsd_port, VTY_NEWLINE); -#else - vty_out(vty, "gps device %s%s", gps.device, VTY_NEWLINE); - if (gps.baud) - vty_out(vty, "gps baudrate %d%s", gps.baud, VTY_NEWLINE); +#ifdef _HAVE_GPSD + vty_out(vty, "gpsd host %s%s", g.gpsd_host, VTY_NEWLINE); + vty_out(vty, "gpsd port %s%s", g.gpsd_port, VTY_NEWLINE); +#endif + vty_out(vty, "gps device %s%s", g.device, VTY_NEWLINE); + if (g.baud) + vty_out(vty, "gps baudrate %d%s", g.baud, VTY_NEWLINE); else vty_out(vty, "gps baudrate default%s", VTY_NEWLINE); -#endif - vty_out(vty, "%sgps enable%s", (gps.enable) ? "" : "no ", VTY_NEWLINE); + vty_out(vty, "%sgps enable%s", (g.enable) ? "" : "no ", VTY_NEWLINE); vty_out(vty, "!%s", VTY_NEWLINE); llist_for_each_entry(ms, &ms_list, entity) @@ -2305,12 +2304,11 @@ int ms_vty_init(void) install_element(ENABLE_NODE, &call_retr_cmd); install_element(ENABLE_NODE, &call_dtmf_cmd); -#ifdef _USE_GPSD +#ifdef _HAVE_GPSD install_element(CONFIG_NODE, &cfg_gps_host_cmd); -#else +#endif install_element(CONFIG_NODE, &cfg_gps_device_cmd); install_element(CONFIG_NODE, &cfg_gps_baud_cmd); -#endif install_element(CONFIG_NODE, &cfg_gps_enable_cmd); install_element(CONFIG_NODE, &cfg_no_gps_enable_cmd); -- 1.7.4 From Andreas.Eversberg at versatel.de Tue Feb 22 09:31:35 2011 From: Andreas.Eversberg at versatel.de (Andreas.Eversberg) Date: Tue, 22 Feb 2011 10:31:35 +0100 Subject: AW: Fwd: gpsd support Message-ID: > I have written the new code that supports gps selection at runtime > through cmdline switches. Send me any comment you have :). looks good to me. if you have access to git, just commit it, else send me all patches (or combined as one patch) and i will commit them. From mailman-bounces at lists.osmocom.org Fri Feb 18 08:00:03 2011 From: mailman-bounces at lists.osmocom.org (mailman-bounces at lists.osmocom.org) Date: Fri, 18 Feb 2011 09:00:03 +0100 Subject: baseband-devel unsubscribe notification Message-ID: arslangali at inbox.ru has been removed from baseband-devel. From alhakeem at gmail.com Fri Feb 18 19:52:29 2011 From: alhakeem at gmail.com (Abdul Hakeem) Date: Fri, 18 Feb 2011 19:52:29 -0000 Subject: Soft GSM client Message-ID: Hello, I was wondering if there is a soft GSM client....the sort you could run like a sip client on your laptop to connect to the GSM/UMTS network just like UMA/GAN phones do via Up interface. Regards, Abdul Hakeem From drasko.draskovic at gmail.com Fri Feb 18 20:25:28 2011 From: drasko.draskovic at gmail.com (Drasko DRASKOVIC) Date: Fri, 18 Feb 2011 21:25:28 +0100 Subject: Soft GSM client In-Reply-To: References: Message-ID: On Fri, Feb 18, 2011 at 8:52 PM, Abdul Hakeem wrote: > Hello, > I was wondering if there is a soft GSM client....the sort you could run like a sip client > on your laptop to connect to the GSM/UMTS network just like UMA/GAN phones do via Up > interface. What would be your RF interface in that case ? Maybe phone ? From alhakeem100 at hotmail.com Fri Feb 18 20:57:32 2011 From: alhakeem100 at hotmail.com (Abdul Hakeem) Date: Fri, 18 Feb 2011 20:57:32 +0000 Subject: Soft GSM client In-Reply-To: References: Message-ID: GSM/UMTS phones with UMA client can use WiFi to communicate with the MSC/HLR elements in the network. The client just needs an IP connectivity to the GAN controller. So the requirement for the traditional gsm Um interface is void in this scenario. Cheers, AH -----Original Message----- From: Drasko DRASKOVIC [mailto:drasko.draskovic at gmail.com] Sent: Friday, February 18, 2011 8:25 PM To: alhakeem at ipextelecom.net Cc: Abdul Hakeem; baseband-devel at lists.osmocom.org Subject: Re: Soft GSM client On Fri, Feb 18, 2011 at 8:52 PM, Abdul Hakeem wrote: > Hello, > I was wondering if there is a soft GSM client....the sort you could > run like a sip client on your laptop to connect to the GSM/UMTS > network just like UMA/GAN phones do via Up interface. What would be your RF interface in that case ? Maybe phone ? From alhakeem at gmail.com Fri Feb 18 21:06:20 2011 From: alhakeem at gmail.com (Abdul Hakeem) Date: Fri, 18 Feb 2011 21:06:20 -0000 Subject: Soft GSM client In-Reply-To: References: Message-ID: GSM/UMTS phones with UMA client can use WiFi to communicate with the MSC/HLR elements in the network. The client just needs an IP connectivity to the GAN controller. So the requirement for the traditional gsm Um interface is void in this scenario. Cheers, AH -----Original Message----- From: Drasko DRASKOVIC [mailto:drasko.draskovic at gmail.com] Sent: Friday, February 18, 2011 8:25 PM To: alhakeem at ipextelecom.net Cc: Abdul Hakeem; baseband-devel at lists.osmocom.org Subject: Re: Soft GSM client On Fri, Feb 18, 2011 at 8:52 PM, Abdul Hakeem wrote: > Hello, > I was wondering if there is a soft GSM client....the sort you could > run like a sip client on your laptop to connect to the GSM/UMTS > network just like UMA/GAN phones do via Up interface. What would be your RF interface in that case ? Maybe phone ? From holger at freyther.de Fri Feb 18 20:55:37 2011 From: holger at freyther.de (Holger Hans Peter Freyther) Date: Fri, 18 Feb 2011 21:55:37 +0100 Subject: Soft GSM client In-Reply-To: References: Message-ID: <4D5EDCC9.9050907@freyther.de> On 02/18/2011 08:52 PM, Abdul Hakeem wrote: > Hello, > I was wondering if there is a soft GSM client....the sort you could run like a sip client > on your laptop to connect to the GSM/UMTS network just like UMA/GAN phones do via Up > interface. Hi, I think we have various possibilities: - Andreas's linux call router supports using a osmocom phone as uplink to the real world... pretty cool stuff. - I have a test phone in progress that connects directly to a MSC that is capable of doing LU, placing calls (work in progress), e.g. with the HTML5 tags one could even do audio recording and playback... - We will have a way to directly connect OsmocomBB to OpenBSC this year.... removing the RF and BTS from the picture. holger From alhakeem at gmail.com Fri Feb 18 21:06:20 2011 From: alhakeem at gmail.com (Abdul Hakeem) Date: Fri, 18 Feb 2011 21:06:20 -0000 Subject: Soft GSM client In-Reply-To: <4D5EDCC9.9050907@freyther.de> References: <4D5EDCC9.9050907@freyther.de> Message-ID: Holger, You hit the nail right on the head ! Is there any way you have this test phone available ? It's very frustrating doing anything useful with the UMA phones out there, this test phone you are working on is it software based or a modified hardware ? Regards, Abdul Hakeem -----Original Message----- From: baseband-devel-bounces at lists.osmocom.org [mailto:baseband-devel-bounces at lists.osmocom.org] On Behalf Of Holger Hans Peter Freyther Sent: Friday, February 18, 2011 8:56 PM To: baseband-devel at lists.osmocom.org Subject: Re: Soft GSM client On 02/18/2011 08:52 PM, Abdul Hakeem wrote: > Hello, > I was wondering if there is a soft GSM client....the sort you could > run like a sip client on your laptop to connect to the GSM/UMTS > network just like UMA/GAN phones do via Up interface. Hi, I think we have various possibilities: - Andreas's linux call router supports using a osmocom phone as uplink to the real world... pretty cool stuff. - I have a test phone in progress that connects directly to a MSC that is capable of doing LU, placing calls (work in progress), e.g. with the HTML5 tags one could even do audio recording and playback... - We will have a way to directly connect OsmocomBB to OpenBSC this year.... removing the RF and BTS from the picture. holger From holger at freyther.de Fri Feb 18 21:14:42 2011 From: holger at freyther.de (Holger Hans Peter Freyther) Date: Fri, 18 Feb 2011 22:14:42 +0100 Subject: Soft GSM client In-Reply-To: References: <4D5EDCC9.9050907@freyther.de> Message-ID: <4D5EE142.8000008@freyther.de> On 02/18/2011 10:06 PM, Abdul Hakeem wrote: > Holger, > You hit the nail right on the head ! > Is there any way you have this test phone available ? > It's very frustrating doing anything useful with the UMA phones out there, this test phone > you are working on is it software based or a modified hardware ? It is software based, written in Smalltalk and runs as a webservice. You will need to have direct access to a MSC to make it useful. The code can be found here[1]. [1] http://cgit.osmocom.org/cgit/smalltalk From sweisman at pobox.com Sun Feb 20 07:07:23 2011 From: sweisman at pobox.com (Scott Weisman) Date: Sun, 20 Feb 2011 09:07:23 +0200 Subject: off-topic apologies - how to unlock sim (not phone) Message-ID: I apologize for this in advance. I figure the collective GSM knowledge here might be able to help me. I have a SIM card that can only be used on one phone. The phone itself is unlocked. But the SIM won't work on any other phone. Does anyone know anything about this or how to unlock a SIM to work on any phone? Yes, I have tried searching, but because PHONE unlocking is such a common theme, this just passes through the cracks. Thanks, Scott -------------- next part -------------- An HTML attachment was scrubbed... URL: From laforge at gnumonks.org Tue Feb 22 12:24:54 2011 From: laforge at gnumonks.org (Harald Welte) Date: Tue, 22 Feb 2011 07:24:54 -0500 Subject: off-topic apologies - how to unlock sim (not phone) In-Reply-To: References: Message-ID: <4D63AB16.9040307@gnumonks.org> On 02/20/2011 02:07 AM, Scott Weisman wrote: > I apologize for this in advance. I figure the collective GSM knowledge > here might be able to help me. Well, I think it is interesting from a 'scientific' point of view, i.e. understanding how such mechanism is implemented. > I have a SIM card that can only be used on one phone. The phone itself > is unlocked. But the SIM won't work on any other phone. Does anyone > know anything about this or how to unlock a SIM to work on any phone? I think the first step is to trace what is happening between phone and sim card, possibly by using osmocom simtrace. Once you have a trace, you can look at the messages and try to identify the mechanism the SIM uses to identify the phone. After that, you could possibly implement a small program for a proxy SIM like bladox or RebelSIM which patches the messages to make the SIM card happy. All in all not an easy undertaking, but it can definitely be solved. Regards, Harald From squalyl at gmail.com Tue Feb 22 14:35:13 2011 From: squalyl at gmail.com (=?UTF-8?Q?S=C3=A9bastien_Lorquet?=) Date: Tue, 22 Feb 2011 15:35:13 +0100 Subject: off-topic apologies - how to unlock sim (not phone) In-Reply-To: References: <4D63AB16.9040307@gnumonks.org> Message-ID: Hi, the phone does not seem to be involved in this topic. It's only about the SIM. And you can't flash a sim like a baseband. That would be too easy. Sebastien On Tue, Feb 22, 2011 at 3:28 PM, Marius Cirsta wrote: > A nicer fix would be to flash it with some open source firmware :). > That would be cool and I guess it's what this project is all about. > > On Tue, Feb 22, 2011 at 5:24 AM, Harald Welte > wrote: > > On 02/20/2011 02:07 AM, Scott Weisman wrote: > >> > >> I apologize for this in advance. I figure the collective GSM knowledge > >> here might be able to help me. > > > > Well, I think it is interesting from a 'scientific' point of view, i.e. > > understanding how such mechanism is implemented. > > > >> I have a SIM card that can only be used on one phone. The phone itself > is > >> unlocked. But the SIM won't work on any other phone. Does anyone know > >> anything about this or how to unlock a SIM to work on any phone? > > > > I think the first step is to trace what is happening between phone and > sim > > card, possibly by using osmocom simtrace. > > > > Once you have a trace, you can look at the messages and try to identify > the > > mechanism the SIM uses to identify the phone. After that, you could > > possibly implement a small program for a proxy SIM like bladox or > RebelSIM > > which patches the messages to make the SIM card happy. > > > > All in all not an easy undertaking, but it can definitely be solved. > > > > Regards, > > Harald > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jakob at weite-welt.com Sun Feb 20 17:33:58 2011 From: jakob at weite-welt.com (Leif Jakob) Date: Sun, 20 Feb 2011 18:33:58 +0100 Subject: success with Pirelli DP-L10 on live network - useful hints for newbies Message-ID: <20110220173358.GQ15313@aegir.asgard.sol> Hi, for anyone also playing with the Pirelli phone, I got mine running on a live network. Here's my recipe: - change header files for Pirelli (see wiki) - compile source - setup usb modprobe -v cp210x echo "0489 e003" > /sys/bus/usb-serial/drivers/cp210x/new_id - attach phone without battery on USB - from src run ./host/osmocon/osmocon -p /dev/ttyUSB0 -m romload ./target/firmware/board/pirelli_dpl10/layer1.highram.bin now the tricky part: sometimes the romloader succeeds when you insert the battery, but most times you have to power on the phone and then power off (now the bootloader uploads the .bin) - run mobile (you need to touch an empty osmocom.cfg) ./host/layer23/src/mobile/mobile -i 127.0.0.1 telnet localhost 4247 - play via telnet - you can't break anything now the real fun, enable transmitting - enable transmitter (don't forget to "make clean") in Makefile - select your local channel (I used an other phones cellid and looked up the channel) stick - use random IMEI (000.. didn't work on my network) imei-random 15 - use test sim (if you know your IMSI/KI - I could't get the SIM working) test-sim imsi 22801 ki comp128 If all works, you'll find in your logfile something like: TMSI 0x25f0ec42 (636546114) assigned if your keys are wrong, you'll see something like: gsm48_mm.c:1581 AUTHENTICATION REJECT I wasn't able to make any real calls from the mobile to any landline but at least signalling in the other direction worked: telnet showed: Incoming call (from +49711xxxxx) Have fun Leif From wsmd78 at gmail.com Tue Feb 22 09:09:50 2011 From: wsmd78 at gmail.com (shrek wu) Date: Tue, 22 Feb 2011 17:09:50 +0800 Subject: about voice In-Reply-To: References: Message-ID: hi all, About voice?I have one question. In the latest git code, when I use bb to call other phone, it will product a file voice.raw. How I can play the voice.raw? which kind of format? 16bit or 8 bit pcm?16khz and 8khz?LSE or MSE? In fact i used the cooledit to play it, both 16khz and 8khz, it has only noise. Other question, I want to input voice from pc that run BB, then the voice can be sent by C123. But I found the voice that be sent by C123 is C123 input voice. Can we realize the idea? Best Regards Shrek W -------------- next part -------------- An HTML attachment was scrubbed... URL: From 246tnt at gmail.com Tue Feb 22 11:02:19 2011 From: 246tnt at gmail.com (Sylvain Munaut) Date: Tue, 22 Feb 2011 12:02:19 +0100 Subject: about voice In-Reply-To: References: Message-ID: Hi, > About voice?I have one question. > In the latest git code, when I use bb to call other phone, it will product a > file voice.raw. > > How I can play the voice.raw? > which kind of format? 16bit or 8 bit pcm?16khz and 8khz?LSE or MSE? > In fact i used the cooledit to play it, both 16khz and 8khz, it has?only > noise. It's the internal, undocumented, calypso buffer format. I have the format details somewhere but not near me ... I (or most likey Jolly) will write a converter soon, it's work in progress. > Other question, I want to input voice from pc that run BB, then the?voice > can be sent by C123. > But I found the voice that be sent by C123 is C123 input voice. > Can we realize the idea? again, WIP ... just wait. Cheers, Sylvain From wsmd78 at gmail.com Fri Feb 25 08:51:50 2011 From: wsmd78 at gmail.com (shrek wu) Date: Fri, 25 Feb 2011 16:51:50 +0800 Subject: about voice In-Reply-To: References: Message-ID: hi Sylvain Thank you! where i can find some doc about the internal, undocumented, calypso buffer format? I want to join bb project. Hope me can do some work. I am linux bsp engineer. Regards Shrek W 2011/2/22 Sylvain Munaut <246tnt at gmail.com> > Hi, > > > About voice?I have one question. > > In the latest git code, when I use bb to call other phone, it will > product a > > file voice.raw. > > > > How I can play the voice.raw? > > which kind of format? 16bit or 8 bit pcm?16khz and 8khz?LSE or MSE? > > In fact i used the cooledit to play it, both 16khz and 8khz, it has only > > noise. > > It's the internal, undocumented, calypso buffer format. > > I have the format details somewhere but not near me ... I (or most > likey Jolly) will write a converter soon, it's work in progress. > > > > Other question, I want to input voice from pc that run BB, then the voice > > can be sent by C123. > > But I found the voice that be sent by C123 is C123 input voice. > > Can we realize the idea? > > again, WIP ... just wait. > > > Cheers, > > Sylvain > -------------- next part -------------- An HTML attachment was scrubbed... URL: From laforge at gnumonks.org Fri Feb 25 09:52:53 2011 From: laforge at gnumonks.org (Harald Welte) Date: Fri, 25 Feb 2011 10:52:53 +0100 Subject: about voice In-Reply-To: References: Message-ID: <20110225095253.GO18675@prithivi.gnumonks.org> On Fri, Feb 25, 2011 at 04:51:50PM +0800, shrek wu wrote: > where i can find some doc about the internal, undocumented, calypso buffer > format? LOL. You want documentation about an _undocumented_ format? Undocumented means there is no documentation! A lot of the stuff we do in OsmocomBB has to do with using hardware (or components thereof) that have no documentation available. Regards, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From 246tnt at gmail.com Fri Feb 25 14:38:09 2011 From: 246tnt at gmail.com (Sylvain Munaut) Date: Fri, 25 Feb 2011 15:38:09 +0100 Subject: about voice In-Reply-To: References: Message-ID: > where i can find some doc about the?internal, undocumented, calypso buffer > format? As pointed out, there is no documentation. I don't remember exactly how I learned what the format was ... (probably trial and error, possibly a few hints from the DSP code ...) I've just pushed support for the FR codec buffer format in gapk (thanks to steve-m for the sample file btw). http://git.osmocom.org/gitweb?p=gapk.git;a=commitdiff;h=cfaec3a2f6590bafcaecbc580eba798988a9a2fa I'll do EFR and HR format whenever I get sample files (but I'm away from my hw right now). Cheers, Sylvain From 246tnt at gmail.com Fri Feb 25 17:12:04 2011 From: 246tnt at gmail.com (Sylvain Munaut) Date: Fri, 25 Feb 2011 18:12:04 +0100 Subject: about voice In-Reply-To: References: Message-ID: > I'll do EFR and HR format whenever I get sample files (but I'm away > from my hw right now). I got samples from Steve, so I now have written and pushed support for EFR & HR in gapk as well. Cheers, Sylvain From 775725965 at qq.com Tue Feb 22 10:06:22 2011 From: 775725965 at qq.com (=?gbk?B?wvPM78rYzfs=?=) Date: Tue, 22 Feb 2011 18:06:22 +0800 Subject: hi all Message-ID: who are know the motorola c375 c450 cant to do osmocom and have a fireware -------------- next part -------------- An HTML attachment was scrubbed... URL: From Andreas.Eversberg at versatel.de Tue Feb 22 11:10:50 2011 From: Andreas.Eversberg at versatel.de (Andreas.Eversberg) Date: Tue, 22 Feb 2011 12:10:50 +0100 Subject: AW: AW: Fwd: gpsd support Message-ID: hi dario, i just tried to compile master and your patch. (heaving gpsd installed) here are some problems: CC gps.o gps.c:41: error: 'gps' redeclared as different kind of symbol /usr/include/gps.h:127: error: previous definition of 'gps' was here gps.c: In function 'osmo_gpsd_cb': gps.c:73: warning: implicit declaration of function 'gps_waiting' gps.c: In function 'osmo_gpsd_open': gps.c:123: warning: implicit declaration of function 'gps_stream' gps.c:123: error: 'WATCH_ENABLE' undeclared (first use in this function) gps.c:123: error: (Each undeclared identifier is reported only once gps.c:123: error: for each function it appears in.) 1. the symbol "gps" is used as structure instance for struct osmo_gps. it is also used in an enum declaration at /usr/include/gps.h: ... enum {gps, glonass, unknown} system; ... 2. the declarations 'gps_waiting', 'gps_stream', 'WATCH_ENABLE' are not defined at gps.h this is maybe one reason why i failed to write gpsd support. symbols in the howtos and examples were missing. here is the latest version i got from the gentoo repository: * sci-geosciences/gpsd Latest version available: 2.32 Latest version installed: 2.32 Size of files: 603 kB Homepage: http://gpsd.berlios.de/ Description: GPS daemon and library to support USB/serial GPS devices and various GPS/mapping clients. License: BSD any ideas? andreas From dario.lombardo at libero.it Tue Feb 22 13:30:16 2011 From: dario.lombardo at libero.it (Dario Lombardo) Date: Tue, 22 Feb 2011 14:30:16 +0100 Subject: AW: AW: Fwd: gpsd support In-Reply-To: References: Message-ID: <4D63BA68.3090906@libero.it> On 02/22/2011 12:10 PM, Andreas.Eversberg wrote: > hi dario, > > i just tried to compile master and your patch. (heaving gpsd installed) > here are some problems: > > CC gps.o > gps.c:41: error: 'gps' redeclared as different kind of symbol > /usr/include/gps.h:127: error: previous definition of 'gps' was here > gps.c: In function 'osmo_gpsd_cb': > gps.c:73: warning: implicit declaration of function 'gps_waiting' > gps.c: In function 'osmo_gpsd_open': > gps.c:123: warning: implicit declaration of function 'gps_stream' > gps.c:123: error: 'WATCH_ENABLE' undeclared (first use in this function) > gps.c:123: error: (Each undeclared identifier is reported only once > gps.c:123: error: for each function it appears in.) > > 1. the symbol "gps" is used as structure instance for struct osmo_gps. > it is also used in an enum declaration at /usr/include/gps.h: > > ... > enum {gps, glonass, unknown} system; > ... > > 2. the declarations 'gps_waiting', 'gps_stream', 'WATCH_ENABLE' are not > defined at gps.h > Everything works for me: ironlady:~/Projects/mobile/osmocom/src$ ironlady:~/Projects/mobile/osmocom/src$ ironlady:~/Projects/mobile/osmocom/src$ grep system /usr/include/gps.h * Values for "system" fields. Note, the encoding logic is senstive to the int system; int system; /* Which system is it? */ int system; /* Which system is it? */ ironlady:~/Projects/mobile/osmocom/src$ ironlady:~/Projects/mobile/osmocom/src$ The enum you said is not present in my gpsd include. Instead I have /* * Values for "system" fields. Note, the encoding logic is senstive to the * actual values of these; it's not sufficient that they're distinct. */ #define NAVSYSTEM_GPS 0 #define NAVSYSTEM_GLONASS 1 #define NAVSYSTEM_GALILEO 2 #define NAVSYSTEM_UNKNOWN 3 The symbols you miss, can be found on my system. ironlady:~/Projects/mobile/osmocom/src$ grep gps_waiting /usr/include/gps.h extern bool gps_waiting(struct gps_data_t *); ironlady:~/Projects/mobile/osmocom/src$ grep gps_stream /usr/include/gps.h extern int gps_stream(struct gps_data_t *, unsigned int, /*@null@*/void *); ironlady:~/Projects/mobile/osmocom/src$ grep WATCH_ENABLE /usr/include/gps.h #define WATCH_ENABLE 0x0001u /* enable streaming */ ironlady:~/Projects/mobile/osmocom/src$ ironlady:~/Projects/mobile/osmocom/src$ ironlady:~/Projects/mobile/osmocom/src$ > this is maybe one reason why i failed to write gpsd support. symbols in > the howtos and examples were missing. here is the latest version i got > from the gentoo repository: > > * sci-geosciences/gpsd > Latest version available: 2.32 > Latest version installed: 2.32 > Size of files: 603 kB > Homepage: http://gpsd.berlios.de/ > Description: GPS daemon and library to support USB/serial GPS > devices and various GPS/mapping clients. > License: BSD > > any ideas? > My gpsd version is much more recent: ironlady:~/Projects/mobile/osmocom/src$ rpm -q gpsd gpsd-2.95-2.fc14.i686 ironlady:~/Projects/mobile/osmocom/src$ From 246tnt at gmail.com Tue Feb 22 13:32:55 2011 From: 246tnt at gmail.com (Sylvain Munaut) Date: Tue, 22 Feb 2011 14:32:55 +0100 Subject: AW: AW: Fwd: gpsd support In-Reply-To: <4D63BA68.3090906@libero.it> References: <4D63BA68.3090906@libero.it> Message-ID: > ironlady:~/Projects/mobile/osmocom/src$ rpm -q gpsd > gpsd-2.95-2.fc14.i686 > ironlady:~/Projects/mobile/osmocom/src$ Then try to find what's the minimum version (see api changes in the gpsd history I guess) and make sure in the configure to check it. Sylvain From dario.lombardo at libero.it Tue Feb 22 13:39:30 2011 From: dario.lombardo at libero.it (Dario Lombardo) Date: Tue, 22 Feb 2011 14:39:30 +0100 Subject: AW: AW: Fwd: gpsd support In-Reply-To: References: <4D63BA68.3090906@libero.it> Message-ID: <4D63BC92.7060308@libero.it> On 02/22/2011 02:32 PM, Sylvain Munaut wrote: > > Then try to find what's the minimum version (see api changes in the > gpsd history I guess) and make sure in the configure to check it. > Nice suggestion. I will add this feature and submit a new version of the patch. This means that Andreas will not be able to compile the support anymore, until its debian gets aligned :). Dario From 246tnt at gmail.com Tue Feb 22 14:09:47 2011 From: 246tnt at gmail.com (246tnt at gmail.com) Date: Tue, 22 Feb 2011 14:09:47 +0000 Subject: AW: AW: Fwd: gpsd support In-Reply-To: <4D63BC92.7060308@libero.it> Message-ID: <001636832f2068d590049cdf8875@google.com> > Nice suggestion. I will add this feature and submit a new version of the > patch. This means that Andreas will not be able to compile the support > anymore, until its debian gets aligned :). Well, the current situation is _worse_ ... it tries to compile the support and fails ... And it's gentoo not debian :) Also if you enable the support of experimental packages for gpsd, it does install the 2.95 Cheers, Sylvain -------------- next part -------------- An HTML attachment was scrubbed... URL: From 246tnt at gmail.com Tue Feb 22 14:09:47 2011 From: 246tnt at gmail.com (246tnt at gmail.com) Date: Tue, 22 Feb 2011 14:09:47 +0000 Subject: AW: AW: Fwd: gpsd support In-Reply-To: <4D63BC92.7060308@libero.it> Message-ID: <001636832f2068d590049cdf8875@google.com> > Nice suggestion. I will add this feature and submit a new version of the > patch. This means that Andreas will not be able to compile the support > anymore, until its debian gets aligned :). Well, the current situation is _worse_ ... it tries to compile the support and fails ... And it's gentoo not debian :) Also if you enable the support of experimental packages for gpsd, it does install the 2.95 Cheers, Sylvain -------------- next part -------------- An HTML attachment was scrubbed... URL: From Andreas.Eversberg at versatel.de Tue Feb 22 13:37:54 2011 From: Andreas.Eversberg at versatel.de (Andreas.Eversberg) Date: Tue, 22 Feb 2011 14:37:54 +0100 Subject: AW: AW: AW: Fwd: gpsd support Message-ID: > Then try to find what's the minimum version (see api changes in the > gpsd history I guess) and make sure in the configure to check it. i found it at http://gpsd.berlios.de/. not both apis must be supported, at least check for version 2.90 or later, to decide to use gpsd. From lukas at funky.at Tue Feb 22 15:12:58 2011 From: lukas at funky.at (lukas at funky.at) Date: Tue, 22 Feb 2011 16:12:58 +0100 Subject: Same Problem | Osmocon not loading Message-ID: <0cabbbefd0392c06e6fa4f3ec34c983e@imap.mynet.at> Hello Sorry for my poor english. Can anyone Help me with the same Problem as http://lists.osmocom.org/pipermail/baseband-devel/2011-January/000939.html I have connect the Motorola C123 with the following cable ( http://www.cellcorner.com/xshp/unlock-phone-codes/motorola-t190-t191-t193-unlock-data-cable.html ) directly to a rs232 and to a usb->rs232 adapter. Result, same Probleme than in the Post "Osmocon not loading". What do you think makes the cable or the mobile phone problems? greetings lukas From osmocom at ngolde.de Wed Feb 23 16:40:21 2011 From: osmocom at ngolde.de (Nico Golde) Date: Wed, 23 Feb 2011 17:40:21 +0100 Subject: Same Problem | Osmocon not loading In-Reply-To: <0cabbbefd0392c06e6fa4f3ec34c983e@imap.mynet.at> References: <0cabbbefd0392c06e6fa4f3ec34c983e@imap.mynet.at> Message-ID: <20110223164021.GA29023@pool.math.tu-berlin.de> Hi, * lukas at funky.at [2011-02-22 17:15]: > Sorry for my poor english. > > Can anyone Help me with the same Problem as > http://lists.osmocom.org/pipermail/baseband-devel/2011-January/000939.html > > I have connect the Motorola C123 with the following cable > ( http://www.cellcorner.com/xshp/unlock-phone-codes/motorola-t190-t191-t193-unlock-data-cable.html > ) > directly to a rs232 and to a usb->rs232 adapter. Result, same > Probleme than in the Post "Osmocon not loading". > > What do you think makes the cable or the mobile phone problems? I'm also interested in this problem. I haven't touched osmocom for a bit and was surprised when I noticed it is not working anymore for me. I can eliminate the cable being the reason, I am using (and also tried 2 other cables, just to be sure) the same cable as I did a few months ago and it worked for me in the past. However, right now I'm suffering of the same problem. Does not make a difference if I use c123 or c123xor. Also tried my old osmocom code just to be sure, same problem. I'm currently using a 2.6.37 kernel and gnu arm 4.0.2. Any input on debugging this is welcome, I doubt it's the cable and since it worked before and my usb is generally working I expect it to be something else (kernel usb/serial maybe?). Does anyone have an idea what else I could try? Kind regards Nico From mattjevans at btinternet.com Wed Feb 23 09:53:34 2011 From: mattjevans at btinternet.com (MATTHEW EVANS) Date: Wed, 23 Feb 2011 09:53:34 +0000 (GMT) Subject: layer23 bursts - strategy for filtering IA's for tmsi based on downlink traffic only? Message-ID: <660251.12099.qm@web86607.mail.ird.yahoo.com> Hi all, I am running some tests/experiments with the burst_ind branch. I want to be able to only follow the immediate assignments for my TMSI as it is difficult to verify that the bursts are indeed my traffic. However, I suspect this is not possible using only downlink traffic as without the channel request from the MS I cannot match the resulting IA? I would need to capture uplink too? I would be grateful if someone could confirm if this is the case or if there is a way around this issue? Many thanks, Matt. From uris at septier.com Wed Feb 23 10:10:56 2011 From: uris at septier.com (Uri Savoray) Date: Wed, 23 Feb 2011 12:10:56 +0200 Subject: Converting Layer1 and/or Layer23 to GSM850 In-Reply-To: <660251.12099.qm@web86607.mail.ird.yahoo.com> References: <660251.12099.qm@web86607.mail.ird.yahoo.com> Message-ID: I am using a GSM900/1800/1900 handset (GTA02), and want it to be able to receive on the GSM850 band as well. This is a challenge I want to take on. Has this been done already? Is is physically possible? Ideas for where to start? Thanks, Uri From mad at auth.se Wed Feb 23 14:34:09 2011 From: mad at auth.se (Mad) Date: Wed, 23 Feb 2011 15:34:09 +0100 Subject: layer23 bursts - strategy for filtering IA's for tmsi based on downlink traffic =?UTF-8?Q?only=3F?= In-Reply-To: <660251.12099.qm@web86607.mail.ird.yahoo.com> References: <660251.12099.qm@web86607.mail.ird.yahoo.com> Message-ID: <18275313f519769eed250fb020c82cfe@auth.se> On Wed, 23 Feb 2011 09:53:34 +0000 (GMT), MATTHEW EVANS wrote: > > I am running some tests/experiments with the burst_ind branch. I want > to be able > to only follow the immediate assignments for my TMSI as it is > difficult to > verify that the bursts are indeed my traffic. However, I suspect this > is not > possible using only downlink traffic as without the channel request > from the MS > I cannot match the resulting IA? I would need to capture uplink too? > Even if you would capture the uplink on the RACH you would not be able to distinguish your phones request using your tmsi because IAs refer to requests by their Random Reference (04.08, 9.1.8). Only if you knew this reference you could follow only your phones DCHs. The first time a tmsi/imsi may be sent is on an already established DCH. Of course you could still implement something that only if a RACH request is received on uplink the IA is followed, so you could be sure to follow only requests from phones in your vicinity. Regards, Mad From dario.lombardo at libero.it Wed Feb 23 10:49:35 2011 From: dario.lombardo at libero.it (Dario Lombardo) Date: Wed, 23 Feb 2011 11:49:35 +0100 Subject: opencellid Message-ID: <4D64E63F.3060101@libero.it> Hi guys I think that many of you know opencellid. Did you find its info precise? When querying for cells of my area, I get a positioning that is far far away from the right one. Are there other areas where their positioning is better? Dario. From henk.vergonet at gmail.com Wed Feb 23 22:52:51 2011 From: henk.vergonet at gmail.com (Henk) Date: Wed, 23 Feb 2011 23:52:51 +0100 Subject: Motorola C116 experiment Message-ID: Hi, I could not resist buying a C116 for 15 euro, so I compiled osmocombb and connected a 3.3V serial cable. Of course the C116 was not in the supported list, but I was hoping it would work as it seems that it is very similar to the C115. Here is my load attempt: (used -m c123 ) but there's no loading of the image. I am not using TX mode, also I don't have a SIM installed. Anything I can try to get it working? ./osmocon -p /dev/ttyS0 -m c123xor ../../target/firmware/board/compal_e88/loader.compalram.bin got 1 bytes from modem, data looks like: 00 ?. got 2 bytes from modem, data looks like: 00 81 ?.. got 4 bytes from modem, data looks like: 1b f6 02 00 ?.... got 1 bytes from modem, data looks like: 41 ?A got 1 bytes from modem, data looks like: 01 ?. got 1 bytes from modem, data looks like: 40 ?@ Received PROMPT1 from phone, responding with CMD read_file(../../target/firmware/board/compal_e88/loader.compalram.bin): file_size=16788, hdr_len=4, dnload_le n=16795 got 1 bytes from modem, data looks like: 66 ?f got 1 bytes from modem, data looks like: 74 ?t got 1 bytes from modem, data looks like: 6d ?m got 1 bytes from modem, data looks like: 74 ?t got 1 bytes from modem, data looks like: 6f ?o got 1 bytes from modem, data looks like: 6f ?o got 1 bytes from modem, data looks like: 6c ?l Received FTMTOOL from phone, ramloader has aborted got 1 bytes from modem, data looks like: 65 ?e got 1 bytes from modem, data looks like: 72 ?r got 1 bytes from modem, data looks like: 72 ?r got 1 bytes from modem, data looks like: 6f ?o got 1 bytes from modem, data looks like: 72 ?r got 1 bytes from modem, data looks like: 00 ?. got 1 bytes from modem, data looks like: 1b ?. got 1 bytes from modem, data looks like: 66 ?f got 1 bytes from modem, data looks like: 6d ?m got 1 bytes from modem, data looks like: 74 ?t got 1 bytes from modem, data looks like: 6f ?o Regards, Henk From thatsit at gmx.ch Wed Feb 23 23:33:04 2011 From: thatsit at gmx.ch (Thatsit) Date: Thu, 24 Feb 2011 00:33:04 +0100 Subject: Motorola C116 experiment In-Reply-To: References: Message-ID: Hi Am 23.02.2011 um 23:52 schrieb Henk: > > Anything I can try to get it working? > > ./osmocon -p /dev/ttyS0 -m c123xor > ../../target/firmware/board/compal_e88/loader.compalram.bin > got 1 bytes from modem, data looks like: 00 . > got 2 bytes from modem, data looks like: 00 81 .. > got 4 bytes from modem, data looks like: 1b f6 02 00 .... > got 1 bytes from modem, data looks like: 41 A > got 1 bytes from modem, data looks like: 01 . > got 1 bytes from modem, data looks like: 40 @ > Received PROMPT1 from phone, responding with CMD > read_file(../../target/firmware/board/compal_e88/loader.compalram.bin): > file_size=16788, hdr_len=4, dnload_le n=16795 > got 1 bytes from modem, data looks like: 66 f > got 1 bytes from modem, data looks like: 74 t > got 1 bytes from modem, data looks like: 6d m > got 1 bytes from modem, data looks like: 74 t > got 1 bytes from modem, data looks like: 6f o > got 1 bytes from modem, data looks like: 6f o > got 1 bytes from modem, data looks like: 6c l > Received FTMTOOL from phone, ramloader has aborted I had the same behavior with other phones when I tried it on a slow machine.. As the boot loader is VERY time critical I commented out the printf statements which print the 'got x bytes from modem, data looks like' messages. Then it worked even on my slow computer:-) Regards Matthias From steve at steve-m.de Thu Feb 24 00:05:55 2011 From: steve at steve-m.de (Steve Markgraf) Date: Thu, 24 Feb 2011 01:05:55 +0100 Subject: Motorola C116 experiment In-Reply-To: References: Message-ID: <4D65A0E3.4030307@steve-m.de> Hi, On 24.02.2011 00:33, Thatsit wrote: > I had the same behavior with other phones when I tried it on a slow machine.. > As the boot loader is VERY time critical I commented out the printf statements which > print the 'got x bytes from modem, data looks like' messages. Then it worked > even on my slow computer:-) Yes, agreed. But instead of removing the printf's (which really shouldn't consume that much time), not re-loading the file should save more time. Here's a small patch for trying that: http://www.steve-m.de/projects/osmocom/0001-osmocon-dont-reload.patch With this patch, the file will only be loaded when starting osmocon, and not after receiving PROMPT1. Regards, Steve From thatsit at gmx.ch Thu Feb 24 08:30:34 2011 From: thatsit at gmx.ch (Thatsit) Date: Thu, 24 Feb 2011 09:30:34 +0100 Subject: Motorola C116 experiment In-Reply-To: <4D65A0E3.4030307@steve-m.de> References: <4D65A0E3.4030307@steve-m.de> Message-ID: Hi Steve Am 24.02.2011 um 01:05 schrieb Steve Markgraf: > Yes, agreed. But instead of removing the printf's (which really shouldn't consume that much time), not re-loading the file should save more time. > > Here's a small patch for trying that: > http://www.steve-m.de/projects/osmocom/0001-osmocon-dont-reload.patch > > With this patch, the file will only be loaded when starting osmocon, > and not after receiving PROMPT1. > > Regards, > Steve When I experimented fixing this problem some time ago, I also thought that loading the file in the time critical phase isn't a good idea. But the I realized that the most critical phase is between receiving the PROMPT1 and sending the CMD, and thats before reading the file. So that didn't helped me a lot. Regards Matthias From osmocom at ngolde.de Thu Feb 24 13:10:47 2011 From: osmocom at ngolde.de (Nico Golde) Date: Thu, 24 Feb 2011 14:10:47 +0100 Subject: Motorola C116 experiment In-Reply-To: <4D65A0E3.4030307@steve-m.de> References: <4D65A0E3.4030307@steve-m.de> Message-ID: <20110224131047.GA3507@pool.math.tu-berlin.de> Hi, * Steve Markgraf [2011-02-24 13:54]: > On 24.02.2011 00:33, Thatsit wrote: > >I had the same behavior with other phones when I tried it on a slow machine.. > >As the boot loader is VERY time critical I commented out the printf statements which > >print the 'got x bytes from modem, data looks like' messages. Then it worked > >even on my slow computer:-) > > Yes, agreed. But instead of removing the printf's (which really > shouldn't consume that much time), not re-loading the file should > save more time. > > Here's a small patch for trying that: > http://www.steve-m.de/projects/osmocom/0001-osmocon-dont-reload.patch Tried your patch since I suffer from the same problem. Doesn't fix this for me though :/ read_file(../../target/firmware/board/compal_e88/layer1.e88flash.bin): file_size=49196, hdr_len=4, dnload_len=49203 got 2 bytes from modem, data looks like: 00 81 .. got 5 bytes from modem, data looks like: 1b f6 02 00 41 ....A got 1 bytes from modem, data looks like: 01 . got 1 bytes from modem, data looks like: 40 @ Received PROMPT1 from phone, responding with CMD got 1 bytes from modem, data looks like: 1b . got 1 bytes from modem, data looks like: f6 . got 1 bytes from modem, data looks like: 02 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 41 A got 1 bytes from modem, data looks like: 02 . got 1 bytes from modem, data looks like: 43 C Received PROMPT2 from phone, starting download handle_write(): 4096 bytes (4096/49203) handle_write(): 4096 bytes (8192/49203) handle_write(): 4096 bytes (12288/49203) handle_write(): 4096 bytes (16384/49203) got 1 bytes from modem, data looks like: 1b . got 1 bytes from modem, data looks like: f6 . got 1 bytes from modem, data looks like: 02 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 45 E got 1 bytes from modem, data looks like: 53 S got 1 bytes from modem, data looks like: 16 . Received DOWNLOAD NACK from phone, something went wrong :( got 1 bytes from modem, data looks like: 66 f got 1 bytes from modem, data looks like: 74 t got 1 bytes from modem, data looks like: 6d m got 1 bytes from modem, data looks like: 74 t got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 6c l Received FTMTOOL from phone, ramloader has aborted got 1 bytes from modem, data looks like: 65 e got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 00 . Any other idea? Kind regards Nico From henk.vergonet at gmail.com Sat Feb 26 18:07:24 2011 From: henk.vergonet at gmail.com (Henk) Date: Sat, 26 Feb 2011 19:07:24 +0100 Subject: Motorola C116 experiment In-Reply-To: <20110224131047.GA3507@pool.math.tu-berlin.de> References: <4D65A0E3.4030307@steve-m.de> <20110224131047.GA3507@pool.math.tu-berlin.de> Message-ID: Thanks you all for the responses. I have disabled the printf's and using -m C123 did the trick. Did some tests hello_world, layer1, loader, And made a backup of the 2MB flash. Strings in flashrom: 0x00800 BOOT.90.04 0x02000 MOTOROLA_E88 0x02020 1.0.17.E Here are some of the logs: OSMOCOM Layer 1 (revision osmocon_v0.0.0-780-gb7a4d8d-modified) ====================================================================== Device ID code: 0xb4fb Device Version code: 0x0000 ARM ID code: 0xfff3 cDSP ID code: 0x0128 Die ID code: 168f2c10cb001251 ====================================================================== REG_DPLL=0x2413 CNTL_ARM_CLK=0xf0a1 CNTL_CLK=0xff91 CNTL_RST=0xfff3 CNTL_ARM_DIV=0xfff9 ====================================================================== Assert DSP into Reset Releasing DSP from Reset Setting some dsp_api.ndb values Setting API NDB parameters DSP Download Status: 0x0001 DSP API Version: 0x0000 0x0000 Finishing download phase OSMOCOM Compal DSP Dumper (revision osmocon_v0.0.0-780-gb7a4d8d-modified) ====================================================================== DSP bootloader version 0x0100 DSP dump: Registers [00000-0005f] 00000 : 0386 0008 0008 0008 0000 0000 181f 2900 0000 0000 0000 0060 0000 0000 0000 28a1 From andre at ac.nl.eu.org Thu Feb 24 08:01:31 2011 From: andre at ac.nl.eu.org (=?UTF-8?B?QW5kcsOpIMSMZXJuw6Jr?=) Date: Thu, 24 Feb 2011 09:01:31 +0100 Subject: Motorola C116 experiment In-Reply-To: References: Message-ID: <4D66105B.9000803@ac.nl.eu.org> I had seen same behaviour on C121. It turned out, that UART RxD path was somehow broken between jack and processor. Saved the day connection to the test points TP13 and TP14 instead of earphone jack, as described here: http://bb.osmocom.org/trac/wiki/MotorolaC123#Testpointsaccessiblefrombatterycompartment On 23/02/11 23:52, Henk wrote: > Hi, > > I could not resist buying a C116 for 15 euro, so I compiled osmocombb > and connected a 3.3V serial cable. > > Of course the C116 was not in the supported list, but I was hoping it > would work as it seems that it is very similar to the C115. > > Here is my load attempt: (used -m c123 ) but there's no loading of the image. > I am not using TX mode, also I don't have a SIM installed. > > Anything I can try to get it working? > > ./osmocon -p /dev/ttyS0 -m c123xor > ../../target/firmware/board/compal_e88/loader.compalram.bin > got 1 bytes from modem, data looks like: 00 . > got 2 bytes from modem, data looks like: 00 81 .. > got 4 bytes from modem, data looks like: 1b f6 02 00 .... > got 1 bytes from modem, data looks like: 41 A > got 1 bytes from modem, data looks like: 01 . > got 1 bytes from modem, data looks like: 40 @ > Received PROMPT1 from phone, responding with CMD > read_file(../../target/firmware/board/compal_e88/loader.compalram.bin): > file_size=16788, hdr_len=4, dnload_le n=16795 > got 1 bytes from modem, data looks like: 66 f > got 1 bytes from modem, data looks like: 74 t > got 1 bytes from modem, data looks like: 6d m > got 1 bytes from modem, data looks like: 74 t > got 1 bytes from modem, data looks like: 6f o > got 1 bytes from modem, data looks like: 6f o > got 1 bytes from modem, data looks like: 6c l > Received FTMTOOL from phone, ramloader has aborted > got 1 bytes from modem, data looks like: 65 e > got 1 bytes from modem, data looks like: 72 r > got 1 bytes from modem, data looks like: 72 r > got 1 bytes from modem, data looks like: 6f o > got 1 bytes from modem, data looks like: 72 r > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: 1b . > got 1 bytes from modem, data looks like: 66 f > got 1 bytes from modem, data looks like: 6d m > got 1 bytes from modem, data looks like: 74 t > got 1 bytes from modem, data looks like: 6f o > > Regards, > > Henk > From list_mailing at libero.it Fri Feb 25 16:31:44 2011 From: list_mailing at libero.it (list_mailing) Date: Fri, 25 Feb 2011 08:31:44 -0800 (PST) Subject: IMSI format Message-ID: <1298651504081-2576369.post@n3.nabble.com> Hello. I'm trying to send a location update message using IMSI, but I never receive a reply from the BSC (Authentication request, identity request or location reject). If I change the location update identity using a TMSI, then I receive an Authentication Request or an Identity Request. Could be the IMSI format worng? The used IMSI is valid. I copy the string containing this one into the subscriber imsi field. Should I use an encoding function? I hope the issue is clear. Thanks in advance for support. -- View this message in context: http://baseband-devel.722152.n3.nabble.com/IMSI-format-tp2576369p2576369.html Sent from the baseband-devel mailing list archive at Nabble.com. From holger at freyther.de Fri Feb 25 16:44:43 2011 From: holger at freyther.de (Holger Hans Peter Freyther) Date: Fri, 25 Feb 2011 17:44:43 +0100 Subject: IMSI format In-Reply-To: <1298651504081-2576369.post@n3.nabble.com> References: <1298651504081-2576369.post@n3.nabble.com> Message-ID: <4D67DC7B.4030805@freyther.de> On 02/25/2011 05:31 PM, list_mailing wrote: > > Hello. Hi, you should generate a trace and then look at it with wireshark. regards holger From 775725965 at qq.com Sun Feb 27 11:38:47 2011 From: 775725965 at qq.com (=?gbk?B?wvPM78rYzfs=?=) Date: Sun, 27 Feb 2011 19:38:47 +0800 Subject: no people to do use usb interface phone for GSM openbts Message-ID: hi no people to do use usb interface phone for GSM openbts -------------- next part -------------- An HTML attachment was scrubbed... URL: From 775725965 at qq.com Sun Feb 27 15:59:23 2011 From: 775725965 at qq.com (=?gbk?B?wvPM78rYzfs=?=) Date: Sun, 27 Feb 2011 23:59:23 +0800 Subject: hi all love GSM and love phone Message-ID: the GSM bts Features =GSM phone we can use usb interface phone to do a same Features GSM bts we can use motorola c375 c450 c550 and MTK chip phone all use interface phone this is a cheap Program can you tell me the osmocom feature isnt same we can use openbts software Connection the phone -------------- next part -------------- An HTML attachment was scrubbed... URL: From squalyl at gmail.com Sun Feb 27 16:08:36 2011 From: squalyl at gmail.com (=?UTF-8?Q?S=C3=A9bastien_Lorquet?=) Date: Sun, 27 Feb 2011 17:08:36 +0100 Subject: hi all love GSM and love phone In-Reply-To: References: Message-ID: seriously... can't we do something about that ? O_o now that's twice a day... 2011/2/27 ???? <775725965 at qq.com> > the GSM bts Features =GSM phone > we can use usb interface phone to do a same Features GSM bts > we can use motorola c375 c450 c550 and MTK chip phone all use interface > phone > this is a cheap Program > can you tell me the osmocom feature isnt same we can use openbts > software Connection the phone -------------- next part -------------- An HTML attachment was scrubbed... URL: From 246tnt at gmail.com Sun Feb 27 16:23:17 2011 From: 246tnt at gmail.com (Sylvain Munaut) Date: Sun, 27 Feb 2011 17:23:17 +0100 Subject: hi all love GSM and love phone In-Reply-To: References: Message-ID: > seriously... can't we do something about that ? O_o > > now that's twice a day... And it happily stayed in my spam / trash folder until you you brought it out ... Sylvain From laforge at gnumonks.org Mon Feb 28 15:42:35 2011 From: laforge at gnumonks.org (Harald Welte) Date: Mon, 28 Feb 2011 16:42:35 +0100 Subject: hi all love GSM and love phone In-Reply-To: References: Message-ID: <20110228154235.GQ27912@prithivi.gnumonks.org> Guys, what's happening here is as follows: 1) Some Chinese native speaker with no/little knowledge of English is trying to communicate on our list but uses something along the lines of google translate 2) He is using QQ (popular IM application, more used than e-mail, Gtalk, MSN or anything else in china) to send the message. I don't think we should 'do something' about it. Even while there are huge communicative differences, cellphone engineers from China can still be quite useful about this project (for example regarding schematics, datasheets, etc. - specifically regarding MTK). That some of those people seem to have a complete lack of technical understanding and somehow think you can use a MTK baseband chipset for a USRP is a different case. But please be careful not to discriminate purely based on the fact that soembody doesn't speak/read/write English that way we do. Regards, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From henk.vergonet at gmail.com Sun Feb 27 19:45:01 2011 From: henk.vergonet at gmail.com (Henk) Date: Sun, 27 Feb 2011 20:45:01 +0100 Subject: Dutch gsm antenna locations Message-ID: It's a little off topic. Hope you'll forgive me... Not yet tested in maps. - Henk -------------- next part -------------- A non-text attachment was scrubbed... Name: gsm-nl.kmz Type: application/vnd.google-earth.kmz Size: 231882 bytes Desc: not available URL: From dario.lombardo at libero.it Sun Feb 27 21:06:36 2011 From: dario.lombardo at libero.it (Dario Lombardo) Date: Sun, 27 Feb 2011 22:06:36 +0100 Subject: Dutch gsm antenna locations In-Reply-To: References: Message-ID: Not only off-topic... also off-land :) Opening with ge, it shows me somewhere near Somalia (sea)... On Sun, Feb 27, 2011 at 8:45 PM, Henk wrote: > It's a little off topic. Hope you'll forgive me... > > Not yet tested in maps. > > - Henk > -------------- next part -------------- An HTML attachment was scrubbed... URL: From henk.vergonet at gmail.com Mon Feb 28 00:15:06 2011 From: henk.vergonet at gmail.com (Henk) Date: Mon, 28 Feb 2011 01:15:06 +0100 Subject: Dutch gsm antenna locations In-Reply-To: References: Message-ID: > Not only off-topic... also off-land :) Yes sorry. it was not yet tested. Stupid me... This one should work... -henk -------------- next part -------------- A non-text attachment was scrubbed... Name: gsm-nl.kmz Type: application/vnd.google-earth.kmz Size: 232952 bytes Desc: not available URL: