tree 34067586b76b6026228ba175bcd9dc44027b674d
parent 559780e3224d90b62a18aedea0fc1bccadc3977e
author Khang D Nguyen <khangng@os.amperecomputing.com> 1743401269 +0700
committer Khang D Nguyen <khangng@os.amperecomputing.com> 1743743395 +0700

Ensure FRU text is printable ASCII

Currently, libcper currently fails to compile on my machine (GCC 13):

    ../cper-utils.c: In function ‘add_untrusted_string’:
    ../cper-utils.c:467:23: error: comparison is always false due to
    limited range of data type [-Werror=type-limits]
      467 |                 if (c < 0) {
          |                       ^

The reason seems to be that char signedness is implementation-defined,
we have to explicitly use unsigned char or signed char to get a portable
char type. In our case, char is unsigned char, hence the warning.

Apparently we are trying to validate ASCII strings from the records.
Those strings seem to be used for display purpose only, so I think
replacing it with a more precise printable ASCII test, which also does
not care about char signedness, is appropriate here.

This changes the JSON fruText property to appear only with printable
ASCII FRU content. As a result, all of the examples have been changed
where applicable. Some sections use FRU content with a predefined format
(pcie, cxlprotocol) so fruText has been completely removed from those
JSON objects like in the case of non-printable ASCII FRU content.

Tested: oompile successfully

Change-Id: I98c7c10a674c8817e0b2cbe82c26f6590d8d716a
Signed-off-by: Khang D Nguyen <khangng@os.amperecomputing.com>