| /openbmc/u-boot/arch/arm/mach-sunxi/ |
| H A D | Kconfig | 575 understood by sunxi_name_to_gpio, e.g. PH1 for pin 1 of port H. 583 takes a string in the format understood by sunxi_name_to_gpio, e.g. 609 format understood by sunxi_name_to_gpio_bank, e.g. PH for port H. 645 format understood by sunxi_name_to_gpio, e.g. PH1 for pin 1 of port H. 652 format understood by sunxi_name_to_gpio, e.g. PH1 for pin 1 of port H. 659 format understood by sunxi_name_to_gpio, e.g. PH1 for pin 1 of port H. 667 a string in the format understood by sunxi_name_to_gpio, e.g. 798 format understood by sunxi_name_to_gpio, e.g. PH1 for pin 1 of port H. 830 format understood by sunxi_name_to_gpio, e.g. PH1 for pin 1 of port H. 838 understood by sunxi_name_to_gpio, e.g. PH1 for pin 1 of port H. [all …]
|
| /openbmc/openbmc/meta-raspberrypi/.github/ |
| H A D | PULL_REQUEST_TEMPLATE.md | 2 Please make sure you've read and understood our contributing guidelines.
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | MIT-CMU | 3 …are and/or its associated documentation, you agree that you have read, understood, and will comply…
|
| H A D | W3C-20150513 | 4 By obtaining and/or copying this work, you (the licensee) agree that you have read, understood, and…
|
| H A D | OGC-1.0 | 3 …and/or copying this work, you (the licensee) agree that you have read, understood, and will comply…
|
| H A D | W3C | 5 …and/or copying this work, you (the licensee) agree that you have read, understood, and will comply…
|
| H A D | W3C-19980720 | 5 …and/or copying this work, you (the licensee) agree that you have read, understood, and will comply…
|
| H A D | GPL-3.0-with-GCC-exception | 19 … part of the Compilation Process, since the Compilation Process can be understood as starting with…
|
| H A D | NAIST-2003 | 44 have agreed and understood, that there is no warranty whatsoever for
|
| H A D | CECILL-2.1 | 161 has read and understood it. 252 distribution of the Software, it being understood that the additional 277 from the distribution of the Modified Software, it being understood
|
| H A D | NLOD-2.0 | 37 …e the information as soon as he or she becomes aware of or should have understood that the informa…
|
| H A D | NLOD-1.0 | 36 …e the information as soon as he or she becomes aware of or should have understood that the informa…
|
| H A D | CECILL-1.1 | 117 …viding them with the terms and conditions for access thereto, it being understood that the additio… 128 …viding them with the terms and conditions for access thereto, it being understood that the additio…
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-kernel/oprofile/oprofile/ |
| H A D | acinclude.m4 | 116 AC_MSG_CHECKING([whether malloc attribute is understood]) 121 ],AC_MSG_RESULT([yes]); AC_DEFINE(MALLOC_ATTRIBUTE_OK, 1, [whether malloc attribute is understood])… 129 AC_MSG_CHECKING([whether __builtin_expect is understood]) 544 AC_MSG_CHECKING([whether ${CC} $2 is understood]) 558 AC_MSG_CHECKING([whether ${CXX} $2 is understood])
|
| /openbmc/openbmc/meta-phosphor/recipes-core/os-release/ |
| H A D | os-release.bbappend | 5 # and pasting into another recipe ensure it is understood
|
| /openbmc/openbmc/poky/bitbake/lib/bb/ |
| H A D | remotedata.py | 37 is understood to be managed externally and cannot be released by calling
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/libusbgx/libusbgx/ |
| H A D | 0001-libusbgx-Add-interface-name-for-NCM-Feature-Descript.patch | 15 interface name of the specified string is understood by the
|
| /openbmc/u-boot/drivers/video/ |
| H A D | Kconfig | 350 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H. 369 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H. 379 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H. 389 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H. 401 option takes a string in the format understood by 'name_to_gpio'
|
| /openbmc/u-boot/drivers/net/mscc_eswitch/ |
| H A D | mscc_mac_table.c | 54 * understood by the hardware. in mscc_mac_table_add()
|
| /openbmc/openbmc-test-automation/lib/ |
| H A D | ipmi_client.py | 58 options Any desired options that are understood by
|
| /openbmc/pldm/pldmtool/ |
| H A D | README.md | 207 This is a platform command and the completion code can be understood from
|
| /openbmc/u-boot/include/ |
| H A D | misc.h | 67 * The semantics of "disable" and "enable" should be understood here as
|
| /openbmc/openbmc-test-automation/bin/ |
| H A D | jenkins_funcs.sh | 110 # parameters understood by the robot program
|
| /openbmc/docs/ |
| H A D | meta-layer-guidelines.md | 6 the rules exist, then can be understood and managed by the project. In general,
|
| /openbmc/openbmc/poky/documentation/ref-manual/ |
| H A D | resources.rst | 148 for BSP components. Having a commonly understood structure encourages
|