| /OK3568_Linux_fs/kernel/net/mac80211/ |
| H A D | Kconfig | 88 bool "Trace all mac80211 debug messages"
93 collect all debugging messages, independent of
96 The overhead in this option is that all the messages
127 many debugging messages. It should not be selected
128 on production systems as some of the messages are
138 debugging messages for the managed-mode MLME. It
140 of the messages are remotely triggerable.
149 debugging messages for station addition/removal.
161 of the messages are remotely triggerable.
170 very verbose OCB debugging messages. It should not
[all …]
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/arm-none-linux-gnueabihf/include/c++/10.3.1/arm-none-linux-gnueabihf/bits/ |
| H A D | messages_members.h | 1 // std::messages implementation details, GNU version -*- C++ -*-
31 // ISO C++ 14882: 22.2.7.1.2 messages functions
44 messages<_CharT>::messages(size_t __refs) in _GLIBCXX_VISIBILITY()
50 messages<_CharT>::messages(__c_locale __cloc, const char* __s, in _GLIBCXX_VISIBILITY()
69 typename messages<_CharT>::catalog in _GLIBCXX_VISIBILITY()
70 messages<_CharT>::open(const basic_string<char>& __s, const locale& __loc, in _GLIBCXX_VISIBILITY()
79 messages<_CharT>::~messages() in _GLIBCXX_VISIBILITY()
87 typename messages<_CharT>::catalog in _GLIBCXX_VISIBILITY()
88 messages<_CharT>::do_open(const basic_string<char>& __s, in _GLIBCXX_VISIBILITY()
99 messages<_CharT>::do_close(catalog) const in _GLIBCXX_VISIBILITY()
[all …]
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/aarch64-none-linux-gnu/include/c++/10.3.1/aarch64-none-linux-gnu/bits/ |
| H A D | messages_members.h | 1 // std::messages implementation details, GNU version -*- C++ -*-
31 // ISO C++ 14882: 22.2.7.1.2 messages functions
44 messages<_CharT>::messages(size_t __refs) in _GLIBCXX_VISIBILITY()
50 messages<_CharT>::messages(__c_locale __cloc, const char* __s, in _GLIBCXX_VISIBILITY()
69 typename messages<_CharT>::catalog in _GLIBCXX_VISIBILITY()
70 messages<_CharT>::open(const basic_string<char>& __s, const locale& __loc, in _GLIBCXX_VISIBILITY()
79 messages<_CharT>::~messages() in _GLIBCXX_VISIBILITY()
87 typename messages<_CharT>::catalog in _GLIBCXX_VISIBILITY()
88 messages<_CharT>::do_open(const basic_string<char>& __s, in _GLIBCXX_VISIBILITY()
99 messages<_CharT>::do_close(catalog) const in _GLIBCXX_VISIBILITY()
[all …]
|
| /OK3568_Linux_fs/kernel/arch/arm/ |
| H A D | Kconfig.debug | 86 bool "Verbose user fault messages"
121 bool "Kernel low-level debugging messages via Alpine UART0"
223 bool "Kernel low-level debugging messages via BCM KONA UART"
255 messages to appear over the UART, select this option.
258 bool "Kernel low-level debugging messages via UART1"
265 bool "Kernel low-level debugging messages via UART2"
304 bool "Kernel low-level debugging messages via footbridge serial port"
311 bool "Kernel low-level debugging messages via Digicolor UA0"
318 bool "Kernel low-level debugging messages via ep93xx UART"
326 bool "Kernel low-level debugging messages via footbridge 8250 at PCI COM1"
[all …]
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/share/doc/gdb/ |
| H A D | Debugging-Output.html | 30 <link href="Messages_002fWarnings.html#Messages_002fWarnings" rel="previous" title="Messages/Warnin…
67 …s_002fWarnings.html#Messages_002fWarnings" accesskey="p" rel="previous">Messages/Warnings</a>, Up:…
70 <a name="Optional-Messages-about-Internal-Happenings"></a>
71 <h3 class="section">22.10 Optional Messages about Internal Happenings</h3>
72 <a name="index-optional-debugging-messages"></a>
74 <p><small>GDB</small> has commands that enable optional debugging messages from
95 <dd><p>Turns on or off display of debugging messages related to ARM AArch64.
100 <dd><p>Displays the current state of displaying debugging messages related to
113 <p>Control display of debugging messages from the AIX shared library
117 <dd><p>Show the current state of displaying AIX shared library debugging messages.
[all …]
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/share/doc/gdb/ |
| H A D | Debugging-Output.html | 30 <link href="Messages_002fWarnings.html#Messages_002fWarnings" rel="previous" title="Messages/Warnin…
67 …s_002fWarnings.html#Messages_002fWarnings" accesskey="p" rel="previous">Messages/Warnings</a>, Up:…
70 <a name="Optional-Messages-about-Internal-Happenings"></a>
71 <h3 class="section">22.10 Optional Messages about Internal Happenings</h3>
72 <a name="index-optional-debugging-messages"></a>
74 <p><small>GDB</small> has commands that enable optional debugging messages from
95 <dd><p>Turns on or off display of debugging messages related to ARM AArch64.
100 <dd><p>Displays the current state of displaying debugging messages related to
113 <p>Control display of debugging messages from the AIX shared library
117 <dd><p>Show the current state of displaying AIX shared library debugging messages.
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/networking/ |
| H A D | kcm.rst | 9 can efficiently send and receive application protocol messages over TCP using
45 The multiplexor provides the message steering. In the transmit path, messages
47 Similarly, in the receive path, messages are constructed on each TCP socket
48 (Psock) and complete messages are steered to a KCM socket.
55 messages on receive as well as other connection specific information for KCM.
63 can be used to send and receive messages from the KCM socket.
73 Messages are sent over a TCP stream with some application protocol message
74 format that typically includes a header which frames the messages. The length
102 socket. The BPF program may also enforce a maximum messages size and report an
105 A timeout may be set for assembling messages on a receive socket. The timeout
[all …]
|
| H A D | netif-msg.rst | 23 to shed the more verbose level messages as they matured.
25 - 0 Minimal messages, only essential information on fatal errors.
26 - 1 Standard messages, initialization status. No run-time messages
27 - 2 Special media selection messages, generally timer-driver.
28 - 3 Interface starts and stops, including normal status messages
29 - 4 Tx and Rx frame error messages, and abnormal driver operation
46 - More selective control over the type of messages emitted.
65 Messages should changes from::
|
| /OK3568_Linux_fs/kernel/Documentation/userspace-api/media/cec/ |
| H A D | cec-ioc-g-mode.rst | 42 used to initiate messages, i.e. it commands other CEC devices. The
43 follower is the filehandle that receives messages sent to the CEC
60 The CEC framework will process core messages unless requested otherwise
62 case, the CEC framework will pass on most core messages without
63 processing them and the follower will have to implement those messages.
64 There are some messages that the core will always process, regardless of
88 - This is not an initiator, i.e. it cannot transmit CEC messages or
95 it can transmit CEC messages and make changes to the CEC adapter,
102 only one that can transmit CEC messages and make changes to the
129 - This is a follower and it will receive CEC messages unless there
[all …]
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-multimedia/gstreamer/gstreamer1.0/ |
| H A D | 0005-bin-Fix-race-conditions-in-tests.patch | 6 The latency messages are non-deterministic and can arrive before/after
11 To solve this, expect latency messages at any time and assert that we
108 GST_DEBUG ("popping %d messages", count);
139 GST_DEBUG ("popped %d messages", count);
155 fail_if (gst_bus_have_pending (bus), "unexpected pending messages");
209 "Unexpected messages on bus");
244 - pop_state_changed (bus, 2); /* pop remaining ready => paused messages off the bus */
245 + pop_state_changed (bus, 2, &had_latency); /* pop remaining ready => paused messages off the …
253 GST_DEBUG ("popping PAUSED -> PLAYING messages");
258 - pop_state_changed (bus, 4); /* pop playing => paused messages off the bus */
[all …]
|
| /OK3568_Linux_fs/kernel/drivers/staging/nvec/ |
| H A D | nvec.h | 83 * @node: Messages are part of various lists in a &struct nvec_chip
85 * @size: For TX messages, the number of bytes used in @data
86 * @pos: For RX messages, the current position to write to. For TX messages,
90 * This structure is used to hold outgoing and incoming messages. Outgoing
91 * messages have a different format than incoming messages, and that is not
111 * @notifier_list: Notifiers to be called on received messages, see
113 * @rx_data: Received messages that have to be processed
114 * @tx_data: Messages waiting to be sent to the controller
120 * @msg_pool: A pool of messages for allocation
122 * @tx_scratch: Used for building pseudo messages
|
| /OK3568_Linux_fs/kernel/drivers/atm/ |
| H A D | Kconfig | 222 bool "Enable debugging messages"
225 Somewhat useful debugging messages are available. The choice of
226 messages is controlled by a bitmap. This may be specified as a
230 When active, these messages can have a significant impact on the
257 bool "Enable debugging messages"
260 Somewhat useful debugging messages are available. The choice of
261 messages is controlled by a bitmap. This may be specified as a
268 When active, these messages can have a significant impact on the
281 bool "Enable debugging messages"
284 Somewhat useful debugging messages are available. The choice of
[all …]
|
| /OK3568_Linux_fs/kernel/include/trace/events/ |
| H A D | iscsi.h | 19 * Declare event class for iscsi debug messages.
42 * Define event to capture iscsi connection debug messages.
51 * Define event to capture iscsi session debug messages.
60 * Define event to capture iscsi error handling debug messages.
69 * Define event to capture iscsi tcp debug messages.
78 * Define event to capture iscsi sw tcp debug messages.
87 * Define event to capture iscsi transport session debug messages.
96 * Define event to capture iscsi transport connection debug messages.
|
| /OK3568_Linux_fs/kernel/sound/usb/line6/ |
| H A D | driver.c | 43 Class for asynchronous messages.
534 /* Enable buffering of incoming messages, flush the buffer */
541 line6->messages.active = 1; in line6_hwdep_open()
542 line6->messages.nonblock = file->f_flags & O_NONBLOCK ? 1 : 0; in line6_hwdep_open()
552 line6->messages.active = 0; in line6_hwdep_release()
566 if (mutex_lock_interruptible(&line6->messages.read_lock)) in line6_hwdep_read()
569 while (kfifo_len(&line6->messages.fifo) == 0) { in line6_hwdep_read()
570 mutex_unlock(&line6->messages.read_lock); in line6_hwdep_read()
572 if (line6->messages.nonblock) in line6_hwdep_read()
576 line6->messages.wait_queue, in line6_hwdep_read()
[all …]
|
| /OK3568_Linux_fs/kernel/drivers/media/pci/bt8xx/ |
| H A D | dst_ca.c | 46 MODULE_PARM_DESC(verbose, "verbose startup messages, default is 1 (yes)");
134 if ((dst_put_ci(state, command, sizeof(command), state->messages, GET_REPLY)) < 0) { in ca_get_app_info()
141 state->messages[7], (state->messages[8] << 8) | state->messages[9], in ca_get_app_info()
142 (state->messages[10] << 8) | state->messages[11], __func__, (char *)(&state->messages[12])); in ca_get_app_info()
146 length = state->messages[5]; in ca_get_app_info()
154 put_command_and_length(&state->messages[0], CA_APP_INFO, length); in ca_get_app_info()
157 memmove(&state->messages[4], &state->messages[7], 5); in ca_get_app_info()
160 state->messages[9] = str_length; in ca_get_app_info()
161 memmove(&state->messages[10], &state->messages[12], str_length); in ca_get_app_info()
173 if ((dst_put_ci(state, slot_command, sizeof (slot_command), state->messages, GET_REPLY)) < 0) { in ca_get_ca_info()
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/ABI/testing/ |
| H A D | dev-kmsg | 8 Injecting messages:
20 is not possible to inject messages from userspace with the
22 the messages can always be reliably determined.
38 Messages in the record ring buffer get overwritten as whole,
39 there are never partial messages received by read().
41 In case messages get overwritten in the circular buffer while
48 messages, in case the buffer gets overwritten. And they allow
64 or write only whole variable length messages (records) that are
113 interleaved with unrelated messages, but merging the lines in
115 similar logic is used internally when messages are printed to
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/share/doc/as.html/ |
| H A D | Errors.html | 69 <a name="Error-and-Warning-Messages"></a>
70 <h3 class="section">1.7 Error and Warning Messages</h3>
73 <a name="index-error-messages"></a>
74 <a name="index-warning-messages"></a>
75 <a name="index-messages-from-assembler"></a>
76 <p><code>as</code> may write warnings and error messages to the standard error
83 <a name="index-format-of-warning-messages"></a>
84 <p>Warning messages have the format
112 <pre class="smallexample"> Assembler messages:
117 <a name="index-format-of-error-messages"></a>
[all …]
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/share/doc/as.html/ |
| H A D | Errors.html | 69 <a name="Error-and-Warning-Messages"></a>
70 <h3 class="section">1.7 Error and Warning Messages</h3>
73 <a name="index-error-messages"></a>
74 <a name="index-warning-messages"></a>
75 <a name="index-messages-from-assembler"></a>
76 <p><code>as</code> may write warnings and error messages to the standard error
83 <a name="index-format-of-warning-messages"></a>
84 <p>Warning messages have the format
112 <pre class="smallexample"> Assembler messages:
117 <a name="index-format-of-error-messages"></a>
[all …]
|
| /OK3568_Linux_fs/buildroot/dl/qt5location/git/src/3rdparty/mapbox-gl-native/include/mbgl/actor/ |
| H A D | actor.hpp | 23 The actor receives messages sent to it asynchronously, in a manner defined its `Scheduler`.
24 To store incoming messages before their receipt, each actor has a `Mailbox`, which acts as
25 a FIFO queue. Messages sent from actor S to actor R are guaranteed to be processed in the
26 order sent. However, relative order of messages sent by two *different* actors S1 and S2
31 a (weak) reference to the actor. Messages can be sent via the `Ref` as well.
33 It's safe -- and encouraged -- to pass `Ref`s between actors via messages. This is how two-way
44 (which it can use to self-send messages), followed by the forwarded arguments passed to
48 Please don't send messages that contain shared pointers or references. That subverts the
|
| /OK3568_Linux_fs/yocto/poky/meta/classes/ |
| H A D | insane.bbclass | 78 def package_qa_check_shebang_size(path, name, d, elf, messages):
98 …oe.qa.add_message(messages, "shebang-size", "%s: %s maximum shebang size exceeded, the maximum siz…
102 def package_qa_check_libexec(path,name, d, elf, messages):
110 …oe.qa.add_message(messages, "libexec", "%s: %s is using libexec please relocate to %s" % (name, pa…
116 def package_qa_check_rpath(file,name, d, elf, messages):
138 …oe.qa.add_message(messages, "rpaths", "package %s contains bad RPATH %s in file %s" % (name, rpath…
141 def package_qa_check_useless_rpaths(file, name, d, elf, messages):
168 …oe.qa.add_message(messages, "useless-rpaths", "%s: %s contains probably-redundant RPATH %s" % (nam…
171 def package_qa_check_dev(path, name, d, elf, messages):
177 …oe.qa.add_message(messages, "dev-so", "non -dev/-dbg/nativesdk- package %s contains symlink .so '%…
[all …]
|
| /OK3568_Linux_fs/buildroot/board/rockchip/electric/fs-overlay/etc/mosquitto/ |
| H A D | mosquitto.conf | 54 # retained messages. It is possible that the client that published the retained
62 # QoS 1 and 2 messages will be allowed inflight per client until this limit
67 # The maximum number of QoS 1 and 2 messages currently inflight per
69 # This includes messages that are partway through handshakes and
72 # and 2 messages.
87 # messages are received. You should be very sure this is the behaviour that you
110 # QoS 1 and 2 messages above those currently in-flight will be queued per
121 # The maximum number of QoS 1 and 2 messages to hold in a queue per client
139 # Received messages that exceed this size will not be accepted by the broker.
140 # The default value is 0, which means that all valid MQTT messages are
[all …]
|
| /OK3568_Linux_fs/kernel/tools/testing/selftests/ipc/ |
| H A D | msgque.c | 32 struct msg1 *messages; member
67 if (msgsnd(msgque->msq_id, &msgque->messages[i].mtype, in restore_queue()
68 msgque->messages[i].msize, IPC_NOWAIT) != 0) { in restore_queue()
97 if (ret != msgque->messages[cnt].msize) { in check_and_destroy_queue()
99 msgque->messages[cnt].msize); in check_and_destroy_queue()
103 if (message.mtype != msgque->messages[cnt].mtype) { in check_and_destroy_queue()
108 if (memcmp(message.mtext, msgque->messages[cnt].mtext, ret)) { in check_and_destroy_queue()
151 msgque->messages = malloc(sizeof(struct msg1) * ds.msg_qnum); in dump_queue()
152 if (msgque->messages == NULL) { in dump_queue()
162 ret = msgrcv(msgque->msq_id, &msgque->messages[i].mtype, in dump_queue()
[all …]
|
| /OK3568_Linux_fs/kernel/drivers/usb/dwc2/ |
| H A D | Kconfig | 68 bool "Enable Debugging Messages"
70 Say Y here to enable debugging messages in the DWC2 Driver.
73 bool "Enable Verbose Debugging Messages"
76 Say Y here to enable verbose debugging messages in the DWC2 Driver.
88 bool "Enable Debugging Messages For Periodic Transfers"
92 Say N here to disable (verbose) debugging messages to be
95 incomplete. Note that this also disables some debug messages
|
| /OK3568_Linux_fs/kernel/Documentation/firmware-guide/acpi/ |
| H A D | debug.rst | 14 option is turned off, the debug messages are not even built into the
20 When CONFIG_ACPI_DEBUG=y, you can select the component and level of messages
24 the debug messages.
73 The "debug_level" is a mask that selects different types of messages, e.g.,
74 those related to initialization, method execution, informational messages, etc.
137 Enable PCI and PCI interrupt routing debug messages::
141 Enable all ACPI hardware-related messages::
145 Enable all ACPI_DB_INFO messages after boot::
|
| /OK3568_Linux_fs/kernel/fs/ntfs/ |
| H A D | Kconfig | 36 performed by the driver as well as additional debugging messages to
37 be written to the system log. Note that debugging messages are
41 you can enable debugging messages by doing (as root):
43 Replacing the "1" with "0" would disable debug messages.
45 If you leave debugging messages disabled, this results in little
46 overhead, but enabling debug messages results in very significant
50 debugging messages while the misbehaviour was occurring.
|