Home
last modified time | relevance | path

Searched full:same (Results 1 – 25 of 3231) sorted by relevance

12345678910>>...130

/openbmc/openbmc-test-automation/redfish/update_service/
H A Dtest_firmware_inventory.robot85 [Documentation] Verify BMC version from FirmwareInventory same as in manager.
170 Check Redfish Functional Image Version Is Same
171 [Documentation] Verify functional image version is same as in Redfish managers.
173 [Template] Verify Redfish Functional Image Version Is Same
180 Check Redfish Backup Image Version Is Same
182 ... is same as in Redfish managers..
184 [Template] Verify Redfish Functional Image Version Is Same
190 Verify Redfish Software Image And Firmware Inventory Are Same
191 [Documentation] Verify the firmware software inventory is same as software images of managers.
213 Check If Firmware Image Is Same In Firmware Inventory And Redfish Read Operation
[all …]
/openbmc/u-boot/test/dm/
H A Drtc.c38 bool same; in cmp_times() local
40 same = expect->tm_sec == time->tm_sec; in cmp_times()
41 same &= expect->tm_min == time->tm_min; in cmp_times()
42 same &= expect->tm_hour == time->tm_hour; in cmp_times()
43 same &= expect->tm_mday == time->tm_mday; in cmp_times()
44 same &= expect->tm_mon == time->tm_mon; in cmp_times()
45 same &= expect->tm_year == time->tm_year; in cmp_times()
46 if (!same && show) { in cmp_times()
51 return same ? 0 : -EINVAL; in cmp_times()
/openbmc/u-boot/doc/device-tree-bindings/net/
H A Dethernet.txt16 - phy-connection-type: the same as "phy-mode" property but described in ePAPR;
19 - phy: the same as "phy-handle" property, not recommended for new bindings.
20 - phy-device: the same as "phy-handle" property, not recommended for new
25 They are described in the phy.txt file in this same directory.
H A Daltera_tse.txt7 the information of registers in the same order as described by reg-names
22 - phy-mode: See ethernet.txt in the same directory.
23 - phy-handle: See ethernet.txt in the same directory.
24 - phy-addr: See ethernet.txt in the same directory. A configuration should
48 - local-mac-address: See ethernet.txt in the same directory.
49 - max-frame-size: See ethernet.txt in the same directory.
H A Dsnps,dwc-qos-ethernet.txt21 same order. See ../clock/clock-bindings.txt.
86 - phy-mode: See ethernet.txt file in the same directory
88 same order. See ../reset/reset.txt.
105 - mac-address: See ethernet.txt in the same directory
106 - local-mac-address: See ethernet.txt in the same directory
120 - phy-handle: See ethernet.txt file in the same directory
133 - fixed-mode device tree subnode: see fixed-link.txt in the same directory
/openbmc/u-boot/drivers/pinctrl/aspeed/
H A DKconfig8 i.e. it uses the same device tree configuration.
17 i.e. it uses the same device tree configuration.
26 i.e. it uses the same device tree configuration.
/openbmc/entity-manager/docs/
H A Daddress_size_detection_modes.md15 from a single location so 8 bytes read will be the same.
22 - If any "2 address bytes" EEPROM from any vendor has the same data in all
26 - ONSEMI EEPROM (a 2 address bytes device) return the same data from the same
50 0x00, the subsequent read byte will be the same for all 8 instructions. The
65 This proposal MODE-2 suffers the same 1st issue as MODE-1 ie. what if the EEPROM
66 has the same data at all those addresses. However, this proposal MODE-2
/openbmc/qemu/include/hw/misc/
H A Dstm32l4x5_rcc_internals.h439 /* Same mapping as: CFGR_SW */
451 /* Same mapping as: PLLCFGR_PLLSRC */
496 /* Same mapping as: BDCR_RTCSEL */
519 /* Same mapping as: CCIPR_USART1SEL */
530 /* Same mapping as: CCIPR_USART2SEL */
541 /* Same mapping as: CCIPR_USART3SEL */
552 /* Same mapping as: CCIPR_UART4SEL */
563 /* Same mapping as: CCIPR_UART5SEL */
574 /* Same mapping as: CCIPR_LPUART1SEL */
585 /* Same mapping as: CCIPR_I2C1SEL */
[all …]
/openbmc/qemu/docs/specs/
H A Dppc-spapr-numa.rst43 considering that the same resource can have multiple connections to the
60 same performance boundaries are expected to have relative NUMA distance
62 to the same first boundary will have the shortest distance from each
95 P1 and P2 have the same third NUMA level, MOD1: Distance between them = 40
98 distance attributes for the same associativity arrays, as the following
118 In a hypothetical platform where all resources inside the same hardware module
119 is considered to be on the same performance boundary:
133 P1 and P2 belongs to the same first order boundary. The distance between then
206 have to accept that a large array of values will be translated to the same
225 Will both be translated to the same values internally:
[all …]
H A Drapl-msr.rst42 Each core belonging to the same Package reading the MSR_PKG_ENERGY_STATUS (i.e
43 "rdmsr 0x611") will retrieve the same value. The value represents the energy
44 for the whole package. Whatever Core reading it will get the same value and a
81 belongs to the same package will return the same value when accessing the
124 It is important that the socket path is the same as the one
/openbmc/qemu/hw/watchdog/
H A Dwatchdog.c50 case WATCHDOG_ACTION_RESET: /* same as 'system_reset' in monitor */ in watchdog_perform_action()
55 case WATCHDOG_ACTION_SHUTDOWN: /* same as 'system_powerdown' in monitor */ in watchdog_perform_action()
60 case WATCHDOG_ACTION_POWEROFF: /* same as 'quit' command in monitor */ in watchdog_perform_action()
64 case WATCHDOG_ACTION_PAUSE: /* same as 'stop' command in monitor */ in watchdog_perform_action()
/openbmc/qemu/target/arm/tcg/
H A Dneon-dp.decode21 # VFP/Neon register fields; same as vfp.decode
36 # 3-reg-same grouping:
40 &3same vm vn vd q size
42 @3same .... ... . . . size:2 .... .... .... . q:1 . . .... \
43 &3same vm=%vm_dp vn=%vn_dp vd=%vd_dp
46 &3same vm=%vm_dp vn=%vn_dp vd=%vd_dp q=0
50 # This converts this encoding to the same MO_8/16/32/64 values that the
55 &3same vm=%vm_dp vn=%vn_dp vd=%vd_dp size=%3same_fp_size
57 &3same vm=%vm_dp vn=%vn_dp vd=%vd_dp q=0 size=%3same_fp_size
59 VHADD_S_3s 1111 001 0 0 . .. .... .... 0000 . . . 0 .... @3same
[all …]
/openbmc/openbmc/poky/documentation/dev-manual/
H A Dlibraries.rst17 - :ref:`How to install multiple versions of the same library in parallel on
18 the same system
19 <dev-manual/libraries:installing multiple versions of the same library>`
226 packages with and without the Multilib feature can exist in the same
232 Installing Multiple Versions of the Same Library
236 of the same library on the same system at the same time. This
240 versions of the same library in parallel on the same system.
252 same system:
262 create the dependency. Continuing with the same example, if you want to
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Software/
H A DREADME.md51 interface will be at the exact same path as the _ImageManager_'s
55 updated with the same image or multiple locations in the same device could hold
56 the same image (such as a primary / secondary flash bank relationship), the
72 each `Software.Version`. This allows the same software version to be contained
73 in multiple locations but represented by the same object path.
81 can be challenging. For the BMC, two different images may both be the same size
99 At the same path as the `Software.Version`, an _ImageManager_ should create an
103 have the same string in its `Inventory.Decorator.Compatible` interface. These
233 same software image (as in a multi-host design). The _ImageManager_ may
242 side `Software.Version` to represent its state from the same service.
/openbmc/qemu/docs/devel/migration/
H A Dcompatibility.rst8 target. There are two cases, they are the same version or they are
9 different versions. The easy case is when they are the same version.
29 First of all, migration is only supposed to work if you use the same
31 configuration needs to be the same also on source and destination.
37 start with the trivial ones, QEMU is the same on source and
47 Exactly the same case than the previous one, but for 5.1.
54 we have the same QEMU version in both sides (qemu-5.2) but we are using
62 both sides are the same QEMU and both sides have exactly the same
89 If qemu-5.1 and qemu-5.2 were the same, there will not be any
130 queue. In qemu-5.2 it has the same number of queues as the number of
[all …]
/openbmc/phosphor-led-manager/manager/
H A Dconfig-validator.cpp16 // Priority for a particular LED needs to stay SAME across all groups
52 /** @brief Validate the Priority of an LED is same across ALL groups
76 "Priority of the LED is not same across groups. Old Priority = " + in validatePriority()
102 // Same LEDs can be part of multiple groups. However, their in validateConfigV1GroupForLedPriority()
153 "When using Group Priority, no 2 Groups may have the same priority"); in validateConfigV1ForGroupPriority()
/openbmc/qemu/tests/qapi-schema/
H A Ddoc-good.txt44 * **one** -- The _one_ {and only}, description on the same line
96 * **i** ("int") -- description starts on the same line remainder
97 indented the same "b" is undocumented
114 same line remainder indented differently
/openbmc/u-boot/drivers/input/
H A Dinput.c325 * first in the array, and in the same order as the ordering. The algorithm
342 int same; /* number of elements which are the same */ in sort_array_by_ordering() local
354 same = dest_count; in sort_array_by_ordering()
362 return same; in sort_array_by_ordering()
368 * Given a list of new key codes, we check how many of these are the same
374 * @param same Returns number of key codes which are the same
377 int keycode[], int num_keycodes, int *same) in input_check_keycodes() argument
385 /* sort the keycodes into the same order as the previous ones */ in input_check_keycodes()
386 *same = sort_array_by_ordering(keycode, num_keycodes, in input_check_keycodes()
392 return *same != num_keycodes; in input_check_keycodes()
[all …]
/openbmc/openbmc/poky/bitbake/lib/prserv/
H A Dtests.py117 # "No history" mode supports multiple PRs for the same checksum
184 # Check that the same request gets the same value
187 …f.assertEqual(result, "0", "getPR: asking for the same PR a second time in a row should return the…
283 # For identical checksums, all servers should return the same PR
289 … self.assertEqual(result, "0", "getPR: initial PR of a package should be '0' (same as upstream)")
292 … self.assertEqual(result, "0", "getPR: initial PR of a package should be '0' (same as upstream)")
294 # Now introduce new checksums on server1 for, same version
302 # Now introduce checksums on server0 for, same version
341 self.assertEqual(self.client1.getPR(version, pkgarch, checksum0), "2") # Same as upstream
342 self.assertEqual(self.client0.getPR(version, pkgarch, checksum0), "2") # Same as upstream
[all …]
/openbmc/qemu/tests/tcg/multiarch/gdbstub/
H A Dinterrupt.py16 Check that, if thread is resumed, we go back to the same thread when the
40 # Check whether the thread we're in after the interruption is the same we
47 Test if interrupting the code always lands us on the same thread when
/openbmc/qemu/docs/
H A Dpci_expander_bridge.txt6 PXB is a "light-weight" host bridge in the same PCI domain
31 …- 2 NUMA nodes for the guest, 0 and 1. (both mapped to the same NUMA node in host, but you can and…
48 …It is a regular PCI Device that resides on the piix host-bridge bus and its bus uses the same PCI …
50 The interrupts from devices behind the PXB are routed through this device the same as if it were a
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-graphics/ttf-fonts/ttf-liberation-sans-narrow/
H A D30-0-liberation-sans-narrow.conf5 <alias binding="same">
11 <alias binding="same">
/openbmc/u-boot/board/buffalo/lsxl/
H A DREADME4 disk NAS server. The PCBs of the LS-XHL and LS-CHLv2 are almost the same.
32 Pressing the same button for at least 10 seconds on power-up will erase the
92 modified to support loading larger kernels. But it should behave the same
101 Same as hdd expect, that the files are loaded from an attached USB mass
106 Same as usb expect, that the file are loaded from the network.
/openbmc/u-boot/doc/device-tree-bindings/timer/
H A Darc_timer.txt23 NOTE: if you specify both timers, clocks always should be the same
24 as each timer is driven by the same core clock.
/openbmc/openbmc/poky/meta/files/common-licenses/
H A DXFree86-1.111 …ntation and/or other materials provided with the distribution, and in the same place and form as o…
13 … in the same place and form as other third-party acknowledgments. Alternately, this acknowledgment…

12345678910>>...130