| /openbmc/linux/tools/testing/selftests/net/forwarding/ |
| H A D | README | 12 However, a similar kind of flexibility can be achieved by using VRFs and
42 on any Linux box using veth pairs to emulate physical loopbacks.
56 o Code shall be checked using ShellCheck [1] prior to submission.
|
| /openbmc/linux/Documentation/firmware-guide/acpi/ |
| H A D | aml-debugger.rst | 24 The userspace utilities can be built from the kernel source tree using
41 started by using the following commands::
61 The interactive debugger interface can be closed by pressing Ctrl+C or using
|
| /openbmc/u-boot/board/freescale/mpc837xerdb/ |
| H A D | README | 62 Assuming you're using BASH shell:
73 5.0 Download over serial line using Kermit:
87 5.1 Reflash U-Boot Image using U-Boot
|
| /openbmc/u-boot/board/keymile/km83xx/ |
| H A D | README.kmeter1 | 30 Assuming you're using BASH shell:
40 4.0 Download over serial line using Kermit:
63 4.1 Reflash U-Boot Image using U-Boot
|
| /openbmc/linux/Documentation/admin-guide/gpio/ |
| H A D | gpio-mockup.rst | 8 using the standard GPIO character device interface as well as manipulated
9 using the dedicated debugfs directory structure.
11 Creating simulated chips using module params
|
| /openbmc/linux/drivers/w1/masters/ |
| H A D | Kconfig | 13 using Matrox's G400 GPIO pins.
48 Say Y here if you want to communicate with your 1-wire devices using
64 Say Y here if you want support for your 1-wire devices using
|
| /openbmc/linux/Documentation/crypto/ |
| H A D | crypto_engine.rst | 25 using container_of. In addition, the engine knows nothing about your
33 engine using ``crypto_engine_stop()`` and destroy the engine with
57 request by using:
|
| /openbmc/u-boot/board/freescale/mpc8544ds/ |
| H A D | README | 12 using the dip-switch SW10, bit 2.
58 using the FPGA sequencer. When the board restarts, it has the option
59 of using either the current or alternate flash bank as the boot
102 you can download that dtb file using a command like:
|
| /openbmc/phosphor-power/phosphor-regulators/docs/config_file/ |
| H A D | phase_fault_detection.md | 33 error. The error log will include any data previously captured using
43 different device using the "device_id" property. If you need to access multiple
63 "comments": [ "Detect phase fault using I/O expander" ],
69 "comments": [ "Detect N phase fault using I/O expander.",
|
| /openbmc/linux/Documentation/driver-api/mei/ |
| H A D | iamt.rst | 42 local application using the same network interface as a remote application
55 The Intel LMS opens a connection using the Intel MEI driver to the Intel LMS
56 firmware feature using a defined GUID and then communicates with the feature
57 using a protocol called Intel AMT Port Forwarding Protocol (Intel APF protocol).
67 2) Intel AMT Remote configuration using a Local Agent
|
| /openbmc/linux/Documentation/networking/devlink/ |
| H A D | iosm.rst | 34 The ``iosm`` driver implements support for flash update using the
37 It supports updating the device flash using a combined flash image which contains
62 has to be passed to the driver using the devlink param command.
65 need to set the erase_full_flash parameter using devlink param command.
71 image using devlink flash command.
|
| /openbmc/linux/fs/ext4/ |
| H A D | Kconfig | 53 features in the filesystem using tune2fs, or formatting a new
71 compiled kernel size by using one file system driver for
93 If you are not using a security module that requires using
103 using dynamic debug control for mb_debug() / ext_debug() msgs.
|
| /openbmc/linux/Documentation/bpf/ |
| H A D | map_sk_storage.rst | 37 Socket-local storage for ``map`` can be retrieved from socket ``sk`` using the
56 Socket-local storage for ``map`` can be deleted from socket ``sk`` using the
71 socket using the ``bpf_map_update_elem()`` libbpf function. The socket is
94 Socket-local storage for map ``map_fd`` can be retrieved from a socket using
106 Socket-local storage for map ``map_fd`` can be deleted from a socket using the
|
| /openbmc/qemu/docs/system/ |
| H A D | secrets.rst | 11 secure manner, using the ``secret`` object type.
13 At startup this can be done using the ``-object secret,...`` command line
14 argument. At runtime this can be done using the ``object_add`` QMP / HMP
77 will be launched under. If using mandatory access control such as SELinux, then
90 The secret used as the AES key must always be configured using the file based
119 The earlier mechanisms described are platform agnostic. If using QEMU on a Linux
120 host, it is further possible to pass secrets to QEMU using the Linux keyring:
|
| /openbmc/linux/Documentation/devicetree/bindings/sound/ |
| H A D | rt5660.txt | 26 1: using GPIO2 pin as dmic1 data pin
27 2: using IN1P pin as dmic1 data pin
|
| /openbmc/openbmc/meta-openembedded/meta-gnome/recipes-graphics/clutter/ |
| H A D | clutter-gst-3.0.inc | 2 DESCRIPTION = "Clutter-Gst is an integration library for using GStreamer with Clutter. \
4 implements the ClutterGstPlayer interface using playbin."
|
| /openbmc/openbmc/meta-openembedded/meta-oe/dynamic-layers/meta-python/recipes-dbs/mongodb/mongodb/ |
| H A D | 0001-wiredtiger-Avoid-using-off64_t.patch | 4 Subject: [PATCH] wiredtiger: Avoid using off64_t
7 default. Therefore replace using off64_t with off_t
|
| /openbmc/openbmc/poky/meta/recipes-devtools/python/python3/ |
| H A D | 0001-Lib-sysconfig.py-use-prefix-value-from-build-configu.patch | 7 This allows correctly substituting them for target installs using
32 # init function to enable using 'get_config_var' in
|
| /openbmc/linux/drivers/vfio/platform/ |
| H A D | Kconfig | 14 use of platform devices present on the system using the VFIO
25 use of ARM AMBA devices present on the system using the VFIO
|
| /openbmc/linux/Documentation/devicetree/bindings/iommu/ |
| H A D | xen,grant-dma.yaml | 14 are to be used with devices connected to the Xen IOMMU using the "iommus"
16 The binding is required to restrict memory access using Xen grant mappings.
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | xarray.rst | 22 clustered; hashing the object and using the hash as the index will not
35 You must first convert it into an entry using xa_mk_value().
66 You can then set entries using xa_store() and get entries
67 using xa_load(). xa_store will overwrite any entry with the
74 You can conditionally replace an entry at an index by using
113 entries in the XArray using the xa_for_each() iterator.
122 You can enquire whether a mark is set on an entry by using
179 special value which can be turned into an errno using xa_err().
180 If you don't need to know exactly which error occurred, using
432 When iterating over a range of the XArray using xas_for_each()
[all …]
|
| H A D | maple_tree.rst | 31 entries then the users can convert the entries using xa_mk_value() and convert
33 value, then the user can convert the value when using the
39 Pre-allocating of nodes is also supported using the
60 You can then set entries using mtree_store() or mtree_store_range().
72 You can search for an entry from an index upwards by using mt_find().
135 You must take care of your own locking while using the advanced API.
154 You can set entries using mas_store(). mas_store() will overwrite any entry
164 You can walk each entry within a range by using mas_for_each(). If you want
182 must be paused using mas_pause().
184 There are a few extra interfaces provided when using an allocation tree.
|
| /openbmc/openbmc/poky/documentation/sdk-manual/ |
| H A D | appendix-customizing.rst | 8 SDK when using in the standalone installer version.
21 configuration is derived using that build system and the filters shown
67 - If your SDK configuration inherits additional classes using the
76 is set using the "?=" operator. Consequently, you will need to
77 either define the entire list by using the "=" operator, or you
78 will need to append a value using either ":append" or the "+="
158 "meta-mydistro" and you are using the same type of file hierarchy as
172 the installed SDKs to update the installed SDKs by using the
192 #. Publish the SDK using the following command::
228 "meta-mydistro" and you are using the same type of file hierarchy as
[all …]
|
| /openbmc/linux/Documentation/PCI/endpoint/ |
| H A D | pci-ntb-function.rst | 24 communicate with each other using SoC as a bridge.
44 | | | (Configured using NTB Function) | | |
61 Config Region is a construct that is specific to NTB implemented using NTB
63 exchange information with each other using this region. Config Region has
68 scratchpad offset and number of memory windows to the host using this region.
184 using GIC ITS will have the same MSI-X address for all the interrupts.
221 Actual transfer of data between the two hosts will happen using the
293 region and scratchpad region (self scratchpad) using BAR0 of EP controller 1.
295 scratchpad region (peer scratchpad) using BAR1 of EP controller 2. This
337 buffers exposed by HOST2 using memory window1 (MW1). Here doorbell and
|
| /openbmc/linux/Documentation/trace/ |
| H A D | events.rst | 13 using the event tracing infrastructure.
15 Not all tracepoints can be traced using the event tracing system;
646 to the event, using dynamic arrays implies that the piecewise
664 first be created using synth_event_gen_cmd_start() or
672 initialize a dynevent_cmd object using synth_event_cmd_init().
697 populated with more fields. Fields are added one by one using
764 the event for the string, using these pointers.
793 the event for the string, using these pointers.
935 should create and initialize a dynevent_cmd object using
957 populated with more fields. Fields can be added using
[all …]
|