| /openbmc/openbmc-test-automation/data/ |
| H A D | boot_table.json | 13 "boot_progress": "^FW Progress, Starting OS|OSStart$",
36 "boot_progress": "^FW Progress, Starting OS|OSStart$",
59 "boot_progress": "^FW Progress, Starting OS|OSStart$",
196 "boot_progress": "^FW Progress, Starting OS|OSStart$",
223 "boot_progress": "^FW Progress, Starting OS|OSStart$",
233 "boot_progress": "^FW Progress, Starting OS|OSStart$",
249 "boot_progress": "^FW Progress, Starting OS|OSStart$",
259 "boot_progress": "^FW Progress, Starting OS|OSStart$",
274 "boot_progress": "^FW Progress, Starting OS|OSStart$",
284 "boot_progress": "^FW Progress, Starting OS|OSStart$",
[all …]
|
| H A D | task_state.json | 4 "TaskState": "Starting",
33 "Starting",
|
| /openbmc/u-boot/disk/ |
| H A D | part_dos.h | 21 unsigned char head; /* starting head */
22 unsigned char sector; /* starting sector */
23 unsigned char cyl; /* starting cylinder */
28 unsigned char start4[4]; /* starting sector counting from 0 */
|
| /openbmc/openbmc/poky/bitbake/doc/bitbake-user-manual/ |
| H A D | bitbake-user-manual-ref-variables-context.rst | 19 Variables starting with ``BB_`` usually configure the behaviour of BitBake itself.
41 - Starting with ``FAKEROOT``, to configure how the ``fakeroot`` command is
53 Variables starting with ``LAYER`` configure how BitBake handles layers.
54 Additionally, variables starting with ``BB`` configure how layers and files are
84 - There are further variables starting with ``SRC`` that specify the sources in
90 starting with ``PREFERRED_``. Those are normally set in the configuration
|
| /openbmc/openbmc/meta-openembedded/meta-webserver/recipes-webadmin/webmin/files/ |
| H A D | remove-startup-option.patch | 15 - my $starting = &init::action_status("webmin");
21 - &ui_hidden("starting", $starting),
22 - &ui_radio("boot", $starting == 2 ? 1 : 0,
|
| /openbmc/u-boot/drivers/usb/dwc3/ |
| H A D | io.h | 29 * We requested the mem region starting from the Globals address in dwc3_readl()
31 * However, the offsets are given starting from xHCI address space. in dwc3_readl()
43 * We requested the mem region starting from the Globals address in dwc3_writel()
45 * However, the offsets are given starting from xHCI address space. in dwc3_writel()
|
| /openbmc/bmcweb/redfish-core/include/generated/enums/ |
| H A D | task.hpp | 13 Starting, enumerator
30 {TaskState::Starting, "Starting"},
|
| H A D | job.hpp | 12 Starting, enumerator
37 {JobState::Starting, "Starting"},
|
| H A D | network_port.hpp | 14 Starting, enumerator
54 {LinkStatus::Starting, "Starting"},
|
| /openbmc/openbmc/meta-arm/meta-arm-systemready/lib/oeqa/runtime/cases/ |
| H A D | arm_systemready_opensuse_unattended.py | 21 'Starting hardware detection...',
23 bb.plain('Installation status: Starting hardware detection...')
31 'Starting Installer',
|
| /openbmc/openbmc/meta-facebook/meta-harma/recipes-phosphor/state/phosphor-state-manager/ |
| H A D | chassis-powercycle | 7 echo "Starting Chassis Power Cycle"
47 echo "Starting Chassis Power Cycle"
50 echo "Starting Aegis Power Cycle"
|
| H A D | host-poweron@.service | 5 Wants=obmc-host-starting@%i.target
6 Before=obmc-host-starting@%i.target
|
| /openbmc/phosphor-state-manager/target_files/ |
| H A D | obmc-host-started@.target | 4 Wants=obmc-host-starting@%i.target
5 After=obmc-host-starting@%i.target
|
| /openbmc/u-boot/include/ |
| H A D | part_efi.h | 64 u8 head; /* starting head */
65 u8 sector; /* starting sector */
66 u8 cyl; /* starting cylinder */
71 __le32 start_sect; /* starting sector counting from 0 */
|
| /openbmc/openbmc/poky/meta/recipes-core/initrdscripts/initramfs-framework/ |
| H A D | exec | 13 msg "No contents to exec in $EXEC_DIR. Starting shell ..."
24 debug "Starting $m"
|
| /openbmc/qemu/tests/functional/qemu_test/ |
| H A D | aspeed.py | |
| /openbmc/qemu/tests/functional/ |
| H A D | aspeed.py | 27 self.wait_for_console_pattern('Starting kernel ...')
42 self.wait_for_console_pattern('Starting kernel ...')
63 self.wait_for_console_pattern('Starting kernel ...')
|
| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 091.out | 4 === Starting QEMU VM1 ===
7 === Starting QEMU VM2 ===
|
| /openbmc/openbmc/poky/meta/recipes-support/libusb/libusb1/ |
| H A D | run-ptest | 11 if [ "${str#*Starting test run:}" != "$str" ]
13 name="${str#Starting test run: }"
|
| /openbmc/openbmc/meta-openpower/recipes-phosphor/host/op-host-control/ |
| H A D | start_host@.service | 5 Wants=obmc-host-starting@%i.target
6 Before=obmc-host-starting@%i.target
|
| /openbmc/openbmc/meta-facebook/meta-catalina/recipes-phosphor/state/phosphor-state-manager/ |
| H A D | host-poweron@.service | 5 Wants=obmc-host-starting@%i.target
6 Before=obmc-host-starting@%i.target
|
| /openbmc/openpower-proc-control/service_files/ |
| H A D | op-continue-mpreboot@.service.in | 4 Wants=obmc-host-starting@%i.target
5 Before=obmc-host-starting@%i.target
|
| /openbmc/openbmc/meta-phosphor/recipes-phosphor/host/obmc-op-control-host/ |
| H A D | op-start-host@.service | 4 Wants=obmc-host-starting@%i.target
5 Before=obmc-host-starting@%i.target
|
| /openbmc/openbmc/poky/meta/recipes-core/systemd/ |
| H A D | systemd.inc | 6 capabilities, uses socket and D-Bus activation for starting services, \
7 offers on-demand starting of daemons, keeps track of processes using \
|
| /openbmc/openbmc/meta-facebook/meta-santabarbara/recipes-phosphor/state/phosphor-state-manager/ |
| H A D | host-poweron@.service | 5 Wants=obmc-host-starting@%i.target
6 Before=obmc-host-starting@%i.target
|