I didn't see a reason to ever see this either, hence I added no
dprintf (also i think "loader" isn't an existing dprintf name, and I
try to avoid introducing those as much as I can).
By "explicitly asking for", I was thinking of the ability to simply
print the path in the config (which admittedly
On 8/2/24 12:52, Mate Kukri wrote:
Users have no reason to see this without explicitly asking for it, and
it can break graphical boot.
If you wanted users to be able to explicitly ask for the the output, you
could use:
grub_dprintf ("loader", ...)
'set debug=loader' then would provide t
The cycle register is not guaranteed to count at constant frequency.
If it is counting at all depends on the state the performance monitoring
unit.
Use the time register to measure time.
Signed-off-by: Heinrich Schuchardt
---
grub-core/kern/riscv/efi/init.c | 15 +++
1 file changed,
