Searched refs:probed (Results 1 – 25 of 32) sorted by relevance
12
33 $(KCONFIG_TOP): generated/Config.in generated/Config.probed34 generated/Config.probed: generated/Config.in
9 /generated/Config.probed
4 source generated/Config.probed
142 probeconfig > generated/Config.probed || rm generated/Config.probed
31 ctx->probed = FALSE; in gst_rtp_packet_rate_ctx_reset()52 if (!ctx->probed) { in gst_rtp_packet_rate_ctx_update()53 ctx->probed = TRUE; in gst_rtp_packet_rate_ctx_update()112 if (time_ms <= 0 || !ctx->probed || ctx->avg_packet_rate == -1) { in gst_rtp_packet_rate_ctx_get_max_dropout()123 if (time_ms <= 0 || !ctx->probed || ctx->avg_packet_rate == -1) { in gst_rtp_packet_rate_ctx_get_max_misorder()
221 gboolean probed; member
226 bool probed:1; member375 bool probed:1; member
3115 if (p->probed) in pa_alsa_path_probe()3117 p->probed = true; in pa_alsa_path_probe()3295 pa_yes_no(p->probed), in pa_alsa_path_dump()5089 if (ps->probed) in pa_alsa_profile_set_probe()5227 ps->probed = true; in pa_alsa_profile_set_probe()5242 pa_yes_no(ps->probed), in pa_alsa_profile_set_dump()
2057 ps->probed = true; in pa_alsa_ucm_add_profile_set()
183 #~ msgid "Your OSS device could not be probed correctly"184 #~ msgstr "Your oss device could not be probed correctly"287 #~ msgstr "Your oss device could not be probed correctly"
206 #~ msgid "Your OSS device could not be probed correctly"
183 #~ msgid "Your OSS device could not be probed correctly"
122 - intel/perf: store the probed i915-perf version
2823 - intel/perf: store the probed i915-perf version
838 #~ msgstr "Your oss device could not be probed correctly"841 #~ msgid "Your OSS device could not be probed correctly"842 #~ msgstr "Your oss device could not be probed correctly"
885 #~ msgid "Your OSS device could not be probed correctly"
858 #~ msgid "Your OSS device could not be probed correctly"
49 Connection to server can also be probed by calling mqtt_client_is_connected(client)
73 msgstr "Your oss device could not be probed correctly"158 msgstr "Your oss device could not be probed correctly"
8 just return MHD_NO after we have probed the request. This way, the connection is closed
46 # Unlike /dev/zero, the MAP_ANON(YMOUS) defines can be probed for.
188 probed and 0 otherwise.
341 function, thus we will just return MHD_NO after we have probed the
5748 the probed caps as it seems that the format enumeration may change17278 interlace mode is not longer probed by v4l2src dues to performance17970 probed list can be directly used for negotation.21835 won't be probed). So let's disable it, in the long term we'll try and22111 visible width/height from G_SELECTION from the probed caps obtained22519 udev-probed = true31998 the known padding from probed caps with the coded size before using them as36182 Also handle the case when a device is probed manually and not through gudev.45297 helper with the probed caps. This allow upstream element taking decision48798 the probed caps. Use integer ranges with steps instead.[all …]