[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DM6PR19MB2636C7C411E220565F39E741FA320@DM6PR19MB2636.namprd19.prod.outlook.com>
Date: Tue, 29 Sep 2020 12:27:13 +0000
From: "Limonciello, Mario" <Mario.Limonciello@...l.com>
To: Hans de Goede <hdegoede@...hat.com>,
Barnabás Pőcze <pobrn@...tonmail.com>,
Takashi Iwai <tiwai@...e.de>
CC: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
"platform-driver-x86@...r.kernel.org"
<platform-driver-x86@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Keyboard regression by intel-vbtn
>I'm afraid that the only answer which I have to these questions
>is not helpful, but in my experience it is true: "firmware sucks".
So FWIW there is a Dell 2-in-1 that has been conflated into this same issue.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822394
Something that is confusing to me is that on the Windows side all these
machines use the same Intel driver for this infrastructure no matter the
OEM.
So they can't possibly be putting in quirk specific stuff in the driver side
can they?
It has to make you wonder if some baseline assumptions made in the
driver early on around tablet mode support are completely false.
Powered by blists - more mailing lists