linux-kernel - Re: Fwd: [PATCH] Add driver to force WMI Thunderbolt controller power status

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] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 6 Sep 2017 20:26:39 +0000
From:   "Bernat, Yehezkel" <yehezkel.bernat@...el.com>
To:     "dvhart@...radead.org" <dvhart@...radead.org>,
        "Mario.Limonciello@...l.com" <Mario.Limonciello@...l.com>
CC:     "mika.westerberg@...ux.intel.com" <mika.westerberg@...ux.intel.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "platform-driver-x86@...r.kernel.org" 
        <platform-driver-x86@...r.kernel.org>,
        "hughsient@...il.com" <hughsient@...il.com>
Subject: Re: Fwd: [PATCH] Add driver to force WMI Thunderbolt controller power
 status

On Wed, 2017-09-06 at 13:09 -0700, Darren Hart wrote:
> The other question I had about this was if the typical use case
> involves the OS,
> or if the firmware update (for example) would be performed as part of
> the
> general platform firmware update (from the UEFI update utility).

First, there is the use-case of add-in card, where it's impossible to
use UEFI-based update, as much as I understand, as the BIOS isn't
expected to expose an ESRT entry for it.

Even for built-in controller, my impression is that most OEMs use a FW
update application (running on Windows) and are not publishing a UEFI-
based solution.