unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 35585@debbugs.gnu.org
Subject: bug#35585: GRUB does not work with USB keyboards when using keyboard-layout
Date: Tue, 7 May 2019 18:39:14 +0200	[thread overview]
Message-ID: <20190507183914.615660dc@scratchpost.org> (raw)
In-Reply-To: <87tve62qic.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]

Hi Ludo,

On Tue, 07 May 2019 18:11:55 +0200
Ludovic Courtès <ludo@gnu.org> wrote:

> > --- a/gnu/bootloader/grub.scm
> > +++ b/gnu/bootloader/grub.scm
> > @@ -360,7 +360,7 @@ entries corresponding to old generations of the system."
> >                               (keyboard-layout-file layout #:grub grub))))
> >            (when keymap
> >              (format port "\
> > -terminal_input at_keyboard
> > +terminal_input at_keyboard usb_keyboard  
> 
> What do others think?  Danny?
> 
> I’d like to make sure this is as harmless as it looks.

AT keyboard should also match USB bootp keyboards, but I guess the mac doesn't
support bootp.  (USB keyboards have a "bootloader" protocol (BOOTP) and
a "normal" protocol with the rationale being that the "normal" protocol is
too compliated to fit into the bootloader - hence, USB keyboard should support
both--and, when talked to using the bootloader protocol, the PC firmware should
transform it into AT keyboard commands in order to further simplify the
bootloader's job)

Why is it specified at all?  If it's not specified, it will default to
the "platform native" inputs which means the ones available in the source code
for that platform.  So aren't we complicating our life for no reason by
specifying it in the first place?

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-05-07 16:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-05 17:35 bug#35585: GRUB does not work with USB keyboards when using keyboard-layout pelzflorian (Florian Pelz)
2019-05-07 16:11 ` Ludovic Courtès
2019-05-07 16:39   ` Danny Milosavljevic [this message]
2019-05-07 22:09     ` pelzflorian (Florian Pelz)
2019-05-08 10:03     ` Ludovic Courtès
2019-05-08 12:23       ` pelzflorian (Florian Pelz)
2019-05-09 10:14         ` Ludovic Courtès
2019-05-09 12:52           ` Danny Milosavljevic
2019-05-13 13:59           ` Giovanni Biscuolo
2019-05-13 20:34             ` Ludovic Courtès
2019-05-07 17:25   ` pelzflorian (Florian Pelz)
2019-05-07 17:48     ` pelzflorian (Florian Pelz)

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=20190507183914.615660dc@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=35585@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 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).