| /openbmc/docs/ |
| H A D | README.md | 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
5 > The kernel development philosphy described below also applies to OpenBMC's
9 general development policy is that code must be upstream first. This is strongly
45 can provide input where appropriate. Be sure to follow the (upstream development
51 development in the community.
62 development of the features upstream, but where this has not happened we can
63 choose to carry the patches in the OpenBMC tree while upstream development
84 Some general hints for kernel development
|
| /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-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/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
118 development. Alternatively, you can use traditional kernel
[all …]
|
| H A D | concepts-appx.rst | 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
107 subsequent Yocto Linux kernel development. The team continually monitors
[all …]
|
| /openbmc/openbmc/poky/documentation/overview-manual/ |
| H A D | development-environment.rst | 7 This chapter takes a look at the Yocto Project development environment.
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
50 A development host or :term:`Build Host` is key to
53 development of those images and applications generally takes place on a
54 system not intended to run the software --- the development host.
56 You need to set up a development host in order to use it with the Yocto
58 function as the development host. However, it is possible to use 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,
41 various development tasks. As another example, the
|
| H A D | index.rst | 15 development-environment
|
| /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 \
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | start.rst | 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`.
103 machines used for application development:
110 - Keep your cross-development toolchains updated. You can do this
[all …]
|
| H A D | index.rst | 20 development-shell
21 python-development-shell
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/sblim-cmpi-devel/ |
| H A D | sblim-cmpi-devel_2.0.3.bb | 4 developers and can be used standalone. If used for C++ provider development \
15 UPSTREAM_CHECK_URI = "https://sourceforge.net/projects/sblim/files/development%20pkgs/sblim-cmpi-de…
|
| /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.
|
| /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/poky/meta/recipes-devtools/gcc/ |
| H A D | gcc-runtime.inc | 215 SUMMARY:libstdc++-dev = "GNU standard C++ library - development files"
220 SUMMARY:libstdc++-staticdev = "GNU standard C++ library - static development files"
233 SUMMARY:libssp-dev = "GNU stack smashing protection library - development files"
235 SUMMARY:libssp-staticdev = "GNU stack smashing protection library - static development files"
244 SUMMARY:libquadmath-dev = "GNU quad-precision math library - development files"
246 SUMMARY:libquadmath-staticdev = "GNU quad-precision math library - static development files"
258 SUMMARY:libgomp-dev = "GNU OpenMP parallel programming library - development files"
260 SUMMARY:libgomp-staticdev = "GNU OpenMP parallel programming library - static development files"
268 SUMMARY:libatomic-dev = "GNU C++11 atomics support library - development files"
270 SUMMARY:libatomic-staticdev = "GNU C++11 atomics support library - static development files"
[all …]
|
| /openbmc/docs/development/ |
| H A D | README.md | 4 they need to get up and going with OpenBMC development. This can be reviewed in
9 Start here. This shows how to setup an OpenBMC development environment using
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/konkretcmpi/ |
| H A D | konkretcmpi_0.9.2.bb | 1 SUMMARY = "Tool for rapid CMPI providers development"
3 KonkretCMPI makes CMPI provider development easier by generating type-safe \
|
| /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/openbmc/meta-aspeed/recipes-kernel/linux/linux-aspeed/ |
| H A D | rsa_oem_fitimage_key.key | 1 # Kernel fitImage 'Insecure' key (also known as 'development' or
2 # 'imprint' key), used to sign development images of the OpenBMC
|
| /openbmc/qemu/rust/ |
| H A D | .gitignore | 1 # Ignore any cargo development build artifacts; for qemu-wide builds, all build
|
| /openbmc/openbmc/meta-phosphor/conf/distro/include/ |
| H A D | phosphor-production.inc | 2 # or deployment environments than development.
|
| /openbmc/openbmc/poky/meta/recipes-core/images/ |
| H A D | core-image-minimal-dev.bb | 4 is suitable for development work."
|
| /openbmc/qemu/docs/system/arm/ |
| H A D | mcimx6ul-evk.rst | 5 MCIMX6UL-EVK development board. It has a single Cortex-A7 CPU.
|
| /openbmc/bmcweb/docs/ |
| H A D | TESTING.md | 14 …[development environment setup](https://github.com/openbmc/docs/blob/master/development/dev-enviro…
15 directions in the development environment setup document. This will get QEMU
18 [gerrit setup](https://github.com/openbmc/docs/blob/master/development/gerrit-setup.md)
46 reaches the QEMU session you set up in your development environment as
|