/external/arm-trusted-firmware/docs/plat/marvell/armada/ |
D | porting.rst | 1 TF-A Porting Guide for Marvell Platforms 14 - The build system will reuse all files from within the soc directory, and take only the porting 17 Files that require porting are located at ``plat/marvell/armada/<soc family>/<soc>_cust`` directory. 20 Armada-70x0/Armada-80x0 Porting 33 PCIe MEM windows, large memory mapped SPI flash...), then porting of the SoC 56 - Porting: 80 DDR Porting (dram_port.c) 93 Each supported platform of the TF-A has its own DDR porting file called 97 porting description. 101 Comphy Porting (phy-porting-layer.h or phy-default-porting-layer.h) [all …]
|
/external/flac/include/FLAC/ |
D | all.h | 118 * \section porting_guide Porting Guide 120 * Starting with FLAC 1.1.3 a \link porting Porting Guide \endlink 155 /** \defgroup porting Porting Guide for New Versions 158 * version to version. It assists in the porting of code that uses 161 * One simple facility for making porting easier that has been added 189 /** \defgroup porting_1_1_2_to_1_1_3 Porting from FLAC 1.1.2 to 1.1.3 190 * \ingroup porting 193 * This module describes porting from FLAC 1.1.2 to FLAC 1.1.3. 327 /** \defgroup porting_1_1_3_to_1_1_4 Porting from FLAC 1.1.3 to 1.1.4 328 * \ingroup porting [all …]
|
/external/python/cpython3/Doc/howto/ |
D | cporting.rst | 6 Porting Extension Modules to Python 3 9 We recommend the following resources for porting extension modules to Python 3: 13 to Python 3 in general, guides the reader through porting an extension 15 * The `Porting guide`_ from the *py3c* project provides opinionated
|
D | pyporting.rst | 4 Porting Python 2 Code to Python 3 24 For help with porting, you can view the archived python-porting_ mailing list. 70 Keep those key points in mind while you read on about the details of porting 124 Once you have your code well-tested you are ready to begin porting your code to 129 `Porting to Python 3`_ book (which is free online). There is also a handy 137 it's time to update your code! You have a choice between two tools in porting 449 .. _python-porting: https://mail.python.org/pipermail/python-porting/
|
/external/python/six/ |
D | README.rst | 24 For questions about six or porting in general, email the python-porting mailing 25 list: https://mail.python.org/mailman/listinfo/python-porting
|
D | PKG-INFO | 32 For questions about six or porting in general, email the python-porting mailing 33 list: https://mail.python.org/mailman/listinfo/python-porting
|
/external/boringssl/src/ssl/test/ |
D | README.md | 37 For porting the test suite to a different implementation see 38 [PORTING.md](./PORTING.md).
|
/external/python/six/six.egg-info/ |
D | PKG-INFO | 32 For questions about six or porting in general, email the python-porting mailing 33 list: https://mail.python.org/mailman/listinfo/python-porting
|
/external/arm-trusted-firmware/plat/arm/board/juno/include/ |
D | platform_def.h | 23 /* Required platform porting definitions */ 36 * Other platform porting definitions are provided by included headers 40 * Required ARM standard platform porting definitions 230 * Required ARM CSS based platform porting definitions 292 * Required ARM CSS SoC based platform porting definitions
|
/external/deqp/external/openglcts/ |
D | README.md | 22 - [Porting](#porting) 23 - [Common Porting Changes](#common-porting-changes) 24 - [Other Allowable Porting Changes](#other-allowable-porting-changes) 132 Porting to a new platform includes either creating a new target file, or 356 Porting section in OpenGL and OpenGL ES 2.0/3.X Conformance Test Instructions 363 ### Common Porting Changes argument 365 Porting the dEQP framework requires implementation of either `glu::Platform` or, 366 on platforms supporting EGL, the `tcu::EglPlatform` interface. The porting layer 381 Porting typically involves three types of changes: 1053 dependencies. Exact list of directory sub-trees that can be modified during porting.
|
/external/python/cpython3/Misc/ |
D | README | 15 Porting Mini-FAQ on porting to new platforms
|
/external/ImageMagick/www/ |
D | porting.html | 10 <title>ImageMagick - Porting to ImageMagick Version 7</title> 15 <meta name="keywords" content="porting, to, imagemagick, version, 7, image processing software" /> 32 <link href="porting.html" rel="canonical" /> 94 <h1 class="text-center">Porting Guide</h1> 95 …porting.html#imv7">ImageMagick Version 7</a> • <a href="porting.html#hdri">High Dynamic Range Imag… 319 … This polarity matches the masks in version 6 of ImageMagick for ease of porting your workflow. F… 673 …<a href="porting.html#"><img class="d-inline" id="wand" alt="And Now a Touch of Magick" width="16"…
|
/external/libusb/ |
D | README.md | 14 be ported to other operating systems. Please see the [PORTING](PORTING)
|
D | README | 14 be ported to other operating systems. Please see the [PORTING](PORTING)
|
/external/python/cpython2/Doc/howto/ |
D | pyporting.rst | 4 Porting Python 2 Code to Python 3 23 For help with porting, you can email the python-porting_ mailing list with 64 Keep those key points in mind while you read on about the details of porting 118 Once you have your code well-tested you are ready to begin porting your code to 123 `Porting to Python 3`_ book (which is free online). There is also a handy 131 it's time to update your code! You have a choice between two tools in porting 445 .. _python-porting: https://mail.python.org/mailman/listinfo/python-porting
|
/external/python/cpython2/Misc/ |
D | README | 23 Porting Mini-FAQ on porting to new platforms
|
/external/bouncycastle/ |
D | README.android | 8 Porting New Versions of Bouncy Castle. 11 The following steps are recommended for porting new Bouncy Castle versions.
|
/external/arm-trusted-firmware/plat/brcm/board/stingray/include/ |
D | plat_macros.S | 21 * The below required platform porting macro 42 * The below required platform porting macro prints
|
/external/icu/android_icu4j/src/main/java/android/icu/impl/coll/ |
D | UVector32.java | 16 // Keep the API parallel to the C++ version for ease of porting. Port methods only as needed. 17 // If & when we start using something else, we might keep this as a thin wrapper for porting.
|
D | UVector64.java | 16 // Keep the API parallel to the C++ version for ease of porting. Port methods only as needed. 17 // If & when we start using something else, we might keep this as a thin wrapper for porting.
|
/external/boringssl/src/ |
D | README.md | 33 * [PORTING.md](/PORTING.md): how to port OpenSSL-using code to BoringSSL.
|
/external/icu/icu4j/main/classes/collate/src/com/ibm/icu/impl/coll/ |
D | UVector32.java | 15 // Keep the API parallel to the C++ version for ease of porting. Port methods only as needed. 16 // If & when we start using something else, we might keep this as a thin wrapper for porting.
|
D | UVector64.java | 15 // Keep the API parallel to the C++ version for ease of porting. Port methods only as needed. 16 // If & when we start using something else, we might keep this as a thin wrapper for porting.
|
/external/perfetto/test/trace_processor/chrome/ |
D | scroll_jank_general_validation.sql | 64 -- This was found by running the previous metric before porting on the 69 -- This was found by running the previous metric before porting on the
|
/external/arm-trusted-firmware/plat/arm/board/fvp/include/ |
D | platform_def.h | 19 /* Required platform porting definitions */ 30 * Other platform porting definitions are provided by included headers 34 * Required ARM standard platform porting definitions
|