From: "Hongren (Zenithal) Zheng" <i@zenithal.me>
To: qemu-devel@nongnu.org
Cc: Thomas Huth <thuth@redhat.com>, Gerd Hoffmann <kraxel@redhat.com>,
contact@canokeys.org
Subject: [PATCH v4 5/6] docs/system/devices/usb: Add CanoKey to USB devices examples
Date: Thu, 27 Jan 2022 17:47:21 +0800 [thread overview]
Message-ID: <YfJqKREYO1YeBnLA@Sun> (raw)
In-Reply-To: <YfJozy5qjVYh24Xp@Sun>
Signed-off-by: Hongren (Zenithal) Zheng <i@zenithal.me>
---
docs/system/devices/usb.rst | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/docs/system/devices/usb.rst b/docs/system/devices/usb.rst
index afb7d6c226..872d916758 100644
--- a/docs/system/devices/usb.rst
+++ b/docs/system/devices/usb.rst
@@ -199,6 +199,10 @@ option or the ``device_add`` monitor command. Available devices are:
``u2f-{emulated,passthru}``
Universal Second Factor device
+``canokey``
+ An Open-source Secure Key implementing FIDO2, OpenPGP, PIV and more.
+ For more information, see :ref:`canokey`.
+
Physical port addressing
^^^^^^^^^^^^^^^^^^^^^^^^
--
2.34.1
next prev parent reply other threads:[~2022-01-27 9:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 9:41 [PATCH v4 0/6] Introduce CanoKey QEMU Hongren (Zenithal) Zheng
2022-01-27 9:45 ` [PATCH v4 1/6] hw/usb: Add CanoKey Implementation Hongren (Zenithal) Zheng
2022-01-27 9:46 ` [PATCH v4 2/6] hw/usb/canokey: Add trace events Hongren (Zenithal) Zheng
2022-01-27 9:46 ` [PATCH v4 3/6] meson: Add CanoKey Hongren (Zenithal) Zheng
2022-01-27 9:47 ` [PATCH v4 4/6] docs: Add CanoKey documentation Hongren (Zenithal) Zheng
2022-01-27 9:47 ` Hongren (Zenithal) Zheng [this message]
2022-01-27 9:47 ` [PATCH v4 6/6] MAINTAINERS: add myself as CanoKey maintainer Hongren (Zenithal) Zheng
2022-02-12 13:29 ` [PATCH v4 0/6] Introduce CanoKey QEMU Hongren (Zenithal) Zheng
2022-03-04 10:51 ` Gerd Hoffmann
2022-03-22 7:18 ` Hongren (Zenithal) Zheng
2022-03-22 10:41 ` Gerd Hoffmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YfJqKREYO1YeBnLA@Sun \
--to=i@zenithal.me \
--cc=contact@canokeys.org \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.