Home
last modified time | relevance | path

Searched full:figure (Results 1 – 25 of 153) sorted by relevance

1234567

/Documentation/admin-guide/blockdev/drbd/
Dfigures.rst8 .. kernel-figure:: DRBD-8.3-data-packets.svg
12 .. kernel-figure:: DRBD-data-packets.svg
20 .. kernel-figure:: conn-states-8.dot
24 .. kernel-figure:: disk-states-8.dot
28 .. kernel-figure:: peer-states-8.dot
/Documentation/sphinx/
Dkfigure.py4 scalable figure and image handling
14 handling from the author's POV. Directives like ``kernel-figure`` implement
21 * ``.. kernel-figure``: for figure handling / a ``.. figure::`` replacement
64 Figure = images.Figure variable
138 # figure handling
139 app.add_directive("kernel-figure", KernelFigure)
464 # figure handling
475 class kernel_figure(nodes.figure):
476 """Node for ``kernel-figure`` directive."""
478 class KernelFigure(Figure):
[all …]
Dparallel-wrapper.sh4 # Figure out if we should follow a specific parallelism from the make
/Documentation/devicetree/
Dof_unittest.rst97 Figure 1, describes a generic structure of machine's un-flattened device tree
126 Figure 1: Generic structure of un-flattened device tree
144 in Figure 2 is attached to the live tree described in Figure 1::
155 Figure 2: Example test data tree to be attached to live tree.
164 data node is attached to the live tree above (Figure 1), the final structure is
165 as shown in Figure 3::
200 Figure 3: Live device tree structure after attaching the testcase-data.
204 sibling compared to the earlier structure (Figure 2). After attaching first
/Documentation/translations/zh_CN/doc-guide/
Dsphinx.rst328 如果要添加图片,应该使用 ``kernel-figure`` 和 ``kernel-image`` 指令。例如,
331 .. kernel-figure:: ../../../doc-guide/svg_image.svg
338 .. kernel-figure:: ../../../doc-guide/svg_image.svg
350 .. kernel-figure:: ../../../doc-guide/hello.dot
357 .. kernel-figure:: ../../../doc-guide/hello.dot
385 *render* 指令包含 *figure* 指令中已知的所有选项,以及选项 ``caption`` 。如果
386 ``caption`` 有值,则插入一个 *figure* 节点,若无,则插入一个 *image* 节点。
/Documentation/scsi/scsi_transport_srp/
Dfigures.rst6 .. kernel-figure:: rport_state_diagram.dot
/Documentation/translations/it_IT/doc-guide/
Dsphinx.rst409 Figure ed immagini
412 Se volete aggiungere un'immagine, utilizzate le direttive ``kernel-figure``
416 .. kernel-figure:: ../../../doc-guide/svg_image.svg
423 .. kernel-figure:: ../../../doc-guide/svg_image.svg
428 Le direttive del kernel per figure ed immagini supportano il formato **DOT**,
436 .. kernel-figure:: ../../../doc-guide/hello.dot
443 .. kernel-figure:: ../../../doc-guide/hello.dot
473 La direttiva *render* ha tutte le opzioni della direttiva *figure*, con
475 un nodo *figure* viene aggiunto. Altrimenti verrà aggiunto un nodo *image*.
/Documentation/translations/zh_CN/devicetree/
Dof_unittest.rst101 Figure 1: 未扁平化的设备树的通用结构
127 Figure 2: 将测试数据树附在实时树上的例子。
169 Figure 3: 附加测试案例数据后的实时设备树结构。
/Documentation/userspace-api/media/v4l/
Ddev-raw-vbi.rst220 .. kernel-figure:: vbi_hsync.svg
224 **Figure 4.1. Line synchronization**
228 .. kernel-figure:: vbi_525.svg
232 **Figure 4.2. ITU-R 525 line numbering (M/NTSC and M/PAL)**
236 .. kernel-figure:: vbi_625.svg
240 **Figure 4.3. ITU-R 625 line numbering**
Dselection-api-targets.rst10 .. kernel-figure:: selection.svg
/Documentation/timers/
Dhighres.rst14 changes in the time(r) related Linux subsystems. Figure #1 (p. 2) shows the
35 also figure #2 (OLS slides p. 15)
49 framework, as illustrated in figure #3 (OLS slides p. 18). The architecture
66 Figure #3 (OLS slides p.18) illustrates the transformation.
139 Figure #4 (OLS slides p.20) illustrates the transformation.
205 Figure #5 (OLS slides p.22) illustrates the transformation.
/Documentation/gpu/amdgpu/display/
Ddcn-overview.rst10 .. kernel-figure:: dc_pipeline_overview.svg
142 .. kernel-figure:: pipeline_4k_no_split.svg
164 .. kernel-figure:: pipeline_4k_split.svg
220 .. kernel-figure:: global_sync_vblank.svg
230 .. kernel-figure:: config_example.svg
Dmpo-overview.rst89 .. kernel-figure:: mpo-cursor.svg
126 .. kernel-figure:: single-display-mpo.svg
188 .. kernel-figure:: multi-display-hdcp-mpo.svg
223 .. kernel-figure:: multi-display-hdcp-mpo-less-pipe-ex.svg
/Documentation/doc-guide/
Dsphinx.rst452 If you want to add an image, you should use the ``kernel-figure`` and
453 ``kernel-image`` directives. E.g. to insert a figure with a scalable
456 .. kernel-figure:: svg_image.svg
463 .. kernel-figure:: svg_image.svg
468 The kernel figure (and image) directive supports **DOT** formatted files, see
475 .. kernel-figure:: hello.dot
482 .. kernel-figure:: hello.dot
512 The *render* directive has all the options known from the *figure* directive,
513 plus option ``caption``. If ``caption`` has a value, a *figure* node is
/Documentation/i2c/
Dsummary.rst36 .. kernel-figure:: i2c_bus.svg
61 For the example configuration in the figure above, you will need one driver for
/Documentation/admin-guide/perf/
Darm_dsu_pmu.rst21 The user should refer to the TRM of the product to figure out the supported events
/Documentation/RCU/Design/Expedited-Grace-Periods/
DExpedited-Grace-Periods.rst45 .. kernel-figure:: ExpRCUFlow.svg
119 .. kernel-figure:: ExpSchedFlow.svg
305 .. kernel-figure:: Funnel0.svg
314 .. kernel-figure:: Funnel1.svg
320 .. kernel-figure:: Funnel2.svg
349 .. kernel-figure:: Funnel3.svg
356 .. kernel-figure:: Funnel4.svg
363 .. kernel-figure:: Funnel5.svg
370 .. kernel-figure:: Funnel6.svg
377 .. kernel-figure:: Funnel7.svg
[all …]
/Documentation/RCU/Design/Memory-Ordering/
DTree-RCU-Memory-Ordering.rst245 .. kernel-figure:: rcu_node-lock.svg
276 figure:
278 .. kernel-figure:: TreeRCU-callback-registry.svg
344 .. kernel-figure:: TreeRCU-gp-init-1.svg
366 .. kernel-figure:: TreeRCU-gp-init-2.svg
373 .. kernel-figure:: TreeRCU-gp-init-3.svg
413 .. kernel-figure:: TreeRCU-qs.svg
488 .. kernel-figure:: TreeRCU-dyntick.svg
511 .. kernel-figure:: TreeRCU-hotplug.svg
532 .. kernel-figure:: TreeRCU-gp-fqs.svg
[all …]
/Documentation/devicetree/bindings/display/msm/
Dgpu.yaml30 figure out the chip-id.
36 figure out the gpu-id and patch level.
42 figure out the gpu-id and patch level.
/Documentation/translations/zh_CN/admin-guide/
Dbug-bisect.rst80 - `Using Git bisect to figure out when brokenness was introduced
/Documentation/devicetree/bindings/mfd/
Dmfd.txt26 figure out what child devices exist etc, this should not be used. In the
/Documentation/driver-api/acpi/
Dlinuxized-acpica.rst33 The following figure depicts the Linux ACPI subsystem where the ACPICA
78 Figure 1. Linux ACPI Software Components
130 illustrated in the following figure::
169 Figure 2. ACPICA -> Linux Upstream Process
205 reduced, but there still are several ones and it takes time to figure
/Documentation/hwmon/
Dpc87427.rst61 not. I couldn't find a way to figure out the external sensor data
/Documentation/translations/zh_TW/admin-guide/
Dbug-bisect.rst83 - `Using Git bisect to figure out when brokenness was introduced
/Documentation/userspace-api/media/
Dintro.rst16 .. kernel-figure:: typical_media_device.svg

1234567