Home
last modified time | relevance | path

Searched refs:within (Results 176 – 200 of 1884) sorted by relevance

12345678910>>...76

/openbmc/phosphor-pcie-presence/
H A DMAINTAINERS23 Where REPO_NAME is the name of the repository within the OpenBMC GitHub
24 organization; FILE_PATH is a file path within the repository, possibly with
/openbmc/openpower-sbe-interface/
H A DMAINTAINERS23 Where REPO_NAME is the name of the repository within the OpenBMC GitHub
24 organization; FILE_PATH is a file path within the repository, possibly with
/openbmc/linux/Documentation/devicetree/bindings/soc/qcom/
H A Dqcom,rpm.yaml44 - description: u32 representing offset to the register within the syscon
45 - description: u32 representing the ipc bit within the register
/openbmc/linux/drivers/soc/bcm/
H A DKconfig30 Drivers can be enabled individually within this menu.
41 can be enabled individually within this menu.
/openbmc/linux/LICENSES/dual/
H A DApache-2.078 subsequently incorporated within the Work.
97 lawsuit) alleging that the Work or a Contribution incorporated within
120 include a readable copy of the attribution notices contained within
123 places: within a NOTICE text file distributed as part of the
124 Derivative Works; within the Source form or documentation, if
125 provided along with the Derivative Works; or, within a display
129 add Your own attribution notices within Derivative Works that You
/openbmc/linux/Documentation/devicetree/bindings/cpu/
H A Dcpu-topology.txt42 The ARM/RISC-V CPU topology is defined within the cpu-map node, which is a direct
77 only be defined within the cpu-map node and every core/thread in the
78 system must be defined within the topology. Any other configuration is
88 which are siblings within a single common parent node must be given a unique and
102 Description: must be declared within a cpu-map node, one node
120 Description: must be declared within a cpu-map node, one node
122 clustering within a single physical socket and cluster
/openbmc/u-boot/board/imgtec/boston/
H A Dconfig.mk6 -fill 0x00 -within $< -binary -range-pad 16 \
/openbmc/openbmc/poky/meta/recipes-sato/images/
H A Dcore-image-sato-dev.bb4 within core-image-sato plus a native toolchain, application development and \
/openbmc/openbmc/poky/meta/files/common-licenses/
H A DECL-2.034 …of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
42 …laim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitut…
51 …within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative…
85 identification within third-party archives.
H A DApache-2.0-with-LLVM-exception64 subsequently incorporated within the Work.
84 or a Contribution incorporated within the Work constitutes direct
109 within such NOTICE file, excluding those notices that do not
111 of the following places: within a NOTICE text file distributed
112 as part of the Derivative Works; within the Source form or
114 within a display generated by the Derivative Works, if and
118 notices within Derivative Works that You distribute, alongside
187 identification within third-party archives.
H A DSHL-0.5133 …of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
37 …laim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitut…
47 …within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative…
63 …he same "printed page" as the copyright notice for easier identification within third-party archiv…
H A DSHL-0.533 …of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
37 …laim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitut…
47 …within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative…
62 …he same "printed page" as the copyright notice for easier identification within third-party archiv…
/openbmc/openbmc/poky/documentation/migration-guides/
H A Dmigration-1.8.rst59 the appropriate bluetooth support within a recipe a little easier. If
112 applies both to the cross-compiler used within the build and to the
132 do not provide a working clean target within their make files. If you
134 :term:`CLEANBROKEN` to "1" within the recipe, for example::
155 - :term:`S` now needs to be set to a valid value within a
/openbmc/linux/arch/m68k/fpsp040/
H A Dsatanh.S14 | Accuracy and Monotonicity: The returned result is within 3 ulps in
15 | 64 significant bit, i.e. within 0.5001 ulp to 53 bits if the
H A Dsasin.S13 | Accuracy and Monotonicity: The returned result is within 3 ulps in
14 | 64 significant bit, i.e. within 0.5001 ulp to 53 bits if the
/openbmc/phosphor-mboxd/
H A DMAINTAINERS23 Where REPO_NAME is the name of the repository within the OpenBMC GitHub
24 organization; FILE_PATH is a file path within the repository, possibly with
/openbmc/pyphosphor/
H A DMAINTAINERS23 Where REPO_NAME is the name of the repository within the OpenBMC GitHub
24 organization; FILE_PATH is a file path within the repository, possibly with
/openbmc/inarp/
H A DMAINTAINERS23 Where REPO_NAME is the name of the repository within the OpenBMC GitHub
24 organization; FILE_PATH is a file path within the repository, possibly with
/openbmc/openpower-inventory-upload/
H A DMAINTAINERS23 Where REPO_NAME is the name of the repository within the OpenBMC GitHub
24 organization; FILE_PATH is a file path within the repository, possibly with
/openbmc/openpower-logging/
H A DMAINTAINERS23 Where REPO_NAME is the name of the repository within the OpenBMC GitHub
24 organization; FILE_PATH is a file path within the repository, possibly with
/openbmc/phosphor-event/
H A DMAINTAINERS23 Where REPO_NAME is the name of the repository within the OpenBMC GitHub
24 organization; FILE_PATH is a file path within the repository, possibly with
/openbmc/boost-dbus/
H A DMAINTAINERS23 Where REPO_NAME is the name of the repository within the OpenBMC GitHub
24 organization; FILE_PATH is a file path within the repository, possibly with
/openbmc/google-ipmi-sys/
H A DMAINTAINERS23 Where REPO_NAME is the name of the repository within the OpenBMC GitHub
24 organization; FILE_PATH is a file path within the repository, possibly with
/openbmc/libbej/
H A DMAINTAINERS23 Where REPO_NAME is the name of the repository within the OpenBMC GitHub
24 organization; FILE_PATH is a file path within the repository, possibly with
/openbmc/linux/Documentation/devicetree/bindings/pci/
H A Dti,am65-pci-host.yaml43 - description: pcie_device_id register offset within SYSCON
51 - description: pcie_ctrl register offset within SYSCON

12345678910>>...76