| /openbmc/linux/Documentation/process/ |
| H A D | stable-api-nonsense.rst | 64 - Depending on the version of the C compiler you use, different kernel
65 data structures will contain different alignment of structures, and
66 possibly include different functions in different ways (putting
68 isn't that important, but the different data structure padding is
72 different things can be assumed by the kernel:
74 - different structures can contain different fields
77 - Memory within the kernel can be aligned in different ways,
80 - Linux runs on a wide range of different processor architectures.
89 different Linux distributions and the number of different supported
91 different build options on different releases. Also realize that each
[all …]
|
| /openbmc/linux/tools/testing/selftests/bpf/prog_tests/ |
| H A D | spin_lock.c | 34 { "lock_id_mismatch_kptr_kptr", "bpf_spin_unlock of different lock" },
35 { "lock_id_mismatch_kptr_global", "bpf_spin_unlock of different lock" },
36 { "lock_id_mismatch_kptr_mapval", "bpf_spin_unlock of different lock" },
37 { "lock_id_mismatch_kptr_innermapval", "bpf_spin_unlock of different lock" },
38 { "lock_id_mismatch_global_global", "bpf_spin_unlock of different lock" },
39 { "lock_id_mismatch_global_kptr", "bpf_spin_unlock of different lock" },
40 { "lock_id_mismatch_global_mapval", "bpf_spin_unlock of different lock" },
41 { "lock_id_mismatch_global_innermapval", "bpf_spin_unlock of different lock" },
42 { "lock_id_mismatch_mapval_mapval", "bpf_spin_unlock of different lock" },
43 { "lock_id_mismatch_mapval_kptr", "bpf_spin_unlock of different lock" },
[all …]
|
| /openbmc/openbmc-test-automation/openpower/ext_interfaces/ |
| H A D | test_vmi.robot | 274 Verify To Configure VMI Static IP Address With Different User Roles
275 [Documentation] Verify to configure vmi static ip address with different user roles.
278 ... AND Create Users With Different Roles users=${USERS} force=${True}
279 [Template] Config VMI Static IP Address Using Different Users
290 [Setup] Create Users With Different Roles users=${USERS} force=${True}
291 [Template] Config VMI Static IP Address Using Different Users
298 Verify To Delete VMI Static IP Address With Different User Roles
299 [Documentation] Verify to delete vmi static IP address with different user roles.
301 [Setup] Create Users With Different Roles users=${USERS} force=${True}
302 [Template] Delete VMI Static IP Address Using Different User
[all...] |
| /openbmc/u-boot/arch/mips/mach-bmips/ |
| H A D | Kconfig | 136 Between its different peripherals there's an integrated switch with 4
147 Between its different peripherals there's an integrated switch with 4
158 Between its different peripherals there's an integrated switch with 4
169 Between its different peripherals there's a BCM5325 switch with 4
180 Between its different peripherals there's an integrated switch with 4
191 Between its different peripherals there's a BCM53115 switch with 5
202 Between its different peripherals there's a BCM5325 switch with 4
213 Between its different peripherals there's a BCM53115 switch with 4
224 Between its different peripherals there's a BCM53125 switch with 5
235 Between its different peripherals there's a BCM5325 switch with 4
[all …]
|
| /openbmc/phosphor-power/tools/power-utils/test/ |
| H A D | test_version.cpp | 22 // Input 2 different version where primary versions are different in TEST()
26 // Input 3 different version where secondary versions are different in TEST()
30 // Input 3 different version where communication versions are different in TEST()
|
| /openbmc/linux/tools/testing/selftests/net/forwarding/ |
| H A D | tc_vlan_modify.sh | 108 check_fail $? "ping between two different vlans passed when should not"
111 check_fail $? "ping6 between two different vlans passed when should not"
119 check_err $? "ping between two different vlans failed when should not"
122 check_err $? "ping6 between two different vlans failed when should not"
135 check_fail $? "ping between two different vlans passed when should not"
138 check_fail $? "ping6 between two different vlans passed when should not"
146 check_err $? "ping between two different vlans failed when should not"
149 check_err $? "ping6 between two different vlans failed when should not"
|
| /openbmc/u-boot/drivers/pinctrl/nxp/ |
| H A D | Kconfig | 17 configuration. This driver is different from the linux one,
31 configuration. This driver is different from the linux one,
45 configuration. This driver is different from the linux one,
59 is different from the linux one, this is a simple implementation,
74 is different from the linux one, this is a simple implementation,
88 is different from the linux one, this is a simple implementation,
102 configuration. This driver is different from the linux one,
|
| /openbmc/openbmc/poky/meta/lib/oeqa/selftest/cases/ |
| H A D | reproducible.py | 29 DIFFERENT = 'DIFFERENT' variable
49 self.different = []
59 elif r.status == DIFFERENT:
65 self.different.append(r)
72 self.different.sort()
77 …return 'same=%i different=%i different_excluded=%i missing=%i total=%i\nunused_exclusions=%s' % (l…
94 result.status = DIFFERENT
119 # different
238 # We want different log files for each build, but a persistent bitbake
308 …oducibleB directories are changed to reproducibleA & reproducibleB-extended to have different size.
[all …]
|
| /openbmc/telemetry/redfish-tests/ |
| H A D | test_telemetry.py | 92 assert r["Id"] == id, "Invalid Id, different then requested"
94 assert r["Id"] == id, "Invalid Id, different then requested"
135 ), "Invalid actions, different then requested"
169 assert len(r["Metrics"]) == 1, "Invalid Metrics, different then requested"
172 ), "Invalid MetricId, different then requested"
175 ), "Invalid MetricProperties, different then requested"
200 ), "Invalid Metrics, different then requested"
216 ), "Different Id then set in request"
219 ), "Different MetricProperty then set in request"
241 ), "Different Id then set in request"
[all …]
|
| /openbmc/linux/Documentation/powerpc/ |
| H A D | vcpudispatch_stats.rst | 11 scenarios, vcpus may be dispatched on a different processor chip (away
33 3. number of times this vcpu was dispatched on a different processor core
35 4. number of times this vcpu was dispatched on a different chip
36 5. number of times this vcpu was dispatches on a different socket/drawer
43 7. number of times this vcpu was dispatched in a different node
69 physical cpu as the last time. 2683 were on a different core, but within
70 the same chip, while 30 dispatches were on a different chip compared to
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/amdzen4/ |
| H A D | cache.json | 29 …"BriefDescription": "Demand data cache fills from L3 cache or different L2 cache in the same CCX.",
47 …"Demand data cache fills from cache of another CCX when the address was in a different NUMA node.",
53 …: "Demand data cache fills from either DRAM or MMIO in a different NUMA node (same or different so…
77 "BriefDescription": "Any data cache fills from L3 cache or different L2 cache in the same CCX.",
83 …"BriefDescription": "Any data cache fills from local L2 cache or L3 cache or different L2 cache in…
101 …": "Any data cache fills from cache of another CCX when the address was in a different NUMA node.",
107 … cache fills from cache of another CCX when the address was in the same or a different NUMA node.",
113 …on": "Any data cache fills from either DRAM or MMIO in a different NUMA node (same or different so…
119 …ion": "Any data cache fills from either DRAM or MMIO in any NUMA node (same or different socket).",
125 …e of another CCX, DRAM or MMIO when the address was in a different NUMA node (same or different so…
[all …]
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/amdzen3/ |
| H A D | memory.json | 132 …scription": "Demand Data Cache Fills by Data Source. From DRAM or IO connected in different Node.",
138 "BriefDescription": "Demand Data Cache Fills by Data Source. From CCX Cache in different Node.",
150 …"BriefDescription": "Demand Data Cache Fills by Data Source. From cache of different CCX in same n…
156 …"BriefDescription": "Demand Data Cache Fills by Data Source. From L3 or different L2 in same CCX.",
168 …fDescription": "Any Data Cache Fills by Data Source. From DRAM or IO connected in different Node.",
174 "BriefDescription": "Any Data Cache Fills by Data Source. From CCX Cache in different Node.",
186 …"BriefDescription": "Any Data Cache Fills by Data Source. From cache of different CCX in same node…
192 "BriefDescription": "Any Data Cache Fills by Data Source. From L3 or different L2 in same CCX.",
342 … "Software Prefetch Data Cache Fills by Data Source. From DRAM or IO connected in different Node.",
348 …scription": "Software Prefetch Data Cache Fills by Data Source. From CCX Cache in different Node.",
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/regulator/ |
| H A D | samsung,s5m8767.yaml | 36 Describes the different operating modes of the LDO's with power mode
37 change in SOC. The different possible values are:
60 Describes the different operating modes of the regulator with power
61 mode change in SOC. The different possible values are:
85 Describes the different operating modes of the regulator with power
86 mode change in SOC. The different possible values are:
|
| /openbmc/linux/Documentation/kbuild/ |
| H A D | reproducible-builds.rst | 78 generate a different temporary key for each build, resulting in the
114 vDSO's debug information may be identical even for different kernel
116 packages for the different kernel versions.
118 To avoid this, you can make the vDSO different for different
125 Uncommitted changes or different commit ids in git can also lead
126 to different compilation results. For example, after executing
129 will be different, which will eventually lead to binary differences.
|
| /openbmc/linux/Documentation/admin-guide/namespaces/ |
| H A D | compatibility-list.rst | 6 may have when creating tasks living in different namespaces.
10 in different other namespaces (the rows):
28 other task living in a different namespace via a shared filesystem
33 2. Intentionally, two equal user IDs in different user namespaces
40 from different user namespaces should not access the same IPC objects
|
| /openbmc/linux/include/uapi/linux/ |
| H A D | falloc.h | 19 * Different filesystems may implement different limitations on the
51 * Different filesystems may implement different limitations on the granularity
68 * Different filesystems may implement different limitations on the
|
| /openbmc/linux/drivers/gpu/drm/msm/ |
| H A D | NOTES | 3 In the current snapdragon SoC's, we have (at least) 3 different
20 with N different kms devices from xf86-video-freedreno. Plus, it
25 So, the approach is one drm driver, with some modularity. Different
27 And one or more 'struct msm_gpu' for the various different gpu sub-
57 than needing a different implementation for DTV, DSI, etc. (Ie. the
58 register interface is same, just different bases.)
|
| /openbmc/openbmc/meta-security/recipes-mac/smack/udp-smack-test/ |
| H A D | test_smack_udp_sockets.sh | 29 # checking access for sockets with different labels
40 echo "Sockets with different labels should not communicate on udp"
44 # granting access between different labels
47 # checking access for sockets with different labels, but having a rule granting rw
58 echo "Sockets with different labels, but having rw access, should communicate on udp"
|
| /openbmc/openbmc/meta-security/recipes-mac/smack/tcp-smack-test/ |
| H A D | test_smack_tcp_sockets.sh | 28 # checking access for sockets with different labels
41 echo "Sockets with different labels should not communicate on tcp"
45 # granting access between different labels
48 # checking access for sockets with different labels, but having a rule granting rw
59 echo "Sockets with different labels, but having rw access, should communicate on tcp"
|
| /openbmc/linux/Documentation/virt/ |
| H A D | paravirt_ops.rst | 7 Linux provides support for different hypervisor virtualization technologies.
8 Historically, different binary kernels would be required in order to support
9 different hypervisors; this restriction was removed with pv_ops.
10 Linux pv_ops is a virtualization API which enables support for different
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | colorspaces.rst | 20 the human eye has color receptors that are sensitive to three different
23 different wavelengths, so instead of RGB we would be using the
34 possible that different SPDs will result in the same stimulation of
36 of the light is different.
68 different wavelengths, the combination of which will stimulate the color
74 Different display devices will have different primaries and some
77 different display technologies or uses. To define a colorspace you need
150 mix of different standards also led to very confusing naming conventions
|
| /openbmc/linux/Documentation/devicetree/bindings/sound/ |
| H A D | rt5663.txt | 23 Based on the different PCB layout, add the manual offset value to
24 compensate the DC offset for each L and R channel, and they are different
38 should compensate different DC offset to avoid the pop sound, and it is
39 also different between headphone and headset. In the example, the
|
| /openbmc/linux/tools/testing/ktest/examples/ |
| H A D | test.conf | 8 # BOX can be different than foo, if the machine BOX has
9 # multiple partitions with different systems installed. For example,
12 # machine, which may be different between which system the machine
55 # The following files each handle a different test case.
|
| /openbmc/linux/Documentation/devicetree/bindings/pinctrl/ |
| H A D | mediatek,mt8186-pinctrl.yaml | 35 Physical address base for GPIO base registers. There are 8 different GPIO
65 define or si unit value(ohm) to set different resistance.
103 Supported pin number and mux varies for different SoCs, and are
125 set different resistance. It can support "MTK_PUPD_SET_R1R0_00" &
129 value(ohm) to set different resistance by identifying property
170 set different resistance. It can support "MTK_PUPD_SET_R1R0_00" &
174 value(ohm) to set different resistance by identifying property
|
| /openbmc/u-boot/doc/ |
| H A D | README.power-framework | 19 designers strive to cut down power consumption. Hence several different types of
27 One package can integrate PMIC and MUIC with different addresses on the I2C bus.
28 The same device - e.g. MAX8997 uses two different I2C busses and addresses.
31 different ICs use different endianess. For this reason struct pmic holds
59 be maintained for different classes of devices.
117 __Example for trats (this can be very different for other board):__
|