From: Skip Ford <skip.ford@verizon.net>
To: James Simmons <jsimmons@transvirtual.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux console project <linuxconsole-dev@lists.sourceforge.net>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [PATCH] New Console system BK
Date: Mon, 1 Jul 2002 20:11:28 -0400 [thread overview]
Message-ID: <afqqrm$7f8$2@main.gmane.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0207011232450.27788-100000@www.transvirtual.com>; from jsimmons@transvirtual.com on Mon, Jul 01, 2002 at 12:52:00PM -0700
James Simmons wrote:
>
> Since 2.5.1 I have placed into the kernel part of the new console system
> code into the DJ tree. So it has been well tested. I was hoping to have
> all the keyboard devices ported over to the input api and the fbdev
> drivers over to the new api. Unfortunely due to time restraints this will
> not be the case. So here goes the first installment of the new console
> system. Please test it yourselves and I will push it to Linus soon.
>
> http://www.transvirtual.com/~jsimmons/console.diff.gz
With your patch, I have to release the alt key between Fx keys to change
VTs. Is that intentional?
Without the patch, I can hold down alt and hit F1, F2, F3, F4, then
release the alt key and I will have switched to each of the VTs.
With this patch, I have to press/release alt for each Fx key.
--
Skip
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next parent reply other threads:[~2002-07-02 0:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0207011232450.27788-100000@www.transvirtual.com>
2002-07-02 0:11 ` Skip Ford [this message]
[not found] ` <200207020011.g620BTZ9000182@pool-141-150-241-241.delv.east.verizon.net>
2002-07-03 15:38 ` [PATCH] New Console system BK Dave Jones
2002-07-03 18:55 ` James Simmons
2002-07-01 19:52 James Simmons
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='afqqrm$7f8$2@main.gmane.org' \
--to=skip.ford@verizon.net \
--cc=jsimmons@transvirtual.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxconsole-dev@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).