From: Robert Millan <rmh@aybabtu.com>
To: grub-devel@gnu.org
Cc: Junichi Uekawa <dancer@netfort.gr.jp>,
429695-forwarded@bugs.debian.org, 429695@bugs.debian.org
Subject: Fwd: Bug#429695: grub-efi: key combinations requiring ctrl do not work
Date: Wed, 20 Jun 2007 15:02:53 +0200 [thread overview]
Message-ID: <20070620130253.GA24431@aragorn> (raw)
In-Reply-To: <87lkegm2ja.dancerj%dancer@netfort.gr.jp>
On Tue, Jun 19, 2007 at 11:39:37PM +0900, Junichi Uekawa wrote:
> Package: grub-efi
> Version: 1.95+20070604-1
>
>
> Hi,
>
> This is a reminder of the bug that upstream also acknowledges, but I
> think it needs to be noted down in order to get grub-efi to be usable
> in prime-time.
>
> grub-efi does not accept ctrl-{character} keys. Since grub2 requires
> ctrl-{character} keys in editing menus (except for the 'escape' and
> enter and up / down) you can't really do too many useful things.
>
> I think either of the following needs to happen
>
> 1. key needs to be remapped
> 2. get ctrl key to start working.
Upstream acknowledges this bug in http://grub.enbug.org/TestingOnEFI and
says:
"[..] I guess I should write my own keyboard driver for EFI and replace the
standard buggy driver."
There's a SoC contributor in the process of writing an AT keyboard driver
as part of the LinuxBIOS/grub2 integration project.
Is it possible that this code can be reused for EFI? Or does EFI block access
to keyboard controller completely?
--
Robert Millan
My spam trap is honeypot@aybabtu.com. Note: this address is only intended
for spam harvesters. Writing to it will get you added to my black list.
next parent reply other threads:[~2007-06-20 13:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87lkegm2ja.dancerj%dancer@netfort.gr.jp>
2007-06-20 13:02 ` Robert Millan [this message]
2007-06-23 20:35 ` Fwd: Bug#429695: grub-efi: key combinations requiring ctrl do not work Yoshinori K. Okuji
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=20070620130253.GA24431@aragorn \
--to=rmh@aybabtu.com \
--cc=429695-forwarded@bugs.debian.org \
--cc=429695@bugs.debian.org \
--cc=dancer@netfort.gr.jp \
--cc=grub-devel@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.
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.