Searched full:discussed (Results 1 – 25 of 105) sorted by relevance
12345
43 Radio devices may have a couple audio controls (as discussed in46 discussed in :ref:`tuner`) with index number zero to select the radio
9 The video standards discussed so far have been dealing with Analog TV
86 discussed in :ref:`pixfmt`. See also the specification of the
89 discussed in :ref:`pixfmt`. See also the specification of the
41 data in the buffer is discussed in the respective device interface
118 - Raw VBI capture or output parameters. This is discussed in more
50 This problem was reported and discussed here:
7 There are various L3 encapsulation standards using UDP being discussed to
15 The radiotap format is discussed in
50 discussed further below).
95 As discussed at :ref:`seqcount_t`, sequence count write side critical164 This contains the :ref:`seqcount_t` mechanism earlier discussed, plus an
522 1. The ``prepare`` phase is discussed in the "Entering System Suspend"536 discussed earlier, except again that the device should not be put into544 discussed earlier. The main difference is that its methods can assume552 7. The ``thaw`` phase is analogous to the ``resume`` phase discussed556 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.
66 The properties of mux-locked and parent-locked multiplexers are discussed
25 > discussed on the mailing lists---I just returned from vacation and
30 be discussed further in Section :ref:`Nodes <nodes>`79 discussed further in Section :ref:`Zones <zones>`.
67 Things related to AP mode should be discussed there.
70 Some parts of the if_conf should be discussed here instead
223 driver (line 16). Platform data will be discussed in276 will be discussed later in :ref:`musb-dev-quirks` and400 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
28 have been encountered by other developers are discussed. Some requirements for130 discussed in greater detail later in this document. Consider:
189 Patches are posted, discussed, and reviewed and if agreed upon, applied to225 The patches discussed and developed on the list can neither be distributed
57 This capabilities module is discussed further in
93 discussed before. Other data is either ignored or results in validity
112 option discussed below) instead of /dev/etherd/interfaces to limit
38 led to the creation of the extent mapping scheme, discussed below.
7 of these fields is discussed in a separate section below):