| /kernel/linux/linux-6.6/tools/testing/selftests/drivers/net/dsa/ |
| D | bridge_mdb.sh | 6 # | + $h1.10 | | + $h2.10 |
21 # | | vid 10 vid 10 | |
40 vlan_create $h1 10 v$h1 192.0.2.1/28 2001:db8:1::1/64
47 vlan_destroy $h1 10
54 vlan_create $h2 10 v$h2 192.0.2.2/28
61 vlan_destroy $h2 10
69 bridge vlan add vid 10 dev br0 self
75 bridge vlan add vid 10 dev $swp1
80 bridge vlan add vid 10 dev $swp2
93 bridge vlan del vid 10 dev $swp2
[all …]
|
| /kernel/linux/linux-6.6/tools/testing/selftests/net/forwarding/ |
| D | bridge_mdb.sh | 6 # | + $h1.10 | | + $h2.10 |
21 # | | vid 10 vid 10 | |
40 vlan_create $h1 10 v$h1 192.0.2.1/28 2001:db8:1::1/64
47 vlan_destroy $h1 10
54 vlan_create $h2 10 v$h2 192.0.2.2/28
61 vlan_destroy $h2 10
69 bridge vlan add vid 10 dev br0 self
75 bridge vlan add vid 10 dev $swp1
80 bridge vlan add vid 10 dev $swp2
93 bridge vlan del vid 10 dev $swp2
[all …]
|
| /kernel/linux/linux-5.10/tools/testing/selftests/net/ |
| D | so_txtime.sh | 20 ./so_txtime -4 -6 -c mono a,-1 a,-1
21 ./so_txtime -4 -6 -c mono a,0 a,0
22 ./so_txtime -4 -6 -c mono a,10 a,10
23 ./so_txtime -4 -6 -c mono a,10,b,20 a,10,b,20
24 ./so_txtime -4 -6 -c mono a,20,b,10 b,20,a,20
27 ! ./so_txtime -4 -6 -c tai a,-1 a,-1
28 ! ./so_txtime -4 -6 -c tai a,0 a,0
29 ./so_txtime -4 -6 -c tai a,10 a,10
30 ./so_txtime -4 -6 -c tai a,10,b,20 a,10,b,20
31 ./so_txtime -4 -6 -c tai a,20,b,10 b,10,a,20
|
| /kernel/linux/linux-6.6/tools/testing/selftests/drivers/net/mlxsw/ |
| D | rtnetlink.sh | 63 # Test that it is possible to set an IP address on a VRF upper despite
67 ip link add name vrf-test type vrf table 10
90 # Create a FID RIF
97 # Prepare a device with a low MAC address
104 check_err $? "Could not attach a device with low MAC to a bridge with RIF"
106 # Port MAC address change should be allowed for a bridge with set MAC.
120 # Test that when a VLAN interface is deleted, its associated router
129 ip link add link br0 name br0.10 type vlan id 10
130 ip -6 address add 2001:db8:1::1/64 dev br0.10
131 ip link del dev br0.10
[all …]
|
| D | ingress_rif_conf_1q.sh | 7 # already has a RIF.
12 # | $h1.10 + | | + $h2.10 |
26 # | br0.10 |
56 vlan_create $h1 10 v$h1 192.0.2.1/28
65 vlan_destroy $h1 10
72 vlan_create $h2 10 v$h2 192.0.2.3/28
77 vlan_destroy $h2 10
99 # By default, a link-local address is generated when netdevice becomes
100 # up. Adding an address to the bridge will cause creating a RIF for it.
108 bridge vlan add vid 10 dev $swp2
[all …]
|
| /kernel/linux/linux-5.10/tools/testing/selftests/drivers/net/mlxsw/ |
| D | rtnetlink.sh | 78 check_fail $? "IP address addition passed for a device with a wrong MAC"
88 # Change of MAC address of a RIF should be forbidden if the new MAC
91 check_fail $? "change of MAC address passed for a wrong MAC"
107 # Test that it is possible to set an IP address on a VRF upper despite
111 ip link add name vrf-test type vrf table 10
132 # Create a FID RIF
138 # Prepare a device with a low MAC address
145 check_fail $? "Device with low MAC was permitted to attach a bridge with RIF"
173 # Create a FID RIF
180 # Prepare a device with a low MAC address
[all …]
|
| /kernel/linux/linux-5.10/include/uapi/drm/ |
| D | drm_fourcc.h | 4 * Permission is hereby granted, free of charge, to any person obtaining a
17 * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
38 * fourcc code, a Format Modifier may optionally be provided, in order to
44 * Format modifiers are used in conjunction with a fourcc code, forming a
56 * vendor-namespaced, and as such the relationship between a fourcc code and a
69 #define fourcc_code(a, b, c, d) ((__u32)(a) | ((__u32)(b) << 8) | \ argument
104 #define DRM_FORMAT_ARGB4444 fourcc_code('A', 'R', '1', '2') /* [15:0] A:R:G:B 4:4:4:4 little endian…
105 #define DRM_FORMAT_ABGR4444 fourcc_code('A', 'B', '1', '2') /* [15:0] A:B:G:R 4:4:4:4 little endian…
106 #define DRM_FORMAT_RGBA4444 fourcc_code('R', 'A', '1', '2') /* [15:0] R:G:B:A 4:4:4:4 little endian…
107 #define DRM_FORMAT_BGRA4444 fourcc_code('B', 'A', '1', '2') /* [15:0] B:G:R:A 4:4:4:4 little endian…
[all …]
|
| /kernel/linux/linux-6.6/tools/testing/selftests/net/ |
| D | so_txtime.sh | 73 do_test 4 mono a,-1 a,-1
74 do_test 6 mono a,0 a,0
75 do_test 6 mono a,10 a,10
76 do_test 4 mono a,10,b,20 a,10,b,20
77 do_test 6 mono a,20,b,10 b,20,a,20
80 ! do_test 4 tai a,-1 a,-1
81 ! do_test 6 tai a,0 a,0
82 do_test 6 tai a,10 a,10
83 do_test 4 tai a,10,b,20 a,10,b,20
84 do_test 6 tai a,20,b,10 b,10,a,20
|
| D | test_bridge_backup_port.sh | 7 # redirected to the VXLAN port (vx0). When a backup nexthop ID is configured,
24 # | br0.10 | | br0.10 |
77 read a
78 [ "$a" = "q" ] && exit 1
85 read a
86 [ "$a" = "q" ] && exit 1
105 if [ "$VERBOSE" = "1" -a -n "$out" ]; then
182 ip -n $ns link add link br0 name br0.10 up type vlan id 10
183 bridge -n $ns vlan add vid 10 dev br0 self
184 ip -n $ns address add $br_addr/28 dev br0.10
[all …]
|
| /kernel/linux/linux-6.6/Documentation/gpu/ |
| D | afbc.rst | 7 AFBC is a proprietary lossless image compression protocol and format.
21 AFBC streams can contain several components - where a component
22 corresponds to a color channel (i.e. R, G, B, X, A, Y, Cb, Cr).
45 * Component 3: A(8)
70 Please note, however, that the inclusion of a "wasted" 'X' channel is
72 formats containing 'X' bits. If a fourth component is
75 '1'. If there is no requirement for a fourth component, then a format
126 - 10-bit per component RGB, with 2-bit alpha
128 * Component 0: R(10)
129 * Component 1: G(10)
[all …]
|
| /kernel/linux/linux-5.10/Documentation/gpu/ |
| D | afbc.rst | 7 AFBC is a proprietary lossless image compression protocol and format.
21 AFBC streams can contain several components - where a component
22 corresponds to a color channel (i.e. R, G, B, X, A, Y, Cb, Cr).
45 * Component 3: A(8)
70 Please note, however, that the inclusion of a "wasted" 'X' channel is
72 formats containing 'X' bits. If a fourth component is
75 '1'. If there is no requirement for a fourth component, then a format
126 - 10-bit per component RGB, with 2-bit alpha
128 * Component 0: R(10)
129 * Component 1: G(10)
[all …]
|
| /kernel/linux/linux-6.6/tools/testing/selftests/hid/tests/ |
| D | test_multitouch.py | 38 "IGNORE_DUPLICATES": BIT(10),
68 self.width = 10
69 self.height = 10
358 self.max_slots = 10
492 …10 95 01 35 00 46 c8 37 09 30 81 02 46 68 1f 09 31 81 02 45 00 c0 c0 05 0d 09 06 15 00 26 ff 00 a1…
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.
652 libevdev.InputEvent(libevdev.EV_ABS.ABS_MT_POSITION_Y, 10) not in events
[all …]
|
| D | test_tablet.py | 92 """Following the state machine in the URL above, with a couple of addition
148 self.width = 10
149 self.height = 10
330 However, a half broken device might export those transitions.
331 For example, a pen that has the eraser button might wobble between
450 # now check for a valid transition
457 """Internal method to test against a list of
459 state_list is a list of PenState objects
460 scribble is a boolean which tells if we need
461 to wobble a little the X,Y coordinates of the pen
[all …]
|
| /kernel/linux/linux-5.10/Documentation/networking/device_drivers/ethernet/3com/ |
| D | vortex.rst | 33 - 3c590 Vortex 10Mbps
34 - 3c592 EISA 10Mbps Demon/Vortex
39 - 3c900 Boomerang 10baseT
40 - 3c900 Boomerang 10Mbps Combo
41 - 3c900 Cyclone 10Mbps TPO
42 - 3c900 Cyclone 10Mbps Combo
43 - 3c900 Cyclone 10Mbps TPC
44 - 3c900B-FL Cyclone 10base-FL
48 - 3c905B Cyclone 10/100/BNC
58 - 3c575 [Megahertz] 10/100 LAN CardBus
[all …]
|
| /kernel/linux/linux-6.6/Documentation/networking/device_drivers/ethernet/3com/ |
| D | vortex.rst | 33 - 3c590 Vortex 10Mbps
34 - 3c592 EISA 10Mbps Demon/Vortex
39 - 3c900 Boomerang 10baseT
40 - 3c900 Boomerang 10Mbps Combo
41 - 3c900 Cyclone 10Mbps TPO
42 - 3c900 Cyclone 10Mbps Combo
43 - 3c900 Cyclone 10Mbps TPC
44 - 3c900B-FL Cyclone 10base-FL
48 - 3c905B Cyclone 10/100/BNC
58 - 3c575 [Megahertz] 10/100 LAN CardBus
[all …]
|
| /kernel/liteos_a/testsuites/unittest/process/basic/pthread/full/ |
| D | pthread_test_001.cpp | 21 * THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
60 g_pthreadTestCount++; // 10 in ThreadFunc4()
70 if (i == 10) { // 10, in loop 10, cancel pthread. in ThreadFunc4()
97 if (i == 10) { // 10, in loop 10, cancel pthread. in ThreadFunc3()
102 ICUNIT_GOTO_EQUAL(i, 10, i, EXIT); // 10, here assert the result. in ThreadFunc3()
145 pthread_attr_t a = { 0 }; in ThreadFunc() local
160 ret = pthread_attr_init(&a); in ThreadFunc()
161 pthread_attr_setinheritsched(&a, PTHREAD_EXPLICIT_SCHED); in ThreadFunc()
163 pthread_attr_setschedparam(&a, ¶m); in ThreadFunc()
164 ret = pthread_create(&newPthread, &a, ThreadFunc2, 0); in ThreadFunc()
[all …]
|
| /kernel/linux/linux-5.10/drivers/staging/greybus/tools/ |
| D | README.loopback | 7 A user could run a test without the need of the test application given
22 Here is a short summary of the sysfs interface files that should be visible:
85 …-m mask - a bit mask of connections to include example: -m 8 = 4th connection -m 9 = 1st and 4…
90 …-p porcelain - when specified printout is in a user-friendly non-CSV format. This option suppr…
91 -a aggregate - show aggregation of all enabled devies
100 3.1 - Using the driver sysfs files to run a test on a single device:
102 * Run a 1000 transfers of a 100 byte packet. Each transfer is started only
113 * Run a 1000 transfers of a 100 byte packet. Transfers are started without
148 * Run a transfer test 10 iterations of size 100 bytes on all available devices
149 #/loopback_test -t transfer -i 10 -s 100
[all …]
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/device-mapper/ |
| D | zero.rst | 5 Device-Mapper's "zero" target provides a block-device that always returns
7 /dev/zero, but as a block-device instead of a character-device.
12 conjunction with dm-snapshot. A sparse device reports a device-size larger
13 than the amount of actual storage space available for that device. A user can
14 write data anywhere within the sparse device and read it back like a normal
15 device. Reads to previously unwritten areas will return a zero'd buffer. When
20 To create a sparse device, start by creating a dm-zero device that's the
21 desired size of the sparse device. For this example, we'll assume a 10TB
24 TEN_TERABYTES=`expr 10 \* 1024 \* 1024 \* 1024 \* 2` # 10 TB in sectors
27 Then create a snapshot of the zero device, using any available block-device as
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/device-mapper/ |
| D | zero.rst | 5 Device-Mapper's "zero" target provides a block-device that always returns
7 /dev/zero, but as a block-device instead of a character-device.
12 conjunction with dm-snapshot. A sparse device reports a device-size larger
13 than the amount of actual storage space available for that device. A user can
14 write data anywhere within the sparse device and read it back like a normal
15 device. Reads to previously unwritten areas will return a zero'd buffer. When
20 To create a sparse device, start by creating a dm-zero device that's the
21 desired size of the sparse device. For this example, we'll assume a 10TB
24 TEN_TERABYTES=`expr 10 \* 1024 \* 1024 \* 1024 \* 2` # 10 TB in sectors
27 Then create a snapshot of the zero device, using any available block-device as
[all …]
|
| /kernel/linux/linux-6.6/Documentation/networking/device_drivers/ethernet/ti/ |
| D | tlan.rst | 7 :Version: 1.14a
31 0e11 ae32 Compaq Netelligent 10/100 TX PCI UTP
32 0e11 ae34 Compaq Netelligent 10 T PCI UTP
34 0e11 ae40 Compaq Netelligent Dual 10/100 TX PCI UTP
35 0e11 ae43 Compaq Netelligent Integrated 10/100 TX UTP
36 0e11 b011 Compaq Netelligent 10/100 TX Embedded UTP
37 0e11 b012 Compaq Netelligent 10 T/2 PCI UTP/Coax
38 0e11 b030 Compaq Netelligent 10/100 TX UTP
53 However, if a card supports 100BaseTx without requiring an add
56 The "Netelligent 10 T/2 PCI UTP/Coax" (b012) device is untested,
[all …]
|
| /kernel/linux/linux-5.10/Documentation/networking/device_drivers/ethernet/ti/ |
| D | tlan.rst | 7 :Version: 1.14a
31 0e11 ae32 Compaq Netelligent 10/100 TX PCI UTP
32 0e11 ae34 Compaq Netelligent 10 T PCI UTP
34 0e11 ae40 Compaq Netelligent Dual 10/100 TX PCI UTP
35 0e11 ae43 Compaq Netelligent Integrated 10/100 TX UTP
36 0e11 b011 Compaq Netelligent 10/100 TX Embedded UTP
37 0e11 b012 Compaq Netelligent 10 T/2 PCI UTP/Coax
38 0e11 b030 Compaq Netelligent 10/100 TX UTP
53 However, if a card supports 100BaseTx without requiring an add
56 The "Netelligent 10 T/2 PCI UTP/Coax" (b012) device is untested,
[all …]
|
| /kernel/linux/linux-5.10/Documentation/i2c/ |
| D | ten-bit-addresses.rst | 6 addresses, and an extended set of 10 bit addresses. The sets of addresses
7 do not intersect: the 7 bit address 0x10 is not the same as the 10 bit
8 address 0x10 (though a single device could respond to both of them).
9 To avoid ambiguity, the user sees 10 bit addresses mapped to a different
10 address space, namely 0xa000-0xa3ff. The leading 0xa (= 10) represents the
11 10 bit mode. This is used for creating device names in sysfs. It is also
12 needed when instantiating 10 bit devices via the new_device file in sysfs.
14 I2C messages to and from 10-bit address devices have a different format.
17 The current 10 bit address support is minimal. It should work, however
20 * Not all bus drivers support 10-bit addresses. Some don't because the
[all …]
|
| /kernel/linux/linux-6.6/Documentation/i2c/ |
| D | ten-bit-addresses.rst | 6 addresses, and an extended set of 10 bit addresses. The sets of addresses
7 do not intersect: the 7 bit address 0x10 is not the same as the 10 bit
8 address 0x10 (though a single device could respond to both of them).
9 To avoid ambiguity, the user sees 10 bit addresses mapped to a different
10 address space, namely 0xa000-0xa3ff. The leading 0xa (= 10) represents the
11 10 bit mode. This is used for creating device names in sysfs. It is also
12 needed when instantiating 10 bit devices via the new_device file in sysfs.
14 I2C messages to and from 10-bit address devices have a different format.
17 The current 10 bit address support is minimal. It should work, however
20 * Not all bus drivers support 10-bit addresses. Some don't because the
[all …]
|
| /kernel/linux/linux-6.6/fs/unicode/ |
| D | utf8-norm.c | 24 * The UTF-8 encoding spreads the bits of a 32bit word over several
29 * 0x00000000 0x000007FF: 110xxxxx 10xxxxxx
30 * 0x00000000 0x0000FFFF: 1110xxxx 10xxxxxx 10xxxxxx
31 * 0x00000000 0x001FFFFF: 11110xxx 10xxxxxx 10xxxxxx 10xxxxxx
32 * 0x00000000 0x03FFFFFF: 111110xx 10xxxxxx 10xxxxxx 10xxxxxx 10xxxxxx
33 * 0x00000000 0x7FFFFFFF: 1111110x 10xxxxxx 10xxxxxx 10xxxxxx 10xxxxxx 10xxxxxx
36 * shortest representation of a 32bit value is to be used. A decoder
38 * Thus the allowed ranges have a lower bound.
41 * 0x00000080 0x000007FF: 110xxxxx 10xxxxxx
42 * 0x00000800 0x0000FFFF: 1110xxxx 10xxxxxx 10xxxxxx
[all …]
|
| /kernel/linux/linux-6.6/samples/vfio-mdev/ |
| D | README.rst | 4 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
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
73 30: 00 00 00 00 00 00 00 00 00 00 00 00 0a 01 00 00
77 serial 0000:00:05.0: PCI INT A -> Link[LNKA] -> GSI 10 (level, high) -> IRQ 10
[all …]
|