GNU bug report logs - #35585
GRUB does not work with USB keyboards when using keyboard-layout

Previous Next

Full log

Message #11 received at 35585 <at> debbugs.gnu.org (full text, mbox):

From: Danny Milosavljevic <dannym <at> scratchpost.org>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 35585 <at> debbugs.gnu.org,
 "pelzflorian \(Florian Pelz\)" <pelzflorian <at> pelzflorian.de>
Subject: Re: bug#35585: GRUB does not work with USB keyboards when using
 keyboard-layout
Date: Tue, 7 May 2019 18:39:14 +0200

[Message part 1 (text/plain, inline)]

Hi Ludo,

On Tue, 07 May 2019 18:11:55 +0200
Ludovic Courtès <ludo <at> 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?

[Message part 2 (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.