linux-kernel - RE: [PATCH v5] Fix the resolution issue in ChromeOS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1A63A1423E772B419A9D2E882CBCF6C402022C10@mail>
Date:	Sat, 13 Jun 2015 15:04:38 +0800
From:	"Hn Chen" <hn.chen@...dahitech.com>
To:	"Frans Klaver" <fransklaver@...il.com>
Cc:	<linux-input@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
	"Dmitry Torokhov" <dmitry.torokhov@...il.com>
Subject: RE: [PATCH v5] Fix the resolution issue in ChromeOS

Hi, Frans,

It can only be delay for the firmware implementation now.

Hn.chen

-----Original Message-----
From: Frans Klaver [mailto:fransklaver@...il.com] 
Sent: Friday, June 12, 2015 6:02 PM
To: Hn Chen
Cc: linux-input@...r.kernel.org; linux-kernel@...r.kernel.org; Dmitry Torokhov
Subject: Re: [PATCH v5] Fix the resolution issue in ChromeOS

On Wed, Jun 10, 2015 at 4:51 PM, Hn Chen <hn.chen@...dahitech.com> wrote:
> Hi, Frans,
>
>> Alright, I was just wondering. Seems like a waste to be waiting for something that's already finished ;-).
>> There's of course a risk that times may fluctuate between firmware versions. Did you take that into account in the code?
>> Or is there a hard maximum time for these operations defined for the firmware?
> Thanks for your reminding.
> After I check with the firmware guy, I will change the value of delay.
> What we do here is to read the data from flash and calculate their 
> checksum and will cost about 6ms for 1024 bytes. So there is a delay for 10 ms per 1024 bytes.
> But in some situation, the controller will change it's running 
> frequency(like do noise immunity), 10ms could be too margin.

Any chance this sort of thing could be detected?