Home
last modified time | relevance | path

Searched +full:00 +full:a (Results 1 – 25 of 1045) sorted by relevance

12345678910>>...42

/linux-6.14.4/Documentation/networking/devlink/
Dice.rst27 - The ice hardware uses hierarchical scheduling for Tx with a fixed
29 points. Root node represents a port, while all the leaves represent
39 One example would be sending traffic to queues that are not a multiple
41 the 9th queue has a different parent than the rest, and it's given
42 more bandwidth credits. This causes a problem when the system is
55 To address this need, you can switch to a 5-layer topology, which
59 is a lower configuration depth of the tree.
63 use a value of 5. For example:
66 Use a value of 9 to set it back to the default value.
130 kernel only displayed a 2-digit version number (major.minor).
[all …]
Ddevlink-port.rst9 ``devlink-port`` is a port that exists on the device. It has a logically
10 separate ingress/egress point of the device. A devlink port can be any one
11 of many flavours. A devlink port flavour along with port attributes
12 describe what a port represents.
14 A device driver that intends to publish a devlink port sets the
28 - This indicates a DSA interconnect port.
30 - This indicates a CPU port applicable only to DSA.
32 - This indicates an eswitch port representing a port of PCI
35 - This indicates an eswitch port representing a port of PCI
38 - This indicates an eswitch port representing a port of PCI
[all …]
/linux-6.14.4/Documentation/bpf/
Dllvm_reloc.rst34 0: 18 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 r1 = 0 ll
36 2: 61 11 00 00 00 00 00 00 r1 = *(u32 *)(r1 + 0)
37 3: 18 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 r2 = 0 ll
39 5: 61 20 00 00 00 00 00 00 r0 = *(u32 *)(r2 + 0)
40 6: 0f 10 00 00 00 00 00 00 r0 += r1
41 7: 18 01 00 00 08 00 00 00 00 00 00 00 00 00 00 00 r1 = 8 ll
43 9: 61 11 00 00 00 00 00 00 r1 = *(u32 *)(r1 + 0)
44 10: 0f 10 00 00 00 00 00 00 r0 += r1
45 11: 18 01 00 00 0c 00 00 00 00 00 00 00 00 00 00 00 r1 = 12 ll
47 13: 61 11 00 00 00 00 00 00 r1 = *(u32 *)(r1 + 0)
[all …]
/linux-6.14.4/drivers/gpu/drm/tests/
Ddrm_kunit_edid.h9 * 00 ff ff ff ff ff ff 00 31 d8 2a 00 00 00 00 00
10 * 00 21 01 03 81 a0 5a 78 0a 00 00 00 00 00 00 00
11 * 00 00 00 00 00 00 01 01 01 01 01 01 01 01 01 01
12 * 01 01 01 01 01 01 02 3a 80 18 71 38 2d 40 58 2c
13 * 45 00 40 84 63 00 00 1e 00 00 00 fc 00 54 65 73
14 * 74 20 45 44 49 44 0a 20 20 20 00 00 00 fd 00 32
15 * 46 1e 46 0f 00 0a 20 20 20 20 20 20 00 00 00 10
16 * 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ab
67 * 00 ff ff ff ff ff ff 00 31 d8 2a 00 00 00 00 00
68 * 00 21 01 03 81 a0 5a 78 02 00 00 00 00 00 00 00
[all …]
/linux-6.14.4/tools/testing/selftests/net/forwarding/
Dbridge_mld.sh11 TEST_GROUP_MAC="33:33:00:00:00:cc"
14 MZPKT_IS_INC="33:33:00:00:00:01:fe:54:00:04:5e:ba:86:dd:60:0a:2d:ae:00:54:00:01:fe:80:00:\
15 00:00:00:00:00:fc:54:00:ff:fe:04:5e:ba:ff:02:00:00:00:00:00:00:00:00:00:00:00:00:00:01:3a:\
16 00:05:02:00:00:00:00:8f:00:8e:d9:00:00:00:01:01:00:00:03:ff:02:00:00:00:00:00:00:00:00:00:\
17 00:00:00:00:cc:20:01:0d:b8:00:01:00:00:00:00:00:00:00:00:00:01:20:01:0d:b8:00:01:00:00:00:\
18 00:00:00:00:00:00:02:20:01:0d:b8:00:01:00:00:00:00:00:00:00:00:00:03"
20 MZPKT_IS_INC2="33:33:00:00:00:01:fe:54:00:04:5e:ba:86:dd:60:0a:2d:ae:00:54:00:01:fe:80:00:\
21 00:00:00:00:00:fc:54:00:ff:fe:04:5e:ba:ff:02:00:00:00:00:00:00:00:00:00:00:00:00:00:01:3a:00:\
22 05:02:00:00:00:00:8f:00:8e:ac:00:00:00:01:01:00:00:03:ff:02:00:00:00:00:00:00:00:00:00:00:00:\
23 00:00:cc:20:01:0d:b8:00:01:00:00:00:00:00:00:00:00:00:10:20:01:0d:b8:00:01:00:00:00:00:00:00:\
[all …]
Dbridge_igmp.sh11 TEST_GROUP_MAC="01:00:5e:0a:0a:0a"
14 ALL_MAC="01:00:5e:00:00:01"
17 MZPKT_IS_INC="22:00:9d:de:00:00:00:01:01:00:00:03:ef:0a:0a:0a:c0:00:02:01:c0:00:02:02:c0:00:02:03"
19 MZPKT_IS_INC2="22:00:9d:c3:00:00:00:01:01:00:00:03:ef:0a:0a:0a:c0:00:02:0a:c0:00:02:0b:c0:00:02:0c"
21 MZPKT_IS_INC3="22:00:5f:b4:00:00:00:01:01:00:00:02:ef:0a:0a:0a:c0:00:02:14:c0:00:02:1e"
23 MZPKT_ALLOW="22:00:99:c3:00:00:00:01:05:00:00:03:ef:0a:0a:0a:c0:00:02:0a:c0:00:02:0b:c0:00:02:0c"
25 MZPKT_ALLOW2="22:00:5b:b4:00:00:00:01:05:00:00:02:ef:0a:0a:0a:c0:00:02:14:c0:00:02:1e"
27 MZPKT_IS_EXC="22:00:da:b6:00:00:00:01:02:00:00:04:ef:0a:0a:0a:c0:00:02:01:c0:00:02:02:c0:00:02:14:c…
29 MZPKT_IS_EXC2="22:00:5e:b4:00:00:00:01:02:00:00:02:ef:0a:0a:0a:c0:00:02:14:c0:00:02:1e"
31 MZPKT_TO_EXC="22:00:9a:b1:00:00:00:01:04:00:00:03:ef:0a:0a:0a:c0:00:02:01:c0:00:02:14:c0:00:02:1e"
[all …]
Dlocal_termination.sh18 BRIDGE_ADDR="00:00:de:ad:be:ee"
19 MACVLAN_ADDR="00:00:de:ad:be:ef"
32 JOINED_MACV4_MC_ADDR="01:00:5e:01:02:03"
33 UNKNOWN_MACV4_MC_ADDR1="01:00:5e:01:02:04"
34 UNKNOWN_MACV4_MC_ADDR2="01:00:5e:01:02:05"
35 UNKNOWN_MACV4_MC_ADDR3="01:00:5e:01:02:06"
42 01:1b:19:00:00:00 00:00:de:ad:be:ef 88:f7 00 02 \
43 00 2c 00 00 02 00 00 00 00 00 00 00 00 00 00 00 \
44 00 00 3e 37 63 ff fe cf 17 0e 00 01 00 00 00 00 \
45 00 00 00 00 00 00 00 00 00 00"
[all …]
Dvxlan_bridge_1d.sh148 bridge fdb append dev vx1 00:00:00:00:00:00 dst 192.0.2.34 self
149 bridge fdb append dev vx1 00:00:00:00:00:00 dst 192.0.2.50 self
157 bridge fdb del dev vx1 00:00:00:00:00:00 dst 192.0.2.50 self
158 bridge fdb del dev vx1 00:00:00:00:00:00 dst 192.0.2.34 self
212 bridge fdb append dev vx2 00:00:00:00:00:00 dst 192.0.2.17 self
213 bridge fdb append dev vx2 00:00:00:00:00:00 dst $other_in_addr self
308 bridge fdb del dev vx1 00:00:00:00:00:00 dst 192.0.2.50 self
309 bridge fdb del dev vx1 00:00:00:00:00:00 dst 192.0.2.34 self
315 bridge fdb append dev vx1 00:00:00:00:00:00 dst 192.0.2.34 self
316 bridge fdb append dev vx1 00:00:00:00:00:00 dst 192.0.2.50 self
[all …]
Dvxlan_bridge_1q.sh190 bridge fdb append dev vx10 00:00:00:00:00:00 dst 192.0.2.34 self
191 bridge fdb append dev vx10 00:00:00:00:00:00 dst 192.0.2.50 self
193 bridge fdb append dev vx20 00:00:00:00:00:00 dst 192.0.2.34 self
194 bridge fdb append dev vx20 00:00:00:00:00:00 dst 192.0.2.50 self
199 bridge fdb del dev vx20 00:00:00:00:00:00 dst 192.0.2.50 self
200 bridge fdb del dev vx20 00:00:00:00:00:00 dst 192.0.2.34 self
202 bridge fdb del dev vx10 00:00:00:00:00:00 dst 192.0.2.50 self
203 bridge fdb del dev vx10 00:00:00:00:00:00 dst 192.0.2.34 self
277 bridge fdb append dev vx10 00:00:00:00:00:00 dst 192.0.2.17 self
278 bridge fdb append dev vx10 00:00:00:00:00:00 dst $other_in_addr self
[all …]
/linux-6.14.4/samples/vfio-mdev/
DREADME.rst4 mtty is a sample vfio-mdev driver that demonstrates how to use the mediated
7 The sample driver creates an mdev device that simulates a serial port over a PCI
12 This step creates a dummy device, /sys/devices/virtual/mtty/mtty/
42 2. Create a mediated device by using the dummy device that you created in the
58 # lspci -s 00:05.0 -xxvv
59 00:05.0 Serial controller: Device 4348:3253 (rev 10) (prog-if 02 [16550])
66 Interrupt: pin A routed to IRQ 10
70 00: 48 43 53 32 01 00 00 02 10 02 00 07 00 00 00 00
71 10: 51 c1 00 00 59 c1 00 00 00 00 00 00 00 00 00 00
72 20: 00 00 00 00 00 00 00 00 00 00 00 00 48 43 53 32
[all …]
/linux-6.14.4/tools/testing/selftests/hid/tests/
Dtest_multitouch.py492 …00 05 09 19 01 29 03 15 00 25 01 95 03 75 01 81 02 95 05 81 03 05 01 15 00 26 ff 0f 55 0e 65 11 75…
497 # this device has *a lot* of different reports, and most of them
498 # have the Touch Screen application. But the first one is a stylus
585 """send a single touch in the first slot of the device,
613 Make sure the kernel sees this as a dual touch.
691 Make sure the kernel sees this as a triple touch.
787 A report should forward an accurate contact count and the kernel
831 """send a single touch in the first slot of the device, with
856 Kernel is supposed to mark the contact with a distance > 0
904 If a touch is reported more than once with the same Contact ID,
[all …]
Dtest_tablet.py34 """Represents whether a button is pressed on the stylus"""
207 """Following the state machine in the URL above, with a couple of addition
337 we now have a button.
414 However, a half broken device might export those transitions.
415 For example, a pen that has the eraser button might wobble between
676 # now check for a valid transition
685 """Internal method to test against a list of
687 state_list is a list of PenState objects
688 scribble is a boolean which tells if we need
689 to wobble a little the X,Y coordinates of the pen
[all …]
/linux-6.14.4/Documentation/scsi/
Dsym53c8xx_2.rst35 8.7 Reset all logical units of a target
36 8.8 Abort all tasks of all logical units of a target
47 10.2.7 Suggest a default SCSI id for hosts
52 10.2.12 Exclude a host from being attached
101 Write a glue code for Linux.
153 |810A | N | N | FAST10 | 10 MB/s | Y | N |
159 |825A | Y | Y | FAST10 | 20 MB/s | Y | N |
165 |875A | Y | Y | FAST20 | 40 MB/s | Y | Y |
171 |895A | Y | Y | FAST40 | 80 MB/s | Y | Y |
217 driver also incorporates a different SCRIPTS set based on MEMORY MOVE, in
[all …]
Dncr53c8xx.rst35 8.9 Reset all logical units of a target
36 8.10 Abort all tasks of all logical units of a target
60 10.2.20 Exclude a host from being attached
61 10.2.21 Suggest a default SCSI id for hosts
74 14.3 Using only 8 bit devices with a WIDE SCSI controller.
75 14.4 Possible data corruption during a Memory Write and Invalidate
94 The initial Linux ncr53c8xx driver has been a port of the ncr driver from
104 It is now available as a bundle of 2 drivers:
108 the new 895A (1 channel LVD SCSI controller).
109 - sym53c8xx enhanced driver (a.k.a. 896 drivers) that drops support of oldest
[all …]
/linux-6.14.4/drivers/tty/vt/
Dcp437.uni13 # Basic IBM dingbats, some of which will never have a purpose clear
17 0x01 U+263a
29 0x0d U+266a
31 0x0f U+263c U+00a4
36 0x14 U+00b6
37 0x15 U+00a7
54 0x22 U+0022 U+00a8
59 0x27 U+0027 U+00b4
62 0x2a U+002a
64 0x2c U+002c U+00b8
[all …]
/linux-6.14.4/tools/testing/selftests/drivers/net/mlxsw/
Ddevlink_trap_control.sh182 )"01:80:C2:00:00:02:"$( : ETH daddr
203 )"01:80:C2:00:00:0E:"$( : ETH daddr
222 $MZ $h1 -c 1 -a own -b 01:00:5E:00:00:01 \
223 -A 192.0.2.1 -B 224.0.0.1 -t ip proto=2,p=11 -p 100 -q
230 "igmp_v1_report" $MZ $h1 -c 1 -a own -b 01:00:5E:00:00:01 \
231 -A 192.0.2.1 -B 244.0.0.1 -t ip proto=2,p=12 -p 100 -q
238 "igmp_v2_report" $MZ $h1 -c 1 -a own -b 01:00:5E:00:00:01 \
239 -A 192.0.2.1 -B 244.0.0.1 -t ip proto=2,p=16 -p 100 -q
246 "igmp_v3_report" $MZ $h1 -c 1 -a own -b 01:00:5E:00:00:01 \
247 -A 192.0.2.1 -B 244.0.0.1 -t ip proto=2,p=22 -p 100 -q
[all …]
/linux-6.14.4/tools/testing/selftests/bpf/
DREADME.rst13 BPF employs a continuous integration (CI) system to check patch submission in an
14 automated fashion. The system runs selftests for each patch in a series. Results
16 violations of other checks (such as additional warnings being emitted or a
21 The CI system executes tests on multiple architectures. It uses a kernel
30 In such a case tests in CI may fail. An example of such a shortcoming is BPF
39 question. This can be the name of a test suite or of an individual test. The
41 classify the entry: column two is a copy and paste of the error being reported
43 available, summarizes the underlying problem. A value of ``trampoline``, for
49 Running Selftests in a VM
57 This script uses the in-tree kernel configuration and downloads a VM userspace
[all …]
/linux-6.14.4/Documentation/networking/device_drivers/ethernet/3com/
Dvortex.rst67 - 3c982 Hydra Dual Port A
91 Where N is a number from 0 to 7. Anything above 3 produces a lot
102 The individual options are composed of a number of bitfields which
121 When generating a value for the 'options' setting, the above media
162 PAUSE command, which means that they will stop sending packets for a
163 short period if they receive a PAUSE frame from the link partner.
165 The driver only allows flow control on a link which is operating in
172 sent to the reserved destination address of 01:80:c2:00:00:01. They
178 for receiving. When a packet arrives, the driver has to decide
180 a smaller buffer and copy the packet across into it.
[all …]
/linux-6.14.4/Documentation/userspace-api/ioctl/
Dioctl-number.rst21 system calls 'write' and 'read'. For example, a SET_FOO ioctl would
23 a GET_FOO ioctl would be _IOR, although the kernel would actually write
28 many drivers share a partial letter with other drivers.
30 If you are writing a driver for a new device and need a letter, pick an
36 The second argument to _IO, _IOW, _IOR, or _IOWR is a sequence number
50 if a program calls an ioctl on the wrong device, it will get an
73 0x00 00-1F linux/fs.h conflict!
74 0x00 00-1F scsi/scsi_ioctl.h conflict!
75 0x00 00-1F linux/fb.h conflict!
76 0x00 00-1F linux/wavefront.h conflict!
[all …]
/linux-6.14.4/Documentation/driver-api/driver-model/
Dporting.rst17 negative effect on kernel drivers, and to allow a gradual transition
20 In a nutshell, the driver model consists of a set of objects that can
39 - Define a struct bus_type for the bus driver::
60 as a module) by doing::
67 Other code may wish to reference the bus type, so declare it in a
93 struct device represents a single device. It mainly contains metadata
97 - Embed a struct device in the bus-specific device type::
144 Also, the location of the device's sysfs directory depends on a
145 device's parent. sysfs exports a directory structure that mirrors
149 The device's bus field is a pointer to the bus type the device
[all …]
/linux-6.14.4/Documentation/hid/
Dhidintro.rst7 This chapter is meant to give a broad overview of what HID report
8 descriptors are, and of how a casual (non-kernel) programmer can deal
25 are using to interact with a computer, be it a mouse, a touchpad, a
26 tablet, a microphone.
29 For example, mice can have any number of buttons; they may have a
36 through the *HID report descriptor*, a fixed set of bytes describing
39 a HID Report Descriptor may specify that "in a report with ID 3 the
40 bits from 8 to 15 is the delta x coordinate of a mouse".
46 ("Feature reports"). A device may support one or more HID reports.
52 needs to be dealt with in a special way, or because some special
[all …]
/linux-6.14.4/Documentation/ABI/stable/
Dsysfs-class-tpm5 Description: The device/ directory under a specific TPM instance exposes
13 Description: The "active" property prints a '1' if the TPM chip is accepting
16 visible to the OS, but will only accept a restricted set of
41 Manufacturer is a hex dump of the 4 byte manufacturer info
42 space in a TPM. TCG version shows the TCG TPM spec level that
51 used to wait for a short, medium and long TPM command. All
54 any longer than necessary before starting to poll for a
64 Durations can be modified in the case where a buggy chip
73 Description: The "enabled" property prints a '1' if the TPM chip is enabled,
75 may be visible but produce a '0' after some operation that
[all …]
/linux-6.14.4/Documentation/ABI/testing/
Dsysfs-driver-toshiba_acpi1 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/kbd_backlight_mode
17 a reboot for changes to take effect.
20 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/kbd_backlight_timeout
33 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/position
40 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/touchpad
52 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/available_kbd_modes
68 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/kbd_type
79 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/usb_sleep_charge
98 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/sleep_functions_on_battery
116 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/usb_rapid_charge
[all …]
/linux-6.14.4/drivers/net/wireless/marvell/libertas/
Dcfg.c170 * TLV-ID SSID 00 00 in lbs_add_ssid_tlv()
171 * length 06 00 in lbs_add_ssid_tlv()
200 * length 0e 00 in lbs_add_channel_list_tlv()
201 * channel 00 01 00 00 00 64 00 in lbs_add_channel_list_tlv()
202 * radio type 00 in lbs_add_channel_list_tlv()
204 * scan type 00 in lbs_add_channel_list_tlv()
205 * min scan time 00 00 in lbs_add_channel_list_tlv()
206 * max scan time 64 00 in lbs_add_channel_list_tlv()
207 * channel 2 00 02 00 00 00 64 00 in lbs_add_channel_list_tlv()
243 * there's a firmware which otherwise doesn't report all
[all …]
/linux-6.14.4/Documentation/trace/
Dhisi-ptt.rst10 HiSilicon PCIe tune and trace device (PTT) is a PCIe Root Complex
18 PCIe cores. Each PCIe core includes several Root Ports and a PTT
52 Each event is presented as a file under $(PTT PMU dir)/tune, and
53 a simple open/read/write/close cycle will be used to tune the event.
86 Writing a negative value will return an error, and out of range
88 indicates a probable level, but is not precise.
101 watermark reached or when timed out. For a busy direction, you should
106 Writing a negative value will return an error, and out of range
108 indicates a probable level, but is not precise.
116 or those downstream of a set of Root Ports on the same core of the PTT
[all …]

12345678910>>...42