mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alex Dewar <alex.dewar@gmx.co.uk>
To: "Lopez, Jorge A (Security)" <jorge.lopez2@hp.com>,
	Hans de Goede <hdegoede@redhat.com>,
	"dmitry.torokhov@gmail.com" <dmitry.torokhov@gmail.com>,
	"tiwai@suse.de" <tiwai@suse.de>,
	"markgross@kernel.org" <markgross@kernel.org>
Cc: "linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"platform-driver-x86@vger.kernel.org" 
	<platform-driver-x86@vger.kernel.org>
Subject: Re: input/i8042: Malfunctioning brightness keys on HP Elite Dragonfly G2
Date: Wed, 13 Jul 2022 09:16:49 +0100	[thread overview]
Message-ID: <afeb858778de9b25d0de655ffccb64b85511c428.camel@gmx.co.uk> (raw)
In-Reply-To: <PH0PR84MB195301AA9C44F2F4ECE4A848A8879@PH0PR84MB1953.NAMPRD84.PROD.OUTLOOK.COM>

On Mon, 2022-07-11 at 14:59 +0000, Lopez, Jorge A (Security) wrote:
> Hi Alex,
> 
> Thank you for the BIOS information.   The problem you are
> experiencing was fixed in BIOS version 01.07.02 Rev.A
> 
>         - Fixes an issue where Fn+F3/F4 do not change the brightness
> of the display panel when the Privacy Panel is enabled in the F10
> settings.
> 
> The latest BIOS version is 01.09.01 Rev.A so the problem will be
> resolved after BIOS upgrade.    BIOS is not available via LVFS, you
> will need to install it via Windows executable.
> https://support.hp.com/us-en/drivers/laptops
> 
> Let me know if the problem is resolved.

That worked a treat. Thanks!

And if you have an internal ticked called "Support Elitebooks on LVFS"
or similar, feel free to add my +1 to it 😉

Best,
Alex

  reply	other threads:[~2022-07-13  8:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-29  9:43 Alex Dewar
2022-07-05 17:25 ` Alex Dewar
2022-07-09 14:56   ` Hans de Goede
2022-07-11  7:49     ` Alex Dewar
2022-07-11 12:09       ` Hans de Goede
2022-07-11 13:10         ` Lopez, Jorge A (Security)
2022-07-11 14:26           ` Lopez, Jorge A (Security)
2022-07-11 14:35             ` Alex Dewar
2022-07-11 14:59               ` Lopez, Jorge A (Security)
2022-07-13  8:16                 ` Alex Dewar [this message]
2022-07-13 16:34                   ` Lopez, Jorge A (Security)
2022-07-14  9:22                     ` Alex Dewar
2022-07-05 17:28 ` Alex Dewar

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=afeb858778de9b25d0de655ffccb64b85511c428.camel@gmx.co.uk \
    --to=alex.dewar@gmx.co.uk \
    --cc=dmitry.torokhov@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=jorge.lopez2@hp.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markgross@kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=tiwai@suse.de \
    /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

all inboxes | Powered by JetHome®