Home
last modified time | relevance | path

Searched refs:application (Results 1 – 25 of 1241) sorted by relevance

12345678910>>...50

/openbmc/linux/net/bluetooth/cmtp/
H A Dcapi.c187 struct cmtp_application *application; in cmtp_recv_interopmsg() local
205 application = cmtp_application_get(session, CMTP_MSGNUM, msgnum); in cmtp_recv_interopmsg()
206 if (application) { in cmtp_recv_interopmsg()
207 application->state = BT_CONNECTED; in cmtp_recv_interopmsg()
208 application->msgnum = 0; in cmtp_recv_interopmsg()
209 application->mapping = CAPIMSG_APPID(skb->data); in cmtp_recv_interopmsg()
218 application = cmtp_application_get(session, CMTP_MAPPING, appl); in cmtp_recv_interopmsg()
219 if (application) { in cmtp_recv_interopmsg()
220 application->state = BT_CLOSED; in cmtp_recv_interopmsg()
221 application->msgnum = 0; in cmtp_recv_interopmsg()
[all …]
/openbmc/openbmc/meta-openembedded/meta-gnome/recipes-connectivity/geary/geary/
H A D0001-application-client.vala-hardcode-some-paths.patch4 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 Dpsu-monitoring.md12 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 …]
/openbmc/linux/drivers/hid/
H A Dwacom_wac.h173 ((f)->application == HID_DG_PEN) || \
174 ((f)->application == HID_DG_DIGITIZER) || \
175 ((f)->application == WACOM_HID_WD_PEN) || \
176 ((f)->application == WACOM_HID_WD_DIGITIZER) || \
177 ((f)->application == WACOM_HID_G9_PEN) || \
178 ((f)->application == WACOM_HID_G11_PEN))
181 ((f)->application == HID_DG_TOUCHSCREEN) || \
182 ((f)->application == WACOM_HID_G9_TOUCHSCREEN) || \
183 ((f)->application == WACOM_HID_G11_TOUCHSCREEN) || \
184 ((f)->application == WACOM_HID_WT_TOUCHPAD) || \
[all …]
H A Dhid-multitouch.c109 unsigned int application; member
156 struct mt_application *application; member
234 static int cypress_compute_slot(struct mt_application *application, in cypress_compute_slot() argument
237 if (*slot->contactid != 0 || application->num_received == 0) in cypress_compute_slot()
419 struct mt_application *application; in mt_set_quirks() local
428 list_for_each_entry(application, &td->applications, list) { in mt_set_quirks()
429 application->quirks = val; in mt_set_quirks()
430 if (!application->have_contact_count) in mt_set_quirks()
431 application->quirks &= ~MT_QUIRK_CONTACT_CNT_ACCURATE; in mt_set_quirks()
528 struct mt_application *application) in mt_allocate_usage() argument
[all …]
/openbmc/openbmc-tools/rootfs_size/
H A Dresults.txt52 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/docs/
H A DREST-cheatsheet.md27 …$ curl -c cjar -b cjar -k -H "Content-Type: application/json" -X POST https://${bmc}/login -d "{\"…
47 …$ export token=`curl -k -H "Content-Type: application/json" -X POST https://${bmc}/login -d '{"use…
61 $ export token=`curl -k -H "Content-Type: application/json" -X POST https://${bmc}/login -d '{"user…
82 …$ curl -k -H "X-Auth-Token: $token" -H "Content-Type: application/json" -d '{"data": "xyz.openbmc_…
88 …$ curl -k -H "X-Auth-Token: $token" -H "Content-Type: application/json" -X PUT -d '{"data":"xyz.op…
94 …$ curl -k -H "X-Auth-Token: $token" -H "Content-Type: application/json" -d '{"data": "xyz.openbmc_…
100 …$ curl -k -H "X-Auth-Token: $token" -H "Content-Type: application/json" -X PUT -d '{"data":"xyz.op…
106 …$ curl -k -H "X-Auth-Token: $token" -H "Content-Type: application/json" -X PUT -d '{"data":"xyz.op…
112 …$ curl -k -H "X-Auth-Token: $token" -H "Content-Type: application/json" -X GET https://${bmc}/xyz/…
118 …$ curl -k -H "X-Auth-Token: $token" -H "Content-Type: application/json" -X DELETE https://${bmc}/x…
[all …]
H A DREDFISH-cheatsheet.md25 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/openbmc/meta-openembedded/meta-webserver/recipes-httpd/nginx/files/
H A Dnginx.conf24 default_type application/octet-stream;
42 …gzip_types text/plain text/css application/json application/javascript text/xml application/xml ap…
/openbmc/linux/Documentation/userspace-api/media/v4l/
H A Dvidioc-subdev-enum-mbus-code.rst34 This call is used by the application to access the enumeration
74 application.
78 Filled in by the application.
115 - The driver allows the application to try to change the default colorspace
116 encoding. The application can ask to configure the colorspace of the
122 - The driver allows the application to try to change the default transform function.
123 The application can ask to configure the transform function of
129 - The driver allows the application to try to change the default Y'CbCr
130 encoding. The application can ask to configure the Y'CbCr encoding of the
136 - The driver allows the application to try to change the default HSV
[all …]
H A Dpixfmt-v4l2.rst47 - The pixel format or type of compression, set by the application.
69 the value requested by the application, returning ``width`` times
111 by the driver for capture streams and by the application for
112 output streams, see :ref:`colorspaces`. If the application sets the
113 flag ``V4L2_PIX_FMT_FLAG_SET_CSC`` then the application can set
148 - Flags set by the application or driver, see :ref:`format-flags`.
155 the driver for capture streams and by the application for output
156 streams, see :ref:`colorspaces`. If the application sets the
157 flag ``V4L2_PIX_FMT_FLAG_SET_CSC`` then the application can set
169 the driver for capture streams and by the application for output
[all …]
H A Dvidioc-enum-fmt.rst87 - Number of the format in the enumeration, set by the application.
91 - Type of the data stream, set by the application. Only these types
131 application. Only applicable to drivers that advertise the
197 - The driver allows the application to try to change the default
199 The application can ask to configure the colorspace of the capture device
204 - The driver allows the application to try to change the default
206 The application can ask to configure the transfer function of the capture
211 - The driver allows the application to try to change the default
213 The application can ask to configure the Y'CbCr encoding of the capture device
218 - The driver allows the application to try to change the default
[all …]
/openbmc/phosphor-power/phosphor-power-sequencer/docs/
H A DREADME.md5 The phosphor-power-sequencer application powers the chassis on/off and monitors
9 application uses information from the power sequencer device to determine the
14 The application is a single-threaded C++ executable. It is a 'daemon' process
15 that runs continually. The application is launched by systemd when the BMC
18 The application is driven by an optional, system-specific JSON configuration
28 This application currently supports the following power sequencer device types:
38 - A BMC application or script sets the `state` property to 1 on the
40 - The phosphor-power-sequencer application writes the value 1 to the named GPIO
50 - The phosphor-power-sequencer application sets the `pgood` property to 1 on the
56 - A BMC application or script sets the `state` property to 0 on the
[all …]
/openbmc/openbmc/poky/meta/recipes-devtools/file/files/
H A D0001-Use-4-in-default-reset-previous-negative-offset-in-m.patch35 -!: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/u-boot/doc/
H A DREADME.u-boot_on_efi8 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-dbus-interfaces/yaml/xyz/openbmc_project/Network/
H A DREADME.md69 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 DNetwork-Configuration.md66 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/linux/Documentation/ABI/testing/
H A Dsysfs-platform-chipidea-usb-otg7 the application running on the A-device wants to use the bus,
8 and to be 0 when the application no longer wants to use
15 Reading: returns 1 if the application running on the A-device
24 application running on the A-device wants to power down
39 that the application running on the B-device wants to use the
40 bus as host, and is 0 when the application no longer wants to
45 Reading: returns if the application running on the B device
H A Dsysfs-class-fc5 This interface allows an admin to set an FC application
8 an application or logical entity such as a virtual
9 machine or container group. The application or logical
13 entities can utilize the application id and FC traffic
25 If an admin wants to remove an FC application identifier
/openbmc/linux/tools/testing/selftests/hid/tests/
H A Dtest_ite_keyboard.py135 def event(self, keys, reportID=None, application=None): argument
136 application = application or "Keyboard"
137 return super().event(keys, reportID, application)
/openbmc/linux/Documentation/networking/device_drivers/wwan/
H A Diosm.rst13 MBIM protocol [1]. Any front end application ( eg: Modem Manager) could easily
21 application to detect port enumeration and enable MBIM functionality.
23 Examples of few such userspace application are:
34 Management application development
51 The userspace application is responsible for all control message fragmentation
56 The MBIM control messages from the management application must not exceed the
61 The management application must accept control messages of up the negotiated
74 The userspace management application is responsible for creating new IP link
/openbmc/obmc-ikvm/
H A DREADME.md3 The obmc-ikvm application is a VNC server that provides access to the host
4 graphics output. The application interfaces with the video device on the BMC
6 (remote framebuffer, also known as VNC) protocol. The application also
13 the BMC, the application can be started with the following command:
/openbmc/openpower-vpd-parser/
H A DREADME.md13 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 VPD 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-power/phosphor-power-sequencer/
H A DREADME.md5 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/linux/Documentation/networking/
H A Dkcm.rst8 interface over TCP for generic application protocols. With KCM an application
9 can efficiently send and receive application protocol messages over TCP using
73 Messages are sent over a TCP stream with some application protocol message
75 of a received message can be deduced from the application protocol header
93 using the socket. When the application gets the error notification for a
195 if an application thread knows that it will be doing a lot of
223 KCM accelerates application layer protocols. Specifically, it allows
228 application layer messages a unit of work in the kernel for the purposes of
238 parallelized). In an application, a KCM socket can be opened for each
255 On transmit, there are three ways an application can batch (pipeline)
[all …]

12345678910>>...50