| /openbmc/openbmc/meta-openembedded/meta-oe/dynamic-layers/selinux/recipes-devtool/android-tools/ |
| H A D | android-tools_29.0.6.r14.bb | 3 LICENSE = "Apache-2.0 & GPL-2.0-only & BSD-2-Clause & BSD-3-Clause"
5 file://${COMMON_LICENSE_DIR}/Apache-2.0;md5=89aea4e17d99a7cacdbeed46a0096b10 \
6 file://${COMMON_LICENSE_DIR}/GPL-2.0-only;md5=801f80980d171dd6425610833a22dbe6 \
7 file://${COMMON_LICENSE_DIR}/BSD-2-Clause;md5=cb641bc04cda31daea161b1bc15da69f \
8 file://${COMMON_LICENSE_DIR}/BSD-3-Clause;md5=550794465ba0ec5312d6919e203a55f9 \
10 DEPENDS = "libbsd libpcre zlib libcap libusb squashfs-tools 7zip libselinux googletest"
15 …git://salsa.debian.org/android-tools-team/android-platform-tools;name=core;protocol=https;branch=m…
18 # Patches copied from android-platform-tools/debian/patches
19 # and applied in the order defined by the file debian/patches/series
21 file://debian/external/libunwind/user_pt_regs.patch \
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/android-tools/ |
| H A D | android-tools_5.1.1.r37.bb | 3 LICENSE = "Apache-2.0 & GPL-2.0-only & BSD-2-Clause & BSD-3-Clause"
5 file://${COMMON_LICENSE_DIR}/Apache-2.0;md5=89aea4e17d99a7cacdbeed46a0096b10 \
6 file://${COMMON_LICENSE_DIR}/GPL-2.0-only;md5=801f80980d171dd6425610833a22dbe6 \
7 file://${COMMON_LICENSE_DIR}/BSD-2-Clause;md5=cb641bc04cda31daea161b1bc15da69f \
8 file://${COMMON_LICENSE_DIR}/BSD-3-Clause;md5=550794465ba0ec5312d6919e203a55f9 \
11 DEPENDS:append:class-target = " openssl"
15 # matches with android-5.1.1_r37
24 …git://${ANDROID_MIRROR}/platform/system/core;name=core;protocol=https;nobranch=1;destsuffix=git/sy…
25 …git://${ANDROID_MIRROR}/platform/system/extras;name=extras;protocol=https;nobranch=1;destsuffix=gi…
29 file://core/0001-adb-remove-selinux-extensions.patch;patchdir=system/core \
[all …]
|
| /openbmc/phosphor-power/phosphor-regulators/src/ |
| H A D | manager.cpp | 5 * you may not use this file except in compliance with the License.
8 * http://www.apache.org/licenses/LICENSE-2.0
53 * Default configuration file name. This is used when the system does not
54 * implement the D-Bus compatible interface.
59 * Standard configuration file directory. This directory is part of the
60 * firmware install image. It contains the standard version of the config file.
62 const fs::path standardConfigFileDir{"/usr/share/phosphor-regulators"};
65 * Test configuration file directory. This directory can contain a test version
66 * of the config file. The test version will override the standard version.
68 const fs::path testConfigFileDir{"/etc/phosphor-regulators"};
[all …]
|
| H A D | manager.hpp | 5 * you may not use this file except in compliance with the License.
8 * http://www.apache.org/licenses/LICENSE-2.0
20 #include "system.hpp"
56 * @param bus the D-Bus bus
62 * Implements the D-Bus "configure" method.
64 * Configures all the voltage regulators in the system.
66 * This method should be called when the system is being powered on. It
72 * Implements the D-Bus "monitor" method.
77 * - regulator sensors will be read and published on D-Bus
78 * - phase fault detection will be performed
[all …]
|
| /openbmc/phosphor-power/phosphor-power-sequencer/docs/config_file/ |
| H A D | README.md | 1 # phosphor-power-sequencer Configuration File
5 - [Overview](#overview)
6 - [Data Format](#data-format)
7 - [Name](#name)
8 - [Contents](#contents)
9 - [Installation](#installation)
13 The `phosphor-power-sequencer` configuration file (config file) contains
14 information about the power sequencer device within a system. This device is
18 The information in the config file is used to determine which voltage rail
21 The config file is optional. If no file is found, the application will log a
[all …]
|
| /openbmc/phosphor-power/phosphor-regulators/docs/config_file/ |
| H A D | README.md | 1 # phosphor-regulators Configuration File
5 - [Overview](#overview)
6 - [Data Format](#data-format)
7 - [Example](#example)
8 - [Name](#name)
9 - [Contents](#contents)
10 - [Validation](#validation)
11 - [Installation](#installation)
12 - [Loading and Reloading](#loading-and-reloading)
13 - [Testing](#testing)
[all …]
|
| /openbmc/phosphor-fan-presence/docs/presence/ |
| H A D | README.md | 1 # Fan Presence Configuration File
5 - [Overview](#overview)
6 - [Data Format](#data-format)
7 - [Example](#example)
8 - [System Config Location](#system-config-location)
9 - [Contents](#contents)
10 - [Validation](#validation)
11 - [Firmware Updates](#firmware-updates)
12 - [Loading and Reloading](#loading-and-reloading)
16 The `phosphor-fan-presence-tach` application is controlled by a configuration
[all …]
|
| /openbmc/openbmc/meta-security/recipes-ids/tripwire/files/ |
| H A D | tripwire.txt | 1 Post-Installation Instructions
3 Note: Once encoded and signed, the configuration file should not be renamed or moved.
4 2. Initialize the Tripwire database file. (/usr/sbin/tripwire--init)
5 3. Run the first integrity check. (/usr/sbin/tripwire--check)
6 4. Edit the configuration file (twcfg.txt) with a text editor, if desired.
7 5. Edit the policy file (twpol.txt) with a text editor, if desired.
9 …file, we recommend you do so before running the configuration script. If you modify the policy fil…
11 Modifying the Policy File
12 …system in the Tripwire policy file (twpol.txt). A default policy file is included in the Tripwire …
14 …file at /etc/tripwire/twpol.txt. An example policy file (located at /usr/doc/tripwire-VER#-REL#…
[all …]
|
| /openbmc/phosphor-fan-presence/docs/control/ |
| H A D | README.md | 1 # Fan Control Configuration File
5 - [Overview](#overview)
6 - [Data Format](#data-format)
7 - [System Config Location](#system-config-location)
8 - [Contents](#contents)
9 - [Validation](#validation)
10 - [Firmware Updates](#firmware-updates)
11 - [Loading and Reloading](#loading-and-reloading)
12 - [Debug](#debug)
16 The `phosphor-fan-control` application is comprised of as set of configuration
[all …]
|
| /openbmc/phosphor-fan-presence/docs/monitor/ |
| H A D | README.md | 1 # Fan Monitor Configuration File
5 - [Overview](#overview)
6 - [Data Format](#data-format)
7 - [Example](#example)
8 - [System Config Location](#system-config-location)
9 - [Contents](#contents)
10 - [Validation](#validation)
11 - [Firmware Updates](#firmware-updates)
12 - [Loading and Reloading](#loading-and-reloading)
16 The `phosphor-fan-monitor` application is controlled by a configuration file
[all …]
|
| /openbmc/openbmc/meta-hpe/meta-rl300-g11/recipes-hpe/power-supplies-monitoring/ |
| H A D | power-supplies-monitoring.bb | 1 inherit obmc-phosphor-systemd
4 SYSTEMD_SERVICE:${PN} = "psu2-monitoring.service psu1-monitoring.service psu2up.service psu2down.se…
5 …file://psu2-monitoring.service file://psu1-monitoring.service file://psus-manager.sh file://psu2up…
7 LICENSE = "Apache-2.0"
8 LIC_FILES_CHKSUM = "file://${COREBASE}/meta/files/common-licenses/Apache-2.0;md5=89aea4e17d99a7cacd…
11 IMAGE_INSTALL += "power-supplies-monitoring "
13 FILES:${PN} = "/usr/share/gpios/* /usr/bin/* /etc/system/*"
16 install -d ${D}${sysconfdir}/system/
17 install -d ${D}/usr/share/gpios
18 install -d ${D}/usr/bin
[all …]
|
| /openbmc/openbmc/meta-hpe/meta-dl360-g11/recipes-hpe/power-supplies-monitoring/ |
| H A D | power-supplies-monitoring.bb | 1 inherit obmc-phosphor-systemd
4 SYSTEMD_SERVICE:${PN} = "psu2-monitoring.service psu1-monitoring.service psu2up.service psu2down.se…
5 …file://psu2-monitoring.service file://psu1-monitoring.service file://psus-manager.sh file://psu2up…
7 LICENSE = "Apache-2.0"
8 LIC_FILES_CHKSUM = "file://${COREBASE}/meta/files/common-licenses/Apache-2.0;md5=89aea4e17d99a7cacd…
11 IMAGE_INSTALL += "power-supplies-monitoring "
13 FILES:${PN} = "/usr/share/gpios/* /usr/bin/* /etc/system/*"
16 install -d ${D}${sysconfdir}/system/
17 install -d ${D}/usr/share/gpios
18 install -d ${D}/usr/bin
[all …]
|
| /openbmc/openbmc/meta-hpe/meta-dl385-g11/recipes-hpe/power-supplies-monitoring/ |
| H A D | power-supplies-monitoring.bb | 1 inherit obmc-phosphor-systemd
4 SYSTEMD_SERVICE:${PN} = "psu2-monitoring.service psu1-monitoring.service psu2up.service psu2down.se…
5 …file://psu2-monitoring.service file://psu1-monitoring.service file://psus-manager.sh file://psu2up…
7 LICENSE = "Apache-2.0"
8 LIC_FILES_CHKSUM = "file://${COREBASE}/meta/files/common-licenses/Apache-2.0;md5=89aea4e17d99a7cacd…
11 IMAGE_INSTALL += "power-supplies-monitoring "
13 FILES:${PN} = "/usr/share/gpios/* /usr/bin/* /etc/system/*"
16 install -d ${D}${sysconfdir}/system/
17 install -d ${D}/usr/share/gpios
18 install -d ${D}/usr/bin
[all …]
|
| /openbmc/openbmc/meta-hpe/meta-rl300-g11/recipes-hpe/power-sequencing/ |
| H A D | power-sequencing.bb | 1 inherit obmc-phosphor-systemd
4 SYSTEMD_SERVICE:${PN} = "monitor-ipmi-power-transition.service power-sequencing.service gpiosdown.s…
5 …file://monitor-ipmi-power-transition.service file://ipmi-power-button-monitoring.sh file://rl300St…
7 LICENSE = "Apache-2.0"
8 LIC_FILES_CHKSUM = "file://${COREBASE}/meta/files/common-licenses/Apache-2.0;md5=89aea4e17d99a7cacd…
11 IMAGE_INSTALL += "power-sequencing "
13 FILES:${PN} = "/usr/share/gpios/* /usr/bin/* /etc/system/*"
16 install -d ${D}${sysconfdir}/system/
17 install -d ${D}/usr/share/gpios
18 install -d ${D}/usr/bin
[all …]
|
| /openbmc/openbmc/meta-hpe/meta-dl360-g11/recipes-hpe/power-sequencing/ |
| H A D | power-sequencing.bb | 1 inherit obmc-phosphor-systemd
4 SYSTEMD_SERVICE:${PN} = "monitor-ipmi-power-transition.service power-sequencing.service gpiosdown.s…
5 …file://monitor-ipmi-power-transition.service file://ipmi-power-button-monitoring.sh file://dl360St…
7 LICENSE = "Apache-2.0"
8 LIC_FILES_CHKSUM = "file://${COREBASE}/meta/files/common-licenses/Apache-2.0;md5=89aea4e17d99a7cacd…
11 IMAGE_INSTALL += "power-sequencing "
13 FILES:${PN} = "/usr/share/gpios/* /usr/bin/* /etc/system/*"
16 install -d ${D}${sysconfdir}/system/
17 install -d ${D}/usr/share/gpios
18 install -d ${D}/usr/bin
[all …]
|
| /openbmc/u-boot/fs/ubifs/ |
| H A D | key.h | 1 /* SPDX-License-Identifier: GPL-2.0+ */
3 * This file is part of UBIFS.
5 * Copyright (C) 2006-2008 Nokia Corporation.
12 * This header contains various key-related definitions and helper function.
19 * Keys are 64-bits long. First 32-bits are inode number (parent inode number
29 * key_mask_hash - mask a valid hash value.
45 * key_r5_hash - R5 hash function (borrowed from reiserfs).
65 * key_test_hash - testing hash function.
79 * ino_key_init - initialize inode key.
80 * @c: UBIFS file-system description object
[all …]
|
| /openbmc/openbmc/poky/meta/recipes-core/systemd/ |
| H A D | systemd-conf_1.0.bb | 1 SUMMARY = "Systemd system configuration"
6 LIC_FILES_CHKSUM = "file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
13 PACKAGECONFIG ??= "dhcp-ethernet"
14 PACKAGECONFIG[dhcp-ethernet] = ""
17 file://journald.conf \
18 file://logind.conf \
19 file://system.conf \
20 file://system.conf-qemuall \
21 file://wired.network \
28 install -D -m0644 ${S}/journald.conf ${D}${systemd_unitdir}/journald.conf.d/00-${PN}.conf
[all …]
|
| /openbmc/openbmc/meta-security/docs/ |
| H A D | overview.txt | 1 Meta-security Docs
9 Bastille is a system hardening / lockdown program which enhances the
10 security of a Unix host. It configures daemons, system settings and
17 bastille -c --os Yocto
19 about the system to be displayed to the user. For each
21 file which is installed with Bastille, will be selected.
24 responses to the configuration file.
27 bastille -l lists the configuration files that Bastille
39 README file and other documentation.
41 Alternatives to Bastille include buck-security and checksecurity,
[all …]
|
| /openbmc/openbmc/meta-facebook/meta-bletchley/recipes-bletchley/plat-tools/ |
| H A D | bletchley-common-tool_0.1.bb | 1 LICENSE = "Apache-2.0"
2 LIC_FILES_CHKSUM = "file://${COREBASE}/meta/files/common-licenses/Apache-2.0;md5=89aea4e17d99a7cacd…
4 inherit obmc-phosphor-systemd
9 RDEPENDS:${PN} += " bash motor-ctrl"
10 RDEPENDS:${PN} += " mdio-tools"
13 file://bletchley-system-state-init \
14 file://bletchley-system-state-init@.service \
15 file://bletchley-usbmux-util \
16 file://bletchley-net-util \
20 install -d ${D}${libexecdir}
[all …]
|
| /openbmc/phosphor-power/phosphor-power-sequencer/docs/ |
| H A D | README.md | 1 # phosphor-power-sequencer
5 The `phosphor-power-sequencer` application powers all the chassis in the system
11 `phosphor-chassis-state-manager` application and the planned new
12 `phosphor-chassis-power` application. This disclaimer will be removed when this
17 `phosphor-power-sequencer` is a single-threaded C++ executable. It is a daemon
19 the Ready state and before the system is powered on.
21 `phosphor-power-sequencer` is driven by an optional, system-specific JSON
22 configuration file. The config file is found and parsed at runtime. The parsing
34 `phosphor-power-sequencer` currently supports the following power sequencer
37 - UCD90160
[all …]
|
| /openbmc/u-boot/test/py/tests/test_fs/ |
| H A D | conftest.py | 1 # SPDX-License-Identifier: GPL-2.0+
21 """Enable --fs-type option.
26 parser: Pytest command-line parser.
31 parser.addoption('--fs-type', action='append', default=None,
35 """Restrict a file system(s) to be tested.
37 A file system explicitly named with --fs-type option is selected
92 """Convert a file system type to an U-boot specific string
94 A generated string can be used as part of file system related commands
95 or a config name in u-boot. Currently fat16 and fat32 are handled
99 fs_type: File system type.
[all …]
|
| H A D | fstest_defs.py | 1 # SPDX-License-Identifier: GPL-2.0+
3 # $MIN_FILE is the name of the 20KB file in the file system image
6 # $SMALL_FILE is the name of the 1MB file in the file system image
7 SMALL_FILE='1MB.file'
9 # $BIG_FILE is the name of the 2.5GB file in the file system image
10 BIG_FILE='2.5GB.file'
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | speeding-up-build.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
6 Build time can be an issue. By default, the build system uses simple
14 - :term:`BB_NUMBER_THREADS`:
17 - :term:`BB_NUMBER_PARSE_THREADS`:
20 - :term:`PARALLEL_MAKE`: Extra
22 :ref:`ref-tasks-compile` task in
25 - :term:`PARALLEL_MAKEINST`:
27 :ref:`ref-tasks-install` task in
31 available on the build system. For single socket systems, this
32 auto-scaling ensures that the build system fundamentally takes advantage
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/openwsman/ |
| H A D | openwsman_2.7.2.bb | 1 SUMMARY = "Opensource Implementation of WS-Management"
2 DESCRIPTION = "Openwsman is a project intended to provide an open-source \
4 (WS-Management) and to expose system management information on the \
5 Linux operating system using the WS-Management protocol. WS-Management \
8 all system management aspects. \
11 SECTION = "Applications/System"
21 file://libssl-is-required-if-eventint-supported.patch \
22 file://openwsmand.service \
23 file://0001-lock.c-Define-PTHREAD_MUTEX_RECURSIVE_NP-if-undefine.patch \
24 file://0001-Link-with-libm-for-floor-function.patch \
[all …]
|
| /openbmc/openbmc/poky/documentation/ref-manual/ |
| H A D | terms.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
14 Files that append build information to a recipe file. Append files are
16 build system expects every append file to have a corresponding recipe
17 (``.bb``) file. Furthermore, the append file and corresponding recipe file
19 file type suffix used (e.g. ``formfactor_0.0.bb`` and
23 similarly-named recipe file. For an example of an append file in use, see
24 the ":ref:`dev-manual/layers:appending other layers metadata with your layer`"
27 When you name an append file, you can use the "``%``" wildcard character
29 append file named as follows::
33 That append file
[all …]
|