> -----Original Message----- > From: Bernat, Yehezkel [mailto:yehezkel.bernat@xxxxxxxxx] > Sent: Wednesday, September 6, 2017 3:27 PM > To: dvhart@xxxxxxxxxxxxx; Limonciello, Mario <Mario_Limonciello@xxxxxxxx> > Cc: mika.westerberg@xxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; platform- > driver-x86@xxxxxxxxxxxxxxx; hughsient@xxxxxxxxx > 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. Yeah I'd agree with that impression. Even if an OEM does choose to publish a UEFI based solution, it's still useful to present FW information for the TBT controller in fwupd however too. Similar to how fwupd displays the information for the ME even though the ME is typically updated via UEFI.
