Searched full:development (Results 1 – 25 of 842) sorted by relevance
12345678910>>...34
/kernel/linux/linux-5.10/arch/arm/mach-mmp/ |
D | Kconfig | 19 bool "Marvell's PXA168 Aspenite Development Board" 24 Aspenite Development Board. 27 bool "Marvell's PXA168 Zylonite2 Development Board" 32 Zylonite2 Development Board. 35 bool "Marvell's PXA168 Avengers Lite Development Board" 40 Avengers Lite Development Board. 43 bool "Marvell's PXA910 TavorEVB Development Board" 48 TavorEVB Development Board. 51 bool "Marvell's PXA910 TavorEVB Development Board" 56 TTC_DKB Development Board. [all …]
|
/kernel/linux/linux-5.10/Documentation/process/ |
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 …]
|
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 …]
|
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
|
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 …]
|
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. 172 provide can help the development community provide useful input on the 200 of a kernel development project, the better off everybody involved will be. 207 need to keep development plans behind closed doors. [all …]
|
D | embargoed-hardware-issues.rst | 92 community compliant development under embargo restrictions. 117 Due to the globally distributed nature of Linux kernel development, 144 development process. 159 participate in the mitigation development. 176 Mitigation development 182 Using a mailing-list is close to the normal Linux development process and 186 The mailing-list operates in the same way as normal Linux development. 190 development branch against the mainline kernel and backport branches for 195 time of the development process and needs to be handled in a timely manner. 210 by the incident team and brought into the development process. [all …]
|
D | 8.Conclusion.rst | 6 There are numerous sources of information on Linux kernel development and 18 Various web sites discuss kernel development at all levels of detail. Your 32 There are a number of books on kernel development: 38 Linux Kernel Development (Robert Love). 73 the direction of kernel development, and more. It is a situation where
|
D | 7.AdvancedTopics.rst | 6 At this point, hopefully, you have a handle on how the development process 9 regular part of the Linux kernel development process. 18 control enabled an immediate acceleration of the kernel development 29 fits into the kernel development process in particular. Developers who 61 of development can be separated into a separate "topic branch" and 64 development in any branch which you intend to ask others to pull from. 66 from development branches when they are in complete form and ready to go - 70 development history. An inconvenient patch (one which breaks bisection, 97 of the reasons why development should be done in private branches (which
|
/kernel/linux/config/ |
D | README.md | 28 2. Configuration files for open-source development boards 30 Configuration file for the open-source development board Hi3516D V300 used in the standard system 40 …fconfig # Small-system defconfig of the open-source Hi3516D V300 development board from HiSi… 41 …fconfig # Standard-system defconfig of the open-source Hi3516D V300 development board from HiSi… 48 …fconfig # Small-system defconfig of the open-source Hi3516D V300 development board from HiSi… 49 …fconfig # Standard-system defconfig of the open-source Hi3516D V300 development board from HiSi… 91 The following uses the Hi3516D V300 development board and Ubuntu x86 server as an example.
|
/kernel/linux/linux-5.10/Documentation/maintainer/ |
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 …]
|
/kernel/linux/linux-5.10/arch/arm/mach-davinci/ |
D | Kconfig | 76 for development is a DM644x EVM 90 for development is a Neuros OSD2 Open Set Top Box. 98 for development is a DM355 EVM 105 for development is a DM355 Leopard board. 114 for development is a DM6467 EVM 125 for development is a DM365 EVM
|
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/omap/ |
D | omap.txt | 128 - OMAP4 SDP : Software Development Board 143 - OMAP3 EVM : Software Development Board for OMAP35x, AM/DM37x 146 - AM335X EVM : Software Development Board for AM335x 167 - AM335X phyCORE-AM335x: Development kit 209 - DRA762 EVM: Software Development Board for DRA762 212 - DRA742 EVM: Software Development Board for DRA742 215 - DRA722 EVM: Software Development Board for DRA722 218 - DRA718 EVM: Software Development Board for DRA718
|
/kernel/linux/linux-5.10/arch/mips/generic/ |
D | Kconfig | 28 development boards, which boot using a legacy boot protocol. 51 Enable this to include the FDT for the MIPS Boston development board 69 bool "Include FDT for Microsemi Ocelot development platforms" 72 Enable this to include the FDT for the Ocelot development platforms
|
/kernel/liteos_m/ |
D | README.md | 81 …development board, you must set up the basic system environment for OpenHarmony first. The basic s… 95 …development boards are provided by community developers. The following provides the links to these… 107 …r porting the OpenHarmony LiteOS-M kernel to support the STM32F429IGTb development board. The code…
|
/kernel/linux/linux-5.10/arch/arm/mach-pxa/ |
D | Kconfig | 43 bool "Intel DBPXA250 Development Platform (aka Lubbock)" 49 bool "Intel HCDDBBVA0 Development Platform (aka Mainstone)" 58 bool "PXA3xx Development Platform (aka Zylonite) PXA300/310" 64 bool "PXA3xx Development Platform (aka Zylonite) PXA320" 219 bool "LogicPD PXA270 Card Engine Development Platform" 228 bool "PHYTEC PCM-990 development board" 679 found on the pxa25x development platform system (Lubbock) and pxa27x 680 development platform system (Mainstone). This IO board supports the
|
/kernel/linux/patches/ |
D | README.md | 46 …fconfig # Small-system defconfig of the open-source Hi3516D V300 development board from HiSi… 47 …fconfig # Standard-system defconfig of the open-source Hi3516D V300 development board from HiSi… 54 …fconfig # Small-system defconfig of the open-source Hi3516D V300 development board from HiSi… 55 …fconfig # Standard-system defconfig of the open-source Hi3516D V300 development board from HiSi… 99 The following uses the Hi3516D V300 development board and Ubuntu x86 server as an example.
|
/kernel/linux/linux-5.10/fs/reiserfs/ |
D | README | 70 Hideous Commercial Pitch: Spread your development costs across other OS 73 the software component development power of the internet. Be the most 75 decentralized internet development, and add value through your branded 98 Vladimir throughout the project's development. He wrote a quite 155 hypertext feature development, MP3.com funded journaling, SuSE funded 156 core development, IntegratedLinux.com funded squid web cache
|
/kernel/linux/linux-5.10/arch/powerpc/platforms/8xx/ |
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.
|
/kernel/linux/linux-5.10/Documentation/usb/ |
D | CREDITS | 38 of hardware, support, time and development (this is from the original 41 The following corporations have helped us in the development 77 - AVM GmbH Berlin is supporting the development of the Linux 111 converter products for development. 119 the driver development.
|
/kernel/liteos_a/ |
D | README.md | 15 …development of the IoT industry, OpenHarmony LiteOS Cortex-A brings small-sized, low-power, and hi… 65 - Applicable development boards: Hi3516D V300 70 …art-appendix-hi3516.md). You can develop and run your applications based on this development board. 76 - [Setting Up Ubuntu Development Environment](https://gitee.com/openharmony/docs/blob/master/en/d…
|
/kernel/linux/linux-5.10/arch/arm/mach-s3c/ |
D | Kconfig.s3c24xx | 196 development board (also known as BAST) 390 Note: This is under development and not all peripherals can be supported 442 development system 445 bool "Avantech AT2440EVB development board" 449 Say Y here if you are using the AT2440EVB development board 452 bool "MINI2440 development board"
|
/kernel/linux/linux-5.10/arch/arm/mach-dove/ |
D | Kconfig | 10 bool "Marvell DB-MV88AP510 Development Board" 15 Marvell DB-MV88AP510 Development Board.
|
/kernel/linux/linux-5.10/arch/arm/boot/dts/ |
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";
|
D | kirkwood-db-88f6281.dts | 3 * Marvell DB-88F6281-BP Development Board Setup 16 model = "Marvell DB-88F6281-BP Development Board";
|
12345678910>>...34