| /openbmc/openbmc/poky/meta/recipes-sato/matchbox-keyboard/files/ |
| H A D | 0001-desktop-file-Hide-the-keyboard-from-app-list.patch | 6 matchbox-keyboard is not a normal app and there's no need to start 8 * when there's no hardware keyboard, the panel applet can be used to 10 * when there is a hardware keyboard, matchbox-keyboard can still be
|
| /openbmc/u-boot/arch/mips/mach-bmips/ |
| H A D | Kconfig | 136 Between its different peripherals there's an integrated switch with 4 147 Between its different peripherals there's an integrated switch with 4 158 Between its different peripherals there's an integrated switch with 4 169 Between its different peripherals there's a BCM5325 switch with 4 180 Between its different peripherals there's an integrated switch with 4 191 Between its different peripherals there's a BCM53115 switch with 5 202 Between its different peripherals there's a BCM5325 switch with 4 213 Between its different peripherals there's a BCM53115 switch with 4 224 Between its different peripherals there's a BCM53125 switch with 5 235 Between its different peripherals there's a BCM5325 switch with 4 [all …]
|
| /openbmc/openbmc/meta-yadro/recipes-phosphor/ipmi/phosphor-ipmi-host/ |
| H A D | 0001-Add-support-for-persistent-only-settings.patch | 40 + // If there are no objects implementing the requested interface, 48 + // On the contrary, if there is just one object, that may mean 52 + // If there's just one object, that's the only kind of setting 59 + // Something must be wrong if there are more objects than expected 66 + // We are here because there were exactly two objects implementing the
|
| /openbmc/u-boot/doc/driver-model/ |
| H A D | serial-howto.txt | 11 forward to convert these, at some point there may come a patch to remove them! 19 - Your board should then build, but will not boot since there will be no serial 40 - update the Makefile there 41 - Add stdout-path to your /chosen device tree node if it is not already there
|
| H A D | i2c-howto.txt | 21 forward to convert these, at some point there may come a patch to remove them! 29 - Your board should then build, but will not work fully since there will be 50 - update the Makefile there 51 - Add stdout-path to your /chosen device tree node if it is not already there
|
| H A D | pci-info.txt | 23 If there is no alias the devices will be numbered sequentially in the device 28 bound to their appropriate driver if available. If there is no driver, then 42 bus, albeit there are justified exceptions. If the compatible string is 96 bus hierarchy: on the root PCI bus, there is a PCIe root port which connects 114 With sandbox we need a device emulator for each device on the bus since there 127 This means that there is a 'sandbox,swap-case' driver at that bus position.
|
| /openbmc/openbmc/poky/meta/recipes-support/libyaml/ |
| H A D | libyaml_0.2.5.bb | 21 CVE_STATUS[CVE-2024-35326] = "upstream-wontfix: Upstream thinks there is no working code that is ex… 22 CVE_STATUS[CVE-2024-35328] = "upstream-wontfix: Upstream thinks there is no working code that is ex…
|
| /openbmc/openbmc/meta-openembedded/meta-webserver/recipes-httpd/apache2/apache2/ |
| H A D | 0002-apache2-bump-up-the-core-size-limit-if-CoreDumpDirec.patch | 12 Note: upstreaming was discussed but there are competing desires; 13 there are portability oddities here too.
|
| /openbmc/openbmc/poky/meta/recipes-devtools/rpm/files/ |
| H A D | 0002-rpmio-rpmglob.c-avoid-using-GLOB_BRACE-if-undefined-.patch | 7 This addresses musl failures; if there is code out there relying on
|
| /openbmc/u-boot/doc/ |
| H A D | README.mpc74xx | 11 the BATs. Currently, there are still problems with the code which 13 anyway). Additionally, there is support for enabling the MMU, which
|
| /openbmc/u-boot/doc/device-tree-bindings/gpio/ |
| H A D | nvidia,tegra20-gpio.txt | 7 there should be 7 interrupts specified, and for Tegra30, there should
|
| /openbmc/openbmc-test-automation/ffdc/docs/ |
| H A D | plugin.md | 172 plugin response if there is any will be written to named file, if 190 - exit_on_error : If there was an error in a plugin stacked, the subsequent 192 - continue_on_error : If there was an error and user declare this directive, 206 This error directive would come into force only if there is an error detected by 210 To go further, there is another directive for plugin to check if the plugin
|
| /openbmc/qemu/docs/specs/ |
| H A D | riscv-aia.rst | 25 - no m-mode is provided, so there is no m-mode APLIC or IMSIC emulation regardless of 28 - with "aia=aplic-imsic" there are two possibilities. If no additional KVM option 29 is provided there will be no APLIC or IMSIC emulation in userspace, and the virtual
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-protocols/openl2tp/openl2tp/ |
| H A D | openl2tp-simplify-gcc-warning-hack.patch | 9 it in place but remove the #if guard since it is only there to ensure that 26 * Is there some C preprocessor magic that could avoid having to do this?
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-graphics/lxdm/lxdm/ |
| H A D | 0001-systemd-lxdm.service-remove-plymouth-quit-conflicts.patch | 7 will hang there as lxdm.service conflicts with plymouth-quit.service 12 Consider there is also After setting for these two services, so
|
| /openbmc/openbmc/meta-openembedded/meta-oe/dynamic-layers/meta-python/recipes-dbs/mongodb/mongodb/ |
| H A D | 0001-Fix-type-mismatch-on-32bit-arches.patch | 9 and there is no matching std::max implementation for mismatching 27 … // On ARM64, the "physical id" field is unpopulated, causing there to be 0 sockets found. In
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/fbset/fbset-modes/ |
| H A D | fb.modes | 1 # By default there is nothing in this file just a reminder to define some
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Control/Service/ |
| H A D | README.md | 21 each instance of the service there will be a D-Bus object 22 `/xyz/openbmc_project/control/service/<service-name>`. For example, if there are 23 two instances of `phosphor-ipmi-net` then there will be two D-Bus objects 45 if the service is disabled, on the next boot it can be started if there are
|
| /openbmc/openbmc/poky/meta/recipes-core/busybox/busybox/ |
| H A D | fail_on_no_media.patch | 31 + * Break if there is no media, no point retrying for all 32 + * fs types since there is no media available
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/libtinyxml/libtinyxml/ |
| H A D | entity-encoding.patch | 25 - // an overflow from happening if there is no ';'. 28 - // However, there is no mechanism (currently) for
|
| /openbmc/qemu/scripts/coccinelle/ |
| H A D | error_propagate_null.cocci | 1 // error_propagate() already ignores local_err==NULL, so there's
|
| /openbmc/qemu/docs/ |
| H A D | bypass-iommu.txt | 6 Traditionally, there is a global switch to enable/disable vIOMMU. All 15 virtual iommu. The bypass_iommu property is valid only when there is a 67 devices might send malicious dma request to virtual machine if there is no 88 so that the devices will by default go through iommu if there exist one.
|
| /openbmc/openbmc/meta-openembedded/meta-perl/recipes-perl/libtest/ |
| H A D | libtest-nowarnings-perl_1.04.bb | 4 adds an extra test that will run when your script ends to check that there \ 5 were no warnings. If there were any warings, the test will give a \\"not ok\\" \
|
| /openbmc/obmc-console/docs/ |
| H A D | mux-support.md | 6 For example, let's say behind `/dev/ttyS0` there are `UART1` and `UART2`, behind 10 Then there will be one obmc-console-server process, and 2 consoles will be 91 Whenever the mux is switched, there should be a way for people reading the log 92 to know that that console was (dis)connected, and at which time. Otherwise there 93 may be confusion as to why there is a gap in the logs.
|
| /openbmc/openbmc/meta-facebook/meta-anacapa/recipes-phosphor/console/ |
| H A D | obmc-console_%.bbappend | 1 # We need the anacapa override here because there is already a machine-type
|