Searched refs:shown (Results 1 – 25 of 121) sorted by relevance
12345
62 The properties of a given CAN controller can be inspected using the ``can show`` subcommand as shown111 subcommand as shown below. The bitrate is specified in bits per second.119 the ``can dbitrate`` subcommand as shown below. The bitrate is specified in bits per second.138 subcommand. An example for enabling loopback mode is shown below.153 ``can start`` subcommand as shown below. This will enable reception and transmission of CAN frames.161 stop`` subcommand as shown below:172 added using the ``can filter add`` subcommand as shown below. The subcommand accepts a CAN ID in185 Received CAN frames matching the added filter(s) are printed to the shell. A few examples are shown…233 Configured CAN RX filters can be removed again using the ``can filter remove`` subcommand as shown245 CAN frames can be queued for transmission using the ``can send`` subcommand as shown below. The[all …]
82 int "Seconds each rendered scene is shown"86 Seconds each rendered scenar is shown
32 note:: The values shown above might differ.
15 int "Maximum length of strings that can be shown on the display"
18 (for example as shown in this
82 are shown like this:174 are shown like this:215 are shown like this:
15 /* SPI bus options here, not shown */
32 characteristic. The passkey for the pairing will be shown on the board's51 #. Wait until "Resetting Device" is shown
14 VBAT is preserved, the incremented value will be shown on the next power-cycle.
73 The two interfaces are shown below:103 Boolean configuration options are shown with :guilabel:`[ ]` brackets,104 while numeric and string-valued configuration symbols are shown with105 :guilabel:`( )` brackets. Symbol values that can't be changed are shown as
51 .. note:: The values shown above might differ.
45 .. note: The values shown above might differ.
28 To connect click on the device shown in the Device List.
66 For each message received, its content is displayed as shown down below then sent back to Linux.115 On the Zephyr console, the received message is displayed as shown below, then sent back to Linux.
51 note:: The values shown above might differ.
71 The reported increment/decrement can be larger/smaller than the one shown
64 .. note:: The values shown above might differ.
50 * pool name is stored and can be shown in debugging prints
53 Once IPv4 LL has completed probing and announcement, details are shown like this:
92 examples are shown. Note that the ``noinit`` section holds variables with94 values shown above.
68 This interval controls how often the net stats data shown on the web page
26 is something in proximity for each sensor. The left sensor is shown on the
18 are shown as well, such as STARVING when the philosopher is hungry but the
17 :ref:`supported board <boards>` and prints the sample output shown to
