| /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
|
| /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 …]
|
| H A D | feature-and-driver-maintainers.rst | 86 Open development
89 Discussions about user reported issues, and development of new code
91 It is common for development within a single company to be conducted
92 behind closed doors. However, development and discussions initiated
148 - (when development is contracted) works for a company which paid
149 for the development rather than the company which did the work
156 role in the development of the code, they should be moved to the CREDITS file.
|
| H A D | messy-diffstat.rst | 11 complicated development history will yield a massive diffstat containing a
20 A Git development history proceeds as a series of commits. In a simplified
21 manner, mainline kernel development looks like this::
46 consider a slightly more complex development history::
60 the ``git diff`` operation to use. The development culminating in cN
|
| /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 Development process <process/development-process>
29 All development-process docs <process/index>
46 Development tools and processes
56 Development tools <dev-tools/index>
|
| /linux/Documentation/process/ |
| 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
136 This document is crucial for understanding the Linux development
138 development on other Operating Systems.
148 for anyone new to kernel development (or anyone simply curious about
159 development. Please consult this list if you do not find what you
164 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.
173 provide can help the development community provide useful input on the
201 of a kernel development project, the better off everybody involved will be.
208 need to keep development plans behind closed doors.
[all …]
|
| H A D | development-process.rst | 3 A guide to the Kernel Development Process
7 work with the development community with a minimum of frustration. It is
10 development (or, indeed, free software development in general). While
|
| H A D | 8.Conclusion.rst | 6 There are numerous sources of information on Linux kernel development and
16 Various web sites discuss kernel development at all levels of detail. Your
30 There are a number of books on kernel development:
36 Linux Kernel Development (Robert Love).
71 the direction of kernel development, and more. It is a situation where
|
| 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,
146 development process.
161 participate in the mitigation development.
178 Mitigation development
184 Using a mailing list is close to the normal Linux development process and
188 The mailing list operates in the same way as normal Linux development.
192 development branch against the mainline kernel and backport branches for
200 Bringing in experts can happen at any time in the development process and
216 is disclosed and brought into the development process.
[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
|
| /linux/arch/powerpc/platforms/8xx/ |
| H A D | Kconfig | 18 MPC86x Application Development System by Freescale Semiconductor.
20 development around the MPC86X processor families.
27 Freescale Semiconductor MPC885 Application Development System (ADS).
30 development around the MPC885 processor family.
|
| /linux/arch/arm/mach-sa1100/ |
| H A D | Kconfig | 33 Microprocessor Development Board (also known as the Assabet).
41 Microprocessor Development Board (Assabet) with the SA-1111
42 Development Board (Nepon).
|
| /linux/Documentation/devicetree/bindings/arm/omap/ |
| H A D | omap.txt | 116 - DRA762 EVM: Software Development Board for DRA762
119 - DRA742 EVM: Software Development Board for DRA742
122 - DRA722 EVM: Software Development Board for DRA722
125 - DRA718 EVM: Software Development Board for DRA718
|
| /linux/Documentation/arch/arc/ |
| H A D | arc.rst | 17 Home for all development activities regarding open source projects for
50 SoC bringup and software development in general.
58 - Cross-compilation: process of compiling for ARC targets on a development
61 (hardware board or a simulator like QEMU) with complete development environment
|
| /linux/Documentation/devicetree/bindings/arm/ti/ |
| H A D | k3.yaml | 78 - toradex,verdin-am62-nonwifi-dev # Verdin AM62 Module on Verdin Development Board
90 - toradex,verdin-am62-wifi-dev # Verdin AM62 Wi-Fi / BT M. on Verdin Development B.
102 … - toradex,verdin-am62p-nonwifi-dev # Verdin AM62P Module on Verdin Development Board
114 … - toradex,verdin-am62p-wifi-dev # Verdin AM62P Wi-Fi / BT M. on Verdin Development B.
171 - toradex,aquila-am69-dev # Aquila AM69 Module on Aquila Development Board
|
| H A D | omap.yaml | 41 - logicpd,dm3730-som-lv-devkit # LogicPD Zoom OMAP35xx SOM-LV Development Kit
42 - logicpd,dm3730-torpedo-devkit # LogicPD Zoom OMAP35xx Torpedo Development Kit
83 - logicpd,dm3730-som-lv-devkit # LogicPD Zoom DM3730 SOM-LV Development Kit
84 … - logicpd,dm3730-torpedo-devkit # LogicPD Zoom DM3730 Torpedo + Wireless Development Kit
|
| /linux/arch/mips/mobileye/ |
| H A D | Kconfig | 18 bool "Include FDT for Mobileye EyeQ5 development platforms"
22 Enable this to include the FDT for the EyeQ5 development platforms
|
| /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";
|
| /linux/arch/arm64/boot/dts/amd/ |
| H A D | amd-overdrive-rev-b1.dts | 3 * DTS file for AMD Seattle Overdrive Development Board
14 model = "AMD Seattle (Rev.B1) Development Board (Overdrive)";
|
| /linux/sound/soc/sof/ |
| H A D | Kconfig | 78 Distributions should not select this option, only SOF development
80 Say Y if you are involved in SOF development and need this option.
93 Say Y if you are involved in SOF development and need this option.
126 If you are not involved in SOF releases and CI development,
137 Say Y if you are involved in SOF development and need this option.
|
| /linux/arch/arm/boot/dts/marvell/ |
| H A D | kirkwood-db-88f6281.dts | 3 * Marvell DB-88F6281-BP Development Board Setup
16 model = "Marvell DB-88F6281-BP Development Board";
|
| H A D | kirkwood-db-88f6282.dts | 3 * Marvell DB-88F6282-BP Development Board Setup
16 model = "Marvell DB-88F6282-BP Development Board";
|
| /linux/arch/arm64/boot/dts/ti/ |
| H A D | k3-am625-verdin-wifi-dev.dts | 6 * https://www.toradex.com/products/carrier-board/verdin-development-board-kit
17 model = "Toradex Verdin AM62 WB on Verdin Development Board";
|
| H A D | k3-am625-verdin-nonwifi-dev.dts | 6 * https://www.toradex.com/products/carrier-board/verdin-development-board-kit
17 model = "Toradex Verdin AM62 on Verdin Development Board";
|