On Wed, Sep 30, 2020 at 4:55 AM Daniel Vetter wrote:
>
> On Wed, Sep 30, 2020 at 11:39:06AM +0200, Michel Dänzer wrote:
> > On 2020-03-17 10:21 p.m., Jason Ekstrand wrote:
> > > Explicit synchronization is the future. At least, that seems to be what
> > > most use
On Sat, Mar 14, 2015 at 12:58 PM, Jason Ekstrand wrote:
> From: Jason Ekstrand
>
> On Wed, 11 Mar 2015 22:50:47, Matthew Garrett wrote:
>> The ACPI spec describes _REV as:
>>
>> "This predefined object evaluates to the revision of the ACPI Specification
>&g
On Mon, Mar 16, 2015 at 1:50 PM, Mario Limonciello
wrote:
>
> On 03/16/2015 03:42 PM, Jason Ekstrand wrote:
>>
>> On Mon, Mar 16, 2015 at 11:50 AM, Mario Limonciello
>> wrote:
>> Thanks,
>> I'm now running a hacked up kernel that's Torvalds'
On Mon, Mar 16, 2015 at 11:50 AM, Mario Limonciello
wrote:
>
> On 03/16/2015 12:10 PM, Jason Ekstrand wrote:
>>
>> On Mon, Mar 16, 2015 at 7:29 AM, Mario Limonciello
>> wrote:
>> It's nothing about the wireless. I swapped it out for an intel card
>> o
> Whether or not that _REV patch gets applied to the kernel we are fixing this
> incorrect behavior for Windows 2013 _OSI and Linux in upcoming BIOS A02.
> In BIOS A02 there will still be a _REV check but it will do this:
> Windows 2013 _OSI, _REV 5: I2C mouse, HDA device in ACPI, configur
From: Jason Ekstrand
On Wed, 11 Mar 2015 22:50:47, Matthew Garrett wrote:
> The ACPI spec describes _REV as:
>
> "This predefined object evaluates to the revision of the ACPI Specification
> that the specified \_OS implements"
>
> We've been assuming tha
6 matches
Mail list logo