All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: The development of GNU GRUB <grub-devel@gnu.org>,
	Daniel Kiper <daniel.kiper@oracle.com>
Subject: Re: [PATCH 2/4] Accept Both ESC and F8 as user interrupt keys
Date: Wed, 28 Mar 2018 17:58:16 +0200	[thread overview]
Message-ID: <af2ee04f-be47-252b-9ab7-4b4a196e19b5@redhat.com> (raw)
In-Reply-To: <20180328151152.iat3ti3hxiehrreb@csclub.uwaterloo.ca>

Hi,

On 28-03-18 17:11, Lennart Sorensen wrote:
> On Wed, Mar 28, 2018 at 05:06:53PM +0200, Hans de Goede wrote:
>> Hmm, well people will still be able to use ESC to get the grub boot
>> menu, rather then the firmware boot-menu on those.
>>
>> The problem is that our current check for ESC only approach is problematic
>> because it conflicts with the enter firmware-setup key on almost all Bay Trail,
>> Cherry Trail and Apollo Lake devices. You need to try hard to find a device
>> in one of those 3 categories which does not use ESC for this. Note I'm
>> aware some devices exist, but using ESC for this is really really common
>> among these devices.
>>
>> I'm open to other suggestions, but I think we really need to add another
>> key to avoid the pressing ESC at boot already has another meaning problem
>> and F8 seems like an ok choice.
>>
>> Either way thank you for the input on this.
> 
> I don't disagree about having another key, I just disagree that F8 is
> a good choice.
> 
> Looking at https://kb.wisc.edu/page.php?id=58779#here it appears no one
> uses F4 for anything.  That would seem like a better choice than F8
> at least.  F6 also seems to be free but F4 seems nicer on desktop
> keyboards.

Looking at that table I have to agree that F4 seems like the best second
key to use. Actually looking at that table ESC seems like a poor choice,
but I guess it makes sense for serial-terminals as well as from a general
UI pov (and we're stuck with it now anyways).

I'm going to wait for Daniel's review of the other patches before I do
a v2 of this patch-set. I will switch to F4 for v2.

Regards,

Hans



  reply	other threads:[~2018-03-28 15:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-28 14:50 [PATCH 0/4] Make hidden menu really hidden Hans de Goede
2018-03-28 14:50 ` [PATCH 1/4] Add new "version" command Hans de Goede
2018-03-29  7:53   ` Olaf Hering
2018-03-29  8:37     ` Thomas Schmitt
2018-03-29 14:57     ` Hans de Goede
2018-03-29 15:02       ` Olaf Hering
2018-04-05 11:41   ` Daniel Kiper
2018-03-28 14:50 ` [PATCH 2/4] Accept Both ESC and F8 as user interrupt keys Hans de Goede
2018-03-28 14:56   ` Lennart Sorensen
2018-03-28 15:06     ` Hans de Goede
2018-03-28 15:11       ` Lennart Sorensen
2018-03-28 15:58         ` Hans de Goede [this message]
2018-04-05 11:47           ` Daniel Kiper
2018-03-28 14:50 ` [PATCH 3/4] Optionally print less messages at boot Hans de Goede
2018-04-05 12:12   ` Daniel Kiper
2018-04-05 17:53     ` Hans de Goede
2018-04-06 11:41       ` Daniel Kiper
2018-03-28 14:50 ` [PATCH 4/4] EFI: Do not set text-mode until we actually need it Hans de Goede
2018-04-05 12:34   ` Daniel Kiper
2018-04-05 18:05     ` Hans de Goede
2018-04-06 11:44       ` Daniel Kiper
2018-03-28 15:04 ` [PATCH 0/4] Make hidden menu really hidden Daniel Kiper

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=af2ee04f-be47-252b-9ab7-4b4a196e19b5@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=daniel.kiper@oracle.com \
    --cc=grub-devel@gnu.org \
    --cc=lsorense@csclub.uwaterloo.ca \
    /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.