From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 26334@debbugs.gnu.org
Subject: bug#26334: [PATCH 1/1] system: grub: Enable the use of a non-graphical GRUB menu.
Date: Sat, 1 Apr 2017 18:43:45 -0400 [thread overview]
Message-ID: <20170401224345.GA13129@jasmine> (raw)
In-Reply-To: <87wpb3g4f9.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]
On Sun, Apr 02, 2017 at 12:15:54AM +0200, Ludovic Courtès wrote:
> Would it be possible to detect whether graphical output is available
> only in GRUB code?
I'm far from a GRUB expert...
Apparently, the terminal input and output devices default to the
"platform's native terminal {input,output}":
https://www.gnu.org/software/grub/manual/html_node/Simple-configuration.html
> Or is the use case a situation where graphical output *is* supported
> but somehow undesirable?
Yes, that is a potential use case. For example, I have a system based on
an embedded system-on-a-chip that includes a GPU, but no physical video
ports; I must use the serial port.
I also have this use case on a laptop as a consequence of
<https://bugs.gnu.org/24948>.
For both of those systems, I've been using a different patch that
has the same effect on the generated grub.cfg.
Perhaps instead of a graphical? toggle, we could expose the different
values of GRUB_TERMINAL_OUTPUT and GRUB_TERMINAL_INPUT:
https://www.gnu.org/software/grub/manual/html_node/Simple-configuration.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-04-01 22:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-01 20:22 bug#26334: [PATCH 1/1] system: grub: Enable the use of a non-graphical GRUB menu Leo Famulari
2017-04-01 22:15 ` Ludovic Courtès
2017-04-01 22:43 ` Leo Famulari [this message]
2017-04-02 0:06 ` ng0
2017-04-01 23:16 ` Leo Famulari
2017-04-02 8:31 ` Ludovic Courtès
2017-04-02 8:34 ` Ludovic Courtès
2017-05-11 7:39 ` bug#26334: CLOSED " Leo Famulari
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=20170401224345.GA13129@jasmine \
--to=leo@famulari.name \
--cc=26334@debbugs.gnu.org \
--cc=ludo@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.