Home
last modified time | relevance | path

Searched full:development (Results 1 – 25 of 799) sorted by relevance

12345678910>>...32

/Linux-v5.4/arch/arm/mach-mmp/
DKconfig19 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 …]
/Linux-v5.4/Documentation/process/
D1.Intro.rst9 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 …]
D2.Process.rst3 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 thus 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 4.16 development cycle went (all dates in
[all …]
Dhowto.rst3 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 …]
Ddevelopment-process.rst3 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
D3.Early-stage.rst6 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 …]
Dembargoed-hardware-issues.rst87 community compliant development under embargo restrictions.
112 Due to the globally distributed nature of Linux kernel development,
139 development process.
154 participate in the mitigation development.
171 Mitigation development
177 Using a mailing-list is close to the normal Linux development process and
181 The mailing-list operates in the same way as normal Linux development.
185 development branch against the mainline kernel and backport branches for
190 time of the development process and needs to be handled in a timely manner.
205 by the incident team and brought into the development process.
[all …]
D8.Conclusion.rst6 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
D7.AdvancedTopics.rst6 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
/Linux-v5.4/Documentation/
Dconf.py64 copyright = 'The kernel development community'
65 author = 'The kernel development community'
387 'The kernel development community', 'manual'),
389 'The kernel development community', 'manual'),
391 'The kernel development community', 'manual'),
392 ('dev-tools/index', 'dev-tools.tex', 'Development tools for the Kernel',
393 'The kernel development community', 'manual'),
395 'The kernel development community', 'manual'),
397 'The kernel development community', 'manual'),
399 'The kernel development community', 'manual'),
[all …]
/Linux-v5.4/Documentation/maintainer/
Drebasing-and-merging.rst17 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 …]
/Linux-v5.4/Documentation/devicetree/bindings/arm/omap/
Domap.txt121 - OMAP4 SDP : Software Development Board
136 - OMAP3 EVM : Software Development Board for OMAP35x, AM/DM37x
139 - AM335X EVM : Software Development Board for AM335x
160 - AM335X phyCORE-AM335x: Development kit
202 - DRA762 EVM: Software Development Board for DRA762
205 - DRA742 EVM: Software Development Board for DRA742
208 - DRA722 EVM: Software Development Board for DRA722
211 - DRA718 EVM: Software Development Board for DRA718
/Linux-v5.4/arch/arm/mach-davinci/
DKconfig77 for development is a DM644x EVM
91 for development is a Neuros OSD2 Open Set Top Box.
99 for development is a DM355 EVM
106 for development is a DM355 Leopard board.
115 for development is a DM6467 EVM
126 for development is a DM365 EVM
/Linux-v5.4/arch/mips/generic/
DKconfig28 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
/Linux-v5.4/arch/arm/mach-pxa/
DKconfig43 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"
236 bool "LogicPD PXA270 Card Engine Development Platform"
245 bool "PHYTEC PCM-990 development board"
696 found on the pxa25x development platform system (Lubbock) and pxa27x
697 development platform system (Mainstone). This IO board supports the
/Linux-v5.4/arch/powerpc/platforms/8xx/
DKconfig18 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-v5.4/fs/reiserfs/
DREADME70 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
/Linux-v5.4/Documentation/usb/
DCREDITS38 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.
/Linux-v5.4/arch/arm/mach-s3c24xx/
DKconfig208 development board (also known as BAST)
402 Note: This is under development and not all peripherals can be supported
454 development system
457 bool "Avantech AT2440EVB development board"
461 Say Y here if you are using the AT2440EVB development board
464 bool "MINI2440 development board"
/Linux-v5.4/Documentation/networking/device_drivers/intel/
Dipw2200.txt82 part of a development project. Conformance to local regulatory
85 solution intended to be used for purposes other than development, please
169 of the ipw2200 development snapshot releases available from the
400 Due to the nature of open source development projects, there are
403 development snapshot releases.
407 major.minor.development
409 Any version where the 'development' portion is 0 (for example
413 Any version where the 'development' portion is not a 0 (for
414 example 1.0.1, 1.1.5, etc.) indicates a development version that is
416 and functionality of the development releases are not know. We make
/Linux-v5.4/arch/arm/mach-dove/
DKconfig10 bool "Marvell DB-MV88AP510 Development Board"
15 Marvell DB-MV88AP510 Development Board.
/Linux-v5.4/arch/arm/boot/dts/
Dr8a7744-iwg20d-q7-dbcm-ca.dts3 * 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";
Dkirkwood-db-88f6281.dts3 * Marvell DB-88F6281-BP Development Board Setup
16 model = "Marvell DB-88F6281-BP Development Board";
Dkirkwood-db-88f6282.dts3 * Marvell DB-88F6282-BP Development Board Setup
16 model = "Marvell DB-88F6282-BP Development Board";
/Linux-v5.4/arch/arm/mach-mv78xx0/
DKconfig17 bool "Marvell DB-78x00-BP Development Board"
20 Marvell DB-78x00-BP Development Board.

12345678910>>...32