| /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/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/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
|
| H A D | kernel-development.md | 1 # OpenBMC kernel development
4 general development policy is that code must be upstream first. This is a strong
40 can provide input where appropriate. Be sure to follow the (upstream development
46 development in the community.
57 development of the features upstream, but where this has not happened we can
58 chose to carry the patches in the OpenBMC tree while the upstream development is
93 Some general hints for kernel development
|
| /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 …]
|
| H A D | index.rst | 4 Yocto Project Development Tasks Manual
20 development-shell
21 python-development-shell
|
| /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/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/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/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/openbmc/poky/documentation/ref-manual/ |
| H A D | images.rst | 58 for development work using the host. The image includes headers and
59 libraries you can use in a host development environment.
78 development headers and libraries to form a complete stand-alone SDK
79 and is suitable for development using the target.
87 development using the host. The image includes libraries needed to
93 development headers and libraries to form a complete standalone SDK
94 and is suitable for development using the target.
112 section in the Yocto Project Development Tasks Manual.
|
| 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/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/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
|
| /openbmc/openbmc/meta-arm/meta-arm-toolchain/ |
| H A D | README.md | 9 Pre-built Arm toolchain for bare-metal development
12 Recipes for pre-built GNU Arm toolchain for bare-metal development are provided
19 bare-metal software development on devices based on 32-bit Arm Cortex-A,
28 software development on devices based on 64-bit Arm Cortex-A processors.
|
| /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/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.
59 GP and HS EVM development platforms. The AM335x
60 GP EVM is a standalone test, development, and
249 GP and HS EVM development platforms.The AM437x
250 GP EVM is a standalone test, development, and
|
| /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/openbmc/poky/meta/files/common-licenses/ |
| H A D | NCSA | 6 Developed by: <Name of Development Group>
8 <URL for Development Group/Institution>
23 Neither the names of <Name of Development Group, Name of
|
| /openbmc/openbmc/poky/meta/recipes-sato/images/ |
| H A D | core-image-sato-dev.bb | 3 DESCRIPTION = "Image with Sato for development work. It includes everything \
4 within core-image-sato plus a native toolchain, application development and \
|