All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: Bug/Oversight in gatchat/gatresult.c with negative numbers
Date: Fri, 06 Aug 2021 09:20:02 -0500	[thread overview]
Message-ID: <3e7af84c-b9be-251e-b288-aa621dcd3e4e@gmail.com> (raw)
In-Reply-To: <0af28d41-60eb-47b7-7b9a-99fc734bab31@dynamicdevices.co.uk>

[-- Attachment #1: Type: text/plain, Size: 975 bytes --]

Hi Alex,

> Denis - I am being directed to the ITU 36.133 spec here
> 
> https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=2420
> 

Sure, same document/section where 27.007 refers to for <rsrp>.  But 
unfortunately 27.007 only defines the range 0..97 where 0 is <rsrp> < 140 dbm. 
How 3GPP decides to represent <rsrp> values between 156 and 140 is up to 3GPP. 
If your vendor is using negative integers in AT commands, then that is a vendor 
extension and not something that is permitted by ITU v.250.

> This document defines this in 9.1.4
> 
> I can't see where RSRP_-17 is defined anywhere but the strong implication to me 
> is that this number should be -17
> 
> Can you confirm where it states that these numbers cannot be negative numbers as 
> I cannot find that requirement.
> 

V.250 Section 5.3.1.  Notice that 27.007 never uses negative integers, there's a 
reason for that.

Regards,
-Denis

  reply	other threads:[~2021-08-06 14:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-20 16:11 Bug/Oversight in gatchat/gatresult.c with negative numbers Alex J Lennon
2021-07-27 14:38 ` Denis Kenzior
2021-07-27 15:02   ` Alex J Lennon
2021-08-03  9:48   ` Alex J Lennon
2021-08-03 14:28     ` Denis Kenzior
2021-08-03 14:45       ` Alex J Lennon
2021-08-06  9:31       ` Alex J Lennon
2021-08-06 14:06       ` Alex J Lennon
2021-08-06 14:20         ` Denis Kenzior [this message]
2021-08-06 14:28           ` Alex J Lennon
2021-08-06 14:44             ` Denis Kenzior
2021-08-06 14:49               ` Alex J Lennon
2021-08-06 15:02                 ` Denis Kenzior
2021-08-09  6:40                   ` Martin =?unknown-8bit?q?Hundeb=C3=B8ll?=

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3e7af84c-b9be-251e-b288-aa621dcd3e4e@gmail.com \
    --to=denkenz@gmail.com \
    --cc=ofono@ofono.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.