| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-graphics/gphoto2/libgphoto2/ |
| H A D | 0001-configure-Filter-out-buildpaths-from-CC.patch | 26 [The C compiler we are using])
38 - [The C compiler we're using])
42 + [The C compiler we are using])
|
| /openbmc/linux/Documentation/devicetree/bindings/input/ |
| H A D | da9062-onkey.txt | 18 - dlg,disable-key-power : Disable power-down using a long key-press. If this
20 press when triggered using a long press of the OnKey.
40 Example: DA9061 using a fall-back compatible for the DA9062 onkey driver
|
| /openbmc/openbmc/poky/meta/recipes-support/bmaptool/ |
| H A D | bmaptool_git.bb | 1 SUMMARY = "Tools to generate block map (AKA bmap) and flash images using bmap"
2 DESCRIPTION = "bmaptool - tools to generate block map (AKA bmap) and flash images using \
4 and copying files using the block map. The idea is that large file containing \
|
| /openbmc/linux/Documentation/hid/ |
| H A D | hidraw.rst | 19 communication with these non-conformant devices is impossible using hiddev.
45 devices, the reports read using read() are the reports sent from the device
48 the O_NONBLOCK flag to open(), or by setting the O_NONBLOCK flag using
61 using a SET_REPORT transfer.
79 This ioctl returns the device's report descriptor using a
115 specification, feature reports are always sent using the control endpoint.
124 This ioctl will request a feature report from the device using the control
135 This ioctl will send an input report to the device, using the control endpoint.
144 This ioctl will request an input report from the device using the control
165 This ioctl will request an output report from the device using the control
[all …]
|
| /openbmc/u-boot/drivers/tpm/ |
| H A D | Kconfig | 33 to the device using the standard TPM Interface Specification (TIS)
42 to the device using the standard TPM Interface Specification (TIS)
66 to the device using the standard TPM Interface Specification (TIS)
76 available using the 'tpm' command, too.
84 to the device using the standard TPM Interface Specification (TIS)
93 to the device using the standard TPM Interface Specification (TIS)
145 to the device using the standard TPM Interface Specification (TIS)
154 to the device using the standard TPM Interface Specification (TIS)
|
| /openbmc/qemu/tests/avocado/ |
| H A D | README.rst | 2 Integration tests using the Avocado Framework
10 section "Integration tests using the Avocado Framework".
|
| /openbmc/linux/Documentation/userspace-api/media/drivers/ |
| H A D | ccs.rst | 21 crop is configured using the ``V4L2_SEL_TGT_CROP`` on the source pad (0) of the
42 Scaling is configured using selection target ``V4L2_SEL_TGT_COMPOSE`` on the
68 The CCS defines an analogue gain model where the gain can be calculated using
93 The ``linear`` and ``exponent`` factors can be set using the
101 using ``V4L2_CID_CCS_SHADING_CORRECTION``. Additionally, the luminance
102 correction level may be changed using
|
| /openbmc/linux/drivers/nvme/host/ |
| H A D | Kconfig | 53 This provides support for the NVMe over Fabrics protocol using
55 to use remote block devices exported using the NVMe protocol set.
69 This provides support for the NVMe over Fabrics protocol using
71 exported using the NVMe protocol set.
86 This provides support for the NVMe over Fabrics protocol using
88 exported using the NVMe protocol set.
|
| /openbmc/linux/Documentation/networking/ |
| H A D | batman-adv.rst | 9 using UDP packets and sets routing tables, batman-advanced operates on ISO/OSI
30 batman-adv can operate. The batman-adv soft-interface can be created using the
40 using/broadcasting on this/these interface(s).
46 The same can also be done using the batctl interface subcommand::
57 which can be modified using batctl. Detailed information about this can be found
86 you. Basically, one "hands over" the data by using the batman interface and
90 IP address which can be either statically configured or dynamically (by using
111 a number of ways. Try using the commands: ``dmesg``, ``logread``, or looking in
123 Those additional debug messages can be accessed using the perf infrastructure::
|
| /openbmc/linux/net/dsa/ |
| H A D | Kconfig | 38 tristate "Tag driver for Broadcom switches using in-frame headers"
45 tristate "Tag driver for Broadcom legacy switches using in-frame headers"
53 tristate "Tag driver for Broadcom switches using prepended headers"
76 tristate "Tag driver for Marvell switches using DSA headers"
83 tristate "Tag driver for Marvell switches using EtherType DSA headers"
102 tristate "Tag driver for Ocelot family of switches, using NPI port"
113 tristate "Tag driver for Ocelot family of switches, using VLAN"
118 Flow control over the CPU port is functional in this mode. When using
164 tristate "Tag driver for switches using a trailer tag"
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | v4l2grab-example.rst | 6 Video Grabber example using libv4l
9 This program demonstrates how to grab V4L2 images in ppm format by using
|
| H A D | dev-event.rst | 16 subscribed using the
19 using the :ref:`VIDIOC_DQEVENT` ioctl. Events may be
20 unsubscribed using VIDIOC_UNSUBSCRIBE_EVENT ioctl. The special event
28 The information on dequeueable events is obtained by using select or
|
| /openbmc/linux/Documentation/misc-devices/ |
| H A D | xilinx_sdfec.rst | 128 Determine the configuration of the SD-FEC core by using the ioctl
136 Setting the order is done by using the ioctl :c:macro:`XSDFEC_SET_ORDER`
151 - Add the LPDC Code Parameters using the ioctl :c:macro:`XSDFEC_ADD_LDPC_CODE_PARAMS`
164 Configuring the Turbo decode parameters is done by using the ioctl :c:macro:`XSDFEC_SET_TURBO` usin…
184 Bypassing the SD-FEC is done by using the ioctl :c:macro:`XSDFEC_SET_BYPASS`
193 Start the SD-FEC core by using the ioctl :c:macro:`XSDFEC_START_DEV`
207 - Get stats by using the ioctl :c:macro:`XSDFEC_GET_STATS`
210 - Get state by using the ioctl :c:macro:`XSDFEC_GET_STATUS`
212 - Clear stats by using the ioctl :c:macro:`XSDFEC_CLEAR_STATS`
221 Stop the device by using the ioctl :c:macro:`XSDFEC_STOP_DEV`
[all …]
|
| /openbmc/linux/drivers/net/wireless/microchip/wilc1000/ |
| H A D | Kconfig | 16 This module adds support for the SDIO interface of adapters using
23 this if your platform is using the SDIO bus.
32 This module adds support for the SPI interface of adapters using
38 VDDIO. Select this if your platform is using the SPI bus.
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-driver-intc_sar | 11 the current SAR regulatory mode on the Dynamic SAR driver using
12 this sysfs node. Such an application can also read back using
44 level using the Band/Antenna/SAR table index information.
52 using POLLPRI event on file-descriptor (fd) obtained by opening
|
| H A D | debugfs-pfo-nx-crypto | 29 The total number of bytes encrypted using AES in any of the driver's
36 The total number of bytes hashed by the hardware using SHA-256.
42 The total number of bytes hashed by the hardware using SHA-512.
|
| /openbmc/telemetry/ |
| H A D | README.md | 26 - using bitbake in yocto environment
27 - using meson as native build
29 To build it using bitbake follow the guide from OpenBMC docs`[5]`. To build it
30 using meson follow the quick guide to install meson`[6]` and then run below
|
| /openbmc/openbmc-test-automation/ipmi/ |
| H A D | test_ipmi_sensor.robot | 2 Documentation Validate IPMI sensor IDs using Redfish.
24 Verify IPMI Temperature Readings using Redfish
34 Verify DCMI Temperature Readings using Redfish
45 [Documentation] Test ambient temperature via IPMI and verify using Redfish.
99 ... verify using Redfish.
148 ... using Redfish.
157 [Documentation] Verify the IPMI sensor for CPU present using Redfish.
166 [Documentation] Verify the IPMI sensor for CPU not present using Redfish.
175 [Documentation] Verify the IPMI sensor for GPU present using Redfish.
193 [Documentation] Test sensor threshold via IPMI and verify using Redfish.
[all …]
|
| /openbmc/openbmc/meta-raspberrypi/recipes-multimedia/gstreamer/ |
| H A D | gstreamer1.0-plugins-base_%.bbappend | 1 # if using bcm driver enable dispmanx not when using VC4 driver
|
| /openbmc/linux/Documentation/fb/ |
| H A D | gxfb.rst | 14 without using tiny, unreadable fonts.
26 Switching modes is done using gxfb.mode_option=<resolution>... boot
27 parameter or using `fbset` program.
|
| H A D | lxfb.rst | 15 without using tiny, unreadable fonts.
27 Switching modes is done using lxfb.mode_option=<resolution>... boot
28 parameter or using `fbset` program.
|
| /openbmc/linux/drivers/nfc/pn533/ |
| H A D | Kconfig | 14 Select this if your platform is using the USB bus.
25 Select this if your platform is using the I2C bus.
36 Select this if your platform is using the UART bus.
|
| /openbmc/linux/drivers/peci/controller/ |
| H A D | Kconfig | 12 connected to it, and communicate with them using PECI protocol.
14 Say Y here if your system runs on ASPEED SoC and you are using it
28 to it and communicate with them using PECI protocol.
|
| /openbmc/linux/Documentation/security/keys/ |
| H A D | ecryptfs.rst | 6 file using a randomly generated File Encryption Key (FEK).
11 using a key, the FEKEK, derived from a user prompted passphrase; in the latter
33 The eCryptfs filesystem may really benefit from using encrypted keys in that the
56 'ecryptfs' and save it using a previously loaded user key "test"::
69 Mount an eCryptfs filesystem using the created encrypted key "1000100010001000"
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/websocketpp/websocketpp-0.8.2/ |
| H A D | 1024.patch | 55 # if a C++11 environment is available build using that, otherwise use boost
68 # if a C++11 environment is available build using that, otherwise use boost
81 # if a C++11 environment is available build using that, otherwise use boost
107 # if a C++11 environment is available build using that, otherwise use boost
120 # if a C++11 environment is available build using that, otherwise use boost
133 # if a C++11 environment is available build using that, otherwise use boost
146 # if a C++11 environment is available build using that, otherwise use boost
159 # if a C++11 environment is available build using that, otherwise use boost
172 # if a C++11 environment is available build using that, otherwise use boost
185 # if a C++11 environment is available build using that, otherwise use boost
[all …]
|