linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Pitt <martin.pitt@ubuntu.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] keymap: support for force_release quirk
Date: Mon, 14 Dec 2009 13:32:45 +0000	[thread overview]
Message-ID: <20091214133245.GB2039@piware.de> (raw)
In-Reply-To: <20091214001219.GA17792@sig21.net>

Johannes Stezenbach [2009-12-14 13:55 +0100]:
> 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)?

No, please don't; such external state keeping is very ugly and error
prone IMHO, and not what udev is designed to do. I rather think we
should do one of:

(1) Demand to have complete force-release tables, and completely
    reset the value with each invocation of the udev rule.

    Pro: Can remove values
    Con: Hard to just fix a single key

(2) Only ever add new values by reading the current value, appending
    our tables, and writing it back.

    Pro: Can fix single keys and potentially simplifies rules
    Con: Needs reboot for bad tables which set quirk erroneously

I suppose that on computers which need these quirks, all Fn keys are
affected equally, so the "fix single key" case is probably irrelevant.
OTOH, I don't think we'll get too many errors like "erroneous quirk",
so both approaches should work well in practice.

Personally I tend to prefer (2).

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

Fixed in git, thanks for pointing out.

Martin

-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

      parent reply	other threads:[~2009-12-14 13:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-14  0:12 [PATCH] keymap: support for force_release quirk Johannes Stezenbach
2009-12-14  9:14 ` Martin Pitt
2009-12-14 10:28 ` Johannes Stezenbach
2009-12-14 10:34 ` Kay Sievers
2009-12-14 12:37 ` Johannes Stezenbach
2009-12-14 12:45 ` Martin Pitt
2009-12-14 12:50 ` Kay Sievers
2009-12-14 12:55 ` Johannes Stezenbach
2009-12-14 13:32 ` Martin Pitt [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=20091214133245.GB2039@piware.de \
    --to=martin.pitt@ubuntu.com \
    --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).