Searched +full:binary +full:- +full:coded (Results 1 – 10 of 10) sorted by relevance
| /Documentation/devicetree/bindings/usb/ |
| D | usb-drd.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/usb/usb-drd.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Greg Kroah-Hartman <gregkh@linuxfoundation.org>
13 otg-rev:
16 which the device and its descriptors are compliant, in binary-coded
18 features (HNP/SRP/ADP) is enabled. If ADP is required, otg-rev should be
25 Tells Dual-Role USB controllers that we want to work on a particular
32 hnp-disable:
[all …]
|
| D | aspeed,usb-vhub.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/usb/aspeed,usb-vhub.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Benjamin Herrenschmidt <benh@kernel.crashing.org>
26 - aspeed,ast2400-usb-vhub
27 - aspeed,ast2500-usb-vhub
28 - aspeed,ast2600-usb-vhub
39 aspeed,vhub-downstream-ports:
46 aspeed,vhub-generic-endpoints:
[all …]
|
| /Documentation/staging/ |
| D | crc32.rst | 5 A CRC is a long-division remainder. You add the CRC to the message,
11 protocols put the end-of-frame flag after the CRC.
15 - We're working in binary, so the digits are only 0 and 1, and
16 - When dividing polynomials, there are no carries. Rather than add and
21 To produce a 32-bit CRC, the divisor is actually a 33-bit CRC polynomial.
24 familiar with the IEEE 754 floating-point format, it's the same idea.)
28 the best error-detecting properties, this should correspond to the
29 order they're actually sent. For example, standard RS-232 serial is
30 little-endian; the most significant bit (sometimes used for parity)
38 back into range. In binary, this is easy - it has to be either 0 or 1,
[all …]
|
| /Documentation/input/ |
| D | event-codes.rst | 1 .. _input-event-codes:
36 - Used as markers to separate events. Events may be separated in time or in
41 - Used to describe state changes of keyboards, buttons, or other key-like
46 - Used to describe relative axis value changes, e.g. moving the mouse 5 units
51 - Used to describe absolute axis value changes, e.g. describing the
56 - Used to describe miscellaneous input data that do not fit into other types.
60 - Used to describe binary state input switches.
64 - Used to turn LEDs on devices on and off.
68 - Used to output sound to devices.
72 - Used for autorepeating devices.
[all …]
|
| /Documentation/devicetree/ |
| D | usage-model.rst | 1 .. SPDX-License-Identifier: GPL-2.0
44 ----------
49 thereby support a majority of available hardware without hard coded
56 In 2005, when PowerPC Linux began a major cleanup and to merge 32-bit
57 and 64-bit support, the decision was made to require DT support on all
60 Tree (FDT) was created which could be passed to the kernel as a binary
61 blob without requiring a real Open Firmware implementation. U-Boot,
63 Device Tree Binary (dtb) and to modify a dtb at boot time. DT was
66 existing non-DT aware firmware.
74 -------------
[all …]
|
| /Documentation/process/ |
| D | 4.Coding.rst | 6 While there is much to be said for a solid and community-oriented design
19 ---------
25 :ref:`Documentation/process/coding-style.rst <codingstyle>`. For much of
33 code to the kernel is very difficult if that code is not coded according to
38 strangely-formatted code.
43 giving up a degree of control in a number of ways - including control over
49 as a way of getting their name into the kernel changelogs - or both. But
59 80-column limit, for example), just do it.
61 Note that you can also use the ``clang-format`` tool to help you with
62 these rules, to quickly re-format parts of your code automatically,
[all …]
|
| /Documentation/networking/ |
| D | arcnet-hardware.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 2) This file is no longer Linux-specific. It should probably be moved out
17 e-mail apenwarr@worldvisions.ca with any settings for your particular card,
39 There are two "types" of ARCnet - STAR topology and BUS topology. This
46 well-designed standard. It uses something called "modified token passing"
47 which makes it completely incompatible with so-called "Token Ring" cards,
63 programming interface also means that when high-performance hardware
73 although they are generally kept down to the Ethernet-style 1500 bytes.
91 - Avery Pennraun <apenwarr@worldvisions.ca>
92 - Stephen A. Wood <saw@hallc1.cebaf.gov>
[all …]
|
| D | ethtool-netlink.rst | 27 wake-on-lan password) omitted.
37 number 1 but any non-zero value should be understood as "true" by recipient.
44 Attributes that need to be filled-in by device drivers and that are dumped to
97 attribute with contents of one of two forms: compact (two binary bitmaps
98 representing bit values and mask of affected bits) and bit-by-bit (list of
101 Verbose (bit-by-bit) bitsets allow sending symbolic names for bits together
121 ``ETHTOOL_A_BITSET_VALUE`` binary bitmap of bit values
122 ``ETHTOOL_A_BITSET_MASK`` binary bitmap of valid bits
126 rounded up to a multiple of 32 bits. They consist of 32-bit words in host byte
141 Bit-by-bit form: nested (bitset) attribute contents:
[all …]
|
| /Documentation/admin-guide/cifs/ |
| D | usage.rst | 18 MS-SMB2 (for detailed SMB2/SMB3/SMB3.1.1 protocol specification)
36 (e.g. /usr/src/linux-2.5.73)
48 the modules directory e.g. /lib/modules/6.3.0-060300-generic/kernel/fs/smb/client/cifs.ko).
57 required, mount.cifs is recommended. Most distros include a ``cifs-utils``
63 found at cifs-utils.git on git.samba.org
122 mounts, unless umount is invoked with -i (which will avoid invoking a umount
166 disabled on a per-mount basis by specifying ``nouser_xattr`` on mount.
184 (the few optional settings are passed in on mount via -o parameters instead).
191 ln -s /mnt/foo bar
196 that is ignored by local server applications and non-cifs clients and that will
[all …]
|
| /Documentation/RCU/Design/Requirements/ |
| D | Requirements.rst | 16 ------------
18 Read-copy update (RCU) is a synchronization mechanism that is often used
19 as a replacement for reader-writer locking. RCU is unusual in that
20 updaters do not block readers, which means that RCU's read-side
28 thought of as an informal, high-level specification for RCU. It is
40 #. `Fundamental Non-Requirements`_
42 #. `Quality-of-Implementation Requirements`_
44 #. `Software-Engineering Requirements`_
53 ------------------------
58 #. `Grace-Period Guarantee`_
[all …]
|