Linux Input/HID development
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Ignacy Gawędzki" <bugs@qult.net>
Cc: Mario Limonciello <Mario_Limonciello@dell.com>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: Re: Dell XPS 13 Fn key bug?
Date: Thu, 2 Feb 2017 08:47:48 -0800	[thread overview]
Message-ID: <20170202164748.GB21924@dtor-ws> (raw)
In-Reply-To: <20170202084033.76d6youemdr2pc5f@zenon.in.qult.net>

On Thu, Feb 02, 2017 at 09:40:33AM +0100, Ignacy Gawędzki wrote:
> On Wed, Feb 01, 2017 at 04:16:13PM -0800, thus spake Dmitry Torokhov:
> > OK, so 'cd' is scancode for KEY_RIGHT and 'cf' is scancode for
> > KEY_END, and it seems that implementation of FN handling is very naive
> > as it emits "release" keycodes for the state FN is currently in, not
> > the state it was when key was pressed.
> > 
> > Ideally Dell would fix that. Mario, any chance of that?
> 
> I'm just wondering whether this is still something that could be fixed
> or worked around in the input driver,

Well, obviously I'd rather fix the bug at its root rather than piling
workarounds in the driver.

> since the bug obviously doesn't
> show up in neither in the linux console nor in Windows.

So where does it not work in Linux? Because keyboard driver in console
and elsewhere is the same. Maybe it is not noticeable when in text
console?

In Windows the bug might be masked if they use hardware autorepeat for
PS/2 keyboards. I don't know if they do or not.

Thanks.

-- 
Dmitry

  reply	other threads:[~2017-02-02 16:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-25  8:47 Dell XPS 13 Fn key bug? Ignacy Gawędzki
2017-02-02  0:16 ` Dmitry Torokhov
2017-02-02  8:40   ` Ignacy Gawędzki
2017-02-02 16:47     ` Dmitry Torokhov [this message]
2017-02-02 17:08       ` Ignacy Gawędzki
2017-02-02 17:15         ` Mario.Limonciello
2017-02-02 17:50           ` Ignacy Gawędzki
2017-02-02 19:53             ` Mario.Limonciello

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=20170202164748.GB21924@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=Mario_Limonciello@dell.com \
    --cc=bugs@qult.net \
    --cc=linux-input@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