From: Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>
To: linux-kernel@vger.kernel.org
Subject: Re: keyboard - was: Re: Linux 2.6.0-test4
Date: Tue, 2 Sep 2003 14:32:52 +0200 [thread overview]
Message-ID: <20030902123252.GC22365@charite.de> (raw)
In-Reply-To: <20030902124717.B1221@pclin040.win.tue.nl>
* Andries Brouwer <aebr@win.tue.nl>:
> Yesterday's data sufficed, and I suppose the patch I gave solves
> this problem.
Nope. I applied the patch and rebuilt the kernel and rebooted.
Linux version 2.6.0-test4-bk2 (root@hummus2) (gcc version 3.2.3 (Debian)) #1 Tue Sep 2 11:45:23 CEST 2003
shows that the kernel I build this moring is actually running.
Right now, my CTRL key is totally "stuck" on the fbconsole. I can't
release it, not even by switching between the consoles and/or X11.
But now I don't get any messages like the one below (yes, the special
code generating this output is still active...)
> > atkbd.c: Unknown key (set 2, scancode 0x9c, on isa0060/serio0) pressed.
> > i8042 history: e0 d0 1c 9c 2e ae 10 90 e0 50 e0 d0 e0 d0 1c 9c
--
Ralf Hildebrandt (Im Auftrag des Referat V a) Ralf.Hildebrandt@charite.de
Charite Campus Mitte Tel. +49 (0)30-450 570-155
Referat V a - Kommunikationsnetze - Fax. +49 (0)30-450 570-916
AIM: ralfpostfix
-
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/
* Andries Brouwer <aebr@win.tue.nl>:
> Yesterday's data sufficed, and I suppose the patch I gave solves
> this problem.
Nope. I applied the patch and rebuilt the kernel and rebooted.
Linux version 2.6.0-test4-bk2 (root@hummus2) (gcc version 3.2.3 (Debian)) #1 Tue Sep 2 11:45:23 CEST 2003
shows that the kernel I build this moring is actually running.
Right now, my CTRL key is totally "stuck" on the fbconsole. I can't
release it, not even by switching between the consoles and/or X11.
But now I don't get any messages like the one below (yes, the special
code generating this output is still active...)
> > atkbd.c: Unknown key (set 2, scancode 0x9c, on isa0060/serio0) pressed.
> > i8042 history: e0 d0 1c 9c 2e ae 10 90 e0 50 e0 d0 e0 d0 1c 9c
--
Ralf Hildebrandt (Im Auftrag des Referat V a) Ralf.Hildebrandt@charite.de
Charite Campus Mitte Tel. +49 (0)30-450 570-155
Referat V a - Kommunikationsnetze - Fax. +49 (0)30-450 570-916
AIM: ralfpostfix
next prev parent reply other threads:[~2003-09-02 12:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-31 16:22 Re:Re: Linux 2.6.0-test4 Chris Heath
2003-09-01 16:01 ` Ralf Hildebrandt
2003-09-02 0:16 ` [PATCH] keyboard - was: " Andries Brouwer
2003-09-02 5:39 ` Ralf Hildebrandt
2003-09-02 8:07 ` Ralf Hildebrandt
2003-09-02 10:47 ` keyboard - was: " Andries Brouwer
2003-09-02 11:18 ` Ralf Hildebrandt
2003-09-02 12:32 ` Ralf Hildebrandt [this message]
2003-09-02 21:41 ` Andries Brouwer
2003-09-03 7:45 ` Ralf Hildebrandt
2003-09-03 13:25 ` Ralf Hildebrandt
-- strict thread matches above, loose matches on Subject: below --
2003-09-04 4:09 Chris Heath
2003-09-04 20:48 ` Jamie Lokier
2003-09-04 22:34 ` Andries Brouwer
2003-09-04 23:00 ` Jamie Lokier
2003-09-05 0:19 ` Andries Brouwer
2003-09-05 3:41 ` Chris Heath
2003-09-05 10:08 ` Andries Brouwer
2003-09-05 13:46 Norman Diamond
2003-09-05 14:57 John Bradford
2003-09-05 23:45 ` Andries Brouwer
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=20030902123252.GC22365@charite.de \
--to=ralf.hildebrandt@charite.de \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox