From mboxrd@z Thu Jan  1 00:00:00 1970
From: Johannes Stezenbach <js@sig21.net>
Date: Mon, 14 Dec 2009 12:55:07 +0000
Subject: Re: [PATCH] keymap: support for force_release quirk
Message-Id: <20091214125507.GA29808@sig21.net>
List-Id: <linux-hotplug.vger.kernel.org>
References: <20091214001219.GA17792@sig21.net>
In-Reply-To: <20091214001219.GA17792@sig21.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: linux-hotplug@vger.kernel.org

Hello Martin,

On Mon, Dec 14, 2009 at 01:45:43PM +0100, Martin Pitt wrote:
> Johannes Stezenbach [2009-12-14 13:37 +0100]:
> 
> > However, what does not work this way is to remove scancodes from
> > force_release. I thought that was what Martin wanted to accomplish
> > on the "change" event.
> 
> Hm, it seems to work just fine here:
> 
> $ echo 133 | sudo tee /sys/devices/platform/i8042/serio0/force_release133
> $ cat /sys/devices/platform/i8042/serio0/force_release
> 133
> 
> So it seems every time you write the file you have to do it completely
> (or read the original one).

Yes, that was my question: Can I just save the original at boot
(first "add" event) into a file (like /dev/.udev/force-release/serioX)?

> So I think your approach is fine after all, and we just need the other
> small cleanups.

Yes, will resend a cleaned up patch asap.


BTW, 95-keymap.rules also doesn't handle "change". Does it need updating
or is there a difference in handling "change" for force_release?


Thanks,
Johannes