Re: Hotkeys generating input as well as ACPI events

Re: Hotkeys generating input as well as ACPI events

[Corentin Chary]

On Wed, Apr 14, 2010 at 8:34 AM, Trent W. Buck <twb-3AaVwj9c10wJYc8buCWFOBCuuivNXqWP@public.gmane.org> wrote:
> Corentin Chary <corentin.chary-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> writes:
>
>> All seems ok and I was able to reproduce the issue (only in screen),
>
> Hmm; I can also reproduce this as root on vt2, without screen.  It's
> more obvious if I run "cat -A" before typing; otherwise I only see a ~
> and hear a beep.
>
>> but I don't really know what's the best way to fix it.
>> Isn't there any way to "ignore" an input device in screen/fbcon ?
>
> I don't know.  I guess that would be disconnecting
>
>    /sys/devices/platform/eeepc/input/input8
>    i.e. SUBSYSTEM=="input", NAME=="Asus EeePC extra buttons"
>
> ...from fbcon.  Obviously I don't want to disable the ACPI events, nor
> the normal keyboard input.  I'll try to find an fbcon guru.
>
> I might be able to patch terminfo/termcap entries to discard those
> escape sequences, but it feels like a bodge.
>

If there is no way to ignore an input device in userspace, maybe the
right way to do it is to add a way to disable an input device using
some /sys/ file.

CC-ing linux-input, they probably have something to tell about that.

-- 
Corentin Chary
http://xf.iksaif.net

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev

Re: [Acpi4asus-user] Hotkeys generating input as well as ACPI events

[Dmitry Torokhov]

On Wed, Apr 14, 2010 at 09:11:24AM +0200, Corentin Chary wrote:
> On Wed, Apr 14, 2010 at 8:34 AM, Trent W. Buck <twb@cybersource.com.au> wrote:
> > Corentin Chary <corentin.chary@gmail.com>
> > writes:
> >
> >> All seems ok and I was able to reproduce the issue (only in screen),
> >
> > Hmm; I can also reproduce this as root on vt2, without screen.  It's
> > more obvious if I run "cat -A" before typing; otherwise I only see a ~
> > and hear a beep.
> >
> >> but I don't really know what's the best way to fix it.
> >> Isn't there any way to "ignore" an input device in screen/fbcon ?
> >
> > I don't know.  I guess that would be disconnecting
> >
> >    /sys/devices/platform/eeepc/input/input8
> >    i.e. SUBSYSTEM=="input", NAME=="Asus EeePC extra buttons"
> >
> > ...from fbcon.  Obviously I don't want to disable the ACPI events, nor
> > the normal keyboard input.  I'll try to find an fbcon guru.
> >
> > I might be able to patch terminfo/termcap entries to discard those
> > escape sequences, but it feels like a bodge.
> >
> 
> If there is no way to ignore an input device in userspace, maybe the
> right way to do it is to add a way to disable an input device using
> some /sys/ file.
> 
> CC-ing linux-input, they probably have something to tell about that.
> 

I'd say kernel should settle on the delivery transport and simply not
use both.

-- 
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html