From: Leo Famulari <leo@famulari.name>
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: 26875-done@debbugs.gnu.org
Subject: bug#26875: [v2] system: grub: Expose GRUB's interactive interface settings.
Date: Sun, 14 May 2017 14:17:52 -0400 [thread overview]
Message-ID: <20170514181752.GA19688@jasmine> (raw)
In-Reply-To: <87efvr99cf.fsf@gmail.com>
On Sun, May 14, 2017 at 09:38:24AM +0200, Mathieu Othacehe wrote:
>
> > Mathieu: is it OK to apply this before the patch series on non-GRUB
> > bootloaders?
>
> Yes no problem !
Awesome! Pushed as e0b2e93005188ab4d6c7413a27832ba2fb7388e8.
> This doesn't seems to difficult to rebase on top of my
> serie. I guess "serial-unit" and "serial-speed" could fit in generic
> "bootloader-configuration". I'm not sure for "terminal_inputs/outputs"
> that seem grub specific.
Yes, the serial-unit (aka COM port) and serial-speed seem generically
useful on their own, as long you take care to handle the different
numbering between GRUB's serial-unit (zero indexed) and the COM port
numbering (indexed from 1).
The terminal inputs and outputs are generic only at the highest level.
At least, the choice between a graphical and text / curses interface
seeems universal. But of course other bootloader implementations will
support their own set of interfaces, and they may require extra
configuration.
next prev parent reply other threads:[~2017-05-14 18:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 7:36 bug#26875: Non-graphical (and other types) of GRUB interfaces Leo Famulari
2017-05-11 7:46 ` ng0
2017-05-13 5:15 ` Leo Famulari
2017-05-13 5:21 ` bug#26875: [v2] system: grub: Expose GRUB's interactive interface settings Leo Famulari
2017-05-13 13:51 ` Ludovic Courtès
2017-05-13 16:40 ` Leo Famulari
2017-05-14 7:38 ` Mathieu Othacehe
2017-05-14 18:17 ` Leo Famulari [this message]
2017-05-15 9:36 ` bug#26875: Non-graphical (and other types) of GRUB interfaces Brendan Tildesley
2017-05-15 18:04 ` Leo Famulari
2017-05-15 20:25 ` 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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170514181752.GA19688@jasmine \
--to=leo@famulari.name \
--cc=26875-done@debbugs.gnu.org \
--cc=m.othacehe@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).