You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Maintaining a hex value for the serial number should resolve this. Converting it to decimal, then to human readable, has no use and makes mapping/identifying devices harder.
The text was updated successfully, but these errors were encountered:
...i.e. that the problem arises from mixing int64 and uint64 json-c APIs. Otherwise it's likely too late to create that ABI breakage for the machine readable version of the serial number.
When I list the memdev information, I see a serial number:
However, when the
-u
(Human Readable) option is provided, this causes an out-of-range condition, so the serial number becomes bogus:The device reports a serial number of:
Converting the integer value returns the correct serial number:
(9947034306373222400)Base10 = (8A0AF70000000000)Base16
Maintaining a hex value for the serial number should resolve this. Converting it to decimal, then to human readable, has no use and makes mapping/identifying devices harder.
The text was updated successfully, but these errors were encountered: