Home
last modified time | relevance | path

Searched full:technically (Results 1 – 25 of 106) sorted by relevance

12345

/openbmc/qemu/tcg/ppc/
H A Dtcg-target-has.h30 * While technically Altivec could support V64, it has no 64-bit store
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/libconfuse/files/
H A D0001-only-apply-search-path-logic-to-relative-pathnames.patch11 This is technically an ABI change, but the current behaviour is quite
/openbmc/qemu/scripts/tracetool/format/
H A Dstap.py19 # Technically 'self' is not used by systemtap yet, but
/openbmc/bmcweb/http/
H A Dcomplete_response_fields.hpp92 // Technically preferred could also be NoMatch here, but we'd in completeResponseFields()
/openbmc/qemu/include/io/
H A Dchannel-file.h36 * devices, FIFOs, pipes and plain files. While it is technically
/openbmc/phosphor-ipmi-flash/bmc/firmware-handler/test/
H A Dfirmware_state_notyetstarted_unittest.cpp29 * you transition out of this state (ensuring the above is true). Technically
/openbmc/openbmc/poky/meta/files/common-licenses/
H A DOPL-UK-3.096 copying, adapting and modifying as may be technically
H A DNCGL-UK-2.065 …ithout limitation distributing, copying, adapting, modifying as may be technically necessary to us…
H A DOGL-UK-1.057 …ithout limitation distributing, copying, adapting, modifying as may be technically necessary to us…
H A DOGL-UK-2.058 …ithout limitation distributing, copying, adapting, modifying as may be technically necessary to us…
H A DOGL-UK-3.056 …ithout limitation distributing, copying, adapting, modifying as may be technically necessary to us…
H A DCC-BY-ND-1.028 …. The above rights include the right to make such modifications as are technically necessary to ex…
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/libpwquality/files/
H A D0001-Use-setuptools-instead-of-distutils.patch40 -# Although technically setuptools is not needed for this package, if it's
/openbmc/bmcweb/redfish-core/src/
H A Derror_message_utils.cpp50 // This check could technically be done in the default construction in addMessageToErrorJson()
/openbmc/qemu/include/user/
H A Dsafe-syscall.h81 * which are only technically blocking (ie which we know in practice won't
/openbmc/u-boot/board/freescale/p2041rdb/
H A Dp2041rdb.c41 * technically be set to force the reference clocks to match the in checkboard()
/openbmc/u-boot/board/freescale/t1040qds/
H A Dt1040qds.c64 * technically be set to force the reference clocks to match the in checkboard()
/openbmc/u-boot/board/freescale/corenet_ds/
H A Dcorenet_ds.c52 * technically be set to force the reference clocks to match the in checkboard()
/openbmc/u-boot/include/configs/
H A Dti_armv7_common.h10 * in all cases. While technically true that some of these details are
/openbmc/qemu/hw/alpha/
H A Ddp264.c97 * Technically, PCI-based Alphas shipped with one of three different in clipper_init()
/openbmc/openbmc/poky/meta/classes-recipe/
H A Drust-common.bbclass115 # arguments. Technically the archiver is always one command but
/openbmc/boost-dbus/include/dbus/
H A Delement.hpp239 // Note: technically std::string is an iterable container, so it needs to be
/openbmc/libbej/include/libbej/
H A Dbej_tree.h77 // Points to the last child. Technically we only need the firstChild
/openbmc/u-boot/drivers/remoteproc/
H A Dk3_system_controller.c206 * Note that while technically the K3 system controller starts up
/openbmc/phosphor-pid-control/test/
H A Dpid_json_unittest.cpp20 // This is technically invalid. in TEST()

12345