Bean wrote: > On Sun, Aug 17, 2008 at 10:43 AM, y.volta <[EMAIL PROTECTED]> wrote: >> btw, i think the grub_dprintf should output to non-display device, this will >> make debuging more easier and comfort . i think the low-cost device is a >> com-port. for, now time virtual machine software has this legancy device >> full supported. >> the freeldr coming with ReactOS have this kind of function (only display a >> string, but can do kernal debug also ) > > Please don't define new debug mechanism. grub_dprintf may not be the > best, but it's already used through grub2, just keep it that way.
Hmm.. How about if we define new targets for dprintf? Like you load module debug_vmware/qemu/serial/or something common. Then it would provide new environment variable where you can set target of dprintf. Though dprintf would then need to provide hook to allow redirecting of those, but that should not be big deal. _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
