From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "Derek John Clark" <derekjohn.clark@gmail.com>,
linux-iio@vger.kernel.org,
"Joaquín Ignacio Aramendía" <samsagax@gmail.com>,
"Hans de Goede" <hdegoede@redhat.com>
Subject: Re: BMI0160/260 conflicts
Date: Mon, 9 Jan 2023 13:42:00 +0200 [thread overview]
Message-ID: <Y7v9iPcebF9RTSOn@smile.fi.intel.com> (raw)
In-Reply-To: <Y7v8yE8+cXZIDUvw@smile.fi.intel.com>
On Mon, Jan 09, 2023 at 01:38:48PM +0200, Andy Shevchenko wrote:
> On Sun, Jan 08, 2023 at 11:53:41AM +0000, Jonathan Cameron wrote:
> > On Sat, 7 Jan 2023 19:51:59 -0800
> > Derek John Clark <derekjohn.clark@gmail.com> wrote:
...
> > > Remediation:
> > > I have reached out to the aforementioned companies about releasing
> > > updated BIOS for each of the respective models to correct the DSDT
> > > ID's. AYANEO and GPD seem receptive as they have each provided beta
> > > BIOS for testing.
> >
> > Great. Hopefully that means that the scope of problem devices from
> > these manufacturers is not going to grow too much going forwards!
>
> Wow, you have Ayaneo response?! Unbelievable!
> If they answering to you, can you ping them on [1] please?
TL;DR: They are using Realtek's ACPI HID for the Bosch sensor device.
> [1]: https://lore.kernel.org/lkml/CACAwPwYQHRcrabw9=0tvenPzAcwwW1pTaR6a+AEWBF9Hqf_wXQ@mail.gmail.com/
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-01-09 11:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-08 3:51 BMI0160/260 conflicts Derek John Clark
2023-01-08 11:53 ` Jonathan Cameron
2023-01-09 11:38 ` Andy Shevchenko
2023-01-09 11:42 ` Andy Shevchenko [this message]
2023-01-09 15:42 ` Derek John Clark
2023-01-09 17:29 ` Andy Shevchenko
2023-01-09 19:04 ` Derek John Clark
2023-01-09 20:49 ` Andy Shevchenko
[not found] ` <E0791B6D696C82E2+202301110931264482331@softwincn.com>
2023-01-12 9:58 ` Andy Shevchenko
2023-01-09 15:31 ` Derek John Clark
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=Y7v9iPcebF9RTSOn@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=derekjohn.clark@gmail.com \
--cc=hdegoede@redhat.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=samsagax@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.