Change in ...osmo-bts[master]: Clarify and refactor link quality (C/I) handling

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/gerrit-log@lists.osmocom.org/.

laforge gerrit-no-reply at lists.osmocom.org
Sun Jul 14 03:59:22 UTC 2019


laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bts/+/14686 )

Change subject: Clarify and refactor link quality (C/I) handling
......................................................................


Patch Set 4:

No matter what we do, the resolutoin of 1/10th of dB (centi-bel) is for sure more than sufficient for the purpose of 

in terms of range, using uint16_t gives a range of 0..655.35 dB, which is certainly sufficient ;)

So both from a resolution and from a range point of view, uint16_t is fine.  What I'm a bit more worried is whether there could be negative values?  But I guess if the interference is stronger than the carrier, we wouldn't detect the training sequence anymore?


-- 
To view, visit https://gerrit.osmocom.org/c/osmo-bts/+/14686
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings

Gerrit-Project: osmo-bts
Gerrit-Branch: master
Gerrit-Change-Id: If624d6fdc0270e6813af8700d95f1345903c8a01
Gerrit-Change-Number: 14686
Gerrit-PatchSet: 4
Gerrit-Owner: Vadim Yanitskiy <axilirator at gmail.com>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: Vadim Yanitskiy <axilirator at gmail.com>
Gerrit-Reviewer: ipse <Alexander.Chemeris at gmail.com>
Gerrit-Reviewer: laforge <laforge at gnumonks.org>
Gerrit-Comment-Date: Sun, 14 Jul 2019 03:59:22 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/gerrit-log/attachments/20190714/c8c423b3/attachment.htm>


More information about the gerrit-log mailing list