From mboxrd@z Thu Jan 1 00:00:00 1970 From: Samuel Thibault Subject: Re: [PATCH] Console keyboard events and accessibility Date: Sat, 1 Sep 2007 14:26:04 +0200 Message-ID: <20070901122604.GA3251@implementation.famille.thibault.fr> References: <20070821005718.GD3658@interface.famille.thibault.fr> <20070821204951.GC3658@interface.famille.thibault.fr> <20070712191932.GA3947@ucw.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <20070712191932.GA3947@ucw.cz> Sender: owner-linux-input@atrey.karlin.mff.cuni.cz List-Help: List-Owner: List-Post: List-Unsubscribe: To: Pavel Machek Cc: Jan Engelhardt , linux-input@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org, akpm@linux-foundation.org, dtor@mail.ru List-Id: linux-input@vger.kernel.org Pavel Machek, le Thu 12 Jul 2007 19:19:32 +0000, a =E9crit : > On Tue 2007-08-21 22:49:51, Samuel Thibault wrote: > > Hi, > >=20 > > Jan Engelhardt, le Tue 21 Aug 2007 22:42:24 +0200, a =E9crit : > > > >- keycodes: even before translation into keysym. > > >=20 > > > They can use the raw xlation for that. > >=20 > > For userland, yes. This is for kernel modules. >=20 > And should speakup be a kernel module? Why? Because userland only begins quite late in the boot process, and userland may hang. > What is missing? Yes, you may want to do a small kernel module to read > kernel bootup messages. That's what it's all about. Samuel