From: "Vesa Jääskeläinen" <chaac@nic.fi>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] romfs support for Grub2
Date: Sun, 17 Aug 2008 10:09:13 +0300 [thread overview]
Message-ID: <48A7CE99.10904@nic.fi> (raw)
In-Reply-To: <ca0f59980808162105h44401cfbu64d5290fc0499c67@mail.gmail.com>
Bean wrote:
> On Sun, Aug 17, 2008 at 10:43 AM, y.volta <f22_storm@163.com> 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.
next prev parent reply other threads:[~2008-08-17 7:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48A6FA9A.45473C.07156@m12-70.163.com>
2008-08-17 2:43 ` [PATCH] romfs support for Grub2 y.volta
2008-08-17 4:05 ` Bean
2008-08-17 7:09 ` Vesa Jääskeläinen [this message]
[not found] <48a80c3d.2c012c0a.0a0b.1ed7SMTPIN_ADDED@mx.google.com>
2008-08-17 13:17 ` y.volta
2008-08-17 13:26 ` Bean
2008-08-17 13:32 ` Felix Zielcke
2008-08-17 15:36 ` Marco Gerards
[not found] <48a8340b.1e0f2c0a.4d32.2809SMTPIN_ADDED@mx.google.com>
2008-08-17 14:30 ` y.volta
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48A7CE99.10904@nic.fi \
--to=chaac@nic.fi \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.