| /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
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/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/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/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/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
|
| /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/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 | development-process.rst | 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 | 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 | maintainer-handbooks.rst | 5 Subsystem and maintainer tree specific development process notes
9 which is supplementary to the general development process handbook
|
| /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 …]
|
| /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/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 | 209 SUMMARY:libstdc++-dev = "GNU standard C++ library - development files"
214 SUMMARY:libstdc++-staticdev = "GNU standard C++ library - static development files"
227 SUMMARY:libssp-dev = "GNU stack smashing protection library - development files"
229 SUMMARY:libssp-staticdev = "GNU stack smashing protection library - static development files"
238 SUMMARY:libquadmath-dev = "GNU quad-precision math library - development files"
240 SUMMARY:libquadmath-staticdev = "GNU quad-precision math library - static development files"
252 SUMMARY:libgomp-dev = "GNU OpenMP parallel programming library - development files"
254 SUMMARY:libgomp-staticdev = "GNU OpenMP parallel programming library - static development files"
262 SUMMARY:libatomic-dev = "GNU C++11 atomics support library - development files"
264 SUMMARY:libatomic-staticdev = "GNU C++11 atomics support library - static development files"
[all …]
|
| /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/linux/Documentation/ |
| H A D | index.rst | 16 Working with the development community
19 The essential guides for interacting with the kernel's development
25 process/development-process
29 All development-process docs <process/index>
|
| /openbmc/linux/arch/arm/boot/dts/renesas/ |
| H A D | r8a7744-iwg20d-q7-dbcm-ca.dts | 3 * Device Tree Source for the iWave Systems RZ/G1N Qseven board development
15 model = "iWave Systems RZ/G1N Qseven development platform with camera add-on";
|
| /openbmc/linux/drivers/staging/board/ |
| H A D | Kconfig | 7 in-tree development and integration of platform devices.
11 This in turn allows for incremental development of both
|
| /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/linux/arch/arm/boot/dts/axis/ |
| H A D | artpec6-devboard.dts | 2 // Axis ARTPEC-6 development board.
8 model = "ARTPEC-6 development board";
|
| /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 …]
|