[coreboot] New on blogs.coreboot.org: Announcing coreboot 4.14

2021-05-10 Thread blogs.coreboot.org via coreboot
A new post titled "Announcing coreboot 4.14" has been published on the coreboot blog. Find the full post at https://blogs.coreboot.org/blog/2021/05/10/announcing-coreboot-4-14/ coreboot 4.14 was released today, on May 10th, 2021. Since 4.13 there have been 3660 new commits by 215 developers.

[coreboot] Re: [RFC] How should we manage tree-wide changes?

2021-05-10 Thread Paul Menzel
Dear Piotr, Am 10.05.21 um 13:51 schrieb Piotr Król: On 5/10/21 1:45 PM, Paul Menzel wrote: Am 10.05.21 um 10:51 schrieb Piotr Król: On 5/8/21 9:24 AM, Paul Menzel wrote: Am 28.04.21 um 00:38 schrieb Piotr Król: (...) This is one part of the problem, other is specifications

[coreboot] Re: [RFC] How should we manage tree-wide changes?

2021-05-10 Thread Piotr Król
On 5/10/21 1:45 PM, Paul Menzel wrote: > Dear Piotr, > > > Am 10.05.21 um 10:51 schrieb Piotr Król: > >> On 5/8/21 9:24 AM, Paul Menzel wrote: > >>> Am 28.04.21 um 00:38 schrieb Piotr Król: >> >> (...) >> This is one part of the problem, other is specifications compatibility where

[coreboot] Re: [RFC] How should we manage tree-wide changes?

2021-05-10 Thread Paul Menzel
Dear Piotr, Am 10.05.21 um 10:51 schrieb Piotr Król: On 5/8/21 9:24 AM, Paul Menzel wrote: Am 28.04.21 um 00:38 schrieb Piotr Król: (...) This is one part of the problem, other is specifications compatibility where ACPI is one that breaks things often. coreboot moves with ACPI compiler

[coreboot] Re: [RFC] How should we manage tree-wide changes?

2021-05-10 Thread Piotr Król
On 5/8/21 9:24 AM, Paul Menzel wrote: > Dear Piotr, Hi Paul, > > > Thank you for bringing up these issues. > > Am 28.04.21 um 00:38 schrieb Piotr Król: (...) >> This is one part of the problem, other is specifications compatibility >> where ACPI is one that breaks things often. coreboot

[coreboot] Re: Default-timings in Designware I2C driver

2021-05-10 Thread Zeh, Werner
Hi Peter. > Does the coreboot code communicate something to the OS driver already? Yes, there is an ACPI entry which reports current timings in dw_i2c_acpi_write_speed_config() [1]. This code used to provide a report for all available speeds but was changed in [2]. Though I am not sure how