| /openbmc/openbmc/meta-openembedded/meta-gnome/recipes-connectivity/geary/geary/ |
| H A D | 0001-application-client.vala-hardcode-some-paths.patch | 4 Subject: [PATCH] application-client.vala: hardcode some paths 7 https://gitlab.gnome.org/GNOME/geary/-/blob/main/src/client/application/application-client.vala?ref… 8 https://gitlab.gnome.org/GNOME/geary/-/blob/main/src/client/application/application-client.vala?ref… 18 src/client/application/application-client.vala | 4 ++-- 21 diff --git a/src/client/application/application-client.vala b/src/client/application/application-cl… 23 --- a/src/client/application/application-client.vala 24 +++ b/src/client/application/application-client.vala
|
| /openbmc/docs/designs/ |
| H A D | psu-monitoring.md | 12 supply application for enterprise class systems. Some enterprise class systems 14 supply types and numbers. An application capable of communicating with the 23 that contains a power supply monitor application and a power sequencer monitor 24 application. The current power supply application is lacking things desired for 27 The intent of this new application design is to enhance the OpenBMC project with 28 a single power supply application that can communicate with one or more 30 in the existing application that has multiple instances talking to a single 38 1. The power supply application must detect, isolate, and report individual 40 2. The power supply application must determine power supply presence, 42 3. The power supply application must report power supply failures to IPMI and [all …]
|
| H A D | voltage-regulator-configuration.md | 17 new application is needed to configure regulators. It should be data-driven to 103 A new application named `phosphor-regulators` will be created to configure 104 voltage regulators. The application will be located in the proposed new 107 _Statement of direction: This application will provide other regulator-based 112 The application will read a JSON file at runtime that defines the configuration 123 directory. The application will search both directories, and the file in the 125 application receives a SIGHUP signal, it will re-read the JSON file. 160 The application will be started using systemd when the BMC is at standby. The 170 The application will communicate with the voltage regulators directly using the 177 Voltage regulators that are configured using this application will not be bound [all …]
|
| /openbmc/openbmc/meta-openembedded/meta-webserver/recipes-httpd/nginx/files/ |
| H A D | nginx.conf | 24 default_type application/octet-stream; 42 …gzip_types text/plain text/css application/json application/javascript text/xml application/xml ap…
|
| /openbmc/docs/ |
| H A D | REDFISH-cheatsheet.md | 25 curl --insecure -H "Content-Type: application/json" -X POST -D headers.txt https://${bmc}/redfish/v… 39 export token=`curl -k -H "Content-Type: application/json" -X POST https://${bmc}/login -d '{"userna… 70 curl -k -H "X-Auth-Token: $token" -H "Content-Type: application/json" -X POST https://${bmc}/redfis… 76 curl -k -H "X-Auth-Token: $token" -H "Content-Type: application/json" -X POST https://${bmc}/redfis… 82 curl -k -H "X-Auth-Token: $token" -H "Content-Type: application/json" -X POST https://${bmc}/redfis… 88 curl -k -H "X-Auth-Token: $token" -H "Content-Type: application/json" -X POST https://${bmc}/redfis… 96 curl -k -H "X-Auth-Token: $token" -H "Content-Type: application/json" -X POST https://${bmc}/redfis… 106 curl -k -H "X-Auth-Token: $token" -H "Content-Type: application/json" -X POST https://${bmc}/redfis… 122 curl -k -H "X-Auth-Token: $token" -H "Content-Type: application/json" -X POST https://${bmc}/redfis… 134 curl -k -H "X-Auth-Token: $token" -H "Content-Type: application/octet-stream" -X POST -T <image fil… [all …]
|
| H A D | REST-cheatsheet.md | 28 …curl -c cjar -b cjar -k -H "Content-Type: application/json" -X POST https://${bmc}/login -d "{\"da… 49 …export token=`curl -k -H "Content-Type: application/json" -X POST https://${bmc}/login -d '{"usern… 63 export token=`curl -k -H "Content-Type: application/json" -X POST https://${bmc}/login -d '{"userna… 84 …curl -k -H "X-Auth-Token: $token" -H "Content-Type: application/json" -d '{"data": "xyz.openbmc_pr… 90 …curl -k -H "X-Auth-Token: $token" -H "Content-Type: application/json" -X PUT -d '{"data":"xyz.open… 96 …curl -k -H "X-Auth-Token: $token" -H "Content-Type: application/json" -d '{"data": "xyz.openbmc_pr… 102 …curl -k -H "X-Auth-Token: $token" -H "Content-Type: application/json" -X PUT -d '{"data":"xyz.open… 108 …curl -k -H "X-Auth-Token: $token" -H "Content-Type: application/json" -X PUT -d '{"data":"xyz.open… 114 …curl -k -H "X-Auth-Token: $token" -H "Content-Type: application/json" -X GET https://${bmc}/xyz/op… 120 …curl -k -H "X-Auth-Token: $token" -H "Content-Type: application/json" -X DELETE https://${bmc}/xyz… [all …]
|
| /openbmc/openbmc-tools/rootfs_size/ |
| H A D | results.txt | 52 167936: /usr/share/mime/application 407 4096: /usr/share/mime/application/x-x509-ca-cert.xml 995 0: /usr/share/mime/application/x-kontour.xml 996 0: /usr/share/mime/application/x-gnuplot.xml 997 0: /usr/share/mime/application/x-bzip-compressed-tar.xml 998 0: /usr/share/mime/application/metalink+xml.xml 999 0: /usr/share/mime/application/vnd.lotus-wordpro.xml 1000 0: /usr/share/mime/application/vnd.ms-powerpoint.addin.macroenabled.12.xml 1001 0: /usr/share/mime/application/x-ipynb+json.xml 1002 0: /usr/share/mime/application/vnd.stardivision.writer.xml [all …]
|
| /openbmc/phosphor-power/phosphor-regulators/docs/ |
| H A D | README.md | 5 The `phosphor-regulators` application configures and monitors voltage 6 regulators. The application is controlled by a JSON configuration file. 8 The application does not control how voltage regulators are enabled or how to 12 application. 16 implemented in this application. The enhancements are also dependent on the 17 planned new `phosphor-chassis-power` application. This disclaimer will be 23 process that runs continually. The application is launched by systemd when the 26 The application is driven by a system-specific JSON configuration file. The JSON 75 Automated test cases exist for most of the code in this application. See
|
| /openbmc/openbmc/poky/meta/recipes-devtools/file/files/ |
| H A D | 0001-Use-4-in-default-reset-previous-negative-offset-in-m.patch | 35 -!:mime application/vnd.keyman.kmp+zip 41 #>30 search/100/b application/epub+zip EPUB document 42 #!:mime application/epub+zip 48 >>30 search/100/b !application/epub+zip 50 -!:mime application/zip 64 !:mime application/vnd.android.package-archive 74 +!:mime application/vnd.keyman.kmp+zip 81 +!:mime application/zip 90 !:mime application/zip
|
| /openbmc/phosphor-power/phosphor-power-sequencer/ |
| H A D | README.md | 5 The phosphor-power-sequencer application powers the chassis on/off and monitors 6 the power sequencer device. The application is configured by an optional JSON 12 - [docs](docs/) contains documentation on this application and the JSON
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Network/ |
| H A D | README.md | 69 curl -c cjar -b cjar -k -H "Content-Type: application/json" -X POST \ 84 curl -c cjar -b cjar -k -H "Content-Type: application/json" -X POST \ 108 curl -c cjar -b cjar -k -H "Content-Type: application/json" -X DELETE \ 123 curl -c cjar -b cjar -k -H "Content-Type: application/json" \ 137 curl -c cjar -b cjar -k -H "Content-Type: application/json" -X PUT \ 155 curl -c cjar -b cjar -k -H "Content-Type: application/json" \ 168 curl -c cjar -b cjar -k -H "Content-Type: application/json" -X PUT \ 184 curl -c cjar -b cjar -k -H "Content-Type: application/json" \ 197 curl -c cjar -b cjar -k -H "Content-Type: application/json" -X PUT \ 213 curl -c cjar -b cjar -k -H "Content-Type: application/json" \ [all …]
|
| /openbmc/u-boot/doc/ |
| H A D | README.u-boot_on_efi | 8 as an application or just as a means of getting U-Boot onto a new platform. 51 U-Boot supports running as an EFI application for 32-bit EFI only. This is 67 To build U-Boot as an EFI application (32-bit EFI required), enable CONFIG_EFI 85 u-boot-app.efi - U-Boot EFI application 86 u-boot-payload.efi - U-Boot EFI payload application 101 run the application. 'bios.bin' is the EFI 'BIOS'. Check [2] to obtain a 109 (or fs0:u-boot-app.efi for the application) 112 that EFI does not support booting a 64-bit application from a 32-bit 122 The application and payload approaches sound similar but are in fact 127 For the application the whole of U-Boot is built as a shared library. The [all …]
|
| /openbmc/phosphor-networkd/docs/ |
| H A D | Network-Configuration.md | 66 curl -c cjar -b cjar -k -H "Content-Type: application/json" -X POST -d 80 curl -c cjar -b cjar -k -H "Content-Type: application/json" -X GET 92 curl -c cjar -b cjar -k -H "Content-Type: application/json" -X PUT -d '{"data": 109 curl -c cjar -b cjar -k -H "Content-Type: application/json" -X GET 120 curl -c cjar -b cjar -k -H "Content-Type: application/json" -X PUT -d '{"data": 137 curl -c cjar -b cjar -k -H "Content-Type: application/json" -X DELETE 150 curl -c cjar -b cjar -k -H "Content-Type: application/json" -X GET 161 curl -c cjar -b cjar -k -H "Content-Type: application/json" -X PUT -d '{"data": 174 curl -c cjar -b cjar -k -H "Content-Type: application/json" -X GET 188 curl -c cjar -b cjar -k -H "Content-Type: application/jon" -X PUT -d '{"data": [all …]
|
| /openbmc/phosphor-power/phosphor-regulators/ |
| H A D | README.md | 5 The `phosphor-regulators` application configures and monitors voltage 6 regulators. The application is controlled by a JSON configuration file. 11 - [docs](docs/) contains documentation on this application and the JSON
|
| /openbmc/openpower-vpd-parser/ |
| H A D | README.md | 13 This is a build-time YAML driven application that parses the OpenPower VPD 20 The application instance must be passed in the file path to the VPD (this can, 35 Making the application runtime JSON driven allows us to support multiple systems 37 well as making the application more flexible for future improvements. 43 parser applications into a single runtime JSON driven application. 44 2. Add details to the README on how to configure and build the application.
|
| /openbmc/phosphor-user-manager/docs/ |
| H A D | README.md | 17 curl -c cjar -b cjar -k -H "Content-Type: application/json" -X POST -d '{"data":[false,"ldap://<lda… 32 curl -c cjar -b cjar -k -H "Content-Type: application/octet-stream" 39 curl -c cjar -b cjar -k -H "Content-Type: application/octet-stream" 46 curl -b cjar -k -H "Content-Type: application/json" -X POST -d '{"data":[]}' https://$BMC_IP/xyz/op…
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/php/php/ |
| H A D | 70_mod_php8.conf | 4 SetHandler application/x-httpd-php 8 SetHandler application/x-httpd-php-source
|
| /openbmc/openbmc/meta-ibm/recipes-phosphor/chassis/ |
| H A D | phosphor-skeleton-control-power_%.bbappend | 4 # control application. That image will use the power control application
|
| /openbmc/phosphor-power/phosphor-power-sequencer/docs/ |
| H A D | README.md | 5 The `phosphor-power-sequencer` application powers all the chassis in the system 10 application. The support is also dependent on changes to the existing 11 `phosphor-chassis-state-manager` application and the planned new 12 `phosphor-chassis-power` application. This disclaimer will be removed when this 96 Automated test cases exist for most of the code in this application. See 103 The `phosphor-chassis-state-manager` application exists in the 110 The `phosphor-chassis-power` application exists in the phosphor-power 115 The `phosphor-power-supply` application exists in the phosphor-power repository.
|
| /openbmc/phosphor-power/phosphor-chassis-power/ |
| H A D | README.md | 7 The `phosphor-chassis-power` application monitors chassis power on multi-chassis 8 systems to handle chassis-level fault monitoring and recovery. The application
|
| /openbmc/phosphor-power/ |
| H A D | README.md | 13 application that monitors chassis power on multi-chassis systems. 15 application that powers the chassis on/off and monitors the power sequencer 18 power supply monitoring application. 19 - [phosphor-regulators](phosphor-regulators/README.md): JSON-driven application 25 - power-sequencer: Original power sequencer monitoring application. 26 - power-supply: Original power supply monitoring application.
|
| /openbmc/openbmc/meta-security/meta-tpm/recipes-tpm2/ibmswtpm2/ |
| H A D | ibmswtpm2_183-2024-03-27.bb | 2 DESCRIPTION = "The software TPM 2.0 is targeted toward application development, \ 5 The intent is that an application can be developed using the software TPM. \ 6 The application should then run using a hardware TPM without changes. \
|
| /openbmc/openbmc/poky/meta-selftest/recipes-test/overlayfs-user/ |
| H A D | overlayfs-user.bb | 11 OVERLAYFS_WRITABLE_PATHS[mnt-overlay] += "/usr/share/my-application" 14 install -d ${D}/usr/share/my-application
|
| /openbmc/openbmc/meta-phosphor/conf/distro/include/ |
| H A D | phosphor-defaults.inc | 60 # The phosphor-ipmi-fru application is data-driven and requires an input 64 # The phosphor-ipmi-fru application is data-driven and requires an input 71 # The phosphor-ipmi-fru application is data-driven and requires an input 84 # The phosphor-host-ipmid application is data-driven. 86 # The phosphor-host-ipmid application is data-driven and requires an input 93 # The phosphor-host-ipmid application is data-driven and requires an input 102 # The phosphor-led-manager application is data-driven and requires an input 109 # The phosphor-logging application has a data driven plugin that adds FRU 118 # The phosphor-fan-presence application is data driven and requires an input 125 # The phosphor-fan-control application is data driven and requires a YAML file [all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Logging/ |
| H A D | README.md | 21 application. Such errors are defined in the application that uses the error. 73 curl -c cjar -b cjar -k -H "Content-Type: application/json" -X POST \ 87 curl -c cjar -b cjar -s -k -H "Content-Type: application/json" -X GET \ 95 curl -c cjar -b cjar -k -H "Content-Type: application/json" -X POST \ 103 curl -c cjar -b cjar -k -H "Content-Type: application/json" -X POST \
|