| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | dev-radio.rst | 43 Radio devices may have a couple audio controls (as discussed in
46 discussed in :ref:`tuner`) with index number zero to select the radio
|
| H A D | dv-timings.rst | 9 The video standards discussed so far have been dealing with Analog TV
|
| /openbmc/openbmc/poky/meta/recipes-multimedia/libsndfile/libsndfile1/ |
| H A D | noopus.patch | 7 silently. The silent issue is discussed in the link below and hints a patch
11 we previously used back whilst the issue is discussed.
|
| /openbmc/openbmc/.github/ISSUE_TEMPLATE/ |
| H A D | question.md | 14 Questions or feature requests should be discussed on the mailing list or
|
| H A D | bug_report.md | 11 Please note that questions or feature requests should be discussed on the
|
| /openbmc/openbmc/poky/meta/conf/ |
| H A D | abi_version.conf | 4 # that breaks the format and have been previously discussed on the mailing list
|
| /openbmc/qemu/.gitlab/issue_templates/ |
| H A D | feature_request.md | 11 be sent to the mailing list where it can be discussed and developed
|
| /openbmc/openbmc/meta-openembedded/meta-webserver/recipes-httpd/apache2/apache2/ |
| H A D | 0002-apache2-bump-up-the-core-size-limit-if-CoreDumpDirec.patch | 12 Note: upstreaming was discussed but there are competing desires;
|
| /openbmc/openbmc/poky/meta/recipes-graphics/vulkan/vulkan-samples/ |
| H A D | 0001-vulkan-samples-Fix-reproducibility-issue.patch | 21 Upstream-Status: Pending [needs to be discussed upstream]
|
| /openbmc/linux/Documentation/trace/rv/ |
| H A D | monitor_wip.rst | 50 This problem was reported and discussed here:
|
| /openbmc/linux/Documentation/driver-api/pm/ |
| H A D | devices.rst | 522 1. The ``prepare`` phase is discussed in the "Entering System Suspend"
536 discussed earlier, except again that the device should not be put into
544 discussed earlier. The main difference is that its methods can assume
552 7. The ``thaw`` phase is analogous to the ``resume`` phase discussed
556 8. The ``complete`` phase is discussed in the "Leaving System Suspend"
564 9. The ``prepare`` phase is discussed above.
633 4. The ``complete`` phase is discussed above.
651 callbacks discussed above, because the callbacks occur too late or too early.
|
| /openbmc/linux/Documentation/locking/ |
| H A D | seqlock.rst | 95 As discussed at :ref:`seqcount_t`, sequence count write side critical
164 This contains the :ref:`seqcount_t` mechanism earlier discussed, plus an
|
| /openbmc/linux/Documentation/networking/ |
| H A D | bareudp.rst | 7 There are various L3 encapsulation standards using UDP being discussed to
|
| /openbmc/linux/include/crypto/ |
| H A D | aead.h | 33 * pendants discussed in the following. In addition, for the AEAD operation,
354 * and how it is filled with data is discussed with the aead_request_*
375 * and how it is filled with data is discussed with the aead_request_*
|
| /openbmc/linux/Documentation/driver-api/usb/ |
| H A D | writing_musb_glue_layer.rst | 223 driver (line 16). Platform data will be discussed in
276 will be discussed later in :ref:`musb-dev-quirks` and
400 device controller, which will be discussed later in :ref:`musb-dev-quirks`.
552 registers. This issue will be discussed when we get to device quirks in
|
| /openbmc/linux/Documentation/arch/x86/ |
| H A D | tdx.rst | 30 details for these instructions are discussed below.
165 #VE-triggering actions (discussed above) while this block is in place.
|
| /openbmc/linux/tools/memory-model/Documentation/ |
| H A D | ordering.txt | 238 Note that the barriers discussed previously use barrier() or its low-level
488 discussed in the "RMW Ordering Augmentation Barriers" section.
512 primitive can be helpful, as can the various ordering primitives discussed
|
| /openbmc/hiomapd/ |
| H A D | README.md | 17 discussed below. The virtual PNOR functionality is written in C++, and due to
|
| /openbmc/qemu/docs/ |
| H A D | memory-hotplug.txt | 42 discussed earlier:
|
| /openbmc/phosphor-mboxd/ |
| H A D | README.md | 35 discussed below. The virtual PNOR functionality is written in C++, and due to
|
| /openbmc/linux/Documentation/process/ |
| H A D | 1.Intro.rst | 28 have been encountered by other developers are discussed. Some requirements for
130 discussed in greater detail later in this document. Consider:
|
| /openbmc/linux/Documentation/mm/ |
| H A D | active_mm.rst | 25 > discussed on the mailing lists---I just returned from vacation and
|
| /openbmc/linux/Documentation/devicetree/bindings/i2c/ |
| H A D | i2c-mux-gpmux.yaml | 66 The properties of mux-locked and parent-locked multiplexers are discussed
|
| /openbmc/linux/Documentation/driver-api/80211/ |
| H A D | mac80211.rst | 67 Things related to AP mode should be discussed there.
|
| /openbmc/docs/designs/ |
| H A D | bmc-boot-ready.md | 35 There are three options that have been discussed to solve this issue:
|