Hi Daniel,
it seems I'm through with the IuPS branch refactoring.
I'm not entirely sure why I'm allowed to do so, but I managed to push the
branch to gerrit as refs/heads/sysmocom/iups, so you should see this in origin:
sysmocom/iups
The branch is fully mergeable to openbsc master as far as I'm concerned, I'm
fairly sure that it shouldn't break 2G GPRS -- but untested!!
Another limitation: the libosmo-netif and libosmo-sccp branches should possibly
be merged to master first.
About sysmocom/iups:
Most commits have been regrouped and relabeled, yet some remain as they were in
the "old" sysmocom/iu branch. I was originally aiming for a 1:1 similarity, but
I "had" to change various things:
* Some of the commit log messages from sysmocom/iu have been placed in the code
as comments instead.
* iu_rab_act_ps() was moved (too gprs specific)
* some changes were dropped because they were bogus
* comments were added, minor cosmetic changes were made
* at least the DRANAP, DSUA have been re-ordered cosmetically (to match)
* A test failure was fixed
* ...
* Some "unrelated" patches waiting for review on gerrit are not included in the
branch (https://gerrit.osmocom.org/91, 93, 94)
Please take a look at the new branch and test it with 3G IuPS. (Since IuCS does
not exist on the branch, maybe you need to trick around to have an osmo-cscn?
It's an interesting discussion how useful IuPS is without IuCS.)
If you have any local further developments on your box, please try to rebase
them onto the new branch.
If any problems show up, let's clear them in the coming days.
Thanks!
~Neels
--
- Neels Hofmeyr <nhofmeyr(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschäftsführer / Managing Directors: Holger Freyther, Harald Welte
My patches https://gerrit.osmocom.org/93 and 94 show as merge conflict in the
overview. Yet when I rebase them onto origin/master, neither has a merge
conflict.
Before 92 was submitted, gerrit said that 93 conflicted with
https://gerrit.osmocom.org/92 which has no overlaps, the changes are more than
60 lines apart. In the log I also see a jenkins build success.
I have no idea what to make of this. How can I see merge conflicts that gerrit
saw and be less confused?
~Neels
--
- Neels Hofmeyr <nhofmeyr(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschäftsführer / Managing Directors: Holger Freyther, Harald Welte
Hello
Hello
I am using the OpenBTS/OpenBsc software and would like to ask if it is
possible to change the following parameters dynamically in the L2/L3 open
SW:
MCC
MNC
The name of the network provider
Band
ARFCN
TA filter
BA List
CA list
LAC
CRO Parameter: in a rage of -126 to 126
RAC
NMO
BSIC
Cell ID
T3212
Power of transmission
Neighbor list for UTRA and E-UTRA (System Info 2)
I saw that changing these parameters via Vty (telnet) affected only the
openbsc.cfg and openbts.cfg files by saving the changes but actually the
BSC was not affected from the changes - only after turning the BSC off and
on. Can we avoid BSC "restart"?
Thanks in advanced,
Ilan
Review at https://gerrit.osmocom.org/100
gprs_rlcmac_sched: fix mistype of CONTROL ACK
Change-Id: If37b33f69cd659d913ed81eb6060a42734ba524f
---
M src/gprs_rlcmac_sched.cpp
1 file changed, 1 insertion(+), 1 deletion(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-pcu refs/changes/00/100/1
diff --git a/src/gprs_rlcmac_sched.cpp b/src/gprs_rlcmac_sched.cpp
index b513b5b..fce3aaf 100644
--- a/src/gprs_rlcmac_sched.cpp
+++ b/src/gprs_rlcmac_sched.cpp
@@ -132,7 +132,7 @@
/*
* Assignments for the same direction have lower precedence,
- * because they may kill the TBF when the CONTOL ACK is
+ * because they may kill the TBF when the CONTROL ACK is
* received, thus preventing the others from being processed.
*/
--
To view, visit https://gerrit.osmocom.org/100
To unsubscribe, visit https://gerrit.osmocom.org/settings
Gerrit-MessageType: newchange
Gerrit-Change-Id: If37b33f69cd659d913ed81eb6060a42734ba524f
Gerrit-PatchSet: 1
Gerrit-Project: osmo-pcu
Gerrit-Branch: master
Gerrit-Owner: lynxis lazus <lynxis(a)fe80.eu>