| /openbmc/docs/architecture/ |
| H A D | optionality.md | 16 These are subsystems that, while widely applicable, a user might choose to
17 remove entire portions of the codebase that might not be needed in that
18 deployment, or not used. This might be done to save binary size in the flash
19 image, or might be done to reduce the security attack surface. These kids of
38 user-facing impact to function, although might do things like improve
56 Many times a system or specific team might want a feature that is intended
57 _only_ for a subset of the OpenBMC audience, and might add OEM parameters to
58 non-standard interfaces, new command sets, or new APIs that might be applicable.
64 disabled. Note, there are cases where _removing_ a feature might cause user
|
| /openbmc/openbmc/poky/bitbake/doc/ |
| H A D | README | 34 Sphinx is written in Python. While it might work with Python2, for
38 Sphinx might be available in your Linux distro packages repositories,
39 however it is not recommend using distro packages, as they might be
|
| /openbmc/qemu/include/hw/misc/ |
| H A D | iotkit-secctl.h | 30 * might provide:
37 * might provide:
46 * might provide:
49 * might provide:
|
| /openbmc/openbmc/meta-security/meta-hardening/recipes-core/initscripts/files/ |
| H A D | mountall.sh | 16 # might want to mount "proc" several times, and mount -v complains
25 # We might have mounted something over /dev, see if /dev/initctl is there.
|
| /openbmc/openbmc/poky/documentation/contributor-guide/ |
| H A D | report-defect.rst | 38 #. Choose a "Documentation change" item for the bug. Fixing a bug might
39 or might not affect the Yocto Project documentation. If you are
61 There are no guarantees about if or when a bug might be worked on since an
|
| /openbmc/boost-dbus/include/dbus/detail/ |
| H A D | async_send_op.hpp | 62 // FIXME Race condition: another thread might have in operator ()()
67 // TODO: does this work, or might it call the notify in operator ()()
68 // function too many times? Might have to use steal_reply in operator ()()
|
| /openbmc/u-boot/include/ |
| H A D | wdt.h | 24 * @flags: Driver specific flags. This might be used to specify
70 * @flags: Driver specific flags. This might be used to specify
96 * reset, where the function is not expected to return, but might not be
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Control/ |
| H A D | VoltageRegulatorMode.interface.yaml | 10 might be "HighPower" or "LowPower" in the case of bipolar power states, or
11 might be something more complex like, "Profile 1", "Profile 2", "Profile 3"
|
| /openbmc/openbmc/poky/meta/recipes-core/initscripts/initscripts-1.0/ |
| H A D | mountall.sh | 20 # might want to mount "proc" several times, and mount -v complains
27 # We might have mounted something over /run; see if
|
| /openbmc/openbmc/poky/meta/recipes-devtools/rust/ |
| H A D | README-rust.md | 34 * Any `-sys` packages your project might need must have RDEPENDs for
39 * Any `-sys` packages your project might need must have RDEPENDs for
|
| /openbmc/u-boot/env/ |
| H A D | nvram.c | 13 * It might not be possible in all cases to use 'memcpy()' to copy
14 * the environment to NVRAM, as the NVRAM might not be mapped into
16 * cases it might be possible to access the NVRAM using a different
|
| /openbmc/qemu/tests/functional/ |
| H A D | test_aarch64_sbsaref_freebsd.py | 53 @skipSlowTest() # Test might timeout due to PAuth emulation
57 @skipSlowTest() # Test might timeout due to PAuth emulation
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | speeding-up-build.rst | 10 If you have multiple CPUs, you might try increasing the default values
81 that you might not need.
107 the static libraries. If so, you might need to exclude them as
|
| H A D | security-subjects.rst | 31 For each layer, you might also look for specific instructions (if any) for
35 Yocto Project/OpenEmbedded, you might want to have a look into the
111 The work of the Security Team might require high confidentiality. Team members
124 They might also request more information.
153 The security policy of the upstream project might include a notification to
|
| /openbmc/u-boot/board/synopsys/hsdk/ |
| H A D | README | 41 - There might be more useful files on that first FAT partition like
45 - Except FAT partition there might be others following the first FAT one
49 - U-Boot might get payload from TFTP server. This might be uImage, rootfs
55 there might be other uses. But note bootROM expects to find a special
|
| /openbmc/u-boot/drivers/ram/ |
| H A D | Kconfig | 17 SPL, enable this option. It might provide a cleaner interface to
26 TPL, enable this option. It might provide a cleaner interface to
|
| /openbmc/openbmc/poky/documentation/ref-manual/ |
| H A D | qa-checks.rst | 66 system used by the software being built, there might be a configure
80 might be a configure option to disable rpath usage completely within
115 go into the ``-dev`` package. This situation might occur if you add
150 not appear in anything but the ``-dbg`` package. This situation might
177 bootloaders, might need to bypass this check. If the file you receive
195 bootloaders, might need to bypass this check. If the file you receive
213 bootloaders, might need to bypass this check. If the file you receive
328 The dependency might have been automatically added because the
330 (e.g. a non-symlink ``.so`` file) or it might have been added
351 The dependency might have been automatically added (because the
[all …]
|
| /openbmc/u-boot/include/linux/byteorder/ |
| H A D | generic.h | 33 * = Linus might want to rename all these macros and files to fit his taste,
39 * = cpu_to_beXX and beXX_to_cpu might some day need to be well
42 * But this might be the case for, say, a port of Linux to 20/21 bit
55 * might like the above to be functions, not macros (why?).
|
| /openbmc/openbmc/poky/meta/recipes-devtools/valgrind/valgrind/ |
| H A D | valgrind-make-ld-XXX.so-strlen-intercept-optional.patch | 7 built with _FORTIFY_SOURCE enabled) the strlen symbol might not be
30 + built with _FORTIFY_SOURCE enabled) the strlen symbol might not be found.
|
| /openbmc/openbmc/poky/documentation/migration-guides/ |
| H A D | migration-general.rst | 7 might need to adapt to in your existing Yocto Project configuration
62 incompatibilities might occur when you upgrade. For example, if your
64 is updated to a newer version, the patch might no longer apply. If
|
| /openbmc/phosphor-power/phosphor-power-sequencer/docs/ |
| H A D | pgood_faults.md | 94 Multiple methods might need to be used on the same rail. For example, the PMBus
95 STATUS_VOUT error bits might be set for a pgood fault after the system powered
96 on, but they might not be set during a power on attempt because the power
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Network/Experimental/ |
| H A D | Bond.interface.yaml | 80 skb_flow_dissect to obtain the header fields which might result
86 skb_flow_dissect to obtain the header fields which might result
|
| /openbmc/phosphor-fan-presence/presence/ |
| H A D | psensor.hpp | 41 * might register signal callbacks or start
53 * might de-register signal callbacks or terminate
|
| /openbmc/qemu/include/hw/arm/ |
| H A D | armsse.h | 70 * might provide:
77 * might provide:
84 * might provide:
87 * might provide:
|
| /openbmc/openbmc/meta-facebook/meta-yosemite4/recipes-phosphor/health/phosphor-health-monitor/ |
| H A D | clean-up-filesystem.service | 2 Description=Clean up files that might full up filesystem
|