Searched refs:design (Results 1 – 25 of 607) sorted by relevance
12345678910>>...25
| /external/perfetto/docs/ |
| D | toc.md | 60 * [API and ABI surface](design-docs/api-and-abi.md)
61 * [Heapprofd design](design-docs/heapprofd-design.md)
62 * [Heapprofd wire protocol](design-docs/heapprofd-wire-protocol.md)
63 * [Life of a tracing session](design-docs/life-of-a-tracing-session.md)
64 * [Perfetto CI](design-docs/continuous-integration.md)
65 * [ProtoZero](design-docs/protozero.md)
66 * [Security model](design-docs/security-model.md)
|
| /external/arm-trusted-firmware/docs/components/ |
| D | index.rst | 15 romlib-design
17 secure-partition-manager-design
18 xlat-tables-lib-v2-design
|
| /external/arm-trusted-firmware/docs/design/ |
| D | index.rst | 12 firmware-design
13 interrupt-framework-design
15 reset-design
|
| /external/u-boot/arch/arm/mach-tegra/tegra20/ |
| D | Kconfig | 49 source "board/avionic-design/medcom-wide/Kconfig"
51 source "board/avionic-design/plutux/Kconfig"
53 source "board/avionic-design/tec/Kconfig"
|
| /external/u-boot/board/avionic-design/plutux/ |
| D | MAINTAINERS | 2 M: Alban Bedel <alban.bedel@avionic-design.de>
4 F: board/avionic-design/plutux/
|
| /external/u-boot/board/avionic-design/tec/ |
| D | MAINTAINERS | 2 M: Alban Bedel <alban.bedel@avionic-design.de>
4 F: board/avionic-design/tec/
|
| /external/u-boot/board/avionic-design/medcom-wide/ |
| D | MAINTAINERS | 2 M: Alban Bedel <alban.bedel@avionic-design.de>
4 F: board/avionic-design/medcom-wide/
|
| /external/u-boot/board/avionic-design/tec-ng/ |
| D | MAINTAINERS | 2 M: Alban Bedel <alban.bedel@avionic-design.de>
4 F: board/avionic-design/tec-ng/
|
| /external/perfetto/src/profiling/memory/ |
| D | README.md | 8 Googlers, for design doc see: http://goto.google.com/heapprofd-design.
|
| /external/perfetto/docs/design-docs/ |
| D | heapprofd-wire-protocol.md | 15 
17 ## High-level design
18 … not block the client's malloc calls. This allows us to simplify the threading design of heapprofd.
26 
44 ## Detailed design
75 ![shared memory sequence diagram](/docs/images/heapprofd-design/Shared-Memory0.png "shared memory s…
84 ## Advantages over current design
90 ## Disadvantages over current design
|
| /external/swiftshader/third_party/llvm-7.0/llvm/lib/Support/ |
| D | README.txt.system | 9 The software located here, of necessity, has very specific and stringent design
34 To accomplish these requirements, the library has numerous design criteria that
35 must be satisfied. Here's a high level summary of the library's design criteria:
|
| /external/llvm/lib/Support/ |
| D | README.txt.system | 9 The software located here, of necessity, has very specific and stringent design
34 To accomplish these requirements, the library has numerous design criteria that
35 must be satisfied. Here's a high level summary of the library's design criteria:
|
| /external/skqp/platform_tools/android/apps/skar_java/src/main/java/com/google/skar/examples/helloskar/helpers/ |
| D | SnackbarHelper.java | 20 import android.support.design.widget.BaseTransientBottomBar;
21 import android.support.design.widget.Snackbar;
|
| /external/skia/platform_tools/android/apps/skar_java/src/main/java/com/google/skar/examples/helloskar/helpers/ |
| D | SnackbarHelper.java | 20 import android.support.design.widget.BaseTransientBottomBar;
21 import android.support.design.widget.Snackbar;
|
| /external/autotest/client/site_tests/suite_HWQual/ |
| D | control.battery_charge_time | 16 at least 80% of design capacity (battery wear can be 20% at most). Over the
25 # battery must be at least 80% of design capacity
|
| /external/gemmlowp/doc/ |
| D | kernel.md | 6 explained in [design.md](design.md).
11 manually designed for each architecture, etc. The design choice made in gemmlowp
146 As explained in [design.md](design.md), gemmlowp starts by packing blocks of the
172 1. Freely design a GEMM kernel with a freely chosen data layout.
|
| D | packing.md | 5 We assume familiarity with [design.md](design.md) and with the overall 3 stages
20 As explained in [design.md](design.md), the primary purpose of packing is to
26 [design.md](design.md): at the innermost level, one tries to work within
31 Thus it has become standard in GEMM design to describe complicated "Z-order" or
|
| /external/u-boot/board/freescale/mx6memcal/ |
| D | Kconfig | 83 Select the number of chip selects used in your board design
88 Select the type of DDR (DDR3 or LPDDR2) used on your design
93 Select this if your board design uses DDR3.
98 Select this if your board design uses LPDDR2.
|
| /external/llvm/lib/Target/WebAssembly/ |
| D | README.txt | 7 For more information on WebAssembly itself, see the design documents:
8 * https://github.com/WebAssembly/design/blob/master/README.md
12 * https://github.com/WebAssembly/design/blob/master/AstSemantics.md
13 * https://github.com/WebAssembly/design/blob/master/BinaryEncoding.md
|
| /external/clang/docs/ |
| D | LibFormat.rst | 6 on Clang. This documents describes the LibFormat interface and design as well
15 FIXME: Write up design.
|
| /external/antlr/runtime/Perl5/docs/ |
| D | design.pod | 3 design.pod - ANTLR::Runtime Design Document
7 This document describes the design of the C<ANTLR::Runtime> Perl 5 port.
|
| /external/llvm/docs/HistoricalNotes/ |
| D | 2000-12-06-MeetingSummary.txt | 59 of the LLVM when we design it? If so, several design issues should
64 compatibility? For example, we could design the system to encode a
|
| /external/swiftshader/third_party/llvm-7.0/llvm/docs/HistoricalNotes/ |
| D | 2000-12-06-MeetingSummary.txt | 59 of the LLVM when we design it? If so, several design issues should
64 compatibility? For example, we could design the system to encode a
|
| /external/skqp/site/dev/design/ |
| D | index.md | 4 Public design documents for major efforts in Skia
|
| /external/skia/site/dev/ |
| D | METADATA | 6 "design",
|
12345678910>>...25