Searched refs:enough (Results 451 – 475 of 708) sorted by relevance
1...<<11121314151617181920>>...29
/openbmc/linux/Documentation/arch/arm/omap/ |
H A D | dss.rst | 74 and CEA-861 audio infoframe structures. This should be enough to support
|
/openbmc/linux/Documentation/admin-guide/sysctl/ |
H A D | fs.rst | 133 enough for most machines. Actual limit depends on ``RLIMIT_NOFILE``
|
/openbmc/linux/Documentation/RCU/ |
H A D | rcubarrier.rst | 300 Interestingly enough, rcu_barrier() was not originally
|
/openbmc/linux/arch/m68k/ |
H A D | Kconfig.cpu | 342 mantissa and round slightly incorrect, what is more than enough
|
H A D | Kconfig.machine | 430 a system with the RAM based at address 0, and leaving enough room
|
/openbmc/linux/Documentation/staging/ |
H A D | remoteproc.rst | 357 Of course, RSC_VDEV resource entries are only good enough for static
|
/openbmc/linux/Documentation/process/ |
H A D | botching-up-ioctls.rst | 139 will mismatch if you look close enough, but if performance measuring tools
|
/openbmc/docs/designs/ |
H A D | external-sensor.md | 24 enough to measure any physical quantity currently supported by OpenBMC.
|
H A D | redfish-spdm-attestation.md | 265 Step 1 can only be handled by the SPDM daemon. Step 2 is simple enough to be
|
/openbmc/qemu/target/hexagon/idef-parser/ |
H A D | README.rst | 444 regex editing will be enough. 632 point it might be easy enough to go directly to the emitted code for the
|
/openbmc/linux/Documentation/spi/ |
H A D | spi-summary.rst | 11 It's a simple "de facto" standard, not complicated enough to acquire a 312 The board_info should provide enough information to let the system work
|
/openbmc/u-boot/doc/ |
H A D | README.nand | 60 as long as the image is short enough to fit even after skipping the
|
/openbmc/u-boot/arch/arm/dts/ |
H A D | rk3399-gru.dtsi | 317 * of the default voltage, but the speed here should be fast enough and we need
|
/openbmc/linux/Documentation/admin-guide/mm/ |
H A D | nommu-mmap.rst | 257 enough pages to honour a mapping. This is required to support POSIX shared
|
/openbmc/linux/Documentation/admin-guide/ |
H A D | perf-security.rst | 92 CAP_SYS_PTRACE capability is not required and CAP_PERFMON is enough to
|
/openbmc/qemu/docs/system/ |
H A D | tls.rst | 156 a certificate. The client certificate contains enough metadata to
|
/openbmc/linux/Documentation/driver-api/usb/ |
H A D | writing_usb_driver.rst | 309 USB drivers, should provide enough examples to help a beginning author
|
/openbmc/linux/Documentation/input/ |
H A D | input-programming.rst | 39 printk(KERN_ERR "button.c: Not enough memory\n");
|
/openbmc/linux/Documentation/arch/x86/ |
H A D | sgx.rst | 265 on the same machine, the user should reserve enough EPC (by taking out
|
/openbmc/linux/Documentation/scsi/ |
H A D | libsas.rst | 138 phy_mask is 32 bit, this should be enough for now, as I
|
/openbmc/openbmc-test-automation/lib/ |
H A D | fan_utils.robot | 420 [Documentation] Shut down when not enough fans.
|
/openbmc/qemu/docs/devel/migration/ |
H A D | postcopy.rst | 258 RAM if it doesn't have enough hugepages, triggering (b) to fail.
|
/openbmc/libpldm/ |
H A D | CHANGELOG.md | 585 C provides enough foot-guns without us encoding them into library APIs.
|
/openbmc/u-boot/common/ |
H A D | Kconfig | 118 This should be large enough to hold the bootstage stash. A value of 388 unless debugging is enabled, so allow enough for ~10 lines of
|
/openbmc/qemu/docs/devel/ |
H A D | style.rst | 363 target-independent code. It is guaranteed to be large enough to hold a 531 implementation defined behavior (to give compiler authors enough leeway to
|
1...<<11121314151617181920>>...29