| /openbmc/openbmc/poky/meta/recipes-support/lzo/lzo/ |
| H A D | 0001-Use-memcpy-instead-of-reinventing-it.patch | 6 least in my brief testing with lzop), and knows the alignment
38 + * constant n to be as fast as handwritten code, and knows which architectures
63 + * constant n to be as fast as handwritten code, and knows which architectures
|
| /openbmc/openbmc/poky/meta/recipes-graphics/xorg-driver/ |
| H A D | xf86-input-evdev_2.11.0.bb | 6 devices. It therefore supports all input devices that the kernel knows \
|
| /openbmc/openbmc/meta-openembedded/meta-gnome/recipes-support/libuser/libuser/ |
| H A D | gtkdoc.patch | 4 This is needed so that gtkdocize as run by autopoint knows where the
|
| /openbmc/openbmc/poky/bitbake/lib/prserv/ |
| H A D | serv.py | 84 # Check whether the local server already knows the requested configuration.
109 # Ask upstream whether it knows the checksum
124 # Let's ask the upstream server whether it knows it
137 # whether it knows our new output hash
143 # Upstream knows this output hash, let's store it and use it too.
|
| /openbmc/openbmc/poky/meta/recipes-graphics/xorg-util/util-macros/ |
| H A D | 0001-xorg-macros.m4.in-do-not-run-AC_CANONICAL_HOST-in-ma.patch | 9 it against any architeture it knows.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/websocketpp/websocketpp-0.8.2/ |
| H A D | 855.patch | 19 …1.40.0" "1.41.0" "1.42.0" "1.43.0" "1.44.0" "1.46.1") # todo: someone who knows better spesify the…
|
| /openbmc/u-boot/arch/x86/lib/ |
| H A D | crt0_x86_64_efi.S | 39 * hand-craft a dummy .reloc section so EFI knows it's a relocatable
|
| H A D | crt0_ia32_efi.S | 41 * hand-craft a dummy .reloc section so EFI knows it's a relocatable
|
| /openbmc/openbmc/poky/meta/recipes-kernel/kexec/kexec-tools/ |
| H A D | 0002-purgatory-Pass-r-directly-to-linker.patch | 7 where as gcc knows how to deal with it and passes it down to linker
|
| /openbmc/phosphor-ipmi-blobs/test/ |
| H A D | ipmi_getcount_unittest.cpp | 39 // Calling BmcBlobGetCount with one handler registered that knows of two in TEST()
|
| /openbmc/u-boot/drivers/virtio/ |
| H A D | Kconfig | 7 # where just the guest's device driver "knows" it is running in a virtual
|
| /openbmc/openbmc/poky/meta/classes-recipe/ |
| H A D | multilib_header.bbclass | 11 # A wrapper will be generated for the architecture that knows how to call
|
| /openbmc/openpower-inventory-upload/ |
| H A D | MAINTAINERS | 4 reviewers. You can use the same method to track down who knows a particular
|
| /openbmc/openpower-logging/ |
| D | MAINTAINERS | |
| /openbmc/phosphor-pcie-presence/ |
| D | MAINTAINERS | |
| /openbmc/openpower-sbe-interface/ |
| H A D | MAINTAINERS | 4 reviewers. You can use the same method to track down who knows a particular
|
| /openbmc/google-ipmi-sys/ |
| H A D | MAINTAINERS | 4 reviewers. You can use the same method to track down who knows a particular
|
| /openbmc/pyphosphor/ |
| H A D | MAINTAINERS | 4 reviewers. You can use the same method to track down who knows a particular
|
| /openbmc/openbmc/poky/meta/recipes-core/images/ |
| H A D | core-image-tiny-initramfs.bb | 36 # Modify our init file so the user knows we drop to shell prompt on purpose
|
| /openbmc/u-boot/tools/binman/etype/ |
| H A D | fmap.py | 20 provides flashrom with a list of areas, so it knows what it in the flash.
|
| /openbmc/phosphor-mboxd/ |
| H A D | MAINTAINERS | 4 reviewers. You can use the same method to track down who knows a particular
|
| /openbmc/inarp/ |
| H A D | MAINTAINERS | 4 reviewers. You can use the same method to track down who knows a particular
|
| /openbmc/boost-dbus/ |
| H A D | MAINTAINERS | 4 reviewers. You can use the same method to track down who knows a particular
|
| /openbmc/phosphor-event/ |
| H A D | MAINTAINERS | 4 reviewers. You can use the same method to track down who knows a particular
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Dump/ |
| H A D | Entry.interface.yaml | 58 application which knows the status of the offload operation should set
|