| /OK3568_Linux_fs/yocto/poky/documentation/sdk-manual/ |
| H A D | working-projects.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
7 You can use the SDK toolchain directly with Makefile and Autotools-based
10 Autotools-Based Projects
13 Once you have a suitable :ref:`sdk-manual/intro:the cross-development toolchain`
15 Autotools-based <https://en.wikipedia.org/wiki/GNU_Build_System>`__
20 .. image:: figures/sdk-autotools-flow.png
23 Follow these steps to create a simple Autotools-based "Hello World"
33 1. *Create a Working Directory and Populate It:* Create a clean
34 directory for your project and then make that directory your working
41 After setting up the directory, populate it with files needed for the flow.
[all …]
|
| H A D | using.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
13 For a side-by-side comparison of main features supported for a
15 ":ref:`sdk-manual/intro:introduction`" section.
17 You can use a standard SDK to work on Makefile and Autotools-based
19 ":ref:`sdk-manual/working-projects:using the sdk toolchain directly`" chapter
25 The Standard SDK provides a cross-development toolchain and libraries
34 usage. You can see the directory structure in the
35 ":ref:`sdk-manual/appendix-obtain:installed standard sdk directory structure`"
44 You can download a tarball installer, which includes the pre-built
46 appropriate :yocto_dl:`toolchain </releases/yocto/yocto-&DISTRO;/toolchain/>` directory within
[all …]
|
| H A D | appendix-obtain.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
7 Locating Pre-Built SDK Installers
10 You can use existing, pre-built toolchains by locating and running an
12 method, you select and download an architecture-specific SDK installer
13 and then run the script to hand-install the toolchain.
15 Follow these steps to locate and hand-install the toolchain:
17 1. *Go to the Installers Directory:* Go to
18 :yocto_dl:`/releases/yocto/yocto-&DISTRO;/toolchain/`
22 ``i686`` for 32-bit machines or ``x86_64`` for 64-bit machines).
30 poky-glibc-host_system-core-image-type-arch-toolchain[-ext]-release.sh
[all …]
|
| /OK3568_Linux_fs/buildroot/docs/manual/ |
| H A D | quickstart.txt | 1 // -*- mode:doc; -*-
16 From the buildroot directory, run
18 --------------------
20 --------------------
22 for the original curses-based configurator, or
24 --------------------
26 --------------------
28 for the new curses-based configurator, or
30 --------------------
32 --------------------
[all …]
|
| H A D | adding-packages-cmake.txt | 1 // -*- mode:doc; -*-
4 === Infrastructure for CMake-based packages
6 [[cmake-package-tutorial]]
8 ==== +cmake-package+ tutorial
10 First, let's see how to write a +.mk+ file for a CMake-based package,
13 ------------------------
21 08: LIBFOO_SOURCE = libfoo-$(LIBFOO_VERSION).tar.gz
25 12: LIBFOO_CONF_OPTS = -DBUILD_DEMOS=ON
26 13: LIBFOO_DEPENDENCIES = libglib2 host-pkgconf
28 15: $(eval $(cmake-package))
[all …]
|
| H A D | adding-packages-autotools.txt | 1 // -*- mode:doc; -*-
4 === Infrastructure for autotools-based packages
6 [[autotools-package-tutorial]]
8 ==== +autotools-package+ tutorial
10 First, let's see how to write a +.mk+ file for an autotools-based
13 ------------------------
21 08: LIBFOO_SOURCE = libfoo-$(LIBFOO_VERSION).tar.gz
25 12: LIBFOO_CONF_OPTS = --disable-shared
26 13: LIBFOO_DEPENDENCIES = libglib2 host-pkgconf
28 15: $(eval $(autotools-package))
[all …]
|
| /OK3568_Linux_fs/external/rknpu2/examples/3rdparty/opencv/opencv-linux-armhf/include/opencv2/core/utils/ |
| H A D | filesystem.hpp | 2 // It is subject to the license terms in the LICENSE file found in the top-level directory
22 * @param path input path. Target file/directory should exist.
32 * Result entries are prefixed by base directory path.
34 * @param directory base directory
35 …* @param pattern filter pattern (based on '*'/'?' symbols). Use empty string to disable filtering …
40 CV_EXPORTS void glob(const cv::String& directory, const cv::String& pattern,
47 * @param directory base directory
48 …* @param pattern filter pattern (based on '*'/'?' symbols). Use empty string to disable filtering …
49 * @param[out] result globbing result with relative paths from base directory
53 CV_EXPORTS void glob_relative(const cv::String& directory, const cv::String& pattern,
[all …]
|
| /OK3568_Linux_fs/external/rknpu2/examples/3rdparty/opencv/opencv-linux-aarch64/include/opencv2/core/utils/ |
| H A D | filesystem.hpp | 2 // It is subject to the license terms in the LICENSE file found in the top-level directory
22 * @param path input path. Target file/directory should exist.
32 * Result entries are prefixed by base directory path.
34 * @param directory base directory
35 …* @param pattern filter pattern (based on '*'/'?' symbols). Use empty string to disable filtering …
40 CV_EXPORTS void glob(const cv::String& directory, const cv::String& pattern,
47 * @param directory base directory
48 …* @param pattern filter pattern (based on '*'/'?' symbols). Use empty string to disable filtering …
49 * @param[out] result globbing result with relative paths from base directory
53 CV_EXPORTS void glob_relative(const cv::String& directory, const cv::String& pattern,
[all …]
|
| /OK3568_Linux_fs/external/rknpu2/examples/3rdparty/opencv/OpenCV-android-sdk/sdk/native/jni/include/opencv2/core/utils/ |
| H A D | filesystem.hpp | 2 // It is subject to the license terms in the LICENSE file found in the top-level directory
22 * @param path input path. Target file/directory should exist.
32 * Result entries are prefixed by base directory path.
34 * @param directory base directory
35 …* @param pattern filter pattern (based on '*'/'?' symbols). Use empty string to disable filtering …
40 CV_EXPORTS void glob(const cv::String& directory, const cv::String& pattern,
47 * @param directory base directory
48 …* @param pattern filter pattern (based on '*'/'?' symbols). Use empty string to disable filtering …
49 * @param[out] result globbing result with relative paths from base directory
53 CV_EXPORTS void glob_relative(const cv::String& directory, const cv::String& pattern,
[all …]
|
| /OK3568_Linux_fs/u-boot/doc/device-tree-bindings/net/ |
| H A D | altera_tse.txt | 1 * Altera Triple-Speed Ethernet MAC driver (TSE)
4 - compatible: Should be "altr,tse-1.0" for legacy SGDMA based TSE, and should
5 be "altr,tse-msgdma-1.0" for the preferred MSGDMA based TSE.
6 - reg: Address and length of the register set for the device. It contains
7 the information of registers in the same order as described by reg-names
8 - reg-names: Should contain the reg names
16 - interrupts: Should contain the TSE interrupts and it's mode.
17 - interrupt-names: Should contain the interrupt names
20 - rx-fifo-depth: MAC receive FIFO buffer depth in bytes
21 - tx-fifo-depth: MAC transmit FIFO buffer depth in bytes
[all …]
|
| /OK3568_Linux_fs/yocto/poky/bitbake/lib/bb/fetch2/ |
| H A D | sftp.py | 10 supports key based authentication, not password. This class, unlike
11 the SSH fetcher, does not support fetching a directory tree from the
14 http://tools.ietf.org/html/draft-ietf-secsh-scp-sftp-ssh-uri-04
15 https://www.iana.org/assignments/uri-schemes/prov/sftp
16 https://tools.ietf.org/html/draft-ietf-secsh-filexfer-13
20 ~ (tilde) to specify a path relative to your home directory.
22 user's home directory is not supported.) Note that the tilde must
29 A path relative to your home directory.
42 # Based in part on bb.fetch2.wget:
45 # SPDX-License-Identifier: GPL-2.0-only
[all …]
|
| /OK3568_Linux_fs/yocto/poky/meta-poky/conf/ |
| H A D | local.conf.sample.extended | 13 # Default to setting automatically based on cpu count
19 #PARALLEL_MAKE ?= "-j 4"
21 # Default to setting automatically based on cpu count
22 #PARALLEL_MAKE ?= "-j ${@oe.utils.cpu_count()}"
24 # For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" would
34 # If you want to get an image based on directfb without x11 alter
40 # packages at build time using qemu-native. Disabling it (by setting it to 0)
45 # If GLIBC_SPLIT_LC_PACKAGES is set to a non-zero value, convert
46 # glibc-binary-localedata-XX-YY to be a meta package depending on
47 # glibc-binary-localedata-XX-YY-lc-address and so on. This enables
[all …]
|
| /OK3568_Linux_fs/buildroot/boot/barebox/barebox-aux/ |
| H A D | Config.in | 29 A space-separated list of configuration fragment files,
35 Space-separated list of barebox images which will be copied to
36 the images directory.
39 - barebox.bin for barebox versions older than 2012.10.
40 - barebox-flash-image for later versions.
53 Path to the directory containing the custom barebox
55 based on either the content of the defaultenv or
56 defaultenv-2 directories in the barebox source code, plus
58 barebox devfs format, stored in the images directory, with
59 the same name as the directory name given here.
[all …]
|
| /OK3568_Linux_fs/buildroot/boot/barebox/barebox/ |
| H A D | Config.in | 29 A space-separated list of configuration fragment files,
35 Space-separated list of barebox images which will be copied to
36 the images directory.
39 - barebox.bin for barebox versions older than 2012.10.
40 - barebox-flash-image for later versions.
58 Path to the directory containing the custom barebox
60 based on either the content of the defaultenv or
61 defaultenv-2 directories in the barebox source code, plus
63 barebox devfs format, stored in the images directory, with
64 the same name as the directory name given here.
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/arm/samsung-s3c24xx/ |
| H A D | overview.rst | 8 ------------
10 The Samsung S3C24XX range of ARM9 System-on-Chip CPUs are supported
21 included under the arch/arm/mach-s3c2416 directory. Note, while core
27 -------------
38 ------
41 arch/arm/plat-s3c24xx with headers in include/asm-arm/plat-s3c24xx.
42 This directory should be kept to items shared between the platform
43 code (arch/arm/plat-s3c24xx) and the arch/arm/mach-s3c24* code.
45 Each cpu has a directory with the support files for it, and the
47 in arch/arm/mach-s3c2410 and S3C2440 in arch/arm/mach-s3c2440
[all …]
|
| /OK3568_Linux_fs/kernel/drivers/fsi/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
11 FSI - the FRU Support Interface - is a simple bus for low-level
12 access to POWER-based hardware.
17 bool "Create '/dev/fsi' directory for char devices"
21 located under a common /dev/fsi/ directory. Set to N unless your
29 symlinks in /dev/fsi/by-path when this option is enabled.
32 tristate "GPIO-based FSI master"
47 tristate "FSI master based on Aspeed ColdFire coprocessor"
68 This option enables an FSI based SCOM device driver.
74 This option enables an FSI based SBEFIFO device driver. The SBEFIFO is
[all …]
|
| /OK3568_Linux_fs/yocto/poky/bitbake/lib/toaster/orm/fixtures/ |
| H A D | README | 1 # Fixtures directory
6 In this directory we have the fixtures which are loaded the first time you start Toaster.
9 - settings.xml This Contains Toaster wide settings, such as the default values for
12 - poky.xml This is the default release data for supported poky based setup
14 - oe-core.xml This is the default release data for supported oe-core based setups
18 - custom.xml
21 "custom.xml" in this directory. If present it will be loaded into the database.
30 https://docs.djangoproject.com/en/1.8/ref/django-admin/#django-admin-loaddata
|
| /OK3568_Linux_fs/yocto/poky/documentation/overview-manual/ |
| H A D | development-environment.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
38 Linus Torvalds in 1991. Conversely, a good example of a non-open source
55 system not intended to run the software - the development host.
61 development host. When you have a Mac or Windows-based system, you can
63 `CROPS <https://github.com/crops/poky-container>`__, which leverages
66 environment that is similar to what you see when using a Linux-based
69 ":ref:`dev-manual/start:setting up to use cross platforms (crops)`"
80 ":ref:`dev-manual/start:setting up a native linux host`"
86 - *Command Lines, BitBake, and Shells:* Traditional development in the
89 BitBake, in a command-line environment from a shell on your
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/net/ |
| H A D | altera_tse.txt | 1 * Altera Triple-Speed Ethernet MAC driver (TSE)
4 - compatible: Should be "altr,tse-1.0" for legacy SGDMA based TSE, and should
5 be "altr,tse-msgdma-1.0" for the preferred MSGDMA based TSE.
8 - reg: Address and length of the register set for the device. It contains
9 the information of registers in the same order as described by reg-names
10 - reg-names: Should contain the reg names
18 - interrupts: Should contain the TSE interrupts and it's mode.
19 - interrupt-names: Should contain the interrupt names
22 - rx-fifo-depth: MAC receive FIFO buffer depth in bytes
23 - tx-fifo-depth: MAC transmit FIFO buffer depth in bytes
[all …]
|
| /OK3568_Linux_fs/u-boot/doc/ |
| H A D | README.mxs | 1 Booting U-Boot on a MXS processor
4 This document describes the MXS U-Boot port. This document mostly covers topics
8 -----------
14 into the unix command prompt in U-Boot source code root directory.
16 The (=>) introduces a snipped of code that should by typed into U-Boot command
20 --------
23 2) Compiling U-Boot for a MXS based board
24 3) Installation of U-Boot for a MXS based board to SD card
25 4) Installation of U-Boot into NAND flash on a MX28 based board
26 5) Installation of U-Boot into SPI NOR flash on a MX28 based board
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/ |
| H A D | README.rst | 11 --------------
14 Linus Torvalds with assistance from a loosely-knit team of hackers across
17 It has all the features you would expect in a modern fully-fledged Unix,
19 loading, shared copy-on-write executables, proper memory management,
22 It is distributed under the GNU General Public License v2 - see the
26 -----------------------------
28 Although originally developed first for 32-bit x86-based PCs (386 or higher),
31 IBM S/390, MIPS, HP PA-RISC, Intel IA-64, DEC VAX, AMD x86-64 Xtensa, and
34 Linux is easily portable to most general-purpose 32- or 64-bit architectures
40 userspace application - this is called UserMode Linux (UML).
[all …]
|
| /OK3568_Linux_fs/yocto/poky/documentation/dev-manual/ |
| H A D | start.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
10 host <dev-manual/start:preparing the build host>`, how to locate
25 you get the results you want. The procedure is high-level and presents
41 - *Application Developer:* This type of developer does application
44 - *Core System Developer:* This type of developer works on the
47 - *Build Engineer:* This type of developer manages Autobuilders and
51 - *Test Engineer:* This type of developer creates and manages
55 2. *Gather the Hardware:* Based on the size and make-up of the team,
59 six-core Xeons with 24 Gbytes of RAM and plenty of disk space). You
70 understand the hardware involved and the make-up of the team, you
[all …]
|
| H A D | qemu.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
34 - `QEMU Website <https://wiki.qemu.org/Main_Page>`__\ *:* The official
37 - `Documentation <https://wiki.qemu.org/Manual>`__\ *:* The QEMU user
49 (SDK). See ":ref:`sdk-manual/intro:the qemu emulator`" section in the
56 - If you cloned the ``poky`` repository or you downloaded and
58 environment script (i.e. :ref:`structure-core-script`)::
61 $ source oe-init-build-env
63 - If you installed a cross-toolchain, you can run the script that
65 the initialization script from the default ``poky_sdk`` directory::
67 . poky_sdk/environment-setup-core2-64-poky-linux
[all …]
|
| /OK3568_Linux_fs/yocto/poky/documentation/ref-manual/ |
| H A D | terms.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
23 similarly-named recipe file. For an example of an append file in use, see
24 the ":ref:`dev-manual/common-tasks:appending other layers metadata with your layer`"
37 .. code-block:: shell
60 the :doc:`/bsp-guide/index`.
62 :term:`Build Directory`
65 script that is found in the Source Directory
66 (i.e. :ref:`ref-manual/structure:\`\`oe-init-build-env\`\``). The
67 :term:`TOPDIR` variable points to the Build Directory.
69 You have a lot of flexibility when creating the Build Directory.
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/filesystems/ |
| H A D | autofs.rst | 2 autofs - how it works
8 The goal of autofs is to provide on-demand mounting and race free
17 media with a media-changing robot.
23 filesystem can even be programmatic rather than database-backed,
24 allowing wildcards for example, and can vary based on the user who
31 There also needs to be a user-space program which looks up names
35 required with any user-space program. Subsequent text refers to this
52 directory should be a mount trap is based on a master map. This master
58 mount is considered to be *indirect*), then the root directory is
59 always a regular directory, otherwise it is a mount trap when it is
[all …]
|