Attention is currently required from: pespin.
4 comments:
File include/osmocom/bsc/gsm_data.h:
Patch Set #2, Line 50: #define GSM_N3101_STRICT_LOWER_BOUND 8UL
STRICT_LOWER_BOUND means simply "MIN" ? :D
Well, no,
Patch Set #2, Line 50: #define GSM_N3101_STRICT_LOWER_BOUND 8UL
STRICT_LOWER_BOUND means simply "MIN" ? :D
The spec states that 'N3101 > 8', so it isn't a minimum (it's not an allowed value).
I put the strict lower bound and not the minimum as a define, because that's how it's stated in the spec.
File src/osmo-bsc/net_init.c:
Patch Set #2, Line 51: { .T = 3142, .default_val = 20,
I know tons of parameters are already added here, but we should not continue adding BTS-specific par […]
So, how do I know which timers are BTS-specific or depend on BTS support?
I first thought the groupings suggested on https://www.rfwireless-world.com/Terminology/GSM-timers.html (GSM Timers, GSM Timers Network Side(BTS), ...) might make sense, but T3142 isn't listed there as a BTS timer, it's listed as a timer for the mobile side (MSC I guess).
I was thinking about adding a group named "bts". Or am I supposed to add several groups for different kinds of BTSs/
File tests/nanobts_omlattr/nanobts_omlattr_test.c:
Patch Set #2, Line 228: 0x02, 0x00, 0x02, 0xa3, 0x00, 0x09,
why is this changing? are you changing the default values?
No default values have been changed. I just added changed the paragraph formatting a bit and added a comment line so that if anyone else reads the code in the future, it's possible to read which octet contains which information without having to go through the entire code.
It shouldn't be necessary for anybody to lose time over looking up this information again, at least not for that line.
To view, visit change 31878. To unsubscribe, or for help writing mail filters, visit settings.