mirror of
https://git.proxmox.com/git/fwupd
synced 2025-07-03 01:54:24 +00:00
078beafb2d
It is far too easy to forget to set FWUPD_DEVICE_FLAG_NO_GUID_MATCHING for new
plugins, and without it it all works really well *until* a user has two devices
of the same type installed at the same time and then one 'disappears' for hard
to explain reasons. Typically we only need it for replug anyway!
Explicitly opt-in to this rarely-required behaviour, with the default to just
use the physical and logical IDs. Also document the update behavior for each
plugin to explain why the flag is being used.
This allows you to have two identical Unifying plugged in without one of them
being hidden from the user, at the same time allowing a HIDRAW<->USB transition
when going to and from bootloader and runtime modes.
This removes the workaround added in 99eb3f06b6.
Fixes https://github.com/fwupd/fwupd/issues/2915
62 lines
1.8 KiB
Markdown
62 lines
1.8 KiB
Markdown
ATA
|
|
===
|
|
|
|
Introduction
|
|
------------
|
|
|
|
This plugin allows updating ATA/ATAPI storage hardware. Devices are enumerated
|
|
from the block devices and if ID_ATA_DOWNLOAD_MICROCODE is supported they can
|
|
be updated with appropriate firmware file.
|
|
|
|
Updating ATA devices is more dangerous than other hardware such as DFU or NVMe
|
|
and should be tested carefully with the help of the drive vendor.
|
|
|
|
The device GUID is read from the trimmed model string.
|
|
|
|
Firmware Format
|
|
---------------
|
|
|
|
The daemon will decompress the cabinet archive and extract a firmware blob in
|
|
an unspecified binary file format.
|
|
|
|
This plugin supports the following protocol ID:
|
|
|
|
* org.t13.ata
|
|
|
|
GUID Generation
|
|
---------------
|
|
|
|
These device use the Microsoft DeviceInstanceId values, e.g.
|
|
|
|
* `IDE\VENDOR[40]REVISION[8]`
|
|
* `IDE\0VENDOR[40]`
|
|
|
|
See https://docs.microsoft.com/en-us/windows-hardware/drivers/install/identifiers-for-ide-devices
|
|
for more details.
|
|
|
|
Update Behavior
|
|
---------------
|
|
|
|
The firmware is deployed when the device is in normal runtime mode, but it is
|
|
only activated when the system is in the final shutdown stages. This is done to
|
|
minimize the chance of data loss if the switch to the new firmware is not done
|
|
correctly.
|
|
|
|
Vendor ID Security
|
|
------------------
|
|
|
|
No vendor ID is set as there is no vendor field in the IDENTIFY response.
|
|
|
|
Quirk use
|
|
---------
|
|
This plugin uses the following plugin-specific quirks:
|
|
|
|
| Quirk | Description | Minimum fwupd version |
|
|
|------------------------|-------------------------------------------|-----------------------|
|
|
| `AtaTransferBlocks` | Blocks to transfer, or `0xffff` for max | 1.2.4 |
|
|
| `AtaTransferMode` | The transfer mode, `0x3`, `0x7` or `0xe` | 1.2.4 |
|
|
|
|
External interface access
|
|
-------------------------
|
|
This plugin requires the `SG_IO` ioctl interface.
|