Home	Sort by relevance Sort by last modified time

Full Search Definition Symbol File Path History   | | Help

    Searched refs:conventional (Results 1 - 25 of 29) sorted by null

1 2

/test/vts/script/
run-local.sh	17 PYTHONPATH=$PYTHONPATH:.. python -m vts.testcases.host.light.conventional.SampleLightTest 18 # PYTHONPATH=$PYTHONPATH:.. python -m vts.testcases.host.bluetooth.conventional.SampleBluetoothTest 19 # PYTHONPATH=$PYTHONPATH:.. python -m vts.testcases.fuzz.hal_light.conventional.LightFuzzTest $ANDROID_BUILD_TOP/test/vts/testcases/fuzz/hal_light/conventional/LightFuzzTest.config 21 # PYTHONPATH=$PYTHONPATH:.. python -m vts.testcases.host.camera.conventional.SampleCameraTest 22 # PYTHONPATH=$PYTHONPATH:.. python -m vts.testcases.host.camera.conventional.2_1.SampleCameraV2Test 23 # PYTHONPATH=$PYTHONPATH:.. python -m vts.testcases.host.camera.conventional.3_4.SampleCameraV3Test
setup-local.sh	74 adb push ${ANDROID_BUILD_TOP}/test/vts/specification/hal/conventional /data/local/tmp/spec/hal/conventional
/test/vts/tools/build/tasks/list/
vts_spec_file_list.mk	17 test/vts/specification/hal/conventional/bluetooth/1.0/BluetoothHalV1bt_interface_t.vts \ 18 test/vts/specification/hal/conventional/bluetooth/1.0/BluetoothHalV1.vts \ 19 test/vts/specification/hal/conventional/light/1.0/LightHalV1.vts \ 20 test/vts/specification/hal/conventional/camera/3.4/CameraHalV3.vts \ 21 test/vts/specification/hal/conventional/camera/3.4/CameraHalV3camera3_device_ops_t.vts \ 22 test/vts/specification/hal/conventional/camera/2.1/CameraHalV2hw_device_t.vts \ 23 test/vts/specification/hal/conventional/camera/2.1/CameraHalV2.vts \ 24 test/vts/specification/hal/conventional/wifi/1.0/WifiHalV1.vts \ 25 test/vts/specification/hal/conventional/gps/1.0/GpsHalV1GpsInterface.vts \ 26 test/vts/specification/hal/conventional/gps/1.0/GpsHalV1.vts     [all...]
/test/vts/specification/
Android.mk	20 hal/conventional/camera/2.1/CameraHalV2.vts \ 21 hal/conventional/camera/2.1/CameraHalV2hw_device_t.vts \ 22 hal/conventional/camera/3.4/CameraHalV3.vts \ 23 hal/conventional/camera/3.4/CameraHalV3camera3_device_ops_t.vts \ 24 hal/conventional/gps/1.0/GpsHalV1.vts \ 25 hal/conventional/gps/1.0/GpsHalV1GpsInterface.vts \ 26 hal/conventional/light/1.0/LightHalV1.vts \ 27 hal/conventional/wifi/1.0/WifiHalV1.vts \ 28 hal/conventional/bluetooth/1.0/BluetoothHalV1.vts \ 29 hal/conventional/bluetooth/1.0/BluetoothHalV1bt_interface_t.vts     [all...]
/test/vts/testcases/fuzz/hal_light/conventional/
Android.mk	22 VTS_CONFIG_SRC_DIR := testcases/fuzz/hal_light/conventional
/test/vts/testcases/host/camera/conventional/2_1/
Android.mk	22 VTS_CONFIG_SRC_DIR := testcases/host/camera/conventional/2_1
/test/vts/testcases/host/camera/conventional/3_4/
Android.mk	22 VTS_CONFIG_SRC_DIR := testcases/host/camera/conventional/3_4
/test/vts/testcases/host/light/conventional/
Android.mk	22 VTS_CONFIG_SRC_DIR := testcases/host/light/conventional
/external/mesa3d/docs/specs/
MESA_texture_signed_rgba.spec	150 Otherwise, the conventional core texture environment clamps 153 This implies that the conventional texture environment 157 by this extension because the conventional texture environment
/prebuilts/go/darwin-x86/src/syscall/
route_bsd.go	62 // conventional BSD kernel form. 121 // conventional BSD kernel form.
/prebuilts/go/darwin-x86/src/vendor/golang_org/x/net/route/
address.go	40 // conventional BSD kernel form. 135 // parseKernelInetAddr parses b as an internet address in conventional
/prebuilts/go/linux-x86/src/syscall/
route_bsd.go	62 // conventional BSD kernel form. 121 // conventional BSD kernel form.
/prebuilts/go/linux-x86/src/vendor/golang_org/x/net/route/
address.go	40 // conventional BSD kernel form. 135 // parseKernelInetAddr parses b as an internet address in conventional
/prebuilts/go/darwin-x86/src/go/build/
doc.go	124 // (any other unsatisfied word will work as well, but ``ignore'' is conventional.)
/prebuilts/go/linux-x86/src/go/build/
doc.go	124 // (any other unsatisfied word will work as well, but ``ignore'' is conventional.)
/prebuilts/go/darwin-x86/src/builtin/
builtin.go	252 // The error built-in interface type is the conventional interface for
/prebuilts/go/linux-x86/src/builtin/
builtin.go	252 // The error built-in interface type is the conventional interface for
/prebuilts/go/darwin-x86/src/cmd/cover/
cover.go	778 // A nice long list of statements-per-block, so we can give a conventional
/prebuilts/go/linux-x86/src/cmd/cover/
cover.go	778 // A nice long list of statements-per-block, so we can give a conventional
/prebuilts/go/darwin-x86/src/reflect/
type.go	1143 // If the tag does not have the conventional format, the value 1155 // the tag string. If the tag does not have the conventional format,     [all...]
value.go	[all...]
/prebuilts/go/linux-x86/src/reflect/
type.go	1143 // If the tag does not have the conventional format, the value 1155 // the tag string. If the tag does not have the conventional format,     [all...]
value.go	[all...]
/external/iproute2/doc/
ip-cref.tex	[all...]
/device/linaro/bootloader/edk2/AppPkg/Applications/Python/Python-2.7.2/Lib/pydoc_data/
topics.py	9 'binary': u'\nBinary arithmetic operations\n****************************\n\nThe binary arithmetic operations have the conventional priority\nlevels. Note that some of these operations also apply to certain non-\nnumeric types. Apart from the power operator, there are only two\nlevels, one for multiplicative operators and one for additive\noperators:\n\n m_expr ::= u_expr | m_expr "*" u_expr | m_expr "//" u_expr | m_expr "/" u_expr\n | m_expr "%" u_expr\n a_expr ::= m_expr | a_expr "+" m_expr | a_expr "-" m_expr\n\nThe ``*`` (multiplication) operator yields the product of its\narguments. The arguments must either both be numbers, or one argument\nmust be an integer (plain or long) and the other must be a sequence.\nIn the former case, the numbers are converted to a common type and\nthen multiplied together. In the latter case, sequence repetition is\nperformed; a negative repetition factor yields an empty sequence.\n\nThe ``/`` (division) and ``//`` (floor division) operators yield the\nquotient of their arguments. The numeric arguments are first\nconverted to a common type. Plain or long integer division yields an\ninteger of the same type; the result is that of mathematical division\nwith the \'floor\' function applied to the result. Division by zero\nraises the ``ZeroDivisionError`` exception.\n\nThe ``%`` (modulo) operator yields the remainder from the division of\nthe first argument by the second. The numeric arguments are first\nconverted to a common type. A zero right argument raises the\n``ZeroDivisionError`` exception. The arguments may be floating point\nnumbers, e.g., ``3.14%0.7`` equals ``0.34`` (since ``3.14`` equals\n``4*0.7 + 0.34``.) The modulo operator always yields a result with\nthe same sign as its second operand (or zero); the absolute value of\nthe result is strictly smaller than the absolute value of the second\noperand [2].\n\nThe integer division and modulo operators are connected by the\nfollowing identity: ``x == (x/y)*y + (x%y)``. Integer division and\nmodulo are also connected with the built-in function ``divmod()``:\n``divmod(x, y) == (x/y, x%y)``. These identities don\'t hold for\nfloating point numbers; there similar identities hold approximately\nwhere ``x/y`` is replaced by ``floor(x/y)`` or ``floor(x/y) - 1`` [3].\n\nIn addition to performing the modulo operation on numbers, the ``%``\noperator is also overloaded by string and unicode objects to perform\nstring formatting (also known as interpolation). The syntax for string\nformatting is described in the Python Library Reference, section\n*String Formatting Operations*.\n\nDeprecated since version 2.3: The floor division operator, the modulo\noperator, and the ``divmod()`` function are no longer defined for\ncomplex numbers. Instead, convert to a floating point number using\nthe ``abs()`` function if appropriate.\n\nThe ``+`` (addition) operator yields the sum of its arguments. The\narguments must either both be numbers or both sequences of the same\ntype. In the former case, the numbers are converted to a common type\nand then added together. In the latter case, the sequences are\nconcatenated.\n\nThe ``-`` (subtraction) operator yields the difference of its\narguments. The numeric arguments are first converted to a common\ntype.\n',     [all...]

Completed in 945 milliseconds

1 2