linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Nagy <public@stefan-nagy.at>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev: Please add keymap for HP Chromebook 14 (Falco)
Date: Mon, 27 Jan 2014 18:20:58 +0000	[thread overview]
Message-ID: <1390846858.6102.7.camel@rosa> (raw)
In-Reply-To: <20140127080821.GB3117@piware.de>

Hi Martin,

Am Montag, den 27.01.2014, 09:08 +0100 schrieb Martin Pitt:

> Thanks for your keymap! I translated it to the current hwdb format
> that systemd uses these days, and committed:
> 
>   http://cgit.freedesktop.org/systemd/systemd/commit/?id‚cd413782

Great, thanks!

> > Two entries in the key mapping are commented out:
> > 
> > 1. 0x3D refresh (?)
> > -> In this case I'm not sure this is the correct KEY_XXXXX constant
> > since it won't work as expected in Iceweasel (I'm running Debian
> > Jessie), though in nautilus it works as expected…
> 
> I commented that back in. On all screenshots of the keyboard that I
> found it does look like a "refresh/reload" key (circular arrow), and
> that seems to be the best match. Of course it's entirely possible that
> some applications don't support that key, but hopefully some do.

OK, maybe I'll file a bug against firefox/iceweasel.

> > 2. 0x3E fullscreen (?)
> > -> In this case I couldn't find a KEY_XXXXX constant which provides
> > the desired functionality. I hope someone can help me out here.
> 
> Indeed there is no such key symbol, so I left it commented out.

Is there any chance this key will work as expected in the future?

> > AFAIK the intended purpose of the key in ChromeOS is to refresh
> > websites in the Chrome browser.
> 
> I guess that applied to the "refresh" key, no the fullscreen key?

Yes, sorry…

Thanks,
Stefan.


  reply	other threads:[~2014-01-27 18:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-27  8:08 udev: Please add keymap for HP Chromebook 14 (Falco) Martin Pitt
2014-01-27 18:20 ` Stefan Nagy [this message]
2014-01-28  7:44 ` 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=1390846858.6102.7.camel@rosa \
    --to=public@stefan-nagy.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).