| /openbmc/linux/Documentation/devicetree/bindings/iio/adc/ |
| H A D | xilinx-xadc.txt | 23 * "xlnx,zynq-xadc-1.00.a": When using the ZYNQ device
25 * "xlnx,axi-xadc-1.00.a": When using the axi-xadc pcore to
27 * "xlnx,system-management-wiz-1.3": When using the
32 - clocks: When using the ZYNQ this must be the ZYNQ PCAP clock,
33 when using the axi-xadc or the axi-system-management-wizard this must be
60 not using external multiplexer mode the property is ignored.
|
| /openbmc/linux/Documentation/bpf/ |
| H A D | map_queue_stack.rst | 15 helpers. These operations are exposed to userspace applications using
38 An element ``value`` can be added to a queue or stack using the
77 A userspace program can push ``value`` onto a queue or stack using libbpf's
91 using the libbpf ``bpf_map_lookup_elem`` function. The ``key`` parameter must be
102 A userspace program can pop a ``value`` from the head of a queue or stack using
|
| /openbmc/linux/drivers/net/wireless/marvell/libertas_tf/ |
| H A D | Kconfig | 7 A library for Marvell Libertas 8xxx devices using thinfirm.
19 A driver for Marvell Libertas 8388 USB devices using thinfirm.
|
| /openbmc/linux/Documentation/dev-tools/ |
| H A D | kgdb.rst | 391 1. Configure kgdboc at boot using kernel parameters::
411 - Example using minicom 2.2
444 consideration when using the kernel debugger.
446 Quick start for kdb using a keyboard connected console
451 1. Configure kgdboc at boot using kernel parameters::
470 - Example using a laptop keyboard:
484 - Example using a PS/2 101-key keyboard
520 Configure kgdboc at boot using kernel parameters::
542 - Example using minicom 2.2
557 Example (using a directly connected port)::
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/arm/marvell/ |
| H A D | 98dx3236.txt | 11 In addition, boards using the Marvell 98DX3336 SoC shall have the
18 In addition, boards using the Marvell 98DX4251 SoC shall have the
|
| H A D | armada-370-xp.txt | 11 In addition, boards using the Marvell Armada 370 SoC shall have the
18 In addition, boards using the Marvell Armada XP SoC shall have the
|
| H A D | armada-38x.txt | 11 In addition, boards using the Marvell Armada 385 SoC shall have the
18 In addition, boards using the Marvell Armada 388 SoC shall have the
|
| /openbmc/u-boot/board/freescale/mpc8610hpcd/ |
| H A D | README | 40 using the FPGA sequencer. When the board restarts, it has the option
41 of using either the current or alternate flash bank as the boot
72 To manually switch the flash banks using the DIP switch
|
| /openbmc/u-boot/board/freescale/mpc8323erdb/ |
| H A D | README | 16 Assuming you're using BASH (or similar) as your shell:
25 3.1 Reflash U-Boot Image using U-Boot
57 netmask, ethaddr, eth1addr, rootpath (if using NFS root),
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/suitesparse/suitesparse/ |
| H A D | 0001-Preserve-CXXFLAGS-from-environment-in-Mongoose.patch | 23 # using Clang
31 # using GCC
40 # using Intel C++
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-kivy_2.3.0.bb | 12 # Also, if using SDL2 as backend, SDL2 needs to be configured with gles
27 # if using Wayland, let's use pure Wayland (and not XWayland)
28 # so do not build using X11 flag when we detect Wayland
|
| /openbmc/qemu/docs/system/arm/ |
| H A D | orangepi.rst | 46 The Orange Pi PC machine can start using the standard -kernel functionality
83 simply configure the kernel using the sunxi_defconfig configuration:
130 using the orangepi_pc_defconfig. Also see https://buildroot.org for more information.
132 When using an image as an SD card, it must be resized to a power of two. This can be
143 For example, to boot using the Orange Pi PC Debian image on SD card, simply add the -sd
164 a real board would do using the BootROM. Simply pass the selected image via the -sd
185 U-Boot mainline can be build and configured using the orangepi_pc_defconfig
186 using similar commands as describe above for Linux. Note that it is recommended
191 To start U-Boot using the Orange Pi PC machine, provide the
220 Next, unzip the NetBSD image and write the U-Boot binary including SPL using:
[all …]
|
| /openbmc/u-boot/drivers/core/ |
| H A D | Kconfig | 16 suitable malloc() implementation. If you are not using the
18 consider using CONFIG_SYS_MALLOC_SIMPLE. In that case you
29 suitable malloc() implementation. If you are not using the
31 consider using CONFIG_SYS_MALLOC_SIMPLE. In that case you
199 bool "Translate addresses using fdt_translate_address"
204 using the fdt_translate_address() function. This is necessary
205 on some platforms (e.g. MVEBU) using complex "ranges"
214 bool "Translate addresses using fdt_translate_address in SPL"
219 using the fdt_translate_address() function. This is necessary
220 on some platforms (e.g. MVEBU) using complex "ranges"
[all …]
|
| /openbmc/linux/Documentation/networking/ |
| H A D | l2tp.rst | 32 are set up using the Linux kernel API, we're just setting up the L2TP
43 2) Create a tunnel context in the kernel, using information
44 obtained from the peer using the control protocol messages.
49 4) Create a session context in the kernel using information
50 obtained from the peer using the control protocol messages.
69 Or for a tunnel using IPv6 addresses and IP encapsulation::
80 should bind the L2TPIP socket using the locally assigned
85 from peers using L2TPIP, it must open a dedicated L2TPIP
260 Sample userspace code using libmnl_:
366 Userspace may control behavior of the tunnel or session using
[all …]
|
| /openbmc/u-boot/doc/ |
| H A D | README.malta | 3 How to flash using a MIPS Navigator Probe:
6 be unable to flash your Malta using a Navigator Probe.
|
| H A D | README.rockusb | 29 using 0x2207 as its USB verdor id.
50 - rl : Read blocks using LBA
51 - wl : Write blocks using LBA
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-extended/pywbemtools/ |
| H A D | python3-pywbemtools_1.2.1.bb | 1 SUMMARY = "A set of tools using pywbem"
2 DESCRIPTION = "A set of tools using pywbem to communicate with WBEM servers"
|
| /openbmc/u-boot/board/ti/ks2_evm/ |
| H A D | README | 83 Load and Run U-Boot on keystone EVMs using CCS
128 Warning: K2HK_EMAC using MAC address from net device
134 U-Boot image can be flashed to first 512KB of the NOR flash using following
142 EVM using CCS", but using address 0x87000000.
155 U-Boot image can be flashed to first 1024KB of the NAND flash using following
163 using CCS", but using address 0x87000000.
173 Load and Run U-Boot on keystone EVMs using UART download
184 Load and Run U-Boot on K2G EVMs using MMC
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/json-spirit/ |
| H A D | json-spirit_4.08.bb | 3 It is written using the Boost Spirit parser generator. If you are \
4 already using Boost, you can use JSON Spirit without any additional \
|
| /openbmc/qemu/docs/specs/ |
| H A D | ppc-spapr-uv-hcalls.rst | 32 SVM file systems are encrypted using a symmetric key. This key is then
33 wrapped/encrypted using the public key of a trusted system which has the private
35 unwrap/unseal the symmetric key using the system's TPM device or a TPM Resource
39 host system boot. All sensitive in and out values will be encrypted using the
41 any sensitive contents will generally be encrypted using this session key.
|
| /openbmc/webui-vue/docs/guide/coding-standards/ |
| H A D | accessibility.md | 26 Coding the UI using semantic markup is the most important step in creating an
40 built into the CI process, integrated with code editors, and run using browser
43 The OpenBMC Web UI developers should test their development pages using one of
44 the tools listed in the tools section below. If using Chrome, the Lighthouse
46 performance and best practices. If there is an issue that is created when using
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | development-shell.rst | 43 To manually run a specific task using ``devshell``, run the
57 the task just as it would be run using the ``bitbake -c`` command.
68 When you are finished using ``devshell``, exit the shell or close the
73 - It is worth remembering that when using ``devshell`` you need to
75 instead of just using ``gcc``. The same applies to other
|
| /openbmc/linux/drivers/input/ |
| H A D | Kconfig | 57 Say Y here if you are using a driver for an input
70 Say Y here if you are using a driver for an input
118 If you're using a digitizer, or a graphic tablet, and want to use
120 screen resolution you are using to correctly scale the data. If
121 you're not using a digitizer, this value is ignored.
128 If you're using a digitizer, or a graphic tablet, and want to use
130 screen resolution you are using to correctly scale the data. If
131 you're not using a digitizer, this value is ignored.
|
| /openbmc/linux/Documentation/devicetree/bindings/hwlock/ |
| H A D | hwlock.txt | 21 Consumers that require specific hwlock(s) should specify them using the
37 1. Example of a node using a single specific hwlock:
49 2. Example of a node using multiple specific hwlocks:
|
| /openbmc/linux/Documentation/devicetree/bindings/media/xilinx/ |
| H A D | video.txt | 9 tree using bindings documented in this directory. Connections between the IP
13 tree using bindings documented in ./xlnx,video.txt.
21 AXI bus between video IP cores, using its VF code as defined in "AXI4-Stream
|