On 2015/03/29 11:55, Denis Lapshin wrote: > Since 4.9 till current 8510p/w read acpi temp with error (enormous high temp > about 2000-5000 C) because SMBus data is not ready for reading. It seems > data reading should be delayed. > > Theo, you told that you don't want to implement "shit" in CVS repository. > Most of ACPI code should be rewritten in new way. > > I have enormous high temperature reading in various ACPI zones on HP Compaq > laptops from time to time. > Still applying delay patch into acpiec.c to have it working. > > On 28.03.2015 22:48, Theo de Raadt wrote: > >>Every release I need to apply a patch after upgrade for reading ACPII > >>data from 8510p in time, to prevent wrong data on SMBUS. Theo replied > >>that the patch will not be implemented in CVS because all ACPI must be > >>rewritten in new manner. But they will do nothing since my last report... > >I doubt I said anything close to your interpretation. > > > > -- > Denis Lapshin > mailto: [email protected] >
>From what I understand of that thread, the embedded controller on those HPs lies about when it's ready. The diff had some definitely wrong things in it (like the local volatile stuff) and at least 3 developers were in agreement that it was the wrong approach. But since everybody who was affected seemed more interested in locally patching with a quick fix rather than working on a correct diff, what can be done? Back to the AST2050. You need more information than that. Whether the machine is going to work depends on more than just which ICs it has. If your question is "does anybody know if machine X works with OpenBSD" then just ask that question instead (though there is still some element of surprise as they may have different BIOS, firmware version, etc). I have machines with other similar Aspeed chips that work fine, but without more details about the machines that's not useful information.
