| /OK3568_Linux_fs/yocto/poky/documentation/overview-manual/ |
| H A D | development-environment.rst | 4 The Yocto Project Development Environment
7 This chapter takes a look at the Yocto Project development environment.
8 The chapter provides Yocto Project Development environment concepts that
19 Open source philosophy is characterized by software development directed
21 developers. Contrast this to the more standard centralized development
28 approaches, and production. These facets of the development process can
32 traditional development environment. In an open source environment, the
48 The Development Host
51 A development host or :term:`Build Host` is key to
54 development of those images and applications generally takes place on a
[all …]
|
| H A D | yp-intro.rst | 13 Yocto Project provides a flexible toolset and a development environment
19 provides advantages in both systems and applications development,
60 move between architectures without moving to new development
110 development.
117 Yocto Project and allows development teams to plan activities.
151 …ansitioning-to-a-custom-environment:transitioning to a custom environment for systems development`"
155 workflow <overview-manual/development-environment:the yocto project development environment>`
157 software development.
158 In a desktop development environment, there are mechanisms to easily pull
167 BitBake build on a development host and then deploying binaries to
[all …]
|
| H A D | intro.rst | 20 components and tools, development methods, the
24 - :ref:`overview-manual/development-environment:the yocto project development environment`\ *:*
26 development environment. You will learn about open source, development hosts,
32 can find conceptual information about components, development,
37 - *Step-by-step Instructions for Development Tasks:* Instructional
41 various development tasks. As another example, the
|
| H A D | concepts.rst | 11 cross-development toolchains, shared state cache, and so forth are
38 section of the Yocto Project Development Tasks Manual.
135 Yocto Project development environment. Layers logically separate
142 There are many layers working in the Yocto Project development environment. The
153 section of the Yocto Project Development Tasks Manual.
185 tests packages, generates images, and generates cross-development
190 Software Development Kit (SDK), produced by the build system. These
197 - *Application Development SDK:* Cross-development tools that are
258 development environment.
312 section in the Yocto Project Development Tasks Manual.
[all …]
|
| /OK3568_Linux_fs/kernel/arch/arm/mach-mmp/ |
| H A D | Kconfig | 19 bool "Marvell's PXA168 Aspenite Development Board"
24 Aspenite Development Board.
27 bool "Marvell's PXA168 Zylonite2 Development Board"
32 Zylonite2 Development Board.
35 bool "Marvell's PXA168 Avengers Lite Development Board"
40 Avengers Lite Development Board.
43 bool "Marvell's PXA910 TavorEVB Development Board"
48 TavorEVB Development Board.
51 bool "Marvell's PXA910 TavorEVB Development Board"
56 TTC_DKB Development Board.
[all …]
|
| /OK3568_Linux_fs/yocto/poky/documentation/kernel-dev/ |
| H A D | intro.rst | 12 set up your build host to support kernel development, introduces the
13 kernel development process, provides background information on the Yocto
30 ":ref:`kernel-dev/concepts-appx:yocto project kernel development and maintenance`" section.
32 Also included is a Yocto Linux kernel development recipe
34 upstream Yocto Linux kernel development and kernel Metadata development.
39 ":ref:`kernel-dev/concepts-appx:yocto project kernel development and maintenance`"
66 development of the Yocto Project.
74 specific Linux kernel development tasks. These instructions assume you
76 open-source development tools. Understanding these concepts will
87 as described in the Yocto Project Application Development and the
[all …]
|
| H A D | concepts-appx.rst | 7 Yocto Project Kernel Development and Maintenance
13 development cycle, the Yocto Project team chooses a Linux kernel based
17 of development by the Linux community. In other words, the Linux kernel
19 release. But, by being in the final stages of external development, the
21 the early stages of the Yocto Project development window.
38 :ref:`overview-manual/development-environment:yocto project source repositories`
76 - *linux-yocto-dev:* A development kernel based on the latest
96 goes into their next development cycle, or upward revision (uprev)
99 feature development upstream is through a kernel uprev process.
105 of Linux kernel development, BSP support, and release timing to select
[all …]
|
| /OK3568_Linux_fs/yocto/poky/documentation/dev-manual/ |
| H A D | start.rst | 14 Creating a Team Development Environment
18 team development environment, or how to scale it for a large team of
36 equipment together and set up your development environment's
53 system development meets desired quality standards.
56 get the hardware together. Ideally, any development, build, or test
66 building Yocto Project development containers to be run under
71 can understand the hardware topology of the development environment.
73 development environment.
81 :ref:`overview-manual/development-environment:git`.
112 5. *Set up the Application Development Machines:* As mentioned earlier,
[all …]
|
| /OK3568_Linux_fs/yocto/poky/meta/lib/oeqa/manual/ |
| H A D | kernel-dev.json | 17 …"action": "Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki.…
18 …"expected_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. http…
39 …"action": "Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki.…
40 …"expected_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. http…
61 …"action": "Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki.…
62 …"expected_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. http…
83 …"action": "Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki.…
84 …"expected_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. http…
105 …"action": "Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki.…
106 …"expected_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. http…
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/process/ |
| H A D | 1.Intro.rst | 9 The rest of this section covers the scope of the kernel development process
14 influence the direction of kernel development. Code contributed to the
17 :ref:`development_process` introduces the development process, the kernel
19 the patch development, review, and merging cycle are covered. There is some
21 with kernel development are encouraged to track down and fix bugs as an
25 emphasis on involving the development community as soon as possible.
33 review. To be taken seriously by the development community, patches must be
40 of the development process; this section offers a number of tips on how to
48 for more information on kernel development.
62 (and companies) wishing to participate in its development. Hardware
[all …]
|
| H A D | 2.Process.rst | 3 How the development process works
6 Linux kernel development in the early 1990's was a pretty loose affair,
10 processes to keep development happening smoothly. A solid understanding of
32 the leading edge of Linux kernel development; the kernel uses a
33 rolling development model which is continually integrating major changes.
36 merging of patches for each release. At the beginning of each development
38 deemed to be sufficiently stable (and which is accepted by the development
40 new development cycle (and all of the major changes) will be merged during
62 best thing to do is to wait for the next development cycle. (An occasional
73 As an example, here is how the 5.4 development cycle went (all dates in
[all …]
|
| H A D | howto.rst | 3 HOWTO do Linux kernel development
8 to work with the Linux kernel development community. It tries to not
29 kernel development. Assembly (any architecture) is not required unless
30 you plan to do low-level development for that architecture. Though they
50 existing development community. It is a diverse group of people, with
137 This document is crucial for understanding the Linux development
139 development on other Operating Systems.
149 for anyone new to kernel development (or anyone simply curious about
160 development. Please consult this list if you do not find what you
165 apply it to the different development branches of the kernel.
[all …]
|
| H A D | 3.Early-stage.rst | 6 When contemplating a Linux kernel development project, it can be tempting
41 entire kernel development process; one of them went back to an audio list
55 - and to discuss it with the development community before investing in the
58 So, when contemplating a kernel development project, one should obtain
74 When planning a kernel development project, it makes great sense to hold
95 Years of experience with the kernel development community have taught a
145 development project.
172 provide can help the development community provide useful input on the
200 of a kernel development project, the better off everybody involved will be.
207 need to keep development plans behind closed doors.
[all …]
|
| H A D | embargoed-hardware-issues.rst | 92 community compliant development under embargo restrictions.
117 Due to the globally distributed nature of Linux kernel development,
144 development process.
159 participate in the mitigation development.
176 Mitigation development
182 Using a mailing-list is close to the normal Linux development process and
186 The mailing-list operates in the same way as normal Linux development.
190 development branch against the mainline kernel and backport branches for
195 time of the development process and needs to be handled in a timely manner.
210 by the incident team and brought into the development process.
[all …]
|
| /OK3568_Linux_fs/yocto/poky/documentation/ref-manual/ |
| H A D | images.rst | 59 for development work using the host. The image includes headers and
60 libraries you can use in a host development environment. This image
66 in the cross-toolchain but also includes development headers and
71 suitable for development using the target.
77 for development work using the host. The image includes headers and
78 libraries you can use in a host development environment.
97 development headers and libraries to form a complete stand-alone SDK
98 and is suitable for development using the target.
106 development using the host. The image includes libraries needed to
112 development headers and libraries to form a complete standalone SDK
[all …]
|
| H A D | terms.rst | 8 development environment might find helpful. While some of these terms are
25 section in the Yocto Project Development Tasks Manual.
108 The system used to build images in a Yocto Project Development
109 environment. The build system is sometimes referred to as the development
134 the Texas Instruments ARM Cortex-A8 development board).
159 :term:`Cross-Development Toolchain`
160 In general, a cross-development toolchain is a collection of software
161 development tools and utilities that run on one architecture and allow you
166 The Yocto Project supports two different cross-development toolchains:
176 ":ref:`overview-manual/concepts:Cross-Development
[all …]
|
| /OK3568_Linux_fs/u-boot/board/logicpd/imx6/ |
| H A D | README | 1 U-Boot for LogicPD i.MX6 Development Kit
4 This file contains information for the port of U-Boot to the Logic PD Development kit.
6 Logic PD has an i.MX6 System On Module (SOM) and a correspondong development
7 board. SOM has a built-in microSD socket, DDR and NAND flash. The development kit has
12 For more details about Logic PD i.MX6 Development kit, visit:
15 Building U-Boot for Logic PD Development Kit
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-devtools/unattended-upgrades/files/ |
| H A D | 0001-unattended-upgrade-Remove-distro_info-usage-to-check.patch | 54 - logging.warning("Could not figure out development release: %s" % e)
59 - syslog.syslog((_("Not running on this development "
63 - logging.warning(_("Not running on this development "
69 - logging.debug("Running on the development release")
70 - elif "(development branch)" in DISTRO_DESC and not\
72 - syslog.syslog(_("Not running on the development release."))
73 - logging.info(_("Not running on the development release."))
|
| /OK3568_Linux_fs/yocto/poky/documentation/sdk-manual/ |
| H A D | intro.rst | 10 Welcome to the Yocto Project Application Development and the Extensible
11 Software Development Kit (eSDK) manual. This manual
17 - *Cross-Development Toolchain*: This toolchain contains a compiler,
25 cross-development environment by defining variables and preparing for
52 The SDK development environment consists of the following:
65 the development process that revolves around use of the SDK.
68 However, the extensible SDK has powerful development tools to help you
107 The Cross-Development Toolchain
110 The :term:`Cross-Development Toolchain` consists
146 SDK Development Model
[all …]
|
| /OK3568_Linux_fs/u-boot/arch/arm/mach-rockchip/rk3288/ |
| H A D | Kconfig | 37 EVB-RK3288 is a RK3288-based development board with 2 USB ports,
57 Fennec is a RK3288-based development board with 2 USB ports,
66 Firefly is a RK3288-based development board with 2 USB ports,
75 MiQi-RK3288 is a RK3288-based development board with 4 USB 2.0
85 development board made by PHYTEC. This board works in a combination
92 PopMetal is a RK3288-based development board with 3 USB host ports,
118 Vyasa is a RK3288-based development board with 2 USB ports,
136 Tinker is a RK3288-based development board with 2 USB ports, HDMI,
|
| /OK3568_Linux_fs/buildroot/package/cppcms/ |
| H A D | Config.in | 12 CppCMS is a Free High Performance Web Development Framework
13 (not a CMS) aimed for Rapid Web Application Development. It
14 differs from most of other web development frameworks like:
18 - It uses modern C++ as primary development language in
20 - It is aimed on development of both Web Sites and Web
|
| /OK3568_Linux_fs/kernel/Documentation/maintainer/ |
| H A D | rebasing-and-merging.rst | 17 development history. Indeed, given the scale of the project, avoiding
42 Used properly, rebasing can yield a cleaner and clearer development
73 between release points; basing development on one of those points
97 Merging is a common operation in the kernel development process; the 5.1
98 development cycle included 1,126 merge commits - nearly 9% of the total.
128 branches. Failure to do so threatens the security of the development
145 sure that there are no conflicts with parallel development and generally
149 Why is that? Back merges will muddy the development history of your own
153 also obscure problems with the development process in your tree; they can
171 in the 5.1 development cycle) and has gotten quite good at conflict
[all …]
|
| /OK3568_Linux_fs/u-boot/arch/arm/ |
| H A D | Kconfig | 859 bool "Support Versatile Express Juno Development Platform"
870 The LS2080A Development System (EMULATOR) is a pre silicon
871 development platform that supports the QorIQ LS2080A
882 The LS2080A Development System (QDS) is a pre silicon
883 development platform that supports the QorIQ LS2080A
897 The LS2080A Development System (QDS) is a high-performance
898 development platform that supports the QorIQ LS2080A
913 development platform that supports the QorIQ LS2080A
927 development platform that supports the QorIQ LS2081A/LS2041A
961 The LS1012A Development System (QDS) is a high-performance
[all …]
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/licenses/ |
| H A D | zsh | 17 are referred to as `the Zsh Development Group'. This is for convenience
28 In no event shall the Zsh Development Group be liable to any party for
31 Development Group have been advised of the possibility of such damage.
33 The Zsh Development Group specifically disclaim any warranties, including,
36 basis, and the Zsh Development Group have no obligation to provide
|
| /OK3568_Linux_fs/u-boot/arch/arm/mach-omap2/am33xx/ |
| H A D | Kconfig | 6 This option specifies support for the TI8168 EVM development platform
17 EVM development platform.
58 GP and HS EVM development platforms. The AM335x
59 GP EVM is a standalone test, development, and
222 GP and HS EVM development platforms.The AM437x
223 GP EVM is a standalone test, development, and
|