From: Corentin Chary <corentin.chary-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "Trent W. Buck" <twb-3AaVwj9c10wJYc8buCWFOBCuuivNXqWP@public.gmane.org>
Cc: debian-eeepc-devel-XbBxUvOt3X2LieD7tvxI8l/i77bcL1HB@public.gmane.org,
acpi4asus-user-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Hotkeys generating input as well as ACPI events
Date: Wed, 14 Apr 2010 09:11:24 +0200 [thread overview]
Message-ID: <s2x71cd59b01004140011jc2416c14x259627e278c6a162@mail.gmail.com> (raw)
In-Reply-To: <87pr22o83t.fsf-3AaVwj9c10wJYc8buCWFOBCuuivNXqWP@public.gmane.org>
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® 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
next parent reply other threads:[~2010-04-14 7:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87vdbvvbp8.fsf@cybersource.com.au>
[not found] ` <g2j71cd59b01004130512ydcecbbf9n5a8c5e271881d080@mail.gmail.com>
[not found] ` <87633uq0oz.fsf@cybersource.com.au>
[not found] ` <r2z71cd59b01004132314r6fdbbd63r3fba622d1c6f105f@mail.gmail.com>
[not found] ` <87pr22o83t.fsf@cybersource.com.au>
[not found] ` <87pr22o83t.fsf-3AaVwj9c10wJYc8buCWFOBCuuivNXqWP@public.gmane.org>
2010-04-14 7:11 ` Corentin Chary [this message]
2010-04-14 22:11 ` [Acpi4asus-user] Hotkeys generating input as well as ACPI events Dmitry Torokhov
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=s2x71cd59b01004140011jc2416c14x259627e278c6a162@mail.gmail.com \
--to=corentin.chary-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=acpi4asus-user-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=debian-eeepc-devel-XbBxUvOt3X2LieD7tvxI8l/i77bcL1HB@public.gmane.org \
--cc=linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=twb-3AaVwj9c10wJYc8buCWFOBCuuivNXqWP@public.gmane.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;
as well as URLs for NNTP newsgroup(s).