From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Detect key modifier status in 'sleep --interruptible'
Date: Mon, 24 Aug 2009 13:57:26 +0200 [thread overview]
Message-ID: <20090824115726.GA18956@thorin> (raw)
In-Reply-To: <20090824091109.GC11691@riva.ucam.org>
On Mon, Aug 24, 2009 at 10:11:10AM +0100, Colin Watson wrote:
> > But in at_keyboard it's definitely possible (check how we handle e.g. CTRL
> > or SHIFT keys).
>
> No, that code only spots make scan codes arriving after GRUB's terminal
> starts up. AFAICS it has no way to tell whether e.g. Shift was held down
> already when GRUB started
Ah, you're right on this..
> (except through the vagaries of key repeat),
..but on this too. Why not check for key repeat? The controller generates
them for all keys AFAIK.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2009-08-24 11:57 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 15:35 [PATCH] Detect key modifier status in 'sleep --interruptible' Colin Watson
2009-08-12 16:10 ` Vladimir 'phcoder' Serbinenko
2009-08-12 16:15 ` Vladimir 'phcoder' Serbinenko
2009-08-12 22:14 ` Colin Watson
2009-08-13 20:52 ` Robert Millan
2009-08-13 21:15 ` Colin Watson
2009-08-23 22:46 ` Vladimir 'phcoder' Serbinenko
2009-08-23 22:56 ` Robert Millan
2009-08-23 23:00 ` Vladimir 'phcoder' Serbinenko
2009-08-23 23:03 ` Robert Millan
2009-08-23 23:05 ` Vladimir 'phcoder' Serbinenko
2009-08-25 19:26 ` Robert Millan
2009-08-24 9:24 ` Colin Watson
2009-08-24 12:23 ` Robert Millan
2009-08-24 12:44 ` Robert Millan
2009-08-24 13:27 ` Colin Watson
2009-08-24 14:28 ` Robert Millan
2009-08-24 16:23 ` Colin Watson
2009-08-24 16:56 ` Colin Watson
2009-08-24 17:03 ` Colin Watson
2009-08-24 22:04 ` Colin Watson
2009-08-24 22:41 ` Robert Millan
2009-08-24 23:02 ` Colin Watson
2009-08-26 15:33 ` Colin Watson
2009-08-26 18:39 ` Robert Millan
2009-08-26 20:26 ` Colin Watson
2009-08-28 12:44 ` Robert Millan
2009-08-28 13:20 ` Colin Watson
2009-08-24 12:56 ` Robert Millan
2009-08-13 20:46 ` Robert Millan
2009-08-23 22:27 ` Robert Millan
2009-08-23 22:41 ` Vladimir 'phcoder' Serbinenko
2009-08-23 22:57 ` Robert Millan
2009-08-24 9:11 ` Colin Watson
2009-08-24 11:57 ` Robert Millan [this message]
2009-08-24 12:50 ` Vladimir 'phcoder' Serbinenko
2009-08-24 12:58 ` Michal Suchanek
2009-08-24 14:29 ` Robert Millan
2009-08-24 12:59 ` Colin Watson
2009-08-24 13:27 ` Robert Millan
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=20090824115726.GA18956@thorin \
--to=rmh@aybabtu.com \
--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.