linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Clemens Buchacher <drizzd@aon.at>
To: linux-hotplug@vger.kernel.org
Subject: Re: Bug#561711: udev: Samsung R70/R71 keymap
Date: Mon, 04 Jan 2010 16:18:51 +0000	[thread overview]
Message-ID: <20100104161851.GA3758@localhost> (raw)
In-Reply-To: <20091219195300.GA19984@bongo.bofh.it>

Hi,

Please add me to Cc. I did not receive any notification about my bug report
and I'm responding now only because I found this in the list archives by
accident.

On Mon, Dec 21, 2009 at 09:25:40AM +0100, Martin Pitt wrote:

> > Fn+F5 (blank screen) and Fn+F8 still do not generate events after
> > this change, howver.
> 
> Seems worth exercising README.keymap.txt for those two then?

/lib/udev/keymap correctly reported the keypress events, but xev did not.
echo 166-245 > /sys/devices/platform/i8042/serio0/force_release finally
fixed the problem. Is there any way to diagnose this issue without trial and
error? Maybe we should include a hint in README.keymap.txt.

It was a real pain to debug this, especially since I didn't even know where
to look, and google returns tons of misleading bug reports concering hal.
I'm afraid README.keymap.txt is the last place that people find. I have no
idea what to do about it though.

I suppose something like the following patch should fix the problem
permanently. Unfortunately, I was unable to test this, because the debian
package would not build with the new source code (rejected patches and other
issues), and after installing udev from git the kernel hangs at boot,
without leaving any traces in syslog.

Cheers,
Clemens

--o<--
Subject: [PATCH] keymap: add Samsung R70/R71 force-release rule


Signed-off-by: Clemens Buchacher <drizzd@aon.at>
---
 extras/keymap/95-keyboard-force-release.rules |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/extras/keymap/95-keyboard-force-release.rules b/extras/keymap/95-keyboard-force-release.rules
index 4d0a877..25bced6 100644
--- a/extras/keymap/95-keyboard-force-release.rules
+++ b/extras/keymap/95-keyboard-force-release.rules
@@ -19,6 +19,6 @@ DRIVER!="atkbd", GOTO="force_release_end"
 ENV{DMI_VENDOR}="$attr{[dmi/id]sys_vendor}"
 
 
-ENV{DMI_VENDOR}="[sS][aA][mM][sS][uU][nN][gG]*", ATTR{[dmi/id]product_name}="*N130*", RUN+="keyboard-force-release.sh $devpath samsung-other"
+ENV{DMI_VENDOR}="[sS][aA][mM][sS][uU][nN][gG]*", ATTR{[dmi/id]product_name}="*N130*|*SR70S/SR71S*", RUN+="keyboard-force-release.sh $devpath samsung-other"
 
 LABEL="force_release_end"
-- 
1.6.6.274.gdcca7


  parent reply	other threads:[~2010-01-04 16:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-19 19:53 Bug#561711: udev: Samsung R70/R71 keymap Marco d'Itri
2009-12-21  8:25 ` Martin Pitt
2010-01-04 16:18 ` Clemens Buchacher [this message]
2010-01-05  8:58 ` Martin Pitt
2010-01-05 15:51 ` Clemens Buchacher
2010-01-05 15:57 ` Martin Pitt

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=20100104161851.GA3758@localhost \
    --to=drizzd@aon.at \
    --cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).