From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Ozan Çağlayan" <ozan@pardus.org.tr>
Cc: Linux Input <linux-input@vger.kernel.org>, hal@lists.freedesktop.org
Subject: Re: ATKBD: adding force-release quirks
Date: Mon, 7 Dec 2009 20:24:49 -0800 [thread overview]
Message-ID: <20091208042448.GF11147@core.coreip.homeip.net> (raw)
In-Reply-To: <4B065F86.8070702@pardus.org.tr>
On Fri, Nov 20, 2009 at 11:21:10AM +0200, Ozan Çağlayan wrote:
> Dmitry Torokhov wrote:
> > Hi,
> >
> > It appears that more and more laptops do not send release events for
> > their multimedia keys requiring adding their DMI info to the atkbd
> > driver. I don't think we can continue this practice any longer and I
> > would like to punt this responsibility to HAL/DevKit/whatever. In 2.6.32
> > there will be a new sysfs attribute, force_release, attached to the
> > serio port that is bound to atkbd driver. Writing to that attribute will
> > allow setting a new bitmap for the keys that require forced release,
> > reading will produce current bitmap. The format as follows:
> >
> > echo 133-139,143,147 > /sys/devices/platform/i8042/serio0/force_release
> >
> >
>
> Is there currently any work for this support in udev/dk?
Johannes Stezenbach <js@sig21.net> started on adding this fucntionality
to udev.
--
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
prev parent reply other threads:[~2009-12-08 4:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 5:12 ATKBD: adding force-release quirks Dmitry Torokhov
2009-11-20 9:21 ` Ozan Çağlayan
2009-12-08 4:24 ` Dmitry Torokhov [this message]
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=20091208042448.GF11147@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=hal@lists.freedesktop.org \
--cc=linux-input@vger.kernel.org \
--cc=ozan@pardus.org.tr \
/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).