aboutsummaryrefslogtreecommitdiff
path: root/boot/vbe.c
diff options
context:
space:
mode:
authorAlgapally Santosh Sagar <santoshsagar.algapally@amd.com>2023-01-25 13:06:21 +0100
committerMichal Simek <michal.simek@amd.com>2023-01-27 08:49:24 +0100
commitf0f86d39fec73479d4904e6d5b9db01a29597d58 (patch)
tree0da06f49945bc5199df1659eacc8acbf282211cf /boot/vbe.c
parent5563167e6e612e87be1722f28881e835d8836a1d (diff)
downloadu-boot-f0f86d39fec73479d4904e6d5b9db01a29597d58.zip
u-boot-f0f86d39fec73479d4904e6d5b9db01a29597d58.tar.gz
u-boot-f0f86d39fec73479d4904e6d5b9db01a29597d58.tar.bz2
fru: ops: Display FRU fields properly for 0xc1 fields
FRU data is not displayed properly in case of 0xc1 fields. The 0xC1 can be used in two cases. 1. Char record type 8-bit ASCII + Latin 1 with length of 1. (For example board revision 'A') 2. C1h (type/length byte encoded to indicate no more info fields). which can follow by 00h to fill all remaining unused space Hence removed the check end-of-the field c1 to allow c1 fields. "ASCII+LATIN1" is defined as the printable characters from the first set of 256 characters of Unicode 6.2 (U+0000h through U+00FFh, inclusive) expressed as an eight-bit value. (Unicode follows ISO/IEC 8859-1 in the layout of printable characters up to U+00FFh). So, print only printable chars and limit range from 0x20 ' ' to 0x7e '-' which will be also indication if 0xc1 behaves as record with one char or end of record. Signed-off-by: Algapally Santosh Sagar <santoshsagar.algapally@amd.com> Signed-off-by: Michal Simek <michal.simek@amd.com> Link: https://lore.kernel.org/r/4198d73de600627872c80a5b07e5068502c589d7.1674648379.git.michal.simek@amd.com
Diffstat (limited to 'boot/vbe.c')
0 files changed, 0 insertions, 0 deletions