linux-kernel - Re: [PATCH v4] platform: x86: Add ACPI driver for 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 for Android: free password hash cracker in your pocket

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

Message-ID: <20200610214033.GB248110@dtor-ws>
Date:   Wed, 10 Jun 2020 14:40:33 -0700
From:   Dmitry Torokhov <dmitry.torokhov@...il.com>
To:     Mario.Limonciello@...l.com
Cc:     enric.balletbo@...labora.com, rjw@...ysocki.net, rafael@...nel.org,
        linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org,
        lenb@...nel.org, kernel@...labora.com, groeck@...omium.org,
        bleung@...omium.org, dtor@...omium.org, gwendal@...omium.org,
        vbendeb@...omium.org, andy@...radead.org, ayman.bagabas@...il.com,
        benjamin.tissoires@...hat.com, blaz@...n.io, dvhart@...radead.org,
        gregkh@...uxfoundation.org, hdegoede@...hat.com,
        jeremy@...tem76.com, 2pi@....nu, mchehab+samsung@...nel.org,
        rajatja@...gle.com, srinivas.pandruvada@...ux.intel.com,
        platform-driver-x86@...r.kernel.org
Subject: Re: [PATCH v4] platform: x86: Add ACPI driver for ChromeOS

On Wed, Jun 10, 2020 at 09:28:36PM +0000, Mario.Limonciello@...l.com wrote:
> > 
> > To give you some references, if I'm not wrong, this prefix is used in all
> > or
> > almost all Intel Chromebook devices (auron, cyan, eve, fizz, hatch,
> > octopus,
> > poppy, strago ...) The ACPI source for this device can be found here [1],
> > and,
> > if not all, almost all Intel based Chromebooks are shipped with the
> > firmware
> > that supports this.
> 
> You can potentially carry a small patch in your downstream kernel for the
> legacy stuff until it reaches EOL.  At least for the new stuff you could
> enact a process that properly reserves unique numbers and changes the driver
> when the interface provided by the ACPI device has changed.

If we use this prefix for hatch EOL is ~7 years from now.

Thanks.

-- 
Dmitry