Can you not just mask of the error bit, and index into the table
(after a bounds check) as opposed to doing this looping search?
Also I think an strerror type interface would be nicer to callers
(maybe in addition) as opposed to this perror stuff, that
way they can do their own grub_error, or othe
This RFC patch introduces a UEFI error message printer that translates
UEFI status codes from hexadecimal values into human-readable strings.
The problem this rfc solves is, undescriptive error messages in Grub (on
failure what
get printed). Specifically the documented firmware spec which UEFI. I
This RFC patch introduces a UEFI error message printer that translates
UEFI status codes from hexadecimal values into human-readable strings.
The idea is inspired by the GNU C Library's "perror()" function, which
translates
"errno" values into descriptive error messages. Similarly, this implement
This RFC patch introduces a UEFI error message printer that translates
UEFI status codes from hexadecimal values into human-readable strings.
The idea is inspired by the GNU C Library's "perror()" function, which
translates
"errno" values into descriptive error messages. Similarly, this implement
