/openbmc/linux/Documentation/devicetree/bindings/mfd/ |
H A D | cirrus,madera.yaml | 157 bindings/gpio.txt. Although optional, it is strongly recommended 170 "mclk1" For the clock supplied on MCLK1, recommended to be a
|
/openbmc/openbmc/poky/meta/recipes-core/sysvinit/sysvinit/ |
H A D | rcS-default | 12 # Assume that the BIOS clock is set to UTC time (recommended)
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/iksemel/iksemel/ |
H A D | avoid-obsolete-gnutls-apis.patch | 13 completely and use the recommended approach of letting gnutls pick a
|
/openbmc/linux/Documentation/driver-api/firmware/ |
H A D | direct-fs-lookup.rst | 12 It is recommended you keep /lib/firmware paths on your root filesystem,
|
/openbmc/qemu/docs/system/openrisc/ |
H A D | virt.rst | 6 It is the recommended board type if you simply want to run
|
/openbmc/linux/drivers/virt/ |
H A D | Kconfig | 22 to reseed the RNG when the VM is cloned. This is highly recommended if
|
/openbmc/linux/Documentation/devicetree/bindings/sound/ |
H A D | tas571x.txt | 4 signals that can be wired up to GPIOs: reset (strongly recommended), and
|
/openbmc/linux/Documentation/userspace-api/media/v4l/ |
H A D | mmap.rst | 109 PROT_READ | PROT_WRITE, /* recommended */ 110 MAP_SHARED, /* recommended */ 189 PROT_READ | PROT_WRITE, /* recommended */ 190 MAP_SHARED, /* recommended */
|
/openbmc/qemu/docs/ |
H A D | igd-assign.txt | 45 has been assigned to a VM. It's therefore generally recommended to prevent 105 region should be created below 4GB (recommended 4KB alignment), sized 109 recommended that firmware should make use of this fw_cfg entry for any
|
/openbmc/qemu/docs/system/ |
H A D | vnc-security.rst | 16 authentication. For this setup it is recommended to restrict it to 59 authentication. The use of x509 certificates is strongly recommended, 175 When not using TLS the recommended configuration is
|
/openbmc/docs/designs/ |
H A D | redfish-tls-user-authentication.md | 117 recommended to use `#CertificateService.ReplaceCertificate` action at 224 credentials according to processing sequence. It is recommended for user to use 236 for chain depth up to 5, but greater ones may work as well). It is recommended
|
/openbmc/linux/Documentation/i2c/busses/ |
H A D | i2c-ali1535.rst | 28 be more consistent with the sequencing recommended by the manufacturer and
|
/openbmc/linux/Documentation/userspace-api/media/dvb/ |
H A D | fe-set-voltage.rst | 49 recommended.
|
/openbmc/linux/Documentation/devicetree/bindings/input/ |
H A D | hid-over-i2c.yaml | 34 - description: Just "hid-over-i2c" alone is allowed, but not recommended.
|
/openbmc/linux/Documentation/devicetree/bindings/power/supply/ |
H A D | maxim,max17042.yaml | 35 Resistance of rsns resistor in micro Ohms (datasheet-recommended value is 10000).
|
/openbmc/linux/Documentation/networking/device_drivers/ethernet/microsoft/ |
H A D | netvsc.rst | 35 hashing. Using L3 hashing is recommended in this case. 112 is not recommended, also not propagated to synthetic NIC, and may be
|
/openbmc/qemu/docs/system/arm/ |
H A D | bananapi_m2u.rst | 83 done with the ``qemu-img`` command. It is recommended to only increase the image size 108 using similar commands as describe above for Linux. Note that it is recommended
|
/openbmc/openbmc/poky/documentation/dev-manual/ |
H A D | speeding-up-build.rst | 40 recommended as compared to ``ext2`` and ``ext3`` due to ``ext4`` 70 system maintainers have recommended that the fastest way to clean up
|
H A D | vulnerabilities.rst | 24 It is recommended to work with Poky and OE-Core upstream maintainers and submit 125 information, it is recommended to fix the information there directly instead of working 193 It is also recommended to add the ``Upstream-Status:`` tag with a link 234 As mentioned previously, if data in the CVE database is wrong, it is recommended 279 When analyzing CVEs, it is recommended to:
|
/openbmc/linux/drivers/pnp/pnpbios/ |
H A D | Kconfig | 42 recommended that you say N here.
|
/openbmc/linux/fs/crypto/ |
H A D | Kconfig | 27 # strongly recommended to enable optimized implementations too. It is safe to
|
/openbmc/openbmc/poky/bitbake/doc/ |
H A D | README | 41 distro. The recommended method to install Sphinx and all required
|
/openbmc/linux/Documentation/dev-tools/ |
H A D | ktap.rst | 62 which case the test plan may be omitted -- it is strongly recommended one is 84 newline. The description is optional, but recommended. 165 kernel output which may help debug the test. It is nevertheless recommended 238 yaml and json in diagnosic message ok not recommended
|
/openbmc/openbmc/meta-security/recipes-ids/tripwire/files/ |
H A D | twinstall.sh | 215 has been preserved for your inspection. It is recommended
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/yajl/yajl/ |
H A D | CVE-2022-24795.patch | 19 A yajl fork mainter recommended calling memory allocation callbacks with
|