3 List of upstream coreboot maintainers
4 and how to submit coreboot changes
6 This represents the list of maintainers that work on the upstream coreboot
7 code base (on coreboot.org). Maintainers are assigned to topics and when
8 applicable to subtrees of the source tree. You'll find some subtrees that
9 don't have a maintainer. If you are looking for reviewers for such a sub-
10 tree, it's often a good choice to look at the git history to see who worked
13 Please try to follow the guidelines below. This will make things
14 easier on the maintainers. Not all of these guidelines matter for every
15 trivial patch so apply some common sense.
17 1. Always _test_ your changes, however small, on at least 1 or
18 2 people, preferably many more.
20 2. Try to release a few ALPHA test versions to gerrit. Announce
21 them onto the coreboot mailing list and IRC channel and await
22 results. This is especially important on coreboot core changes,
23 but also for device drivers, because often that's the only way
24 you will find things like the fact revision 3 chipset needs
25 a magic fix you didn't know about, or some clown changed the
26 chips on a board and not its name. (Don't laugh!)
28 3. Make sure your changes compile correctly in multiple
29 configurations. In particular check that changes work for all
30 boards in the tree (use abuild!)
32 4. When you are happy with a change make it generally available for
33 testing in gerrit and await feedback.
35 5. Make your patch available through coreboot's gerrit code review
36 system, and add the relevant maintainer from this list as a code
37 reviewer. Be prepared to get your changes sent back with seemingly
38 silly requests about formatting and variable names. These aren't
39 as silly as they seem. One job the maintainers do is to keep
40 things looking the same. Sometimes this means that the clever
41 hack in your mainboard or chipset to get around a problem actually
42 needs to become a generalized coreboot feature ready for next time.
44 PLEASE check your patch with the automated style checker
45 (util/lint/checkpatch.pl) to catch trival style violations.
46 See https://www.coreboot.org/Coding_Style for guidance here.
48 PLEASE add the maintainers that are generated by
49 util/scripts/get_maintainer.pl as reviewers. The results returned
50 by the script will be best if you have git installed and are
51 making your changes in a branch derived from coreboot.org's latest
54 PLEASE try to include any credit lines you want added with the
55 patch. It avoids people being missed off by mistake and makes
56 it easier to know who wants adding and who doesn't.
58 PLEASE document known bugs. If it doesn't work for everything
59 or does something very odd once a month document it.
61 PLEASE remember that submissions must be made under the terms
62 of the OSDL certificate of contribution and should include a
63 Signed-off-by: line. The current version of this "Developer's
64 Certificate of Origin" (DCO) is listed at
65 https://www.coreboot.org/Development_Guidelines#Sign-off_Procedure.
67 6. Make sure you have the right to send any changes you make. If you
68 do changes at work you may find your employer owns the patch
73 Descriptions of section entries:
75 M: Maintainer: FullName <address@domain>
76 Must be registered to Gerrit (https://review.coreboot.org/).
77 Should have experience with upstream coreboot development.
78 R: Designated reviewer: FullName <address@domain>
79 These reviewers should be CCed on patches.
80 L: Mailing list that is relevant to this area
81 W: Web-page with status/info
82 Q: Patchwork web based patch tracking system site
83 T: SCM tree type and location.
84 Type is one of: git, hg, quilt, stgit, topgit
85 S: Status, one of the following:
86 Supported: Someone is continuously paid to look after this and
87 a reaction to review requests can be expected
88 within a few days, a month at most.
89 Maintained: Someone actually looks after it and a reaction to
90 review requests can usually be expected within a
92 Odd Fixes: It has a maintainer but they don't have time to do
93 much other than throw the odd patch in. See below..
94 Orphan: No current maintainer [but maybe you could take the
95 role as you write your new code].
96 Obsolete: Old code. Something tagged obsolete generally means
97 it has been replaced by a better system and you
99 F: Files and directories with wildcard patterns.
100 A trailing slash includes all files and subdirectory files.
101 F: drivers/net/ all files in and below drivers/net
102 F: drivers/net/* all files in drivers/net, but not below
103 F: */net/* all files in "any top level directory"/net
104 One pattern per line. Multiple F: lines acceptable.
105 N: Files and directories with regex patterns.
106 N: [^a-z]tegra all files whose path contains the word tegra
107 One pattern per line. Multiple N: lines acceptable.
108 scripts/get_maintainer.pl has different behavior for files that
109 match F: pattern and matches of N: patterns. By default,
110 get_maintainer will not look at git log history when an F: pattern
111 match occurs. When an N: match occurs, git log history is used
112 to also notify the people that have git commit signatures.
113 X: Files and directories that are NOT maintained, same rules as F:
114 Files exclusions are tested before file matches.
115 Can be useful for excluding a specific subdirectory, for instance:
118 matches all files in and below net excluding net/ipv6/
119 K: Keyword perl extended regex pattern to match content in a
120 patch or file. For instance:
122 matches patches or files that contain "of_get_profile"
123 K: \b(printk|pr_(info|err))\b
124 matches patches or files that contain one or more of the words
125 printk, pr_info or pr_err
126 One regex pattern per line. Multiple K: lines acceptable.
128 Note: For the hard of thinking, this list is meant to remain in alphabetical
129 order. If you could add yourselves to it in alphabetical order that would be
132 Maintainers List (try to look for most precise areas first)
134 -----------------------------------
137 M: Ronald Minnich <rminnich@gmail.com>
138 M: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
139 R: Philipp Hug <philipp@hug.cx>
144 F: src/mainboard/emulation/*-riscv/
145 F: src/mainboard/sifive/
149 M: Ronald Minnich <rminnich@gmail.com>
150 M: Timothy Pearson <tpearson@raptorengineeringinc.com>
153 F: src/cpu/qemu-power8/
154 F: src/mainboard/emulation/qemu-power8/
157 M: Alexander Couzens <lynxis@fe80.eu>
162 M: Alexander Couzens <lynxis@fe80.eu>
163 M: Patrick Rudolph <siro@das-labor.org>
165 F: src/mainboard/lenovo/
168 M: Patrick Georgi <patrick@georgi.software>
170 F: src/mainboard/getac/p470
172 INTEL PINEVIEW CHIPSET
173 M: Damien Zammit <damien@zamaudio.com>
175 F: src/northbridge/intel/pineview/
177 INTEL D510MO MAINBOARD
178 M: Damien Zammit <damien@zamaudio.com>
180 F: src/mainboard/intel/d510mo
183 M: Damien Zammit <damien@zamaudio.com>
185 F: src/northbridge/intel/x4x/
187 GIGABYTE GA-G41M-ES2L MAINBOARD
188 M: Damien Zammit <damien@zamaudio.com>
190 F: src/mainboard/gigabyte/ga-g41m-es2l
192 GIGABYTE GA-H61M-S2PV MAINBOARD
193 M: Angel Pons <th3fanbus@gmail.com>
195 F: src/mainboard/gigabyte/ga-h61m-s2pv
197 GOOGLE PANTHER MAINBOARD
198 M: Stefan Reinauer <stefan.reinauer@coreboot.org>
200 F: src/mainboard/google/panther/
202 GOOGLE MAINBOARDS (Intel-based, legacy/inactive)
203 M: Matt DeVillier <MrChromebox@gmail.com>
205 F: src/mainboard/google/auron/
206 F: src/mainboard/google/beltino/
207 F: src/mainboard/google/butterfly/
208 F: src/mainboard/google/cyan/
209 F: src/mainboard/google/glados/
210 F: src/mainboard/google/jecht/
211 F: src/mainboard/google/link/
212 F: src/mainboard/google/parrot/
213 F: src/mainboard/google/slippy/
214 F: src/mainboard/google/stout/
217 M: Philipp Deppenwiese <zaolin.daisuki@gmail.com>
218 M: Patrick Rudolph <patrick.rudolph@9elements.com>
220 F: src/mainboard/ocp/wedge100s/
221 F: src/mainboard/ocp/monolake/
223 OPENCELLULAR MAINBOARDS
224 M: Philipp Deppenwiese <zaolin.daisuki@gmail.com>
225 M: Patrick Rudolph <patrick.rudolph@9elements.com>
227 F: src/mainboard/opencellular/rotundu/
228 F: src/mainboard/opencellular/elgon/
231 M: Matt DeVillier <matt.devillier@puri.sm>
233 F: src/mainboard/purism
235 SAMSUNG CHROMEOS MAINBOARDS
236 M: Matt DeVillier <MrChromebox@gmail.com>
238 F: src/mainboard/samsung/lumpy/
239 F: src/mainboard/samsung/stumpy/
241 INTEL MINNOWBOARD MAX MAINBOARD
242 M: Huang Jin <huang.jin@intel.com>
243 M: York Yang <york.yang@intel.com>
245 F: src/mainboard/intel/minnowmax/
247 INTEL FSP BAYTRAIL CHIP & CRBs
248 M: Huang Jin <huang.jin@intel.com>
249 M: York Yang <york.yang@intel.com>
250 M: Philipp Deppenwiese <zaolin.daisuki@gmail.com>
252 F: src/soc/intel/fsp_baytrail/
253 F: src/vendorcode/intel/fsp1_0/baytrail/
254 F: src/mainboard/intel/bakersport_fsp/
255 F: src/mainboard/intel/bayleybay_fsp/
257 INTEL FSP BROADWELL-DE SOC & CRB
258 M: York Yang <york.yang@intel.com>
259 M: Philipp Deppenwiese <zaolin.daisuki@gmail.com>
261 F: src/soc/intel/fsp_broadwell_de/
262 F: src/vendorcode/intel/fsp1_0/broadwell_de/
263 F: src/mainboard/intel/camelbackmountain_fsp/
265 INTEL FSP DENVERTON-NS SOC & HARCUVAR CRB
266 M: Vanessa Eusebio <vanessa.f.eusebio@intel.com>
267 M: David Guckian <david.guckian@intel.com>
269 F: src/mainboard/intel/harcuvar/
270 F: src/soc/intel/denverton_ns/
271 F: src/vendorcode/intel/fsp/fsp2_0/denverton_ns/
273 FSP 1.0 RANGELEY & CRB
274 M: David Guckian <david.guckian@intel.com>
275 M: Fei Wang <fei.z.wang@intel.com>
277 F: src/cpu/intel/fsp_model_406dx/
278 F: src/northbridge/intel/fsp_rangeley/
279 F: src/southbridge/intel/fsp_rangeley/
280 F: src/vendorcode/intel/fsp1_0/rangeley/
281 F: src/mainboard/intel/mohonpeak/
284 M: Huang Jin <huang.jin@intel.com>
285 M: York Yang <york.yang@intel.com>
286 M: Philipp Deppenwiese <zaolin.daisuki@gmail.com>
288 F: src/drivers/intel/fsp1_0/
289 F: src/vendorcode/intel/fsp1_0/broadwell_de/
292 M: Lee Leahy <leroy.p.leahy@intel.com>
293 M: Huang Jin <huang.jin@intel.com>
294 M: York Yang <york.yang@intel.com>
296 F: src/drivers/intel/fsp1_1/
299 M: Andrey Petrov <andrey.petrov@gmail.com>
301 F: src/drivers/intel/fsp2_0/
303 INTEL STRAGO MAINBOARD
304 M: Hannah Williams <hannah.williams@intel.com>
306 F: /src/mainboard/intel/strago/
309 M: Piotr Król <piotr.krol@3mdeb.com>
310 M: Michał Żygowski <michal.zygowski@3mdeb.com>
311 M: Frans Hendriks <fhendriks@eltan.com>
313 F: /src/soc/intel/braswell
314 F: /src/vendorcode/intel/fsp/fsp1_1/braswell
317 M: Andrey Petrov <andrey.petrov@gmail.com>
319 F: src/soc/intel/apollolake/
321 ASROCK G41C-GS MAINBOARD & VARIANTS
322 M: Angel Pons <th3fanbus@gmail.com>
324 F: src/mainboard/asrock/g41c-gs/
326 ASROCK H81M-HDS MAINBOARD
327 M: Tristan Corrick <tristan@corrick.kiwi>
329 F: src/mainboard/asrock/h81m-hds/
331 ASUS KFSN4-DRE & KFSN4-DRE_K8 MAINBOARDS
332 M: Timothy Pearson <tpearson@raptorengineeringinc.com>
334 F: src/mainboard/asus/kfsn4-dre/
335 F: src/mainboard/asus/kfsn4-dre_k8/
337 ASUS KCMA-D8 MAINBOARD
338 M: Timothy Pearson <tpearson@raptorengineeringinc.com>
340 F: src/mainboard/asus/kcma-d8/
342 ASUS KGPE-D16 MAINBOARD
343 M: Timothy Pearson <tpearson@raptorengineeringinc.com>
345 F: src/mainboard/asus/kgpe-d16/
347 ASUS MAXIMUS IV GENE-Z MAINBOARD
348 M: Tristan Corrick <tristan@corrick.kiwi>
350 F: src/mainboard/asus/maximus_iv_gene-z/
352 ASUS P5QC PRO MAINBOARD & VARIANTS
353 M: Angel Pons <th3fanbus@gmail.com>
355 F: src/mainboard/asus/p5qc/
357 ASUS P8H61-M LX MAINBOARD
358 M: Tristan Corrick <tristan@corrick.kiwi>
360 F: src/mainboard/asus/p8h61-m_lx/
362 ASUS P8H61-M PRO MAINBOARD
363 M: Angel Pons <th3fanbus@gmail.com>
365 F: src/mainboard/asus/p8h61-m_pro/
367 PC ENGINES ALL MAINBOARDS
368 M: Piotr Król <piotr.krol@3mdeb.com>
369 M: Michał Żygowski <michal.zygowski@3mdeb.com>
371 F: src/mainboard/pcengines/
373 SIEMENS MC_xxxx MAINBOARDS
374 M: Werner Zeh <werner.zeh@siemens.com>
376 F: src/mainboard/siemens/mc_apl1/
377 F: src/mainboard/siemens/mc_bdx1/
378 F: src/mainboard/siemens/mc_tcu3/
380 SUPERMICRO X10SLM+-F MAINBOARD
381 M: Tristan Corrick <tristan@corrick.kiwi>
383 F: src/mainboard/supermicro/x10slm-f/
385 FACEBOOK FBG1701 MAINBOARD
386 M: Frans Hendriks <fhendriks@eltan.com>
387 M: Wim Vervoorn <wvervoorn@eltan.com>
389 F: src/mainboard/facebook/fbg1701/
391 AMD FAMILY10H & FAMILY15H (NON-AGESA) CPUS & NORTHBRIDGE
392 M: Timothy Pearson <tpearson@raptorengineeringinc.com>
394 F: src/cpu/amd/family_10h-family_15h/
395 F: src/northbridge/amd/amdfam10/
396 F: src/northbridge/amd/amdmct/
397 F: src/northbridge/amd/amdht/
399 AMD SB700 (NON-CIMX) SOUTHBRIDGE
400 M: Timothy Pearson <tpearson@raptorengineeringinc.com>
402 F: src/southbridge/amd/sb700/
404 AMD SR5650 SOUTHBRIDGE
405 M: Timothy Pearson <tpearson@raptorengineeringinc.com>
407 F: src/southbridge/amd/sr5650/
409 ASPEED AST2050 DRIVER & COMMON CODE
410 M: Timothy Pearson <tpearson@raptorengineeringinc.com>
412 F: src/drivers/aspeed/common/
413 F: src/drivers/aspeed/ast2050/
417 F: src/drivers/ati/mach64/
420 M: Patrick Georgi <patrick@georgi-clan.de>
421 M: Martin Roth <gaumless@gmail.com>
427 F: src/arch/x86/acpi/
431 M: Julius Werner <jwerner@chromium.org>
433 F: src/commonlib/lz4*
434 F: payloads/libpayload/liblz4/
435 F: util/cbfstool/lz4/
438 M: Julius Werner <jwerner@chromium.org>
450 F: src/cpu/allwinner/
456 F: util/arm_boot_tools/
471 F: src/include/cpu/x86/
474 M: Patrick Rudolph <siro@das-labor.org>
476 F: src/vendorcode/intel/
478 F: src/northbridge/intel/
479 F: src/southbridge/intel/
481 F: src/drivers/intel/
482 F: src/include/cpu/intel/
485 F: src/vendorcode/amd/
487 F: src/northbridge/amd/
488 F: src/southbridge/amd/
489 F: src/include/cpu/amd/
493 F: src/northbridge/via/
494 F: src/southbridge/via/
497 M: Patrick Georgi <patrick@georgi-clan.de>
498 M: Martin Roth <gaumless@gmail.com>
503 M: Stefan Reinauer <stefan.reinauer@coreboot.org>
507 M: Philipp Deppenwiese <zaolin.daisuki@gmail.com>
511 M: Nicola Corna <nicola@corna.info>
512 W: https://github.com/corna/me_cleaner
517 M: Stefan Reinauer <stefan.reinauer@coreboot.org>
521 M: Patrick Georgi <patrick@georgi-clan.de>
522 M: Martin Roth <gaumless@gmail.com>
526 F: src/include/kconfig.h
533 F: util/board_status/
540 F: src/vendorcode/google/chromeos/
542 F: src/include/tpm_lite/
546 F: src/include/device/
547 F: src/include/cpu/cpu.h
549 OPTION ROM EXECUTION & X86EMU
553 F: src/include/cbfs.h
554 F: src/include/cbfs_serialized.h
558 F: src/include/cbmem.h
559 F: src/include/cbmem_id.h
564 F: src/include/console/
570 F: payloads/nvramcui/
573 F: payloads/libpayload/
579 F: payloads/coreinfo/
581 EXTERNAL PAYLOADS INTEGRATION
582 M: Stefan Reinauer <stefan.reinauer@coreboot.org>
583 M: Martin Roth <gaumless@gmail.com>
586 LINUXBOOT PAYLOAD INTEGRATION
587 M: Philipp Deppenwiese <zaolin.daisuki@gmail.com>
588 M: Marcello Sylvester Bauer <info@marcellobauer.com>
590 F: payloads/external/LinuxBoot
593 M: Aaron Durbin <adurbin@chromium.org>
594 F: src/security/vboot/
597 M: Philipp Deppenwiese <zaolin.daisuki@gmail.com>
599 F: src/drivers/*/tpm/
600 F: src/security/vboot/vboot_crtm.*
604 M: Martin Roth <gaumless@gmail.com>
615 SUPERIOS & SUPERIOTOOL
616 M: Felix Held <felix-coreboot@felixheld.de>
622 M: Julius Werner <jwerner@chromium.org>
627 MISSING: TIMERS / DELAYS
637 MISSING: DMP / QEMU-X86
643 # *** Infrastructure Owners***
644 # This is intended to let people know who they should contact for issues with various infrastructure pieces.
646 # Owners: Stefan, Patrick
650 # Owners: Stefan, Patrick
654 # Owners: Martin, Philipp
655 # Backups: Patrick, Stefan
657 # Documentation Website
658 # Owners: Patrick, Philipp
662 # Owners: Stefan, Patrick
666 # Owners: Stefan, Patrick
670 # Owners: Patrick, Martin
678 # Owners: Stefan, Patrick
681 # Software Freedom Conservancy
682 # Main contact: Martin
683 # “Official” contact: Stefan