/openbmc/openbmc/poky/meta/recipes-devtools/binutils/ |
H A D | binutils-2.42.inc | 36 file://0013-Define-alignof-using-_Alignof-when-using-C11-or-newe.patch \
|
/openbmc/openbmc/meta-nuvoton/recipes-phosphor/ipmi/ |
H A D | phosphor-ipmi-flash_%.bbappend | 1 # NPCM8xx is using 0x0850 as PCI device-id.
|
/openbmc/openbmc/poky/meta/files/common-licenses/ |
H A D | Python-2.0 | 7 otherwise using this software ("Python") in source or binary form and 47 8. By copying, installing or otherwise using Python, Licensee 58 Individual or Organization ("Licensee") accessing and otherwise using 96 7. By copying, installing or otherwise using the software, Licensee 106 ("Licensee") accessing and otherwise using Python 1.6.1 software in 121 Python 1.6.1 may be located on the Internet using the following 124 using the following URL: http://hdl.handle.net/1895.22/1013". 165 installing or otherwise using Python 1.6.1, Licensee agrees to be
|
/openbmc/openbmc/poky/meta-selftest/recipes-test/man-db/ |
H A D | man-db_%.bbappend | 1 # This bbappend is used to alter the recipe using the test_recipe.inc file created by tests.
|
/openbmc/openbmc/poky/meta-selftest/recipes-test/m4/ |
H A D | m4_%.bbappend | 1 # This bbappend is used to alter the recipe using the test_recipe.inc file created by tests.
|
/openbmc/openbmc/poky/meta-selftest/recipes-test/xcursor-transparent-theme/ |
H A D | xcursor-transparent-theme_%.bbappend | 1 # This bbappend is used to alter the recipe using the test_recipe.inc file created by tests.
|
/openbmc/openbmc/poky/meta-selftest/recipes-test/systemd-machine-units/ |
H A D | systemd-machine-units_%.bbappend | 1 # This bbappend is used to alter the recipe using the test_recipe.inc file created by tests.
|
/openbmc/openbmc/poky/meta-selftest/recipes-test/base-files/ |
H A D | base-files_%.bbappend | 1 # This bbappend is used to alter the recipe using the test_recipe.inc file created by tests.
|
/openbmc/openbmc/poky/meta-selftest/recipes-test/binutils/ |
H A D | binutils_%.bbappend | 1 # This bbappend is used to alter the recipe using the test_recipe.inc file created by tests.
|
/openbmc/sdbusplus/tools/sdbusplus/templates/ |
H A D | property.aserver.tag.hpp.mako | 7 using value_type = ${p_type};
|
/openbmc/openbmc/poky/meta-selftest/recipes-test/gcc-source/ |
H A D | gcc-source_%.bbappend | 1 # This bbappend is used to alter the recipe using the test_recipe.inc file created by tests.
|
/openbmc/openbmc/poky/meta-selftest/recipes-test/aspell/ |
H A D | aspell_%.bbappend | 1 # This bbappend is used to alter the recipe using the test_recipe.inc file created by tests.
|
/openbmc/openbmc/poky/meta-selftest/recipes-test/perlcross/ |
H A D | perlcross_%.bbappend | 1 # This bbappend is used to alter the recipe using the test_recipe.inc file created by tests.
|
/openbmc/linux/Documentation/devicetree/bindings/gpio/ |
H A D | gpio.txt | 50 Example of a node using GPIOs: 75 using a pin control binding. 81 using a pin control binding. 101 any software using that binding would statically program the device to use 146 in a lot of designs, some using all 32 bits, some using 18 and some using 170 specific devices, using a pin number or the names on the header is fine 307 Both both <pinctrl-base> and <count> must set to 0 when using named pin groups 340 pinctrl1 GPIO ranges are defined using pin numbers whereas the GPIO ranges 341 in pinctrl2 are defined using the pin groups named "foo" and "bar".
|
/openbmc/phosphor-fan-presence/ |
H A D | README.md | 12 applications that control and monitor the cooling of a system using fans. Each 82 each using JSON. 93 supported using the JSON based configuration are listed below:** 108 Controls the fans based on a set of events that are configured using a group of 143 Monitors the presence state of fans using GPIOs, nonzero tach feedbacks, or a 179 \*_Actions to be taken based on the state of fans is only available using a JSON
|
/openbmc/qemu/docs/system/ |
H A D | introduction.rst | 44 emulation can be offloaded from the main QEMU process using either 56 like devices using stdio, files, unix sockets and TCP networking. 65 Manager <https://virt-manager.org/>`_ using the `libvirt framework 85 While the project doesn't want to discourage users from using the 162 We then define the 4 vCPUs using the ``max`` option which gives us all 200 port output (we can switch between the two using :ref:`keys in the
|
H A D | images.rst | 33 disk images by using the ``commit`` monitor command (or C-a s in the 44 writable block device using the ``qcow2`` disk image format. Normally 72 When using the (unrelated) ``-snapshot`` option
|
/openbmc/linux/Documentation/ABI/testing/ |
H A D | debugfs-driver-habanalabs | 45 transaction. This custom interface is needed (instead of using 60 transaction. This custom interface is needed (instead of using 76 This custom interface is needed (instead of using the generic 105 Description: Specify the size of the DMA transaction when using DMA to read 202 value can be set using the debugfs file memory_scrub_val. 209 scrubs the dram using 'memory_scrub' debugfs file and 210 the scrubbing value when using module param 'memory_scrub' 240 This custom interface is needed (instead of using the generic 242 and cannot be accessed using PCI read.
|
/openbmc/linux/Documentation/scheduler/ |
H A D | completion.rst | 14 misuse of locks/semaphores and busy-loops. Any time you think of using 16 you probably want to look into using one of the wait_for_completion*() 19 The advantage of using completions is that they have a well defined, focused 23 is highly efficient using low level scheduler sleep/wakeup facilities. 36 There are three main parts to using completions: 78 Particular care should be taken when using the _timeout() or _killable()/_interruptible() 120 Note that when using completion objects as local variables you must be 125 To emphasise this again: in particular when using some of the waiting API variants 135 exceeds the life time of any helper threads using the completion object,
|
/openbmc/u-boot/doc/ |
H A D | README.iscsi | 27 provides mutual authentication using the CHAP protocol. It typically runs on 44 U-Boot loads the EFI application iPXE snp.efi using the bootefi command. This 52 the mutual authentication using the CHAP protocol. After the authentication iPXE 108 The iSCSI protocol is not encrypted. The traffic could be secured using IPsec 110 the iSCSI traffic from all other network traffic. This can be achieved using a
|
/openbmc/linux/Documentation/admin-guide/cifs/ |
H A D | todo.rst | 26 using Directory Leases, currently only the root file handle is cached longer 36 using compounding but more can be done. In addition we could 37 significantly reduce redundant opens by using deferred close (with 38 handle caching leases) and better using reference counters on file 121 3) Additional performance testing and optimization using iozone and similar -
|
/openbmc/qemu/ |
H A D | README.rst | 9 need for hardware virtualization support. By using dynamic translation, 19 architecture ABI (e.g. the Linux PPC64 ABI) to be run on a host using a 27 It is commonly invoked indirectly via the libvirt library when using 125 $ # making changes to the commits (using 'git rebase', for example) 140 If using QEMU via an operating system vendor pre-built binary package, it
|
/openbmc/linux/tools/perf/Documentation/ |
H A D | tips.txt | 7 Save output of perf stat using: perf stat record <target workload> 9 Search options using a keyword: perf report -h <keyword> 11 List events using substring match: perf list <keyword>
|
/openbmc/linux/Documentation/filesystems/ |
H A D | dnotify.rst | 12 on a directory using a fcntl(2) call and the notifications themselves 13 being delivered using signals. 54 exists in two directories (a and b) then a change to the file using the
|
/openbmc/linux/Documentation/misc-devices/ |
H A D | apds990x.rst | 25 using clear channel only. Lux value and the threshold level on the HW 29 only lux values. Lux value is calculated using information from the both 44 Driver controls chip operational state using pm_runtime framework.
|