X86 platform drivers
 help / color / mirror / Atom feed
From: Dana Goyette <danagoyette@gmail.com>
To: platform-driver-x86 <platform-driver-x86@vger.kernel.org>
Subject: Re: [PATCH] platform/x86: hp-wmi: Add support for home in HP OMEN laptops
Date: Fri, 27 Nov 2020 18:19:46 -0800	[thread overview]
Message-ID: <b8c32747-2704-8a2d-dc32-b6154128d295@gmail.com> (raw)
In-Reply-To: <cad5f2ab-e319-b6fd-360d-5beb62d6899f@redhat.com>

On 9/26/20 3:47 AM, Hans de Goede wrote:>
> So after looking at:
>
 > 
http://s3.amazonaws.com/digitaltrends-uploads-prod/2017/09/HP-Omen-15-review-keyboard-2.jpg 

>
>
> I understand what you mean with "where home key should be". So I've been
> thinking
> a bit about what is the best thing to do here. Arguably mapping it to
> KEY_CONTROLPANEL would be more accurate. But I can completely understand
> how
> you just want to have a working "home" key; and it indeed is in the place
> where on HP laptop keyboards with a num-pad, you would expect the > home key.
>
> So lets just map it to KEY_HOME as you suggest:
>
> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
>
> Regards,
>
> Hans
>
>
>

FYI, the HP Omen 15 2020 has a different keyboard, where Home is a 
proper separate key.  The India model has yet another layout, with a 
full numeric keypad that also includes Home.  So unless we want to get 
into DMI matching, it's safest to map the key to something distinct.

Layout on the US model:

[Omen]   [Calc] [PrtScr]
[Insert] [Home] [PgUp]
[Pause]  [End]  [PgDn]

Layout on the India model:
[Omen]    [Calc] [Insert] [PrtScr]
[NumLock] [/]    [*]      [-]
[7/Home]  [8]    [9/PgUp] [+]

(Where's Delete?  Above Backspace.)

  reply	other threads:[~2020-11-28  2:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <174c79fb794.120dada4b39603.5369737602791060462@sidsun.com>
2020-09-26 10:47 ` [PATCH] platform/x86: hp-wmi: Add support for home in HP OMEN laptops Hans de Goede
2020-11-28  2:19   ` Dana Goyette [this message]
2020-11-28  2:55     ` Dana Goyette
2020-11-28 11:13       ` Hans de Goede
2020-11-29  5:38         ` Dana Goyette
2020-11-29 12:09           ` Hans de Goede

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=b8c32747-2704-8a2d-dc32-b6154128d295@gmail.com \
    --to=danagoyette@gmail.com \
    --cc=platform-driver-x86@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