From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: x86 serial support
Date: Sun, 11 Sep 2005 21:52:49 +0200 [thread overview]
Message-ID: <200509112152.49770.okuji@enbug.org> (raw)
In-Reply-To: <431A46E8.3030308@omniflux.com>
On Sunday 04 September 2005 02:59 am, Omniflux wrote:
> Option 'a' is certainly the easiest, but how do I choose which terminals
> to support? How do I test them?
Having a static table (for all terminals) is clearly nonsense for tparm.c,
since the purpose of this file is to interpret a terminfo file. If we embed
binary code, there is no reason to have such interpretation code.
> Option 'b', choosing which terminals and testing them is no longer my
> problem, but this moves all the burden onto the user.
I think you know this, but GRUB Legacy uses this way. For now, I think this is
the best way, since most terminals are vt100-compatible, and the user does
not have to do anything in this case.
> Option 'c', problems as listed above.
For me, this sounds overkill.
Okuji
prev parent reply other threads:[~2005-09-11 20:00 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
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 [this message]
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=200509112152.49770.okuji@enbug.org \
--to=okuji@enbug.org \
--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.