On Wed, Jan 11, 2023 at 09:31:27AM +0800, liudk@xxxxxxxxxxxxx wrote: > HI： > We have been verifying the BMI0160 ACPI ID on WIN4. If there is no problem with the verification, it will be updated to WinMax2 synchronously. At present, the feedback is that the chip of BMI 260 under Linux does not seem to be able to use the driver of BMI 160, and we are still trying the latest Linux driver Thank you for confirming the ID. The devices discussed in the thread [1] below have the Realtek ID (in accordance with PCI and ACPI specifications). I hope that that is fixed now. > 中软赢科技术有限公司 > 软件部 刘德康 > 电话： 18674743475 > 地址： 深圳市南山区软件产业基地4D栋1006 > > From: Andy Shevchenko > Date: 2023-01-10 04:49 > To: Derek John Clark > CC: Jonathan Cameron; linux-iio; Joaquín Ignacio Aramendía; Hans de Goede; liudk > Subject: Re: BMI0160/260 conflicts > On Mon, Jan 09, 2023 at 11:04:38AM -0800, Derek John Clark wrote: > > They typically communicate through discord or whatsapp. I've sent them > > the link for the thread a few times and I've asked for an email > > address I can CC on the LKML so we'll see if they provide one. I don't > > think this will be an issue, from them at least, in the future. For a > > bit of history, the original tablet was designed by a different team > > which they were obligated to finish through an IndieGoGo campaign > > after the company was bought out halfway through production. All > > subsequent releases from AyaNeo (7 models by my count) have all used > > the BMI0160 ACPI ID. I'm personally more concerned personally with GPD > > having released new products over a year later using the same Realtek > > ACPI ID, and currently sending out engineering sample units of a > > second model. I've included my GPD contact in this thread for their > > awareness. > > Thank you very much for this effort! > > Btw, feel free to tell them if they need any assistance in ACPI understanding > they may publicly or privately ask me and other Linux kernel developers from > Intel related to ACPI (see MAINTAINERS for that list). > > > On Mon, Jan 9, 2023 at 9:29 AM Andy Shevchenko > > <andriy.shevchenko@xxxxxxxxxxxxxxx> wrote: > > > > > > On Mon, Jan 09, 2023 at 07:42:01AM -0800, Derek John Clark wrote: > > > > On Mon, Jan 9, 2023 at 3:38 AM Andy Shevchenko > > > > <andriy.shevchenko@xxxxxxxxxxxxxxx> 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@xxxxxxxxx> 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? [1]: https://lore.kernel.org/lkml/CACAwPwYQHRcrabw9=0tvenPzAcwwW1pTaR6a+AEWBF9Hqf_wXQ@xxxxxxxxxxxxxx/ > > > > I've been knocking on this door for a few months now. They recently > > > > sent me a test BIOS with the alleged fix for testing. Hopefully they > > > > do a wide release once it is fully validated. > > > > > > At least they reacted to your knock, that's why I'm asking you to ping them so > > > they would know that they have an issue with the ACPI ID for the accelerometer > > > device. -- With Best Regards, Andy Shevchenko
