On 04.04.2012 07:06, Dave Mielke wrote: > Maybe this'll help explain my question regarding reporting grub errors. In > ls.c, I found: > > grub_error (GRUB_ERR_BAD_ARGUMENT, "invalid argument"); > > In this case, the writer of the code knows which text matches the error code. > When we call the serial driver's configure() method, however, we get back an > error code but we don't know what it is. Do we just trust that the > configure() > method has already called grub_error()? Yes > What if it hasn't? Then it's buggy and has to be fixed. > > > Does grub have a function that converts a grub_err_t value to an errno value? It's identity. > Does grub have functions for disabling and reenabling interrupts? No. The only interrupts currently enabled are traps on invalid operations or debugging and only when the module for it is loaded, only on x86.
-- Regards Vladimir 'φ-coder/phcoder' Serbinenko
signature.asc
Description: OpenPGP digital signature
_______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: [email protected] For general information, go to: http://mielke.cc/mailman/listinfo/brltty
