| /openbmc/openbmc/meta-openembedded/meta-xfce/recipes-xfce/garcon/files/ |
| H A D | 0001-xfce-applications.menu-don-t-bloat-settings-menu-by-.patch | 4 Subject: [garcon] xfce-applications.menu: don't bloat settings menu by
16 data/xfce/xfce-applications.menu | 3 +++
19 diff --git a/data/xfce/xfce-applications.menu b/data/xfce/xfce-applications.menu
21 --- a/data/xfce/xfce-applications.menu
22 +++ b/data/xfce/xfce-applications.menu
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | vidioc-g-priority.rst | 38 To query the current access priority applications call the
42 To request an access priority applications store the desired priority in
60 - Lowest priority, usually applications running in background, for
62 in user space will be necessary if multiple applications want to
69 - Medium priority, usually applications started and interactively
71 or just "panel" applications to change the channel or video
78 applications which must not be interrupted, like video recording.
|
| H A D | format.rst | 13 Different devices exchange different kinds of data with applications,
18 applications should always negotiate a data format before engaging in
21 to satisfy the request. Of course applications can also just query the
35 initialization sequence. Prior to this point multiple panel applications
53 When applications omit the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl its locking side
66 All drivers exchanging data with applications must support the
78 by all drivers exchanging image data with applications.
85 routine or library for integration into applications.
90 seems useless, but there are applications serving as proxy between
91 drivers and the actual video applications for which this is useful.
|
| H A D | app-pri.rst | 9 When multiple applications share a device it may be desirable to assign
12 applications from changing video controls or switching the current TV
13 channel. Another objective is to permit low priority applications
15 applications and automatically regain control of the device at a later
|
| H A D | vidioc-enum-dv-timings.rst | 40 applications can enumerate a list of known supported timings. Call
45 To query the available timings, applications initialize the ``index``
51 DV timings, applications shall begin at index zero, incrementing by one
62 or outputs (for DV transmitters), applications must specify the desired
84 video node applications must set this field to zero.
87 - Reserved for future extensions. Drivers and applications must set
|
| H A D | io.rst | 10 a device. All drivers exchanging data with applications must support at
19 with memory mapped or user buffers applications call the
28 each file descriptor. The only exceptions are applications not
29 exchanging data with a driver ("panel applications", see :ref:`open`)
|
| H A D | vidioc-g-parm.rst | 53 To get and set the streaming parameters applications call the
104 - Set by drivers and applications, see :ref:`parm-flags`.
124 period. To reset manually applications can just set this field to
132 applications and drivers must set this field to zero. Applications
145 - Reserved for future extensions. Drivers and applications must set
163 - Set by drivers and applications, see :ref:`parm-flags`.
184 period. To reset manually applications can just set this field to
192 applications and drivers must set this field to zero. Applications
205 - Reserved for future extensions. Drivers and applications must set
236 imaging applications. The idea is to get the best possible image
|
| H A D | rw.rst | 31 To read from the device applications use the :c:func:`read()`
33 must implement one I/O method if they exchange data with applications,
39 It would be desirable if applications could depend on drivers
42 require this interface, which is most useful for simple applications
|
| /openbmc/openbmc/poky/meta/recipes-sato/puzzles/ |
| H A D | puzzles_git.bb | 26 rm ${D}/${datadir}/applications/net.desktop
29 install -d ${D}/${datadir}/applications/
35 echo "making ${D}/${datadir}/applications/$prog.desktop"
36 cat <<STOP > ${D}/${datadir}/applications/$prog.desktop
40 Icon=applications-games
|
| /openbmc/openbmc/poky/meta/recipes-sato/shutdown-desktop/ |
| H A D | shutdown-desktop.bb | 12 install -d ${D}${datadir}/applications
13 install -m 0644 shutdown.desktop ${D}${datadir}/applications/
15 sed -i ${D}${datadir}/applications/shutdown.desktop -e 's#^Exec=\(.*\)#Exec=${base_sbindir}/\1#'
20 sed -i $D${datadir}/applications/shutdown.desktop -e 's#^Exec=\(.*\)/halt#Exec=\1/reboot#' \
|
| /openbmc/openbmc/meta-phosphor/recipes-phosphor/packagegroups/ |
| H A D | packagegroup-obmc-apps.bb | 85 # Use the fan control package group for applications
111 SUMMARY:${PN}-inventory = "Inventory applications"
117 SUMMARY:${PN}-leds = "LED applications"
124 SUMMARY:${PN}-logging = "Logging applications"
129 SUMMARY:${PN}-remote-logging = "Remote logging applications"
135 SUMMARY:${PN}-sensors = "Sensor applications"
140 SUMMARY:${PN}-software = "Software applications"
161 SUMMARY:${PN}-settings = "Settings applications"
176 SUMMARY:${PN}-user-mgmt = "User management applications"
|
| /openbmc/linux/Documentation/scsi/ |
| H A D | megaraid.rst | 11 user applications in a similar way. They understand the same firmware control
12 commands. Furthermore, the applications also can treat different classes of
14 interfaces with the applications on one side and all the low level drivers
63 The applications interface with the common module via the character device
68 applications into uioc_t. After driver handles the uioc_t, the common module
69 will convert that back into the old format before returning to applications.
71 As new applications evolve and replace the old ones, the old packet format
|
| /openbmc/phosphor-power/ |
| H A D | README.md | 5 This repository contains applications for configuring and monitoring devices
8 Actively-maintained applications:
21 Legacy applications:
28 To build all applications in this repository:
44 - Which applications to build and install.
50 Several applications in this repository require a PSU JSON config to run. The
|
| /openbmc/linux/Documentation/userspace-api/media/mediactl/ |
| H A D | media-controller-intro.rst | 15 presented to userspace applications as V4L2 and ALSA capture devices.
18 available directly to applications by the drivers, can usually be
28 applications to access hardware parameters. As newer hardware expose an
30 applications really require based on limited information, thereby
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-platform-dell-privacy-wmi | 14 Identifies the local microphone can be muted by hardware, no applications
44 consumed by various applications interested in knowing the Privacy
49 Identifies the local microphone can be muted by hardware, no applications
60 and cannot send stream to OS applications
65 and camera module to OS applications
|
| /openbmc/openbmc/meta-phosphor/ |
| H A D | recipes.txt | 1 recipes-connectivity - Libraries and applications related to communication with other devices
6 recipes-kernel - The kernel and generic applications/libraries with strong kernel dependencies
7 recipes-phosphor - Phosphor OpenBMC applications and configuration
|
| /openbmc/linux/Documentation/driver-api/rapidio/ |
| H A D | mport_cdev.rst | 13 devices directly to applications, in a manner that allows the numerous and
17 for user-space applications. Most of RapidIO operations are supported through
24 Using available set of ioctl commands user-space applications can perform
37 - Enable/Disable reporting of RapidIO doorbell events to user-space applications
39 - Enable/Disable reporting of RIO port-write events to user-space applications
58 as user-space applications while using remaining functionality provided by
102 API library and applications that use this device driver are available from
|
| /openbmc/linux/Documentation/fb/ |
| H A D | api.rst | 11 This document describes the frame buffer API used by applications to interact
17 the recommended API implementation, but applications should be prepared to
148 Screen information are queried by applications using the FBIOGET_FSCREENINFO
154 be directly modified by applications, but can be changed by the driver when an
222 To modify variable information, applications call the FBIOPUT_VSCREENINFO
227 applications should call the FBIOGET_VSCREENINFO ioctl and modify only the
240 for applications when using RGB and grayscale formats, as well as legacy
243 To select a format, applications set the fb_var_screeninfo bits_per_pixel field
247 - For grayscale formats, applications set the grayscale field to one. The red,
248 blue, green and transp fields must be set to 0 by applications and ignored by
[all …]
|
| /openbmc/openbmc/meta-facebook/meta-tiogapass/ |
| H A D | recipes.txt | 1 recipes-kernel - The kernel and generic applications/libraries with strong kernel dependencies
2 recipes-phosphor - Phosphor OpenBMC applications and configuration
|
| /openbmc/openbmc/meta-yadro/meta-nicole/ |
| H A D | recipes.txt | 1 recipes-kernel - The kernel and generic applications/libraries with strong kernel dependencies
2 recipes-phosphor - Phosphor OpenBMC applications and configuration
|
| /openbmc/openbmc/meta-amd/meta-ethanolx/ |
| H A D | recipes.txt | 1 recipes-kernel - The kernel and generic applications/libraries with strong kernel dependencies
2 recipes-phosphor - Phosphor OpenBMC applications and configuration
|
| /openbmc/openbmc/meta-ibm/meta-palmetto/ |
| H A D | recipes.txt | 1 recipes-kernel - The kernel and generic applications/libraries with strong kernel dependencies
2 recipes-phosphor - Phosphor OpenBMC applications and configuration
|
| /openbmc/openbmc/meta-bytedance/meta-g220a/ |
| H A D | recipes.txt | 1 recipes-kernel - The kernel and generic applications/libraries with strong kernel dependencies
2 recipes-phosphor - Phosphor OpenBMC applications and configuration
|
| /openbmc/openbmc/meta-ibm/meta-romulus/ |
| H A D | recipes.txt | 1 recipes-kernel - The kernel and generic applications/libraries with strong kernel dependencies
2 recipes-phosphor - Phosphor OpenBMC applications and configuration
|
| /openbmc/openbmc/meta-amd/meta-daytonax/ |
| H A D | recipes.txt | 1 recipes-kernel - The kernel and generic applications/libraries with strong kernel dependencies
2 recipes-phosphor - Phosphor OpenBMC applications and configuration
|