Searched full:typical (Results 1 – 25 of 495) sorted by relevance
12345678910>>...20
38 // Simulate the typical usage of a service in TEST_F()62 // Simulate the typical usage of a service in TEST_F()94 // Simulate the typical usage of a service in TEST_F()124 // Simulate the typical usage of a service in TEST_F()149 // Simulate the typical usage of a service in TEST_F()
17 * or initialization. Typical implementations might register dbus22 * their setup. Typical implementations will forward the call
40 * for detecting presence. Typical implementations52 * state change notifications. Typical implementations
16 For a test / debug build, a typical configuration is
3 …. Supports a moderately wide range of drivers that should boot and be usable on "typical" hardware.
21 For a test / debug build, a typical configuration is
7 that do or do not meet the MSL. Typical reactions might be to prevent a
7 A typical use of this would be to prevent (delay) the power-on of a managed
7 A typical use of this would be to prevent the power-on of a managed host
20 For a test / debug build, a typical configuration is:
18 This is executed by U-Boot when needed early during startup. A typical
18 is executed by U-Boot when needed early during startup. A typical filename
23 A typical filename is 'me.bin'.
70 Typical example of rcw.cfg file:81 Typical example of pbi.cfg file: