Searched full:within (Results 1 – 25 of 3554) sorted by relevance
12345678910>>...143
| /openbmc/linux/drivers/net/ethernet/sfc/ |
| D | enum.h | |
| /openbmc/linux/drivers/net/ethernet/sfc/siena/ |
| D | enum.h | |
| /openbmc/linux/drivers/net/ethernet/sfc/falcon/ |
| D | enum.h | |
| /openbmc/docs/designs/ |
| H A D | target-fail-monitoring.md | 15 is used within OpenBMC.
21 target or service within them hitting some sort of error condition. In some
25 critical that if a systemd target fails within OpenBMC, the user be notified.
28 a running service within that target fails. Some services are not all that
38 state management and systemd within OpenBMC.
52 The proposal within this document is to monitor for these other results and log
57 restarts within a 30 second window.
96 - Must be able to monitor any arbitrary systemd service within OpenBMC
162 Units have an OnError directive. Could put the error logging logic within that
166 Could implement this within the existing state manager applications since they
[all …]
|
| /openbmc/linux/Documentation/ABI/stable/ |
| D | sysfs-devices-system-cpu | |
| /openbmc/docs/ |
| H A D | hw-vendor-repos-policy.md | 31 within this document
47 If someone wishes to create a recipe within OpenBMC to point to an external
53 If a recipe is created within OpenBMC (in any meta-X layer) to point to an
58 within OpenBMC
112 For example, OpenPOWER systems have a separate power management device within
121 for hosting a hardware/vendor specific repository within the openbmc github
139 Within OpenBMC there are two areas of "vendor specific" repositories:
147 We need a policy within OpenBMC on how we handle each of these types of
153 repositories that are hosted within OpenBMC. Having the source under the OpenBMC
159 big changes like that on repositories hosted within OpenBMC directly (vs. trying
[all …]
|
| /openbmc/u-boot/arch/x86/include/asm/arch-quark/ |
| H A D | msg_port.h | 11 * the internal message network within the host bridge (D0:F0). Accesses
42 * @reg: register number within a port
50 * @reg: register number within a port
60 * @reg: register number within a port
69 * @reg: register number within a port
79 * @reg: register number within a port
88 * @reg: register number within a port
98 * @reg: register number within a port
|
| /openbmc/phosphor-power/phosphor-regulators/src/ |
| H A D | chassis.hpp | 37 * A chassis within the system.
62 * @param number Chassis number within the system. Chassis numbers start at
65 * @param devices Devices within this chassis, if any. The vector should
105 * Close the devices within this chassis, if any.
112 * Configure the devices within this chassis, if any.
133 * Returns the devices within this chassis, if any.
156 * Returns the chassis number within the system.
178 * Chassis number within the system.
191 * Devices within this chassis, if any.
|
| /openbmc/linux/drivers/clk/ingenic/ |
| D | cgu.h | |
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/MCTP/ |
| H A D | Endpoint.interface.yaml | 4 functionality within a physical device that communicates using the MCTP
13 network within a platform. The network IDs are used by the MCTP stack
22 a particular MCTP endpoint within a system for MCTP communication and
24 that comprise an MCTP communication network within a system. MCTP EIDs
25 are only unique within a particular MCTP network. That is, they can be
|
| /openbmc/u-boot/include/ |
| H A D | bitfield.h | 10 * width bitfields within a word. One use of this would be to use data tables
11 * to determine how to reprogram fields within R/W hardware registers.
47 /* Extract the value of a bitfield found within a given register value */
54 * Replace the value of a bitfield found within a given register value
71 /* Extract the value of a bitfield found within a given register value */
80 * Replace the value of a bitfield found within a given register value
|
| /openbmc/phosphor-state-manager/ |
| H A D | README.md | 4 the state of different objects within OpenBMC. This currently includes the BMC,
16 applications running within an OpenBMC system. This tool itself runs within an
20 As with all OpenBMC applications, interfaces and properties within
32 ensure all generic services installed within the PSM targets complete
39 - Use systemd targets for everything and keep the code within PSM minimal
50 and `Ready` once all services within the default.target have executed. It is
87 and host (see `obmcutil --help` within an OpenBMC system).
99 The `PowerRestoreDelay` property within the interface defines a maximum time the
107 enabled within PSM that will not allow chassis or host operations (other then
142 Active state though so that the chassis object within PSM will correctly
|
| /openbmc/linux/tools/testing/selftests/bpf/progs/ |
| D | verifier_runtime_jit.c | |
| /openbmc/linux/Documentation/netlabel/ |
| D | draft-ietf-cipso-ipsecurity-01.txt | |
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | python-development-shell.rst | 6 Similar to working within a development shell as described in the
7 previous section, you can also spawn and work within an interactive
30 See the ":ref:`bitbake-user-manual/bitbake-user-manual-metadata:functions you can call from within …
44 interpreter within the OpenEmbedded build environment. The
|
| /openbmc/bmcweb/docs/ |
| H A D | OEM_SCHEMAS.md | 13 and can be maintained forever. Within OpenBMC, we have no such group of
43 compared to the experts within DMTF. Getting a DMTF opinion almost always leads
45 code we write within the industry.
86 The OpenBMC project maintains OEM schemas within the OpenBMC namespace, which,
94 To avoid versioning complications with clients, schemas within the OpenBMC
97 for schema branching within a namespace, therefore, if a system intends to ship
|
| /openbmc/linux/tools/include/linux/ |
| D | list.h | |
| /openbmc/linux/Documentation/devicetree/bindings/ptp/ |
| D | ptp-ines.txt | |
| /openbmc/linux/Documentation/devicetree/bindings/mips/cavium/ |
| D | ciu.txt | |
| D | ciu2.txt | |
| /openbmc/u-boot/doc/device-tree-bindings/gpio/ |
| H A D | nvidia,tegra186-gpio.txt | 33 name and an integer GPIO name within the port. For example, GPIO_PA0, GPIO_PN6,
37 implemented GPIOs within each port varies. GPIO registers within a controller
41 the mapping from port name to register offset within a controller, are both
45 sorted within a particular controller. Drivers need to map between the DT GPIO
49 represents the aggregate status for all GPIOs within a set of ports. Thus, the
58 handle subsets of the interrupts within a port. The status of each of these
|
| /openbmc/linux/Documentation/ABI/testing/ |
| D | debugfs-scmi-raw | |
| /openbmc/linux/drivers/soc/ti/ |
| D | pruss.h | |
| /openbmc/linux/Documentation/sound/soc/ |
| D | pops-clicks.rst | |
| /openbmc/linux/include/linux/ |
| D | rio_drv.h | |
12345678910>>...143