| /openbmc/linux/Documentation/driver-api/gpio/ |
| H A D | using-gpio.rst | 16 using appropriate kernel drivers is paramount. Submit your code for inclusion
33 from userspace will likely be a good fit for using GPIO lines from userspace as
38 productify the prototype: rewrite it using proper kernel drivers. Do not under
39 any circumstances deploy any uniform products using GPIO from userspace.
|
| /openbmc/linux/Documentation/admin-guide/device-mapper/ |
| H A D | dm-crypt.rst | 6 using the kernel crypto API.
112 Perform encryption using the same cpu that IO was submitted on.
121 thread because it benefits CFQ to have writes submitted using the
161 encryption with dm-crypt using the 'cryptsetup' utility, see
167 # Create a crypt device using dmsetup
173 # Create a crypt device using dmsetup when encryption key is stored in keyring service
179 # Create a crypt device using cryptsetup and LUKS header with default cipher
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | parport.rst | 12 because there are a lot of people using the same IRQ for their
17 using the port).
33 0x3bc with no IRQ, one at 0x378 using IRQ 7, and one at 0x278 with an
140 ``devices/active`` A list of the device drivers using that port. A "+"
141 will appear by the name of the device currently using
144 using that port.
212 override this, though, by using parameters either when you load the lp
237 the command line, or with ``insmod plip timid=1`` when using modules,
254 - interrupt-driven, protocol in hardware using PIO
255 - interrupt-driven, protocol in hardware using DMA
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | customizing-images.rst | 16 packages using local variables this way, you need to realize that these
20 To add a package to your image using the local configuration file, use
45 You can add packages using a similar approach through the
53 high-level image features by using the
57 equivalent, best practices dictate using :term:`IMAGE_FEATURES` from within
58 a recipe and using :term:`EXTRA_IMAGE_FEATURES` from within your
115 Defining the software using a custom recipe gives you total control over
183 build an image using these package group packages, you need to add
197 variable in the ``base-files`` recipe using either an append file or a
211 results in all the images using the name "testme". Once testing is
|
| H A D | wic.rst | 6 Creating an image for a particular hardware target using the
36 ":ref:`dev-manual/wic:using the wic plugin interface`" section
41 to use the Wic utility, provides information on using the Wic plugins
119 commands except "help" by using the following form::
242 run as root when using the utility.
377 a partition using an implementation-specific function::
464 Generate an Image using an Existing Kickstart File
484 INFO: The image(s) were created using OE kickstart file:
582 INFO: The image(s) were created using OE kickstart file:
620 INFO: The image(s) were created using OE kickstart file:
[all …]
|
| /openbmc/linux/Documentation/power/ |
| H A D | energy-model.rst | 15 from one platform to another. These power costs can be estimated using
107 performance domains using cpumask. For other devices than CPUs the last
116 Registration of EM using DT
119 The EM can also be registered using OPP framework and information in DT
143 platform. Special care should be taken by other frameworks which are using EM
149 The 'simple' EM is registered using the framework helper function
155 The EM which is registered using this method might not reflect correctly the
168 Subsystems interested in the energy model of a CPU can retrieve it using the
172 The energy consumed by a performance domain can be estimated using the
198 performance domain in the Energy Model framework using the (fake) 'foo'
|
| /openbmc/linux/Documentation/devicetree/bindings/extcon/ |
| H A D | extcon-palmas.txt | 14 it performs id-detection using GPIO else using OTG core.
|
| /openbmc/u-boot/doc/device-tree-bindings/firmware/ |
| H A D | linaro,optee-tz.txt | 3 OP-TEE is a piece of software using hardware features to provide a Trusted
7 We're using "linaro" as the first part of the compatible property for
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/aoetools/ |
| H A D | aoetools_36.bb | 4 storage protocol, a simple protocol for using storage over anethernet LAN. \
5 The vblade program (storage target) exports a blockdevice using AoE. \
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/kconfig-frontends/files/ |
| H A D | 0001-Avoid-using-hard-coded-usr-include-paths.patch | 4 Subject: [PATCH] Avoid using hard coded /usr/include paths
6 The system could end up using an include path that points to the host
|
| /openbmc/linux/Documentation/w1/masters/ |
| H A D | w1-gpio.rst | 12 wire and the GPIO pin can be specified using GPIO machine descriptor tables.
13 It is also possible to define the master using device tree, see
|
| /openbmc/openbmc-test-automation/xcat/ |
| H A D | test_power_operation.robot | 18 [Documentation] Power on system via XCAT and verify using REST.
26 [Documentation] Power off system via XCAT and verify using REST.
34 [Documentation] Verify BMC state using REST and XCAT.
|
| /openbmc/openbmc/poky/documentation/toaster-manual/ |
| H A D | setup-and-use.rst | 27 using this command::
102 computer supports by using the shortcut "0.0.0.0:port".
212 - If you are using Ubuntu, run the following::
216 - If you are using Fedora or a RedHat distribution, run the
221 - If you are using openSUSE, run the following::
237 be using ``/var/www/toaster``::
360 If you are using Fedora or RedHat, put it here::
364 If you are using openSUSE, put it here::
449 attach to it using this command::
457 You can now open up a browser and start using Toaster.
[all …]
|
| /openbmc/openbmc/meta-yadro/recipes-phosphor/ipmi/phosphor-ipmi-host/ |
| H A D | 0002-Add-support-for-boot-initiator-mailbox.patch | 58 +using MboxVec = std::vector<uint8_t>;
63 + using namespace chassis::internal;
64 + using namespace chassis::internal::cache;
92 + using namespace chassis::internal;
93 + using namespace chassis::internal::cache;
121 + using namespace chassis::internal;
122 + using namespace chassis::internal::cache;
150 + using namespace chassis::internal;
151 + using namespace chassis::internal::cache;
|
| /openbmc/qemu/docs/system/ |
| H A D | authz.rst | 45 ``joebloggs``, while if using Kerberos/GSSAPI it can have a realm
54 created at startup using the ``-object`` argument, or at runtime using the
167 The object can be created on the command line using
218 On the command line it can be created using
226 here, and it is possible to implement brand new plugins using the PAM API.
232 The authorization driver is created using the ``-object`` argument and then
238 will provide ``tls-authz`` property, while any server using SASL will provide
241 Thus an example using SASL and authorization for the VNC server would look
|
| /openbmc/openbmc/poky/documentation/kernel-dev/ |
| H A D | intro.rst | 15 common tasks you can perform using the kernel tools, shows you how to
86 workflow <sdk-manual/extensible:using \`\`devtool\`\` in your sdk workflow>`
125 ":ref:`kernel-dev/common:getting ready to develop using \`\`devtool\`\``"
137 Yocto's :term:`Build Directory` if you are using ``devtool``. For more
139 ":ref:`kernel-dev/common:using \`\`devtool\`\` to patch the kernel`"
142 If you are using traditional kernel development, you edit the source
144 ":ref:`kernel-dev/common:using traditional kernel development to patch the kernel`"
149 :ref:`menuconfig <kernel-dev/common:using \`\`menuconfig\`\`>`,
162 Once you are satisfied with the configuration changes made using
|
| /openbmc/linux/Documentation/networking/ |
| H A D | tls.rst | 61 Transmit and receive are set separately, but the setup is the same, using either
68 socket is encrypted using TLS and the parameters provided in the socket option.
97 call using MSG_MORE, the MSG_MORE data is left on the socket buffer.
103 are decrypted using TLS parameters provided. A full TLS record must
130 using a record of type @record_type.
134 /* send TLS control message using record_type */
213 of calling send directly after a handshake using gnutls.
223 All options are set per-socket using setsockopt(), and their
224 state can be checked using getsockopt() and via socket diag (``ss``).
|
| /openbmc/linux/Documentation/networking/device_drivers/ethernet/freescale/dpaa2/ |
| H A D | mac-phy-support.rst | 79 case, to integrate it with PHYLINK using the dpaa2_mac_connect() API, which
84 - connect to the PHY using phylink_of_phy_connect()
92 - .mac_config() will configure the MAC in the new configuration using the
95 - .mac_link_up() / .mac_link_down() will update the MAC link using the same
179 when necessary using the below listed API::
188 this condition using the following helper::
|
| /openbmc/linux/Documentation/devicetree/bindings/dma/ti/ |
| H A D | k3-bcdma.yaml | 51 1 - block copy channel using global trigger 1
52 2 - block copy channel using global trigger 2
53 3 - block copy channel using local trigger
64 if cell 1 is 1 or 2 (block copy channel using global trigger):
68 channels using global triggers should not be requested directly, but
70 if cell 1 is 3 (block copy channel using local trigger):
|
| /openbmc/linux/Documentation/trace/rv/ |
| H A D | deterministic_automata.rst | 32 in multiple formats. For example, using a *graphical representation*, using
110 of an automaton using the (textual) DOT language as the source code.
133 using the dot utility, or into an ASCII art using graph-easy. For
161 For example, the formal description using set theory is better suitable
|
| /openbmc/linux/Documentation/bpf/ |
| H A D | map_xskmap.rst | 49 Descriptors (FDs). The number of array elements is typically set or adjusted using
82 XSK entry references of type ``struct xdp_sock *`` can be retrieved using the
98 XSK entries can be added or updated using the ``bpf_map_update_elem()``
125 XSK entries can be deleted using the ``bpf_map_delete_elem()``
187 The most comprehensive resource for using XSKMAPs and AF_XDP is `libxdp`_.
192 .. _libxdp-readme: https://github.com/xdp-project/xdp-tools/tree/master/lib/libxdp#using-af_xdp-soc…
|
| /openbmc/openbmc/meta-security/meta-integrity/classes/ |
| H A D | kernel-modsign.bbclass | 8 # using the example key directory.
12 # The default is okay when using the example key directory.
|
| /openbmc/openbmc/poky/meta/recipes-devtools/python/ |
| H A D | python3-flit-core_3.9.0.bb | 1 SUMMARY = "This provides a PEP 517 build backend for packages using Flit."
2 DESCRIPTION = "This provides a PEP 517 build backend for packages using \
|
| /openbmc/linux/drivers/pinctrl/intel/ |
| H A D | Kconfig.tng | 22 an interface that allows configuring of SoC pins and using them as
30 an interface that allows configuring of SoC pins and using them as
|
| /openbmc/linux/drivers/mtd/devices/ |
| H A D | Kconfig | 58 This enables access to AT45xxx DataFlash chips, using SPI.
86 This enables access to Microchip 23K256 SRAM chips, using SPI.
96 This enables access to Microchip 48L640 EERAM chips, using SPI.
103 This enable SNOR support on SPEAR platforms using SMI controller
127 you can still use it for storage or swap by using this driver to
140 tristate "Test driver using RAM"
167 tristate "MTD using block device"
176 be removed during a write (using the floppy drive).
|