/openbmc/bmcweb/test/include/ |
H A D | http_utility_test.cpp | 17 EXPECT_TRUE(isContentTypeAllowed("application/octet-stream", in TEST() 21 isContentTypeAllowed("application/json", ContentType::JSON, false)); in TEST() 23 isContentTypeAllowed("application/cbor", ContentType::CBOR, false)); in TEST() 24 EXPECT_TRUE(isContentTypeAllowed("application/json, text/html", in TEST() 30 EXPECT_FALSE(isContentTypeAllowed("application/octet-stream", in TEST() 33 isContentTypeAllowed("application/html", ContentType::JSON, false)); in TEST() 35 isContentTypeAllowed("application/json", ContentType::CBOR, false)); in TEST() 37 isContentTypeAllowed("application/cbor", ContentType::HTML, false)); in TEST() 38 EXPECT_FALSE(isContentTypeAllowed("application/json, text/html", in TEST() 58 getPreferredContentType("text/html, application/json", contentType), in TEST() [all …]
|
/openbmc/docs/designs/ |
H A D | psu-monitoring.md | 1 # Power Supply Monitoring Application 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, [all …]
|
H A D | voltage-regulator-configuration.md | 17 new application is needed to configure regulators. It should be data-driven to 101 ### Application subsection 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 110 ### Application Data File 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 [all …]
|
/openbmc/intel-ipmi-oem/ |
H A D | ipmi-allowlist.conf | 185 0x30:0x01:0x7f7f //<Intel General Application>:<Get FW Version String> 186 0x30:0x02:0x7f7f //<Intel General Application>:<Restore Configuration> 187 0x30:0x03:0x7f7f //<Intel General Application>:<Restore SDR> 188 0x30:0x04:0xff7f //<Intel General Application>:<Get NW Switch MIB> 189 0x30:0x05:0xff7f //<Intel General Application>:<Get PDB FW Version> 190 0x30:0x09:0xff7f //<Intel General Application>:<Get BMC Config> 191 0x30:0x14:0xff7f //<Intel General Application>:<Get SM Signal> 192 0x30:0x15:0x7f7f //<Intel General Application>:<Set SM Signal> 193 0x30:0x19:0xff7f //<Intel General Application>:<Read LAN Channel Port Value> 194 0x30:0x1a:0xff7f //<Intel General Application>:<Get NIC Info> [all …]
|
/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 25 @@ -39,9 +39,9 @@ public class Application.Client : Gtk.Application {
|
/openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
H A D | Application_v1.xml | 4 <!--# Redfish Schema: Application v1.0.1 --> 37 <Schema xmlns="http://docs.oasis-open.org/odata/ns/edm" Namespace="Application"> 41 <EntityType Name="Application" BaseType="Resource.v1_0_0.Resource" Abstract="true"> 42 …<Annotation Term="OData.Description" String="The `Application` schema represents an application or… 43 … Term="OData.LongDescription" String="This resource shall represent an application or service runn… 69 <Annotation Term="OData.Description" String="This action resets the application."/> 70 <Annotation Term="OData.LongDescription" String="This action shall reset the application."/> 71 <Parameter Name="Application" Type="Application.v1_0_0.Actions"/> 74 …application. `GracefulShutdown` and `ForceOff` shall indicate requests to stop or disable the app… 79 <Schema xmlns="http://docs.oasis-open.org/odata/ns/edm" Namespace="Application.v1_0_0"> [all …]
|
/openbmc/openbmc/poky/bitbake/lib/toaster/toastermain/ |
H A D | wsgi.py | 8 This module contains the WSGI application used by Django's development server 10 named ``application``. Django's ``runserver`` and ``runfcgi`` commands discover 11 this application via the ``WSGI_APPLICATION`` setting. 13 Usually you will have the standard Django WSGI application here, but it also 14 might make sense to replace the whole Django WSGI application with a custom one 16 middleware here, or combine a Django application with an application of another 28 # This application object is used by any WSGI server configured to use this 32 application = get_wsgi_application() variable 36 # application = HelloWorldApplication(application)
|
/openbmc/bmcweb/test/http/ |
H A D | parsing_test.cpp | 12 EXPECT_TRUE(isJsonContentType("application/json")); in TEST() 16 EXPECT_TRUE(isJsonContentType("application/json;charset=utf-8")); in TEST() 17 EXPECT_TRUE(isJsonContentType("application/json;charset=ascii")); in TEST() 21 EXPECT_TRUE(isJsonContentType("application/json; charset=utf-8")); in TEST() 23 EXPECT_TRUE(isJsonContentType("APPLICATION/JSON")); in TEST() 24 EXPECT_TRUE(isJsonContentType("APPLICATION/JSON; CHARSET=UTF-8")); in TEST() 25 EXPECT_TRUE(isJsonContentType("APPLICATION/JSON;CHARSET=UTF-8")); in TEST() 27 EXPECT_FALSE(isJsonContentType("application/xml")); in TEST() 30 EXPECT_FALSE(isJsonContentType("application/json;")); in TEST() 31 EXPECT_FALSE(isJsonContentType("application/json; ")); in TEST()
|
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
H A D | Application.v1_0_1.json | 2 "$id": "http://redfish.dmtf.org/schemas/v1/Application.v1_0_1.json", 3 "$ref": "#/definitions/Application", 26 "#Application.Reset": { 37 "Application": { object 39 …"description": "The `Application` schema represents an application or service running on a compute… 40 …"longDescription": "This resource shall represent an application or service running on a computer … 85 "description": "The URIs to which this application pushes data.", 93 …cription": "This property shall contain an array of URIs to which this application pushes data. T… 107 … "description": "The URIs that provide access to data or other information in this application.", 115 …ion in this application. This is typically for applications that allow external users to perform … [all …]
|
/openbmc/linux/arch/arm/mach-pxa/ |
D | pxa3xx-regs.h |
|
/openbmc/docs/ |
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 …]
|
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 …]
|
/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. 18 EFI Application 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 [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 20 ## Application section in phosphor-regulators 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/linux/net/netlabel/ |
D | netlabel_mgmt.h |
|
D | netlabel_unlabeled.h |
|
/openbmc/openbmc/poky/meta/files/common-licenses/ |
H A D | LGPL-3.0-only | 14 “The Library” refers to a covered work governed by this License, other than an Application or a Com… 16 An “Application” is any work that makes use of an interface provided by the Library, but which is n… 18 A “Combined Work” is a work produced by combining or linking an Application with the Library. The p… 20 …s of the Combined Work that, considered in isolation, are based on the Application, and not on the… 22 …Application Code” for a Combined Work means the object code and/or source code for the Application… 28 …ications, a facility refers to a function or data to be supplied by an Application that uses the f… 30 …ided that you make a good faith effort to ensure that, in the event an Application does not supply… 35 The object code form of an Application may incorporate material from a header file that is part of … 48 …the Corresponding Application Code in a form suitable for, and under terms that permit, the user t… 50 …Application with a modified version of the Linked Version. (If you use option 4d0, the Installatio…
|
H A D | LGPL-3.0-or-later | 25 an Application or a Combined Work as defined below. 29 An "Application" is any work that makes use of an interface provided by the 36 A "Combined Work" is a work produced by combining or linking an Application 44 Combined Work that, considered in isolation, are based on the Application, 49 The "Corresponding Application Code" for a Combined Work means the object 50 code and/or source code for the Application, including any data and utility 51 programs needed for reproducing the Combined Work from the Application, but 62 refers to a function or data to be supplied by an Application that uses the 67 that, in the event an Application does not supply the function or data, the 76 The object code form of an Application may incorporate material from a header [all …]
|
/openbmc/linux/Documentation/userspace-api/media/v4l/ |
D | pixfmt-v4l2.rst |
|
/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/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/docs/development/ |
H A D | devtool-hello-world.md | 3 **Document Purpose:** Walk through compiling and running an OpenBMC application 82 ## Loading an Application Directly Into a Running QEMU 110 3. Create a safe file system for your application 112 Now is time to load your Hello World application in to QEMU virtual hardware. 114 first so you could simply scp your application in to /usr/local/bin, run it 117 application paths are hardcoded in the service files. Let's start our journey 140 ## Run the Application in QEMU 148 2. Run the application in your QEMU session: 155 application. In general, this is not how you will test new applications. 158 3. Start application via systemd service [all …]
|
/openbmc/linux/drivers/iio/accel/ |
D | mma9551_core.c |
|
/openbmc/u-boot/include/ |
H A D | tee.h | 55 * struct tee_optee_ta_uuid - OP-TEE Trusted Application (TA) UUID format 86 * struct tee_param_memref - memory reference for a Trusted Application 100 * struct tee_param_value - value parameter for a Trusted Application 112 * struct tee_param - invoke parameter for a Trusted Application 132 * @uuid: [in] UUID of the Trusted Application 150 * @func: [in] Trusted Application function, specific to the TA 173 * @open_session: Opens a session to a Trusted Application in the TEE, 174 * @close_session: Closes a session to Trusted Application, 175 * @invoke_func: Invokes a function in a Trusted Application, 187 * open_session() - Open a session to a Trusted Application [all …]
|