From: Andrei Borzenkov <arvidjaar@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH] menu_entry: Disable cursor during update_screen()
Date: Sat, 30 Jan 2016 10:33:20 +0300 [thread overview]
Message-ID: <56AC6740.6090008@gmail.com> (raw)
In-Reply-To: <1454077618-18986-1-git-send-email-thuth@redhat.com>
29.01.2016 17:26, Thomas Huth пишет:
> When running grub in a VGA console of a KVM pseries guest on PowerPC,
> you can see the cursor sweeping over the whole line when entering a
> character in editor mode. This is visible because grub always refreshes
> the whole line when entering a character in editor mode, and drawing
> characters is quite a slow operation with the firmware used for the
> powerpc pseries guests (SLOF).
> To avoid this ugliness, the cursor should be disabled when refreshing
> the screen contents during update_screen().
>
While it looks OK - any reason it is not present in Fedora grub2 GIT?
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> grub-core/normal/menu_entry.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/grub-core/normal/menu_entry.c b/grub-core/normal/menu_entry.c
> index 62c7e16..68359eb 100644
> --- a/grub-core/normal/menu_entry.c
> +++ b/grub-core/normal/menu_entry.c
> @@ -250,6 +250,8 @@ update_screen (struct screen *screen, struct per_term_screen *term_screen,
> mode = ALL_LINES;
> }
>
> + grub_term_setcursor (term_screen->term, 0);
> +
> if (mode != NO_LINE)
> {
> /* Draw lines. This code is tricky, because this must calculate logical
> @@ -357,6 +359,8 @@ update_screen (struct screen *screen, struct per_term_screen *term_screen,
>
> }
>
> + grub_term_setcursor (term_screen->term, 1);
> +
> grub_term_refresh (term_screen->term);
> }
>
>
next prev parent reply other threads:[~2016-01-30 7:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 14:26 [PATCH] menu_entry: Disable cursor during update_screen() Thomas Huth
2016-01-30 7:33 ` Andrei Borzenkov [this message]
2016-01-31 15:02 ` Thomas Huth
2016-02-13 7:41 ` Andrei Borzenkov
2016-02-15 10:23 ` Thomas Huth
2016-02-12 8:19 ` Thomas Huth
2016-02-22 7:00 ` Andrei Borzenkov
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=56AC6740.6090008@gmail.com \
--to=arvidjaar@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).