Home
last modified time | relevance | path

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

12345678910>>...42

/Linux-v6.1/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-v6.1/Documentation/networking/devlink/
Dice.rst39 kernel only displayed a 2-digit version number (major.minor).
49 incremented whenever a major breaking change occurs, or when the
53 a fix is delivered as a patch against an older base Option ROM.
68 variation of the DDP package has a unique name.
97 ``devlink-flash`` interface. It supports updating the device flash using a
127 The ``ice`` driver supports activating new firmware after a flash update
135 The new firmware is activated by issuing a device specific Embedded
146 a predefined set of available port split options for the whole device.
148 A system reboot is required for port split to be applied.
175 ``devlink port unsplit`` will select the option with a split count of 1. If
[all …]
/Linux-v6.1/tools/testing/selftests/drivers/net/dsa/
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 …]
/Linux-v6.1/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 …]
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-v6.1/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-v6.1/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-v6.1/tools/testing/selftests/drivers/net/mlxsw/
Ddevlink_trap_control.sh181 )"01:80:C2:00:00:02:"$( : ETH daddr
202 )"01:80:C2:00:00:0E:"$( : ETH daddr
221 $MZ $h1 -c 1 -a own -b 01:00:5E:00:00:01 \
222 -A 192.0.2.1 -B 224.0.0.1 -t ip proto=2,p=11 -p 100 -q
229 "igmp_v1_report" $MZ $h1 -c 1 -a own -b 01:00:5E:00:00:01 \
230 -A 192.0.2.1 -B 244.0.0.1 -t ip proto=2,p=12 -p 100 -q
237 "igmp_v2_report" $MZ $h1 -c 1 -a own -b 01:00:5E:00:00:01 \
238 -A 192.0.2.1 -B 244.0.0.1 -t ip proto=2,p=16 -p 100 -q
245 "igmp_v3_report" $MZ $h1 -c 1 -a own -b 01:00:5E:00:00:01 \
246 -A 192.0.2.1 -B 244.0.0.1 -t ip proto=2,p=22 -p 100 -q
[all …]
/Linux-v6.1/tools/testing/selftests/bpf/
DREADME.rst10 Running Selftests in a VM
17 This script downloads a suitable Kconfig and VM userspace image from the system used by
60 // r9 is a pointer to map_value
61 // r7 is a scalar
62 17: bf 96 00 00 00 00 00 00 r6 = r9
63 18: 0f 76 00 00 00 00 00 00 r6 += r7
67 19: a5 07 01 00 01 01 00 00 if r7 < 257 goto +1
68 20: bf 96 00 00 00 00 00 00 r6 = r9
123 This is due to a llvm BPF backend bug. `The fix`__
147 14: 16 05 40 00 00 00 00 00 if w5 == 0 goto +64 <LBB0_6>
[all …]
/Linux-v6.1/Documentation/driver-api/
Dvfio-mediated-device.rst21 software, we have identified common requirements and a unified management
26 space in a secure, IOMMU-protected environment. This framework is used for
31 The mediated core driver provides a common interface for mediated device
33 provides a generic interface to perform these operations:
35 * Create and destroy a mediated device
36 * Add a mediated device to and remove it from a mediated bus driver
37 * Add a mediated device to and remove it from an IOMMU group
39 The mediated core driver also provides an interface to register a bus driver.
41 supports VFIO APIs. The mediated bus driver adds a mediated device to and
42 removes it from a VFIO group.
[all …]
/Linux-v6.1/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-v6.1/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-v6.1/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-v6.1/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-v6.1/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-v6.1/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 …]
/Linux-v6.1/tools/usb/usbip/
DREADME9 network. Server is a machine which provides (shares) a USB device. Client is
10 a machine which uses USB device provided by server over the network.
11 The USB device may be either physical device connected to a server or
12 software entity created on a server using USB gadget subsystem.
16 A client side kernel module which provides a virtual USB Host Controller
17 and allows to import a USB device from a remote machine.
20 A server side module which provides a USB device driver which can be
21 bound to a physical USB device to make it exportable.
24 A server side module which provides a virtual USB Device Controller and allows
25 to export a USB device created using USB Gadget Subsystem.
[all …]
/Linux-v6.1/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-v6.1/Documentation/staging/
Dstatic-keys.rst30 performance-sensitive fast-path kernel code, via a GCC feature and a code
31 patching technique. A quick example::
56 Currently, tracepoints are implemented using a conditional branch. The
57 conditional check requires checking a global variable for each tracepoint.
72 gcc (v4.5) adds a new 'asm goto' statement that allows branching to a label:
80 For example, if we have a simple branch that is disabled by default::
86 consist of a single atomic 'no-op' instruction (5 bytes on x86), in the
88 'no-op' in the straight-line codepath with a 'jump' instruction to the
100 In order to make use of this optimization you must first define a key::
146 reference counting. For example, if the key is initialized true, a
[all …]
/Linux-v6.1/tools/testing/selftests/drivers/net/mlxsw/spectrum-2/
Dvxlan_flooding_ipv6.sh4 # Test VxLAN flooding. The device stores flood records in a singly linked list
7 # of a record in the middle of the list.
176 bridge fdb append 00:00:00:00:00:00 dev vxlan0 self \
234 declare -a packets=(1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1)
251 # and check that packet is flooded correctly when we remove a record
256 bridge fdb del 00:00:00:00:00:00 dev vxlan0 self dst 2001:db8:2::10
257 bridge fdb del 00:00:00:00:00:00 dev vxlan0 self dst 2001:db8:2::11
258 bridge fdb del 00:00:00:00:00:00 dev vxlan0 self dst 2001:db8:2::12
259 bridge fdb del 00:00:00:00:00:00 dev vxlan0 self dst 2001:db8:2::13
269 bridge fdb del 00:00:00:00:00:00 dev vxlan0 self dst 2001:db8:2::2
[all …]
/Linux-v6.1/tools/testing/selftests/drivers/net/mlxsw/spectrum/
Dvxlan_flooding_ipv6.sh4 # Test VxLAN flooding. The device stores flood records in a singly linked list
7 # of a record in the middle of the list.
165 bridge fdb append 00:00:00:00:00:00 dev vxlan0 self \
217 declare -a packets=(1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1)
234 # and check that packet is flooded correctly when we remove a record
239 bridge fdb del 00:00:00:00:00:00 dev vxlan0 self dst 2001:db8:2::12
240 bridge fdb del 00:00:00:00:00:00 dev vxlan0 self dst 2001:db8:2::13
241 bridge fdb del 00:00:00:00:00:00 dev vxlan0 self dst 2001:db8:2::14
242 bridge fdb del 00:00:00:00:00:00 dev vxlan0 self dst 2001:db8:2::15
243 bridge fdb del 00:00:00:00:00:00 dev vxlan0 self dst 2001:db8:2::16
[all …]
/Linux-v6.1/Documentation/s390/
Ds390dbf.rst11 The goal of this feature is to provide a kernel debug logging API
14 One purpose of this is to inspect the debug logs after a production system crash
17 If the system still runs but only a subcomponent which uses dbf fails,
18 it is possible to look at the debug logs on a live system via the Linux
27 This function initializes a
28 debug log for the caller. For each debug log exists a number of debug areas
35 of the active debug area is reached, a wrap around is done (ring buffer)
42 overwritten when a wrap around for the current area occurs.
44 The debug areas themselves are also ordered in form of a ring buffer.
60 The debug logs can be inspected in a live system through entries in
[all …]

12345678910>>...42