Home
last modified time | relevance | path

Searched full:ideal (Results 1 – 25 of 160) sorted by relevance

1234567

/freebsd/contrib/ntp/ntpsnmpd/
H A Dntp_snmp.h8 * ideal to rearrange its includes so that our config.h is first, but
/freebsd/sys/dev/videomode/
H A Dvesagtf.c479 /* 18. Find the ideal blanking duty cycle from the blanking duty cycle in vesagtf_mode_params()
482 * [IDEAL DUTY CYCLE] = [C'] - ([M']*[H PERIOD]/1000) in vesagtf_mode_params()
500 print_value(18, "[IDEAL DUTY CYCLE]", ideal_duty_cycle); in vesagtf_mode_params()
507 * [IDEAL DUTY CYCLE] / in vesagtf_mode_params()
508 * (100-[IDEAL DUTY CYCLE]) / in vesagtf_mode_params()
/freebsd/contrib/wpa/src/ap/
H A Dacs.c44 * 3. ideal channel is picked depending on channel width by using adjacent
52 * - Ideal channel may end up overlapping a channel with 40 MHz intolerant BSS
62 * guess about an ideal channel (perhaps CSA could be used to migrate AP to a
65 * when choosing the ideal channel
119 * To find an ideal channel the above data is combined by taking into account
240 * ACS: Ideal channel is 13 (2472 MHz) with total interference factor of 0.0680776
1057 /* Reset puncturing bitmap for the previous ideal in acs_find_ideal_chan_mode()
1147 wpa_printf(MSG_DEBUG, "ACS: Ideal channel is %d (%d MHz) with total interference factor of %Lg", in acs_find_ideal_chan()
1282 wpa_printf(MSG_ERROR, "ACS: Failed to compute ideal channel"); in acs_study()
/freebsd/contrib/libucl/uthash/
H A Duthash.h421 * explanation. First, keep in mind that we're calculating the ideal
424 * Since the ideal chain length is an integer, we want to calculate
683 /* in an ideal situation (all buckets used equally), no bucket would have
684 * more than ceil(#items/#buckets) items. that's the ideal chain length. */
688 * exceeds the ideal chain maxlen. these items pay the penalty for an uneven
689 * hash distribution; reaching them in a chain traversal takes >ideal steps */
/freebsd/crypto/openssl/test/testutil/
H A Dapps_shims.c21 * This isn't ideal but it is what the app's app_malloc() does on failure. in app_malloc()
/freebsd/sys/contrib/device-tree/Bindings/leds/
H A Dleds-ktd2692.txt3 KTD2692 is the ideal power solution for high-power flash LEDs.
H A Dkinetic,ktd2692.yaml13 KTD2692 is the ideal power solution for high-power flash LEDs.
/freebsd/sys/contrib/openzfs/module/os/freebsd/spl/
H A Dspl_vm.c53 * This is not ideal because FILE/LINE used by assertions will not in zfs_vmobject_assert_wlocked()
/freebsd/sys/contrib/device-tree/Bindings/usb/
H A Dti,hd3ss3220.yaml16 Dual Role Port (DRP) making it ideal for any application.
/freebsd/contrib/llvm-project/llvm/lib/MC/
H A DMCValue.cpp24 // FIXME: prints as a number, which isn't ideal. But the meaning will be in print()
/freebsd/sys/cddl/compat/opensolaris/kern/
H A Dopensolaris_vm.c49 * This is not ideal because FILE/LINE used by assertions will not in zfs_vmobject_assert_wlocked()
/freebsd/sys/contrib/device-tree/Bindings/regulator/
H A Drenesas,raa215300.yaml18 ideal for System-On-Module (SOM) applications. A spread spectrum feature
/freebsd/contrib/elftoolchain/common/
H A Duthash.h634 * explanation. First, keep in mind that we're calculating the ideal
637 * Since the ideal chain length is an integer, we want to calculate
882 /* in an ideal situation (all buckets used equally), no bucket would have
883 * more than ceil(#items/#buckets) items. that's the ideal chain length. */
887 * exceeds the ideal chain maxlen. these items pay the penalty for an uneven
888 * hash distribution; reaching them in a chain traversal takes >ideal steps */
/freebsd/share/doc/papers/timecounter/
H A Dtimecounter.ms762 It is obvious from the above description that the ideal hardware
890 Ideal timecounter hardware
921 from the ideal time.
930 ideal noise performance.
932 Now compare this to ``ideal'' timecounter to the normal setup
/freebsd/tools/regression/priv/
H A Dpriv_vfs_generation.c36 * up, which is non-ideal, but better than not testing for a problem.
/freebsd/contrib/llvm-project/llvm/include/llvm/CodeGen/GlobalISel/
H A DGISelWorkList.h48 // - so the ideal place to use this is during the initial prepopulating phase
/freebsd/lib/libsys/
H A Dgetlogin.2105 which is an ideal way of detaching from a controlling terminal and
/freebsd/sys/contrib/device-tree/Bindings/gpu/
H A Darm,mali-utgard.yaml70 # Not ideal as any order and combination are allowed
/freebsd/share/doc/smm/contents/
H A Dcontents.ms187 The Practical Extraction and Report Language is ideal for
/freebsd/tools/test/stress2/misc/
H A Dpfl2.sh48 size=$((2 * 1024 * 1024 * 1024)) # Ideal disk size is 2G
/freebsd/sys/arm/freescale/
H A Dfsl_ocotp.c54 * the load order of devices. In an ideal world this device would be up and
/freebsd/usr.bin/script/
H A Dscript.1289 mode, echo cancelling is far from ideal.
/freebsd/sys/contrib/zstd/programs/
H A DREADME.md250 decompression speed with and without long distance matching on an ideal use
252 `3.5.1`) with a total size of `244889600 B`. This is an ideal use case as there
/freebsd/contrib/llvm-project/compiler-rt/lib/scudo/standalone/
H A Dchunk.h51 // Note that in an ideal world, `State` and `Origin` should be `enum class`, and
/freebsd/contrib/arm-optimized-routines/math/
H A DDir.mk82 # This is not ideal, but allows custom symbols in mathbench to get resolved.

1234567