All of lore.kernel.org
 help / color / mirror / Atom feed
From: Omniflux <omniflux+lists@omniflux.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: x86 serial support
Date: Fri, 12 Aug 2005 16:18:49 -0600	[thread overview]
Message-ID: <42FD2049.2050903@omniflux.com> (raw)
In-Reply-To: <874q9vm9ek.fsf@student.han.nl>

Marco Gerards wrote:

>>>BTW, do you have any suggestion about the so-called "dumb terminal"? 
>>
>>The only thing I can think of is to disable the menu and replace clear
>>screen with a newline, which is what Legacy does IIRC.
> 
> Why can't we use a menu?  Is it really that slow to update the menu
> over a serial console?

This is a communication problem caused by the fact that dumb terminal 
does not have a universally accepted definition. In this case, we are 
talking about a terminal without cursor control, such as a glass tty or 
teletype.

The following paragraph can be ignored if the above clarifies the issue. 
It contains examples for anyone else.

To implement a menu for this terminal would entail redrawing the screen 
each time something must be changed. This could be incredibly slow as 
many of these terminals have speeds of less then 110 bps. This also 
leaves the problem of marking the current menu selection, as we cannot 
use either color or reverse video. We would also be unable to reposition 
the cursor to (0,0) for the redraw, because we cannot be sure of the 
display size and thus the number of newlines which must be sent to move 
a line of text to that position. If the terminal is actually a display 
on paper terminal, we also have the problem of the waste of paper 
redisplaying the screen would create.

Why anyone would now be using such a terminal I do not know, but if we 
do not mention the proper way to use such a terminal, or not to use such 
a terminal at all, I'm sure someone will try it.

-- 
Omniflux




  parent reply	other threads:[~2005-08-12 22:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-21 12:38 x86 serial support Omniflux
2005-03-02 21:33 ` Yoshinori K. Okuji
2005-08-10  0:41   ` Omniflux
2005-08-12 10:51     ` Vladimir Serbinenko
2005-08-12 16:01     ` Marco Gerards
2005-08-12 20:17       ` Yoshinori K. Okuji
2005-08-12 22:19         ` Douglas Wade Needham
2005-08-12 22:18       ` Omniflux [this message]
2005-08-14 13:03         ` Marco Gerards
2005-08-14 14:54           ` Yoshinori K. Okuji
2005-09-03 17:08     ` Yoshinori K. Okuji
2005-09-03 23:12       ` Marco Gerards
2005-09-11 19:46         ` Yoshinori K. Okuji
2005-09-04  0:59       ` Omniflux
2005-09-11 19:52         ` Yoshinori K. Okuji

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=42FD2049.2050903@omniflux.com \
    --to=omniflux+lists@omniflux.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 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.