| /external/eclipse-basebuilder/basebuilder-3.6.2/org.eclipse.releng.basebuilder/plugins/ |
| org.eclipse.equinox.p2.console_1.0.200.v20100601.jar | |
| /external/libpcap/ |
| INSTALL.txt | 177 packet timestamps aren't very good. This appears to be due to haphazard
283 timestamps to the resolution of the SS-1 clock (1 us) rather than the
284 lousy 20ms timestamps Sun gives you (tcpdump will print out the full
|
| sf-pcap.c | 100 * Navtel Communcations' format, with nanosecond timestamps,
106 * Normal libpcap format, except for seconds/nanoseconds timestamps,
245 * Will we need to scale the timestamps to match what the
|
| /hardware/ti/omap3/omx/audio/src/openmax_il/aac_enc/inc/ |
| OMX_AacEnc_Utils.h | 594 /** Keep buffer timestamps **/
596 /** Index to arrBufIndex[], used for input buffer timestamps */
598 /** Index to arrBufIndex[], used for output buffer timestamps */
|
| /system/update_engine/ |
| p2p_manager.cc | 17 // This provides access to timestamps with nanosecond resolution in
293 // sequence of elements where newer (high timestamps) elements precede
294 // older ones (low timestamps).
|
| /external/chromium-trace/catapult/third_party/flot/ |
| NEWS.md | [all...] |
| /external/chromium-trace/catapult/telemetry/telemetry/timeline/ |
| trace_event_importer_unittest.py | 516 self.assertEqual([0, 0.01, 0.02], ctr.timestamps)
550 self.assertEqual([0, 0.01], ctr.timestamps)
558 self.assertEqual([0.01, 0.015, 0.018], ctr.timestamps)
566 self.assertEqual([0.02], ctr.timestamps)
573 ctr.timestamps = [0, 1, 2, 3, 4, 5, 6, 7]
614 self.assertEqual(sorted([0, 0.01, 0.02]), sorted(ctr.timestamps))
[all...] |
| thread.py | 99 non-monotonically-decreasing timestamps.
|
| /external/iptables/utils/ |
| pf.os | 92 # - Timestamp - some systems that implement timestamps set them to
172 # functionality, enable or disable timestamps or selective ACK,
239 # Popular cluster config scripts disable timestamps and
257 S4:64:1:52:M*,N,N,S,N,W0: Linux:2.4:ts:Linux 2.4 w/o timestamps
258 S22:64:1:52:M*,N,N,S,N,W0: Linux:2.2:ts:Linux 2.2 w/o timestamps
286 # 16384:64:1:60:M*,N,N,N,N,N,N,T:FreeBSD:4.4:noTS:FreeBSD 4.4 (w/o timestamps)
|
| /docs/source.android.com/src/devices/graphics/ |
| implement.jd | 197 recommended), and the timestamps returned must be extremely accurate.</p>
213 causes. And centralized SurfaceFlinger presentation timestamps show when events
491 VSYNC <li> <em>Feedback</em> - Retire fence signal timestamps from Hardware
|
| /external/clang/include/clang/Serialization/ |
| ASTWriter.h | 125 /// \brief Indicates whether timestamps should be written to the produced
127 /// module cache, where we need the timestamps to determine if the module
594 /// include timestamps in the output file.
[all...] |
| /external/webrtc/talk/app/webrtc/java/jni/ |
| androidmediaencoder_jni.cc | 201 int64_t current_timestamp_us_; // Current frame timestamps in us.
657 // Save input image timestamps for later output
[all...] |
| /ndk/build/tools/ |
| common-build-host-funcs.sh | 684 # The directory that will contain our timestamps
685 BH_STAMPS_DIR=$BH_BUILD_DIR/timestamps
687 fail_panic "Could not create timestamps dir"
|
| /cts/apps/CameraITS/pymodules/its/ |
| caps.py | 206 """Returns whether the camera and motion sensor timestamps for the device
|
| /docs/source.android.com/src/devices/tech/debug/ |
| index.jd | 41 stack. Here is example output (with timestamps and extraneous information removed): </p>
|
| /external/bouncycastle/ |
| import_bouncycastle.sh | 164 echo -n "Restoring timestamps for ${target_dir}... "
|
| /external/chromium-trace/catapult/telemetry/docs/pydoc/ |
| telemetry.web_perf.metrics.rendering_stats.html | 97 <dl><dt><a name="-GetTimestampEventName"><strong>GetTimestampEventName</strong></a>(process)</dt><dd><tt>Returns the name of the events used to count frame timestamps.</tt></dd></dl>
|
| telemetry.web_perf.metrics.smoothness.html | 63 frame_time_discrepancy: The absolute discrepancy of frame timestamps<br>
|
| /external/chromium-trace/catapult/telemetry/telemetry/web_perf/metrics/ |
| rendering_stats.py | 125 """ Returns the name of the events used to count frame timestamps. """
|
| /external/chromium-trace/catapult/third_party/gsutil/gslib/commands/ |
| rsync.py | 201 rsync command, gsutil rsync does not use timestamps to determine if the
203 object's timestamp (hence, timestamps of identical files/objects cannot be
214 width data, such as timestamps).
253 1. The gsutil rsync command doesn't make the destination object's timestamps
[all...] |
| /external/chromium-trace/catapult/tracing/tracing/extras/importer/ |
| battor_importer.html | 284 // Shift by the difference between the explicit sync timestamps.
|
| /external/chromium-trace/catapult/tracing/tracing/importer/ |
| import.html | 165 // need to shift the timestamps of other events.
|
| /external/chromium-trace/catapult/tracing/tracing/model/ |
| thread.html | 101 * Shifts all the timestamps inside this thread forward by the amount
|
| /external/e2fsprogs/misc/ |
| ext4.5.in | 93 extended metadata such as nanosecond timestamps and file creation time,
|
| /external/ltrace/testsuite/ |
| README | 168 timestamps in different format.
|
