Dear all,
so far the osmocom.org mailing lists have always been in a 'non-members
are manually moderated' mode. This has created a lot of work for manual
list moderation, where a lot of the messages caught are simply spam, and
only the occasional valid message is being received.
I'd like to thank the list moderators for taking care of this.
However, in more recent discussions, we were considering to move the
lists to a completely closed mode, i.e. postings would automatically be
rejected from non-members.
The automatic response would contain a description of how to subscribe
in 'nomail' mode, i.e. to subscribe in a way to be able to post to the
list, while still not receiving any incoming traffic. The latter should
be fine for occasional posters who don't want the bulk e-mail that goes
with a full/regular subscription.
Please provide feedback in case you disagree with that change. Unless
there is major opposition, we will likely transition to the 'closed'
mode within one month.
Thanks,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Hi.
While looking at osmocom-bb compilation warnings I've noticed that there are plenty
of those cause by signed-unsigned comparison with msgb-related functions. Attached is
a trivial patch which fixes that by changing int -> uint16_t. For the sake of
completeness I've also changed other functions to explicitly use uint16_t - this is
used for length fields in "struct msgb" anyway.
Although technically it's API change I do not expect any sane code to break. If you
still think it's potentially insecure, this could be applied during next api version
bump alongside with gprs api change.
--
best regards,
Max, http://fairwaves.ru
---
include/osmocom/core/msgb.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/osmocom/core/msgb.h b/include/osmocom/core/msgb.h
index fe2733b..5610a22 100644
--- a/include/osmocom/core/msgb.h
+++ b/include/osmocom/core/msgb.h
@@ -147,7 +147,7 @@ static inline unsigned int msgb_headlen(const struct msgb *msgb)
* This function computes the amount of octets left in the underlying
* data buffer after the end of the message.
*/
-static inline int msgb_tailroom(const struct msgb *msgb)
+static inline unsigned int msgb_tailroom(const struct msgb *msgb)
{
return (msgb->head + msgb->data_len) - msgb->tail;
}
@@ -159,7 +159,7 @@ static inline int msgb_tailroom(const struct msgb *msgb)
* This function computes the amount of bytes left in the underlying
* data buffer before the start of the actual message.
*/
-static inline int msgb_headroom(const struct msgb *msgb)
+static inline unsigned int msgb_headroom(const struct msgb *msgb)
{
return (msgb->data - msgb->head);
}
--
1.8.3.2
--------------070704060003090203050700--
Hi all.
I'd like to see osmocom-bb builds less cluttered by compiler warnings - attached is
(far from complete) attempt to do so. It's tested which means it builds on my machine
and resulting mobile app seems to run fine - no in-depth testing were made.
However I'd like to get some feedback before going further: there seems to be some
evil hackery happening around src/target/firmware/apps/loader/main.c:
Why do we have external "unsigned char _start" which later used as msgb_put_u32(msg,
&_start);
Do we make some assumptions on the size of unsigned char? Is this documented
somewhere by any chance?
Also there are plenty of warnings regarding alignment: some things are marked as
"__attribute__ ((packed))" and some are not which seems to make compiler unhappy. Is
there rule of thumb to decide when we should care about alignment?
--
best regards,
Max, http://fairwaves.ru
Hi,
I am cleaning up my office and would like to get rid of a R&S CTS55.
The device powers up but I have never used it for any development. It
is currently located in Germany and before posting it on eBay I would
be happy to give it someone involved/intersted in the OsmocomBB project.
Please contact me off list in case you would like to have it.
holger
Hi everyone,
I m receiving the following errors:
(I am using the "Ja! Mobil" SIM card with Motorola C118)
root@neetesh-VirtualBox:/opt/osmocom-bb/src/host/osmocon# telnet localhost 4247
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Welcome to the OsmocomBB control interface
OsmocomBB> en
OsmocomBB# conf t
OsmocomBB(config)# ms 1
OsmocomBB(ms)#no shutdown
OsmocomBB(ms)#en
OsmocomBB# write
Configuration saved to /home/neetesh/.osmocom/bb/mobile.cfg
OsmocomBB# show ms 1
MS '1' is down, radio is not started
IMEI: 000000000000000
IMEISV: 0000000000000000
IMEI generation: fixed
automatic network selection state: A0 null
cell selection state: C0 null
radio ressource layer state: idle
mobility management layer state: MM idle, PLMN search
OsmocomBB# show subs 1
Mobile Subscriber of MS '1':
No SIM present.
OsmocomBB# sim read 1
OsmocomBB# show subs
Mobile Subscriber of MS '1':
IMSI:
Status: U2_NOT_UPDATED IMSI detached LAI: invalid
Access barred cells: no
Access classes:
Can anyone tell me whether the problem is related to SIM card or it is related to phone?
Do you have any clue how to fix it?
I tried to fix the patch of SIM, but then I am not able to compile source (errors occurred).
Please let me know your views.
regards,
neetesh
On Thu, Jan 09, 2014 at 04:00:27PM -0000, neetesh saxena wrote:
> Thanks for your help. Now I am able to compile and run the source of
> osmocmBB. The problem was I had not installed toolchain as a root.
Great that it works now.
Just as a side note:
It is not necessary to perform any operation as root.
I assume you installed the toolchain in /usr/local or so which is not
writable as a normal user.
You can have e.g. a ~/install and then add $HOME/install/bin to your
path.
Kind regards,
-Alex
Hi everyone,
Thanks for your help. Now I am able to compile and run the source of osmocmBB.
The problem was I had not installed toolchain as a root.
But unfortunately, now I m receiving the same error as I was getting earlier which is as follows:
(I am using the "Ja! Mobil" SIM card)
root@neetesh-VirtualBox:/opt/osmocom-bb/src/host/osmocon# telnet localhost 4247
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Welcome to the OsmocomBB control interface
OsmocomBB> en
OsmocomBB# conf t
OsmocomBB(config)# ms 1
OsmocomBB(ms)#no shutdown
OsmocomBB(ms)#en
OsmocomBB# write
Configuration saved to /home/neetesh/.osmocom/bb/mobile.cfg
OsmocomBB# show ms 1
MS '1' is down, radio is not started
IMEI: 000000000000000
IMEISV: 0000000000000000
IMEI generation: fixed
automatic network selection state: A0 null
cell selection state: C0 null
radio ressource layer state: idle
mobility management layer state: MM idle, PLMN search
OsmocomBB# show subs 1
Mobile Subscriber of MS '1':
No SIM present.
OsmocomBB# sim read 1
OsmocomBB# show subs
Mobile Subscriber of MS '1':
IMSI:
Status: U2_NOT_UPDATED IMSI detached LAI: invalid
Access barred cells: no
Access classes:
I tried the patches SIM in the firmware provided by Lukas Kuzmiak available at :
http://baseband-devel.722152.n3.nabble.com/patches-for-SIM-in-the-firmware-…
But in my first attempt I am getting some error in l23_api.c while I am compileing the osmocomBB source because I think when I am changing the code then I need to recompile and run it.
Didi anyone help me on this? Has anybody used this patch earlier?
Am i doing something wrong?
With regards
Neetesh Saxena...