linux-kernel - Re: [PATCH v9 1/2] i2c: i801: add support of Host Notify

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]

Date:   Fri, 19 Aug 2016 15:19:18 +0200
From:   Benjamin Tissoires <benjamin.tissoires@...hat.com>
To:     Jean Delvare <jdelvare@...e.de>
Cc:     Wolfram Sang <wsa@...-dreams.de>,
        Dmitry Torokhov <dmitry.torokhov@...il.com>,
        Andrew Duggan <aduggan@...aptics.com>,
        Christopher Heiny <cheiny@...aptics.com>,
        linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v9 1/2] i2c: i801: add support of Host Notify

On Aug 01 2016 or thereabouts, Jean Delvare wrote:
> On Thu, 28 Jul 2016 11:44:57 +0200, Benjamin Tissoires wrote:
> > On Jul 18 2016 or thereabouts, Jean Delvare wrote:
> > > On Fri, 24 Jun 2016 16:39:49 +0200, Benjamin Tissoires wrote:
> > > > The i801 chip can handle the Host Notify feature since ICH 3 as mentioned
> > > > in http://www.intel.com/content/dam/doc/datasheet/82801ca-io-controller-hub-3-datasheet.pdf
> > > > 
> > > > Enable the functionality unconditionally and propagate the alert
> > > > on each notification.
> > > > 
> > > > With a T440s and a Synaptics touchpad that implements Host Notify, the
> > > > payload data is always 0x0000, so I am not sure if the device actually
> > > > sends the payload or if there is a problem regarding the implementation.
> > > 
> > > Out of curiosity, does it work on at least one machine?
> > 
> > I have tested the T440, t450 and t460 (3 different generation of Intel
> > processor), and none seems to be working. The Synaptics touchpad used is
> > mostly the same, so maybe that's a device issue.
> 
> May I ask why you are pushing the code upstream then, if it has no
> known (working) user?
> 

K. Then I guess I'll just have to remove these reads from the driver.

Cheers,
Benjamin