From 7e691c813bdf26bf9c51f03ee926818c00cc6e39 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Tue, 31 Jan 2023 05:17:04 +0100 Subject: Merging upstream version 1.3. Signed-off-by: Daniel Baumann --- doc/mi.rst.in | 11 +++++++++++ 1 file changed, 11 insertions(+) (limited to 'doc/mi.rst.in') diff --git a/doc/mi.rst.in b/doc/mi.rst.in index 2806668..a75fd69 100644 --- a/doc/mi.rst.in +++ b/doc/mi.rst.in @@ -13,6 +13,17 @@ Most of the MI API is transport-agnostic, except for the endpoint constructor functions. Once an endpoint object (``nvme_mi_ep_t``) is created, the generic functions can be used to manage it. +When endpoints are created (through one of the transport-specific functions, +like ``nvme_mi_open_mctp()``), the endpoint hardware will be probed to +see if any device-specific workarounds ("quirks") are required. This is +implemented as an Identify Controller command, requesting a small amount of +data on controller ID 0. + +To suppress this probe, the ``LIBNVME_MI_PROBE_ENABLED`` environment var can be +set. Values of ``0``, ``false`` and ``disabled`` will disable the probe, and no +quirks will be applied. Other values, or an unset environment variable, will +enable the probe. + MCTP Transport -------------- -- cgit v1.2.3