/hardware/intel/common/libmix/mix_audio/ |
D | ChangeLog | 3 * Updated version to 0.3.5 and submit for build. 4 * Updated call to Audio Manager to use stream name. 5 * Removed the check to allow decode to be called during PAUSE. 9 * Updated version to 0.3.4 10 * Updated MixCommon dependency to v 0.1.6. 11 * Updated the parameter conversion code for AAC to detect codec value from parameters. 13 * Added methods to replace AAC parameters direct accessing. 25 …* Added aac core operating frequency param for AAC Param object. Needed to configure HE-AAC decode… 30 * Added more utility function to populate param object. 31 * Added MixAudio API to read output configuration (get params) [all …]
|
/hardware/bsp/intel/peripheral/sensors/mraa/doc/ |
D | Doxyfile | 3 # This file describes the settings to be used by the documentation system 37 # The PROJECT_NUMBER tag can be used to enter a project or revision number. This 52 # to the output directory. 56 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path 58 # entered, it will be relative to the location where doxygen was started. If 63 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 4096 sub- 73 # The OUTPUT_LANGUAGE tag is used to specify the language in which all 75 # information to generate all constant output in the proper language. 88 # If the BRIEF_MEMBER_DESC tag is set to YES doxygen will include brief member 90 # documentation (similar to Javadoc). Set to NO to disable this. [all …]
|
/hardware/bsp/intel/peripheral/libupm/doxy/ |
D | Doxyfile.in | 3 # This file describes the settings to be used by the documentation system 37 # The PROJECT_NUMBER tag can be used to enter a project or revision number. This 52 # to the output directory. 56 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path 58 # entered, it will be relative to the location where doxygen was started. If 63 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 4096 sub- 73 # The OUTPUT_LANGUAGE tag is used to specify the language in which all 75 # information to generate all constant output in the proper language. 88 # If the BRIEF_MEMBER_DESC tag is set to YES doxygen will include brief member 90 # documentation (similar to Javadoc). Set to NO to disable this. [all …]
|
D | Doxyfile.java.in | 3 # This file describes the settings to be used by the documentation system 37 # The PROJECT_NUMBER tag can be used to enter a project or revision number. This 52 # to the output directory. 56 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path 58 # entered, it will be relative to the location where doxygen was started. If 63 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 4096 sub- 73 # The OUTPUT_LANGUAGE tag is used to specify the language in which all 75 # information to generate all constant output in the proper language. 88 # If the BRIEF_MEMBER_DESC tag is set to YES doxygen will include brief member 90 # documentation (similar to Javadoc). Set to NO to disable this. [all …]
|
/hardware/bsp/intel/peripheral/libmraa/ |
D | Doxyfile.java.in | 3 # This file describes the settings to be used by the documentation system 37 # The PROJECT_NUMBER tag can be used to enter a project or revision number. This 52 # to the output directory. 56 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path 58 # entered, it will be relative to the location where doxygen was started. If 63 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 4096 sub- 73 # The OUTPUT_LANGUAGE tag is used to specify the language in which all 75 # information to generate all constant output in the proper language. 88 # If the BRIEF_MEMBER_DESC tag is set to YES doxygen will include brief member 90 # documentation (similar to Javadoc). Set to NO to disable this. [all …]
|
D | Doxyfile.in | 3 # This file describes the settings to be used by the documentation system 37 # The PROJECT_NUMBER tag can be used to enter a project or revision number. This 52 # to the output directory. 56 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path 58 # entered, it will be relative to the location where doxygen was started. If 63 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 4096 sub- 73 # The OUTPUT_LANGUAGE tag is used to specify the language in which all 75 # information to generate all constant output in the proper language. 88 # If the BRIEF_MEMBER_DESC tag is set to YES doxygen will include brief member 90 # documentation (similar to Javadoc). Set to NO to disable this. [all …]
|
/hardware/intel/common/omx-components/videocodec/libvpx_internal/libvpx/ |
D | libs.doxy_template | 14 # This file describes the settings to be used by the documentation system 41 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) 43 # If a relative path is entered, it will be relative to the location 48 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 57 # The OUTPUT_LANGUAGE tag is used to specify the language in which all 59 # information to generate all constant output in the proper language. 69 # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will 71 # the file and class documentation (similar to java_doc). 72 # Set to NO to disable this. 76 # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend [all …]
|
D | usage_dx.dox | 5 decoded images. The decoder expects packets to comprise exactly one image 7 application wishes to associate some data with the frame, the 10 spend working on the frame. This is typically used to support adaptive 18 There are two methods for the application to access decoded frame data. Some 20 that allow the application to register a callback to be invoked by the 21 decoder when decoded data becomes available. Decoders are not required to 24 frame-based and slice-based variants. Frame based callbacks conform to the 26 frame has been decoded. Slice based callbacks conform to the signature of 29 macroblock row. However, the number and size of slices to return is 33 examine the rectangles that describe what data is valid to access and what [all …]
|
D | usage.dox | 4 supported codecs. This abstraction allows applications using this SDK to 6 "special casing." This section describes the interface common to all codecs. 9 The following sections are common to all codecs: 25 There are two important data structures to consider in this interface. 29 codec may write into to store details about a single instance of that codec. 30 Most of the context is implementation specific, and thus opaque to the 36 instances are codec specific. That is, the codec to be used for the encoded 42 into the generic interface are dispatched to their codec-specific 43 implementations. Applications \ref MUSTNOT attempt to examine or override 44 this storage, as it contains internal implementation details likely to [all …]
|
/hardware/intel/common/libva/doc/ |
D | Doxyfile | 3 # This file describes the settings to be used by the documentation system 30 # The PROJECT_NUMBER tag can be used to enter a project or revision number. 43 # Doxygen will copy the logo to the output directory. 47 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) 49 # If a relative path is entered, it will be relative to the location 54 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 63 # The OUTPUT_LANGUAGE tag is used to specify the language in which all 65 # information to generate all constant output in the proper language. 76 # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will 78 # the file and class documentation (similar to JavaDoc). [all …]
|
/hardware/bsp/intel/peripheral/libmraa/docs/ |
D | contributing.md | 1 Contributing to libmraa {#contributing} 4 libmraa is an opensource project and we are actively looking for people to help 8 - People to extend the functionality, API with useful functions 11 The recommended method to contribute is to fork on github, and then send pull 12 requests to the main project. You can open issues if you find any bugs/have 15 If you'd rather not use github you are more than welcome to send git formatted 16 patches to brendan.le.foll@intel.com. 23 - Try not to break master. In any commit. 24 - Try to split commits up logically, you will be asked to rebase them if they 26 - Try to stick to the established coding style regardless of your personal [all …]
|
/hardware/intel/common/omx-components/videocodec/libvpx_internal/libvpx/vp9/encoder/x86/ |
D | vp9_variance_impl_mmx.asm | 97 movq mm0, [rax] ; Copy eight bytes to mm0 98 movq mm1, [rbx] ; Copy eight bytes to mm1 102 punpcklbw mm0, mm6 ; unpack to higher prrcision 104 punpckhbw mm2, mm6 ; unpack to higher prrcision 106 psubsw mm0, mm1 ; A-B (low order) to MM0 107 psubsw mm2, mm3 ; A-B (high order) to MM2 116 movq mm1, [rbx] ; Copy eight bytes to mm1 122 movq mm0, [rax] ; Copy eight bytes to mm0 126 punpcklbw mm0, mm6 ; unpack to higher prrcision 128 punpckhbw mm2, mm6 ; unpack to higher prrcision [all …]
|
/hardware/bsp/intel/peripheral/libupm/docs/ |
D | building.md | 4 UPM uses cmake in order to make compilation relatively painless. Cmake runs 5 build out of tree so the recommended way is to clone from git and make a build/ 8 This project depends on libmraa, so that needs to be installed first. Use the 9 following environment variables to configure the paths: 15 UPM will attempt to build all directories inside src/ and they must contain 33 Changing install path from /usr/local to /usr 58 Setting the python library to use: 71 If you intend to turn on all the options and build everything at once (C++, 72 Node, Python and Documentation) you will have to edit the src/doxy2swig.py file 73 and change the line endings from Windows style to Linux format. This has to be [all …]
|
D | porting.md | 4 Porting arduino libraries to libmraa as UPM libraries is usually fairly easy. 9 ### Adding a new module to UPM 19 headers need to be added to module_h and all source files need to be in 32 The easiest way to do this is to have a look at a similar sensor to yours. 35 required to talk to the board's IO. An I2c sensor will create a 43 ### Mapping arduino API to libmraa 45 Your constructor is similar to the setup() function in arduino, you should 54 CMakelists.txt file you have done all that is required to add your sensor to 57 ### Sending your module to us for inclusion in UPM 60 request! We'd love to include your sensor in our repository.
|
D | max31855.md | 4 The Maxim Integrated MAX31855 is a thermocouple amplifier allowing you to read 12 This is a spi module so we will use the mraa spi functions to build our module. 13 First thing to do is to create a tree structure like this in upm/src/max31855: 21 And then an example file to use & test our lib with in upm/examples/max31855.cxx. 26 contain essentially the same thing and are very simple. The only thing to 27 change between the javascript & node.js one is the argument to %module. 31 The %include parameter defines which functions will be available to the 34 either of those args. The upm.i is just a shortcut to include some commonly 59 Then we also need to implement a nice cleanup in our destructor. 63 Then to read data, we will use spi_write_buf which will allow us to write a [all …]
|
/hardware/intel/common/libmix/mix_common/ |
D | INSTALL | 8 unlimited permission to copy, distribute and modify it. 16 instructions specific to this package. 18 The `configure' shell script attempts to guess correct values for 20 those values to create a `Makefile' in each directory of the package. 23 you can run in the future to recreate the current configuration, and a 29 the results of its tests to speed up reconfiguring. Caching is 30 disabled by default to prevent problems with accidental use of stale 33 If you need to do unusual things to compile the package, please try 34 to figure out how `configure' could check whether to do them, and mail 35 diffs or instructions to the address given in the `README' so they can [all …]
|
/hardware/intel/common/omx-components/videocodec/libvpx_internal/libvpx/third_party/googletest/src/ |
D | README | 24 Google Test is designed to have fairly minimal requirements to build 27 effort to support other platforms (e.g. Solaris, AIX, and z/OS). 29 to these platforms, Google Test may have outstanding issues there. If 36 These are the base requirements to build and use Google Test from a source 56 Also, you'll need CMake 2.6.4 or higher if you want to build the 62 We welcome patches. If you plan to contribute a patch, you need to 84 formats are provided, but the only difference is the tools used to 109 To build Google Test and your tests that use it, you need to tell your 110 build system where to find its headers and source files. The exact 111 way to do it depends on which build system you use, and is usually [all …]
|
/hardware/intel/bootstub/ |
D | LICENSE | 14 Everyone is permitted to copy and distribute verbatim copies 19 The licenses for most software are designed to take away your 20 freedom to share and change it. By contrast, the GNU General Public 21 License is intended to guarantee your freedom to share and change free 22 software--to make sure the software is free for all its users. This 23 General Public License applies to most of the Free Software 24 Foundation's software and to any other program whose authors commit to 26 the GNU Library General Public License instead.) You can apply it to 29 When we speak of free software, we are referring to freedom, not 30 price. Our General Public Licenses are designed to make sure that you [all …]
|
/hardware/bsp/intel/peripheral/libupm/docs/images/ |
D | LICENSE_CC_3_0.txt | 50 c. "Distribute" means to make available to the public the original and 75 composition with or without words; a cinematographic work to which are 76 assimilated works expressed by a process analogous to cinematography; 78 lithography; a photographic work to which are assimilated works 79 expressed by a process analogous to photography; a work of applied 81 relative to geography, topography, architecture or science; a 82 performance; a broadcast; a phonogram; a compilation of data to the 84 a variety or circus performer to the extent it is not otherwise 88 respect to the Work, or who has received express permission from the 89 Licensor to exercise rights under this License despite a previous [all …]
|
/hardware/ti/omap3/dspbridge/libbridge/ |
D | COPYING | 6 Everyone is permitted to copy and distribute verbatim copies 15 The licenses for most software are designed to take away your 16 freedom to share and change it. By contrast, the GNU General Public 17 Licenses are intended to guarantee your freedom to share and change 18 free software--to make sure the software is free for all its users. 20 This license, the Lesser General Public License, applies to some 22 Free Software Foundation and other authors who decide to use it. You 25 strategy to use in any particular case, based on the explanations below. 27 When we speak of free software, we are referring to freedom of use, 28 not price. Our General Public Licenses are designed to make sure that [all …]
|
/hardware/bsp/intel/peripheral/libmraa/cmake/modules/ |
D | LICENSE.LGPL | 6 Everyone is permitted to copy and distribute verbatim copies 15 The licenses for most software are designed to take away your 16 freedom to share and change it. By contrast, the GNU General Public 17 Licenses are intended to guarantee your freedom to share and change 18 free software--to make sure the software is free for all its users. 20 This license, the Lesser General Public License, applies to some 22 Free Software Foundation and other authors who decide to use it. You 25 strategy to use in any particular case, based on the explanations below. 27 When we speak of free software, we are referring to freedom of use, 28 not price. Our General Public Licenses are designed to make sure that [all …]
|
/hardware/intel/common/omx-components/videocodec/libvpx_internal/libvpx/vp8/common/x86/ |
D | variance_impl_mmx.asm | 97 movq mm0, [rax] ; Copy eight bytes to mm0 98 movq mm1, [rbx] ; Copy eight bytes to mm1 102 punpcklbw mm0, mm6 ; unpack to higher prrcision 104 punpckhbw mm2, mm6 ; unpack to higher prrcision 106 psubsw mm0, mm1 ; A-B (low order) to MM0 107 psubsw mm2, mm3 ; A-B (high order) to MM2 116 movq mm1, [rbx] ; Copy eight bytes to mm1 122 movq mm0, [rax] ; Copy eight bytes to mm0 126 punpcklbw mm0, mm6 ; unpack to higher prrcision 128 punpckhbw mm2, mm6 ; unpack to higher prrcision [all …]
|
/hardware/intel/common/omx-components/videocodec/libvpx_internal/libvpx/third_party/libwebm/ |
D | RELEASE.TXT | 14 * Added Block::GetOffset() to get a frame's offset in a block 15 * Changed cluster count type from size_t to long 16 * Parsed SeekHead to find cues 18 * Added not to attempt to reparse cues element 21 * Allowed cue points to be loaded incrementally 22 * Implemented to load lazily cue points as they're searched 34 * added this file, RELEASE.TXT, to repository
|
/hardware/broadcom/wlan/bcmdhd/firmware/ |
D | LICENSE.TXT | 5 software is licensed to you under the terms of this Software License 14 product(s) sold by Broadcom with which the Software was designed to be used, 21 1.3. "Software" shall mean that software made available by Broadcom to 26 2.1. License Grants. Subject to the terms and conditions of this Agreement, 27 Broadcom hereby grants to Licensee a non-exclusive, non-transferable, 28 royalty-free license (i) to use and integrate the Software in conjunction 29 with any other software; and (ii) to reproduce and distribute the Software 32 2.2. Restriction on Modification. If and to the extent that the Software is 33 designed to be compliant with any published communications standard 35 Licensee may not make any modifications to the Software that would cause the [all …]
|
/hardware/invensense/6515/libsensors_iio/ |
D | License.txt | 5 software is licensed to you under the terms of this Software License 14 product(s) sold by InvenSense with which the Software was designed to be used, 21 1.3. "Software" shall mean that software made available by InvenSense to 26 2.1. License Grants. Subject to the terms and conditions of this Agreement, 27 InvenSense hereby grants to Licensee a non-exclusive, non-transferable, 28 royalty-free license (i) to use and integrate the Software in conjunction 29 with any other software; and (ii) to reproduce and distribute the Software 32 2.2. Restriction on Modification. If and to the extent that the Software is 33 designed to be compliant with any published communications standard 35 Licensee may not make any modifications to the Software that would cause the [all …]
|