Lines Matching full:qemu

3 CanoKey QEMU
24 In QEMU, yet another CanoKey virt-card is implemented.
25 CanoKey QEMU exposes itself as a USB device to the guest OS.
31 CanoKey QEMU provides much convenience for debugging:
33 * libcanokey-qemu supports debugging output thus developers can
35 * CanoKey QEMU supports trace event thus event
36 * QEMU USB stack supports pcap thus USB packet between the guest
52 libcanokey-qemu is required to use CanoKey QEMU.
56     git clone https://github.com/canokeys/canokey-qemu
57     mkdir canokey-qemu/build
58     pushd canokey-qemu/build
60 If you want to install libcanokey-qemu in a different place,
78 Using CanoKey QEMU
81 CanoKey QEMU stores all its data on a file of the host specified by the argument
82 when invoking qemu.
91 afterwards CanoKey QEMU would just read this file.
96 and find CanoKey QEMU there:
101     Bus 001 Device 002: ID 20a0:42d4 Clay Logic CanoKey QEMU
108 CanoKey QEMU consists of two parts, ``libcanokey-qemu.so`` and ``canokey.c``,
109 the latter of which resides in QEMU. The former provides core functionality
114 libcanokey-qemu, you should add ``-DQEMU_DEBUG_OUTPUT=ON`` in cmake command
137 Currently libcanokey-qemu.so has dozens of global variables as it was originally
138 designed for embedded systems. Thus one qemu instance can not have
139 multiple CanoKey QEMU running, namely you can not
146 Also, there is no lock on canokey-file, thus two CanoKey QEMU instance