From: Vojtech Pavlik <vojtech@suse.cz>
To: Nigel Cunningham <ncunningham@clear.net.nz>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: drivers/char/keyboard.c now unused?
Date: Fri, 31 Jan 2003 18:55:58 +0100 [thread overview]
Message-ID: <20030131185558.A25927@ucw.cz> (raw)
In-Reply-To: <1043894474.1623.6.camel@laptop-linux.cunninghams>; from ncunningham@clear.net.nz on Thu, Jan 30, 2003 at 03:41:15PM +1300
On Thu, Jan 30, 2003 at 03:41:15PM +1300, Nigel Cunningham wrote:
> Hi all.
>
> I've been doing some work on porting my patches to the 2.4 version of
> software suspend to 2.5. Under 2.4, I use the shift_state variable from
> drivers/char/keyboard.c to provide interactive, step-by-step progression
> through the process. That is, there is an option for you to be able to
> press and release shift before the next stage starts. With the new input
> layer, drivers/char/keyboard.c still exists, but seems to be unused. Can
> I get confirmation that my understand is correct, and (if possible) a
> pointer to information on how I can reimplement the functionality under
> 2.5?
Your understanding is not correct, and drivers/char/keyboard.c is very
much used for all keyboard input in 2.5.
> Oh and before anyone has a hernia, I'm not intending to leave this
> functionality in the final version - its just for debugging purposes.
>
> Thanks in advance,
>
> Nigel
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Vojtech Pavlik
SuSE Labs
prev parent reply other threads:[~2003-01-31 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-30 2:41 drivers/char/keyboard.c now unused? Nigel Cunningham
2003-01-30 3:27 ` Valdis.Kletnieks
2003-01-31 17:55 ` Vojtech Pavlik [this message]
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=20030131185558.A25927@ucw.cz \
--to=vojtech@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@clear.net.nz \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox