/openbmc/openbmc/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 47 The Development Host 50 A development host or :term:`Build Host` is key to 53 development of those images and applications generally takes place on a [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 | 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 …]
|
/openbmc/openbmc/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 …]
|
/openbmc/openbmc/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 …]
|
/openbmc/openbmc/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`. 100 #. *Set up the Application Development Machines:* As mentioned earlier, [all …]
|
/openbmc/linux/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 | development-process.rst | 3 A guide to the Kernel Development Process 22 work with the development community with a minimum of frustration. It is 25 development (or, indeed, free software development in general). While
|
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 …]
|
/openbmc/linux/arch/mips/generic/ |
H A D | Kconfig | 28 development boards, which boot using a legacy boot protocol. 56 Enable this to include the FDT for the MIPS Boston development board 80 bool "Include FDT for Microsemi Ocelot development platforms" 83 Enable this to include the FDT for the Ocelot development platforms 88 bool "Include FDT for Microsemi Luton development platforms" 91 Enable this to include the FDT for the Luton development platforms 96 bool "Include FDT for Microsemi Jaguar2 development platforms" 99 Enable this to include the FDT for the Jaguar2 development platforms 104 bool "Include FDT for Microsemi Serval development platforms" 107 Enable this to include the FDT for the Serval development platforms
|
/openbmc/docs/ |
H A D | README.md | 18 ## OpenBMC Development 22 - [cheatsheet.md](cheatsheet.md): Quick reference for some common development 27 - [development tutorials](development/README.md): Tutorials for getting up to 28 speed on OpenBMC development 30 - [kernel-development.md](kernel-development.md): Reference for common kernel 31 development tasks
|
/openbmc/openbmc/poky/documentation/ref-manual/ |
H A D | images.rst | 61 for development work using the host. The image includes headers and 62 libraries you can use in a host development environment. This image 68 in the cross-toolchain but also includes development headers and 73 suitable for development using the target. 79 for development work using the host. The image includes headers and 80 libraries you can use in a host development environment. 99 development headers and libraries to form a complete stand-alone SDK 100 and is suitable for development using the target. 108 development using the host. The image includes libraries needed to 114 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 113 Build tools in binary form, providing required versions of development 115 system on a development host without such minimum versions. 122 A set of :term:`buildtools` binaries extended with additional development 156 the Texas Instruments ARM Cortex-A8 development board). 179 :term:`Cross-Development Toolchain` 180 In general, a cross-development toolchain is a collection of software [all …]
|
/openbmc/docs/tof/ |
H A D | membership-and-voting.md | 8 Development Community by vote. The current number of members is **7** and this 12 TOF members must themselves be members of the OpenBMC Development Community. 25 Members are elected by Ranked Choice Voting of the OpenBMC Development Community 42 | Jan 1st | July 1st | Developer contributions close for OpenBMC Development Community mem… 65 ## OpenBMC Development Community 67 Membership in the OpenBMC development community is determined by development 72 Membership is determined using data from the previous 6 months of development 79 There are two tiers of membership in the development community: normal and 93 might be: development in upstream Open Source communities not directly 113 - Development of a non-trivial commit (10+ lines) - 3 points.
|
/openbmc/openbmc/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."))
|
/openbmc/u-boot/arch/arm/mach-rockchip/rk3288/ |
H A D | Kconfig | 48 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,
|
/openbmc/openbmc/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
|
/openbmc/u-boot/arch/arm/ |
H A D | Kconfig | 1011 bool "Support Versatile Express Juno Development Platform" 1024 The LS2080A Development System (EMULATOR) is a pre silicon 1025 development platform that supports the QorIQ LS2080A 1036 The LS2080A Development System (QDS) is a pre silicon 1037 development platform that supports the QorIQ LS2080A 1051 The LS1088A Development System (QDS) is a high-performance 1052 development platform that supports the QorIQ LS1088A 1069 The LS2080A Development System (QDS) is a high-performance 1070 development platform that supports the QorIQ LS2080A 1088 development platform that supports the QorIQ LS2080A [all …]
|
/openbmc/linux/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 …]
|
/openbmc/openbmc/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 …]
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/sblim-cmpi-devel/ |
H A D | sblim-cmpi-devel_2.0.3.bb | 1 SUMMARY = "SBLIM CMPI Provider Development Support" 4 developers and can be used standalone. If used for C++ provider development \ 9 SECTION = "Development/Libraries" 15 UPSTREAM_CHECK_URI = "https://sourceforge.net/projects/sblim/files/development%20pkgs/sblim-cmpi-de…
|
/openbmc/docs/development/ |
H A D | README.md | 4 they need to get up and going with OpenBMC development. This can be reviewed in 7 1. [Development Environment Setup](dev-environment.md) 9 Start here. This shows how to setup an OpenBMC development environment using 17 3. [Web UI Development](web-ui.md)
|
/openbmc/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
|