Lines Matching +full:secure +full:- +full:firmware
5 should be a userspace tool that handles all the low-level details, keeps
9 found in ``Documentation/ABI/testing/sysfs-bus-thunderbolt``.
13 ``/etc/udev/rules.d/99-local.rules``::
22 -----------------------------------
33 All devices are automatically connected by the firmware. No user
43 secure
45 addition to UUID the device (if it supports secure connect) is sent
51 The firmware automatically creates tunnels for Display Port and
56 The firmware automatically creates tunnels for the USB controller and
65 If the security level reads as ``user`` or ``secure`` the connected
74 Authorizing devices when security level is ``user`` or ``secure``
75 -----------------------------------------------------------------
78 /sys/bus/thunderbolt/devices/0-1/authorized - 0
79 /sys/bus/thunderbolt/devices/0-1/device - 0x8004
80 /sys/bus/thunderbolt/devices/0-1/device_name - Thunderbolt to FireWire Adapter
81 /sys/bus/thunderbolt/devices/0-1/vendor - 0x1
82 /sys/bus/thunderbolt/devices/0-1/vendor_name - Apple, Inc.
83 /sys/bus/thunderbolt/devices/0-1/unique_id - e0376f00-0300-0100-ffff-ffffffffffff
88 # echo 1 > /sys/bus/thunderbolt/devices/0-1/authorized
92 If the device supports secure connect, and the domain security level is
93 set to ``secure``, it has an additional attribute ``key`` which can hold
94 a random 32-byte value used for authorization and challenging the device in
97 /sys/bus/thunderbolt/devices/0-3/authorized - 0
98 /sys/bus/thunderbolt/devices/0-3/device - 0x305
99 /sys/bus/thunderbolt/devices/0-3/device_name - AKiTiO Thunder3 PCIe Box
100 /sys/bus/thunderbolt/devices/0-3/key -
101 /sys/bus/thunderbolt/devices/0-3/vendor - 0x41
102 /sys/bus/thunderbolt/devices/0-3/vendor_name - inXtron
103 /sys/bus/thunderbolt/devices/0-3/unique_id - dc010000-0000-8508-a22d-32ca6421cb16
107 If the user does not want to use secure connect they can just ``echo 1``
111 If the user wants to use secure connect, the first time the device is
114 # key=$(openssl rand -hex 32)
115 # echo $key > /sys/bus/thunderbolt/devices/0-3/key
116 # echo 1 > /sys/bus/thunderbolt/devices/0-3/authorized
124 # echo $key > /sys/bus/thunderbolt/devices/0-3/key
125 # echo 2 > /sys/bus/thunderbolt/devices/0-3/authorized
137 -------------------------------------------
138 Since most of the functionality is handled in firmware running on a
139 host controller or a device, it is important that the firmware can be
141 Typically OEMs provide this firmware from their support site.
143 There is also a central site which has links where to download firmware
148 Before you upgrade firmware on a device or host, please make sure it is a
157 device - then you need to connect that particular device).
159 Note an OEM-specific method to power the controller up ("force power") may
163 After that we can write the firmware to the non-active parts of the NVM
167 # dd if=KYK_TBT_FW_0018.bin of=/sys/bus/thunderbolt/devices/0-0/nvm_non_active0/nvmem
172 # echo 1 > /sys/bus/thunderbolt/devices/0-0/nvm_authenticate
179 We can verify that the new NVM firmware is active by running the following
182 # cat /sys/bus/thunderbolt/devices/0-0/nvm_authenticate
184 # cat /sys/bus/thunderbolt/devices/0-0/nvm_version
196 --------------------------------------------------
207 ---------------------------------
216 ``thunderbolt-net`` driver is loaded automatically. If the other host is
217 also Linux you should load ``thunderbolt-net`` manually on one host (it
220 # modprobe thunderbolt-net
223 is built-in to the kernel image, there is no need to do anything.
231 -------------
237 For example the intel-wmi-thunderbolt driver exposes this attribute in:
238 /sys/bus/wmi/devices/86CCFD48-205E-4A77-9C48-2021CBEDE341/force_power