| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 059.out | 2062 … use relative paths with VMDK descriptor file $QUORUM_FILE: Cannot generate a base directory for q…
2277 e100000000: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a ................
2278 e100000010: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a ................
2279 e100000020: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a ................
2280 e100000030: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a ................
2281 e100000040: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a ................
2282 e100000050: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a ................
2283 e100000060: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a ................
2284 e100000070: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a ................
2285 e100000080: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a ................
[all …]
|
| /openbmc/linux/Documentation/networking/devlink/ |
| H A D | ice.rst | 54 kernel only displayed a 2-digit version number (major.minor).
64 incremented whenever a major breaking change occurs, or when the
68 a fix is delivered as a patch against an older base Option ROM.
83 variation of the DDP package has a unique name.
112 ``devlink-flash`` interface. It supports updating the device flash using a
142 The ``ice`` driver supports activating new firmware after a flash update
150 The new firmware is activated by issuing a device specific Embedded
161 a predefined set of available port split options for the whole device.
163 A system reboot is required for port split to be applied.
190 ``devlink port unsplit`` will select the option with a split count of 1. If
[all …]
|
| H A D | devlink-port.rst | 9 ``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 …]
|
| /openbmc/linux/Documentation/bpf/ |
| H A D | llvm_reloc.rst | 34 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 …]
|
| /openbmc/phosphor-logging/test/openpower-pels/ |
| H A D | pel_manager_test.cpp | 6 * You may obtain a copy of the License at
135 // a PEL saved in the repository.
149 // Create a PEL, write it to a file, and pass that filename into in TEST_F()
192 // Create a PEL, write it to a file, and pass that filename into in TEST_F()
224 // Check that the bad PEL data was saved to a file. in TEST_F()
229 // Test that the message registry can be used to build a PEL.
254 "Description": "A PGOOD Fault", in TEST_F()
255 "Message": "PS had a PGOOD Fault" in TEST_F()
268 "Message": "This is a generic SRC" in TEST_F()
302 // Ensure a PEL was created in the repository in TEST_F()
[all …]
|
| H A D | device_callouts_test.cpp | 6 * You may obtain a copy of the License at
333 "fsi-master/fsi0/slave@00:00/00:00:00:0a/fsi-master/fsi1/" in TEST_F()
334 "slave@01:00/01:01:00:06/sbefifo2-dev0/occ-hwmon.2"), in TEST_F()
342 "fsi-master/fsi0/slave@00:00/00:00:00:0a/fsi-master/fsi1/" in TEST_F()
343 "slave@01:00/01:01:00:03/i2c-211/211-0055"), in TEST_F()
352 "fsi0/slave@00:00/00:00:00:0a/fsi-master/fsi1/slave@08:00/" in TEST_F()
353 "01:03:00:04/spi_master/spi9/spi9.0/spi9.00/nvmem"), in TEST_F()
369 "fsi-master/fsi0/slave@00:00/00:00:00:0a/fsi-master/fsi1/" in TEST_F()
370 "slave@01:00/01:01:00:03/i2c-211/211-0055"), in TEST_F()
387 "fsi0/slave@00:00/00:00:00:0a/fsi-master/fsi1/slave@08:00/" in TEST_F()
[all …]
|
| /openbmc/linux/samples/vfio-mdev/ |
| H A 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
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 …]
|
| /openbmc/linux/tools/testing/selftests/hid/tests/ |
| H A D | test_tablet.py | 92 """Following the state machine in the URL above, with a couple of addition
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
564 However, a half broken device might export those transitions.
565 For example, a pen that has the eraser button might wobble between
[all …]
|
| H A D | test_multitouch.py | 492 …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 …]
|
| /openbmc/linux/tools/testing/selftests/net/forwarding/ |
| H A D | bridge_mld.sh | 11 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 …]
|
| H A D | bridge_igmp.sh | 11 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 …]
|
| /openbmc/linux/tools/testing/selftests/drivers/net/dsa/ |
| H A D | bridge_mld.sh | 11 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 …]
|
| /openbmc/linux/Documentation/scsi/ |
| H A D | sym53c8xx_2.rst | 35 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 …]
|
| /openbmc/openpower-hw-diags/analyzer/ras-data/data/ |
| H A D | ras-data-explorer-20.json | 382 "00": { object
383 "00": "level2_M_th1" string
386 "00": "ocmb_M_th1" string
389 "00": "ocmb_M_th1", string
393 "00": "ocmb_M_th1", string
397 "00": "level2_M_th1" string
400 "00": "level2_M_th1" string
403 "00": "level2_M_th1" string
406 "00": "level2_M_th1" string
409 "00": "level2_M_th1" string
[all …]
|
| H A D | ras-data-explorer-11.json | 382 "00": { object
383 "00": "level2_M_th1" string
386 "00": "ocmb_M_th1" string
389 "00": "ocmb_M_th1", string
393 "00": "ocmb_M_th1", string
397 "00": "level2_M_th1" string
400 "00": "level2_M_th1" string
403 "00": "level2_M_th1" string
406 "00": "level2_M_th1" string
409 "00": "level2_M_th1" string
[all …]
|
| H A D | ras-data-odyssey-10.json | 585 "00": { object
586 "00": "level2_M_th_1", string
590 "00": "mem_port0_M_th_1", string
594 "00": "mem_port0_M_th_1", string
598 "00": "mem_port0_M_th_1", string
602 "00": "mem_port0_M_th_1", string
606 "00": "level2_M_th_1", string
610 "00": "mem_port0_M_th_1", string
615 "00": "level2_M_th_1", string
619 "00": "level2_M_th_1", string
[all …]
|
| H A D | ras-data-p10-10.json | 11604 "00": { object
11605 "00": "level2_M_self_L_th_1" string
11608 "00": "level2_M_self_L_th_1" string
11611 "00": "level2_M_self_L_th_1" string
11614 "00": "level2_M_th_1" string
11617 "00": "level2_M_self_L_th_1" string
11620 "00": "level2_M_th_1" string
11623 "00": "level2_M_self_L_th_1" string
11626 "00": "level2_M_th_1" string
11629 "00": "level2_M_th_1" string
[all …]
|
| H A D | ras-data-p10-20.json | 11604 "00": { object
11605 "00": "level2_M_self_L_th_1" string
11608 "00": "level2_M_self_L_th_1" string
11611 "00": "level2_M_self_L_th_1" string
11614 "00": "level2_M_th_1" string
11617 "00": "level2_M_self_L_th_1" string
11620 "00": "level2_M_th_1" string
11623 "00": "level2_M_self_L_th_1" string
11626 "00": "level2_M_th_1" string
11629 "00": "level2_M_th_1" string
[all …]
|
| /openbmc/qemu/docs/devel/testing/ |
| H A D | blkverify.rst | 7 This document describes how to use the ``blkverify`` protocol to test that a block
12 of the executable. Other times obscure errors are raised by a program inside
26 The "raw" device is a raw image, a flat file, that has identical starting
28 read/write operations correctly and not corrupt data. It can be used as a
31 After a mirrored read operation completes, ``blkverify`` will compare the data and
52 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
53 00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
55 000001e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
56 000001f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
62 $ ./qemu-io -c 'read 0 512' blkverify:a.img:b.img
[all …]
|
| /openbmc/linux/drivers/tty/vt/ |
| H A D | cp437.uni | 13 # 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 …]
|
| /openbmc/linux/tools/testing/selftests/drivers/net/mlxsw/ |
| H A D | devlink_trap_control.sh | 182 )"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 …]
|
| /openbmc/u-boot/arch/x86/dts/ |
| H A D | chromebook_samus.dts | 256 03 11 01 08 0a 00 50 01
258 10 04 3c 3c 01 90 00 00
259 00 80 00 00 00 00 00 a8
260 00 00 00 00 00 00 00 00
261 00 00 00 00 00 00 00 00
262 00 00 00 00 0f 11 02 00
263 00 00 00 00 00 00 00 00
264 00 00 00 00 00 00 00 00
265 00 00 00 00 00 00 00 00
266 00 00 00 00 00 00 00 00
[all …]
|
| H A D | chromebook_link.dts | 246 03 52 01 08 0a 00 fe 00
249 00 00 00 00 00 00 00 00
250 00 00 00 00 00 00 00 00
251 00 00 00 00 00 00 00 00
252 00 00 00 00 0f 11 42 00
253 00 00 00 00 00 00 00 00
254 00 00 00 00 00 00 00 00
255 00 00 00 00 00 00 00 00
256 00 00 00 00 00 00 00 00
257 00 00 00 00 00 00 00 00
[all …]
|
| /openbmc/linux/tools/testing/selftests/bpf/ |
| H A D | README.rst | 13 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 …]
|
| /openbmc/qemu/docs/ |
| H A D | qemupciserial.inf | 5 ; emulated by qemu has, and to apply a name tag to it which windows
8 ; Installing the driver: Go to device manager. You should find a "pci
9 ; serial card" tagged with a yellow question mark. Open properties.
11 ; (Com+Lpt)" from the list. Click "Have a disk". Select this file.
12 ; Procedure may vary a bit depending on the windows version.
73 HKR,Child0000,VaryingResourceMap,1,00, 00,00,00,00, 08,00,00,00
78 HKR,Child0000,VaryingResourceMap,1,00, 00,00,00,00, 08,00,00,00
81 HKR,Child0001,VaryingResourceMap,1,00, 08,00,00,00, 08,00,00,00
86 HKR,Child0000,VaryingResourceMap,1,00, 00,00,00,00, 08,00,00,00
89 HKR,Child0001,VaryingResourceMap,1,00, 08,00,00,00, 08,00,00,00
[all …]
|