Home
last modified time | relevance | path

Searched refs:recommended (Results 101 – 125 of 682) sorted by relevance

12345678910>>...28

/openbmc/linux/Documentation/devicetree/bindings/mfd/
H A Dcirrus,madera.yaml157 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 DrcS-default12 # Assume that the BIOS clock is set to UTC time (recommended)
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/iksemel/iksemel/
H A Davoid-obsolete-gnutls-apis.patch13 completely and use the recommended approach of letting gnutls pick a
/openbmc/linux/Documentation/driver-api/firmware/
H A Ddirect-fs-lookup.rst12 It is recommended you keep /lib/firmware paths on your root filesystem,
/openbmc/qemu/docs/system/openrisc/
H A Dvirt.rst6 It is the recommended board type if you simply want to run
/openbmc/linux/drivers/virt/
H A DKconfig22 to reseed the RNG when the VM is cloned. This is highly recommended if
/openbmc/linux/Documentation/devicetree/bindings/sound/
H A Dtas571x.txt4 signals that can be wired up to GPIOs: reset (strongly recommended), and
/openbmc/linux/Documentation/userspace-api/media/v4l/
H A Dmmap.rst109 PROT_READ | PROT_WRITE, /* recommended */
110 MAP_SHARED, /* recommended */
189 PROT_READ | PROT_WRITE, /* recommended */
190 MAP_SHARED, /* recommended */
/openbmc/qemu/docs/
H A Digd-assign.txt45 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 Dvnc-security.rst16 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 Dredfish-tls-user-authentication.md117 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 Di2c-ali1535.rst28 be more consistent with the sequencing recommended by the manufacturer and
/openbmc/linux/Documentation/userspace-api/media/dvb/
H A Dfe-set-voltage.rst49 recommended.
/openbmc/linux/Documentation/devicetree/bindings/input/
H A Dhid-over-i2c.yaml34 - description: Just "hid-over-i2c" alone is allowed, but not recommended.
/openbmc/linux/Documentation/devicetree/bindings/power/supply/
H A Dmaxim,max17042.yaml35 Resistance of rsns resistor in micro Ohms (datasheet-recommended value is 10000).
/openbmc/linux/Documentation/networking/device_drivers/ethernet/microsoft/
H A Dnetvsc.rst35 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 Dbananapi_m2u.rst83 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 Dspeeding-up-build.rst40 recommended as compared to ``ext2`` and ``ext3`` due to ``ext4``
70 system maintainers have recommended that the fastest way to clean up
H A Dvulnerabilities.rst24 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 DKconfig42 recommended that you say N here.
/openbmc/linux/fs/crypto/
H A DKconfig27 # strongly recommended to enable optimized implementations too. It is safe to
/openbmc/openbmc/poky/bitbake/doc/
H A DREADME41 distro. The recommended method to install Sphinx and all required
/openbmc/linux/Documentation/dev-tools/
H A Dktap.rst62 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 Dtwinstall.sh215 has been preserved for your inspection. It is recommended
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/yajl/yajl/
H A DCVE-2022-24795.patch19 A yajl fork mainter recommended calling memory allocation callbacks with

12345678910>>...28