׍sphinx.addnodesdocument)}( rawsourcechildren]( translations LanguagesNode)}(hhh](h pending_xref)}(hhh]docutils.nodesTextChinese (Simplified)}parenthsba attributes}(ids]classes]names]dupnames]backrefs] refdomainstdreftypedoc reftarget'/translations/zh_CN/arch/sh/new-machinemodnameN classnameN refexplicitutagnamehhh ubh)}(hhh]hChinese (Traditional)}hh2sbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget'/translations/zh_TW/arch/sh/new-machinemodnameN classnameN refexplicituh1hhh ubh)}(hhh]hItalian}hhFsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget'/translations/it_IT/arch/sh/new-machinemodnameN classnameN refexplicituh1hhh ubh)}(hhh]hJapanese}hhZsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget'/translations/ja_JP/arch/sh/new-machinemodnameN classnameN refexplicituh1hhh ubh)}(hhh]hKorean}hhnsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget'/translations/ko_KR/arch/sh/new-machinemodnameN classnameN refexplicituh1hhh ubh)}(hhh]hSpanish}hhsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget'/translations/sp_SP/arch/sh/new-machinemodnameN classnameN refexplicituh1hhh ubeh}(h]h ]h"]h$]h&]current_languageEnglishuh1h hh _documenthsourceNlineNubhcomment)}(h SPDX-License-Identifier: GPL-2.0h]h SPDX-License-Identifier: GPL-2.0}hhsbah}(h]h ]h"]h$]h&] xml:spacepreserveuh1hhhhhhA/var/lib/git/docbuild/linux/Documentation/arch/sh/new-machine.rsthKubhsection)}(hhh](htitle)}(hAdding a new board to LinuxSHh]hAdding a new board to LinuxSH}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhhhhhKubh block_quote)}(h!Paul Mundt h]h paragraph)}(h Paul Mundt h](h Paul Mundt <}(hhhhhNhNubh reference)}(hlethal@linux-sh.orgh]hlethal@linux-sh.org}(hhhhhNhNubah}(h]h ]h"]h$]h&]refurimailto:lethal@linux-sh.orguh1hhhubh>}(hhhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKhhubah}(h]h ]h"]h$]h&]uh1hhhhKhhhhubh)}(hThis document attempts to outline what steps are necessary to add support for new boards to the LinuxSH port under the new 2.5 and 2.6 kernels. This also attempts to outline some of the noticeable changes between the 2.4 and the 2.5/2.6 SH backend.h]hThis document attempts to outline what steps are necessary to add support for new boards to the LinuxSH port under the new 2.5 and 2.6 kernels. This also attempts to outline some of the noticeable changes between the 2.4 and the 2.5/2.6 SH backend.}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK hhhhubh)}(hhh](h)}(h1. New Directory Structureh]h1. New Directory Structure}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhj hhhhhKubh)}(hXThe first thing to note is the new directory structure. Under 2.4, most of the board-specific code (with the exception of stboards) ended up in arch/sh/kernel/ directly, with board-specific headers ending up in include/asm-sh/. For the new kernel, things are broken out by board type, companion chip type, and CPU type. Looking at a tree view of this directory hierarchy looks like the following:h]hXThe first thing to note is the new directory structure. Under 2.4, most of the board-specific code (with the exception of stboards) ended up in arch/sh/kernel/ directly, with board-specific headers ending up in include/asm-sh/. For the new kernel, things are broken out by board type, companion chip type, and CPU type. Looking at a tree view of this directory hierarchy looks like the following:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj hhubh)}(hBoard-specific code::h]hBoard-specific code:}(hj(hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj hhubh literal_block)}(hX. |-- arch | `-- sh | `-- boards | |-- adx | | `-- board-specific files | |-- bigsur | | `-- board-specific files | | | ... more boards here ... | `-- include `-- asm-sh |-- adx | `-- board-specific headers |-- bigsur | `-- board-specific headers | .. more boards here ...h]hX. |-- arch | `-- sh | `-- boards | |-- adx | | `-- board-specific files | |-- bigsur | | `-- board-specific files | | | ... more boards here ... | `-- include `-- asm-sh |-- adx | `-- board-specific headers |-- bigsur | `-- board-specific headers | .. more boards here ...}hj8sbah}(h]h ]h"]h$]h&]hhuh1j6hhhKhj hhubh)}(hNext, for companion chips::h]hNext, for companion chips:}(hjFhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK.hj hhubj7)}(h. `-- arch `-- sh `-- cchips `-- hd6446x `-- hd64461 `-- cchip-specific filesh]h. `-- arch `-- sh `-- cchips `-- hd6446x `-- hd64461 `-- cchip-specific files}hjTsbah}(h]h ]h"]h$]h&]hhuh1j6hhhK0hj hhubh)}(h... and so on. Headers for the companion chips are treated the same way as board-specific headers. Thus, include/asm-sh/hd64461 is home to all of the hd64461-specific headers.h]h... and so on. Headers for the companion chips are treated the same way as board-specific headers. Thus, include/asm-sh/hd64461 is home to all of the hd64461-specific headers.}(hjbhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK8hj hhubh)}(h0Finally, CPU family support is also abstracted::h]h/Finally, CPU family support is also abstracted:}(hjphhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj hhubh)}(hIt should be noted that CPU subtypes are _not_ abstracted. Thus, these still need to be dealt with by the CPU family specific code.h]hIt should be noted that CPU subtypes are _not_ abstracted. Thus, these still need to be dealt with by the CPU family specific code.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKVhj hhubeh}(h]new-directory-structureah ]h"]1. new directory structureah$]h&]uh1hhhhhhhhKubh)}(hhh](h)}(h2. Adding a New Boardh]h2. Adding a New Board}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhKZubh)}(hThe first thing to determine is whether the board you are adding will be isolated, or whether it will be part of a family of boards that can mostly share the same board-specific code with minor differences.h]hThe first thing to determine is whether the board you are adding will be isolated, or whether it will be part of a family of boards that can mostly share the same board-specific code with minor differences.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK\hjhhubh)}(hXIn the first case, this is just a matter of making a directory for your board in arch/sh/boards/ and adding rules to hook your board in with the build system (more on this in the next section). However, for board families it makes more sense to have a common top-level arch/sh/boards/ directory and then populate that with sub-directories for each member of the family. Both the Solution Engine and the hp6xx boards are an example of this.h]hXIn the first case, this is just a matter of making a directory for your board in arch/sh/boards/ and adding rules to hook your board in with the build system (more on this in the next section). However, for board families it makes more sense to have a common top-level arch/sh/boards/ directory and then populate that with sub-directories for each member of the family. Both the Solution Engine and the hp6xx boards are an example of this.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK`hjhhubh)}(hXAfter you have setup your new arch/sh/boards/ directory, remember that you should also add a directory in include/asm-sh for headers localized to this board (if there are going to be more than one). In order to interoperate seamlessly with the build system, it's best to have this directory the same as the arch/sh/boards/ directory name, though if your board is again part of a family, the build system has ways of dealing with this (via incdir-y overloading), and you can feel free to name the directory after the family member itself.h]hXAfter you have setup your new arch/sh/boards/ directory, remember that you should also add a directory in include/asm-sh for headers localized to this board (if there are going to be more than one). In order to interoperate seamlessly with the build system, it’s best to have this directory the same as the arch/sh/boards/ directory name, though if your board is again part of a family, the build system has ways of dealing with this (via incdir-y overloading), and you can feel free to name the directory after the family member itself.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKghjhhubh)}(hX|There are a few things that each board is required to have, both in the arch/sh/boards and the include/asm-sh/ hierarchy. In order to better explain this, we use some examples for adding an imaginary board. For setup code, we're required at the very least to provide definitions for get_system_type() and platform_setup(). For our imaginary board, this might look something like::h]hX}There are a few things that each board is required to have, both in the arch/sh/boards and the include/asm-sh/ hierarchy. In order to better explain this, we use some examples for adding an imaginary board. For setup code, we’re required at the very least to provide definitions for get_system_type() and platform_setup(). For our imaginary board, this might look something like:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKphjhhubj7)}(hX/* * arch/sh/boards/vapor/setup.c - Setup code for imaginary board */ #include const char *get_system_type(void) { return "FooTech Vaporboard"; } int __init platform_setup(void) { /* * If our hardware actually existed, we would do real * setup here. Though it's also sane to leave this empty * if there's no real init work that has to be done for * this board. */ /* Start-up imaginary PCI ... */ /* And whatever else ... */ return 0; }h]hX/* * arch/sh/boards/vapor/setup.c - Setup code for imaginary board */ #include const char *get_system_type(void) { return "FooTech Vaporboard"; } int __init platform_setup(void) { /* * If our hardware actually existed, we would do real * setup here. Though it's also sane to leave this empty * if there's no real init work that has to be done for * this board. */ /* Start-up imaginary PCI ... */ /* And whatever else ... */ return 0; }}hjsbah}(h]h ]h"]h$]h&]hhuh1j6hhhKwhjhhubh)}(h`Our new imaginary board will also have to tie into the machvec in order for it to be of any use.h]h`Our new imaginary board will also have to tie into the machvec in order for it to be of any use.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubh)}(h3machvec functions fall into a number of categories:h]h3machvec functions fall into a number of categories:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubh)}(hXV- I/O functions to IO memory (inb etc) and PCI/main memory (readb etc). - I/O mapping functions (ioport_map, ioport_unmap, etc). - a 'heartbeat' function. - PCI and IRQ initialization routines. - Consistent allocators (for boards that need special allocators, particularly for allocating out of some board-specific SRAM for DMA handles). h]h bullet_list)}(hhh](h list_item)}(hEI/O functions to IO memory (inb etc) and PCI/main memory (readb etc).h]h)}(hj"h]hEI/O functions to IO memory (inb etc) and PCI/main memory (readb etc).}(hj$hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj ubah}(h]h ]h"]h$]h&]uh1jhjubj)}(h6I/O mapping functions (ioport_map, ioport_unmap, etc).h]h)}(hj9h]h6I/O mapping functions (ioport_map, ioport_unmap, etc).}(hj;hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj7ubah}(h]h ]h"]h$]h&]uh1jhjubj)}(ha 'heartbeat' function.h]h)}(hjPh]ha ‘heartbeat’ function.}(hjRhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjNubah}(h]h ]h"]h$]h&]uh1jhjubj)}(h$PCI and IRQ initialization routines.h]h)}(hjgh]h$PCI and IRQ initialization routines.}(hjihhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjeubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hConsistent allocators (for boards that need special allocators, particularly for allocating out of some board-specific SRAM for DMA handles). h]h)}(hConsistent allocators (for boards that need special allocators, particularly for allocating out of some board-specific SRAM for DMA handles).h]hConsistent allocators (for boards that need special allocators, particularly for allocating out of some board-specific SRAM for DMA handles).}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj|ubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]bullet-uh1jhhhKhjubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubh)}(hThere are machvec functions added and removed over time, so always be sure to consult include/asm-sh/machvec.h for the current state of the machvec.h]hThere are machvec functions added and removed over time, so always be sure to consult include/asm-sh/machvec.h for the current state of the machvec.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubh)}(hXPThe kernel will automatically wrap in generic routines for undefined function pointers in the machvec at boot time, as machvec functions are referenced unconditionally throughout most of the tree. Some boards have incredibly sparse machvecs (such as the dreamcast and sh03), whereas others must define virtually everything (rts7751r2d).h]hXPThe kernel will automatically wrap in generic routines for undefined function pointers in the machvec at boot time, as machvec functions are referenced unconditionally throughout most of the tree. Some boards have incredibly sparse machvecs (such as the dreamcast and sh03), whereas others must define virtually everything (rts7751r2d).}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubh)}(hGAdding a new machine is relatively trivial (using vapor as an example):h]hGAdding a new machine is relatively trivial (using vapor as an example):}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubh)}(hIf the board-specific definitions are quite minimalistic, as is the case for the vast majority of boards, simply having a single board-specific header is sufficient.h]hIf the board-specific definitions are quite minimalistic, as is the case for the vast majority of boards, simply having a single board-specific header is sufficient.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubh)}(hX- add a new file include/asm-sh/vapor.h which contains prototypes for any machine specific IO functions prefixed with the machine name, for example vapor_inb. These will be needed when filling out the machine vector. Note that these prototypes are generated automatically by setting __IO_PREFIX to something sensible. A typical example would be:: #define __IO_PREFIX vapor #include somewhere in the board-specific header. Any boards being ported that still have a legacy io.h should remove it entirely and switch to the new model. - Add machine vector definitions to the board's setup.c. At a bare minimum, this must be defined as something like:: struct sh_machine_vector mv_vapor __initmv = { .mv_name = "vapor", }; ALIAS_MV(vapor) - finally add a file arch/sh/boards/vapor/io.c, which contains definitions of the machine specific io functions (if there are enough to warrant it). h]j)}(hhh](j)}(hX1add a new file include/asm-sh/vapor.h which contains prototypes for any machine specific IO functions prefixed with the machine name, for example vapor_inb. These will be needed when filling out the machine vector. Note that these prototypes are generated automatically by setting __IO_PREFIX to something sensible. A typical example would be:: #define __IO_PREFIX vapor #include somewhere in the board-specific header. Any boards being ported that still have a legacy io.h should remove it entirely and switch to the new model. h](h)}(hadd a new file include/asm-sh/vapor.h which contains prototypes for any machine specific IO functions prefixed with the machine name, for example vapor_inb. These will be needed when filling out the machine vector.h]hadd a new file include/asm-sh/vapor.h which contains prototypes for any machine specific IO functions prefixed with the machine name, for example vapor_inb. These will be needed when filling out the machine vector.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubh)}(hNote that these prototypes are generated automatically by setting __IO_PREFIX to something sensible. A typical example would be::h]hNote that these prototypes are generated automatically by setting __IO_PREFIX to something sensible. A typical example would be:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubj7)}(h5#define __IO_PREFIX vapor #include h]h5#define __IO_PREFIX vapor #include }hjsbah}(h]h ]h"]h$]h&]hhuh1j6hhhKhjubh)}(hsomewhere in the board-specific header. Any boards being ported that still have a legacy io.h should remove it entirely and switch to the new model.h]hsomewhere in the board-specific header. Any boards being ported that still have a legacy io.h should remove it entirely and switch to the new model.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hAdd machine vector definitions to the board's setup.c. At a bare minimum, this must be defined as something like:: struct sh_machine_vector mv_vapor __initmv = { .mv_name = "vapor", }; ALIAS_MV(vapor) h](h)}(hrAdd machine vector definitions to the board's setup.c. At a bare minimum, this must be defined as something like::h]hsAdd machine vector definitions to the board’s setup.c. At a bare minimum, this must be defined as something like:}(hj'hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj#ubj7)}(h]struct sh_machine_vector mv_vapor __initmv = { .mv_name = "vapor", }; ALIAS_MV(vapor)h]h]struct sh_machine_vector mv_vapor __initmv = { .mv_name = "vapor", }; ALIAS_MV(vapor)}hj5sbah}(h]h ]h"]h$]h&]hhuh1j6hhhKhj#ubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hfinally add a file arch/sh/boards/vapor/io.c, which contains definitions of the machine specific io functions (if there are enough to warrant it). h]h)}(hfinally add a file arch/sh/boards/vapor/io.c, which contains definitions of the machine specific io functions (if there are enough to warrant it).h]hfinally add a file arch/sh/boards/vapor/io.c, which contains definitions of the machine specific io functions (if there are enough to warrant it).}(hjMhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjIubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]jjuh1jhhhKhjubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubeh}(h]adding-a-new-boardah ]h"]2. adding a new boardah$]h&]uh1hhhhhhhhKZubh)}(hhh](h)}(h 3. Hooking into the Build Systemh]h 3. Hooking into the Build System}(hjxhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjuhhhhhKubh)}(hNow that we have the corresponding directories setup, and all of the board-specific code is in place, it's time to look at how to get the whole mess to fit into the build system.h]hNow that we have the corresponding directories setup, and all of the board-specific code is in place, it’s time to look at how to get the whole mess to fit into the build system.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjuhhubh)}(hLarge portions of the build system are now entirely dynamic, and merely require the proper entry here and there in order to get things done.h]hLarge portions of the build system are now entirely dynamic, and merely require the proper entry here and there in order to get things done.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjuhhubh)}(h[The first thing to do is to add an entry to arch/sh/Kconfig, under the "System type" menu::h]h^The first thing to do is to add an entry to arch/sh/Kconfig, under the “System type” menu:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjuhhubj7)}(hoconfig SH_VAPOR bool "Vapor" help select Vapor if configuring for a FooTech Vaporboard.h]hoconfig SH_VAPOR bool "Vapor" help select Vapor if configuring for a FooTech Vaporboard.}hjsbah}(h]h ]h"]h$]h&]hhuh1j6hhhKhjuhhubh)}(hXdnext, this has to be added into arch/sh/Makefile. All boards require a machdir-y entry in order to be built. This entry needs to be the name of the board directory as it appears in arch/sh/boards, even if it is in a sub-directory (in which case, all parent directories below arch/sh/boards/ need to be listed). For our new board, this entry can look like::h]hXcnext, this has to be added into arch/sh/Makefile. All boards require a machdir-y entry in order to be built. This entry needs to be the name of the board directory as it appears in arch/sh/boards, even if it is in a sub-directory (in which case, all parent directories below arch/sh/boards/ need to be listed). For our new board, this entry can look like:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjuhhubj7)}(h$machdir-$(CONFIG_SH_VAPOR) += vaporh]h$machdir-$(CONFIG_SH_VAPOR) += vapor}hjsbah}(h]h ]h"]h$]h&]hhuh1j6hhhKhjuhhubh)}(hMprovided that we've placed everything in the arch/sh/boards/vapor/ directory.h]hOprovided that we’ve placed everything in the arch/sh/boards/vapor/ directory.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjuhhubh)}(hXeNext, the build system assumes that your include/asm-sh directory will also be named the same. If this is not the case (as is the case with multiple boards belonging to a common family), then the directory name needs to be implicitly appended to incdir-y. The existing code manages this for the Solution Engine and hp6xx boards, so see these for an example.h]hXeNext, the build system assumes that your include/asm-sh directory will also be named the same. If this is not the case (as is the case with multiple boards belonging to a common family), then the directory name needs to be implicitly appended to incdir-y. The existing code manages this for the Solution Engine and hp6xx boards, so see these for an example.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjuhhubh)}(hXOnce that is taken care of, it's time to add an entry for the mach type. This is done by adding an entry to the end of the arch/sh/tools/mach-types list. The method for doing this is self explanatory, and so we won't waste space restating it here. After this is done, you will be able to use implicit checks for your board if you need this somewhere throughout the common code, such as::h]hXOnce that is taken care of, it’s time to add an entry for the mach type. This is done by adding an entry to the end of the arch/sh/tools/mach-types list. The method for doing this is self explanatory, and so we won’t waste space restating it here. After this is done, you will be able to use implicit checks for your board if you need this somewhere throughout the common code, such as:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjuhhubj7)}(h]/* Make sure we're on the FooTech Vaporboard */ if (!mach_is_vapor()) return -ENODEV;h]h]/* Make sure we're on the FooTech Vaporboard */ if (!mach_is_vapor()) return -ENODEV;}hjsbah}(h]h ]h"]h$]h&]hhuh1j6hhhKhjuhhubh)}(hXalso note that the mach_is_boardname() check will be implicitly forced to lowercase, regardless of the fact that the mach-types entries are all uppercase. You can read the script if you really care, but it's pretty ugly, so you probably don't want to do that.h]hXalso note that the mach_is_boardname() check will be implicitly forced to lowercase, regardless of the fact that the mach-types entries are all uppercase. You can read the script if you really care, but it’s pretty ugly, so you probably don’t want to do that.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjuhhubh)}(hNow all that's left to do is providing a defconfig for your new board. This way, other people who end up with this board can simply use this config for reference instead of trying to guess what settings are supposed to be used on it.h]hNow all that’s left to do is providing a defconfig for your new board. This way, other people who end up with this board can simply use this config for reference instead of trying to guess what settings are supposed to be used on it.}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjuhhubh)}(hAlso, as soon as you have copied over a sample .config for your new board (assume arch/sh/configs/vapor_defconfig), you can also use this directly as a build target, and it will be implicitly listed as such in the help text.h]hAlso, as soon as you have copied over a sample .config for your new board (assume arch/sh/configs/vapor_defconfig), you can also use this directly as a build target, and it will be implicitly listed as such in the help text.}(hj.hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjuhhubh)}(hELooking at the 'make help' output, you should now see something like:h]hILooking at the ‘make help’ output, you should now see something like:}(hj<hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjuhhubh)}(h#Architecture specific targets (sh):h]h#Architecture specific targets (sh):}(hjJhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjuhhubh)}(hX======================= ============================================= zImage Compressed kernel image (arch/sh/boot/zImage) adx_defconfig Build for adx cqreek_defconfig Build for cqreek dreamcast_defconfig Build for dreamcast ... vapor_defconfig Build for vapor ======================= ============================================= h]htable)}(hhh]htgroup)}(hhh](hcolspec)}(hhh]h}(h]h ]h"]h$]h&]colwidthKuh1jfhjcubjg)}(hhh]h}(h]h ]h"]h$]h&]colwidthK-uh1jfhjcubhtbody)}(hhh](hrow)}(hhh](hentry)}(hhh]h)}(hzImageh]hzImage}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(h-Compressed kernel image (arch/sh/boot/zImage)h]h-Compressed kernel image (arch/sh/boot/zImage)}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhj~ubj)}(hhh](j)}(hhh]h)}(h adx_defconfigh]h adx_defconfig}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(h Build for adxh]h Build for adx}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhj~ubj)}(hhh](j)}(hhh]h)}(hcqreek_defconfigh]hcqreek_defconfig}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(hBuild for cqreekh]hBuild for cqreek}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj ubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhj~ubj)}(hhh](j)}(hhh]h)}(hdreamcast_defconfigh]hdreamcast_defconfig}(hj0hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM hj-ubah}(h]h ]h"]h$]h&]uh1jhj*ubj)}(hhh]h)}(hBuild for dreamcasth]hBuild for dreamcast}(hjGhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM hjDubah}(h]h ]h"]h$]h&]uh1jhj*ubeh}(h]h ]h"]h$]h&]uh1jhj~ubj)}(hhh](j)}(hhh]h)}(h...h]h...}(hjghhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM hjdubah}(h]h ]h"]h$]h&]uh1jhjaubj)}(hhh]h}(h]h ]h"]h$]h&]uh1jhjaubeh}(h]h ]h"]h$]h&]uh1jhj~ubj)}(hhh](j)}(hhh]h)}(hvapor_defconfigh]hvapor_defconfig}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM hjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(hBuild for vaporh]hBuild for vapor}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM hjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhj~ubeh}(h]h ]h"]h$]h&]uh1j|hjcubeh}(h]h ]h"]h$]h&]colsKuh1jahj^ubah}(h]h ]h"]h$]h&]uh1j\hjXubah}(h]h ]h"]h$]h&]uh1hhhhMhjuhhubh)}(hwhich then allows you to do::h]hwhich then allows you to do:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjuhhubj7)}(h?$ make ARCH=sh CROSS_COMPILE=sh4-linux- vapor_defconfig vmlinuxh]h?$ make ARCH=sh CROSS_COMPILE=sh4-linux- vapor_defconfig vmlinux}hjsbah}(h]h ]h"]h$]h&]hhuh1j6hhhMhjuhhubh)}(hwhich will in turn copy the defconfig for this board, run it through oldconfig (prompting you for any new options since the time of creation), and start you on your way to having a functional kernel for your new board.h]hwhich will in turn copy the defconfig for this board, run it through oldconfig (prompting you for any new options since the time of creation), and start you on your way to having a functional kernel for your new board.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjuhhubeh}(h]hooking-into-the-build-systemah ]h"] 3. hooking into the build systemah$]h&]uh1hhhhhhhhKubeh}(h]adding-a-new-board-to-linuxshah ]h"]adding a new board to linuxshah$]h&]uh1hhhhhhhhKubeh}(h]h ]h"]h$]h&]sourcehuh1hcurrent_sourceN current_lineNsettingsdocutils.frontendValues)}(hN generatorN datestampN source_linkN source_urlN toc_backlinksjfootnote_backlinksK sectnum_xformKstrip_commentsNstrip_elements_with_classesN strip_classesN report_levelK halt_levelKexit_status_levelKdebugNwarning_streamN tracebackinput_encoding utf-8-siginput_encoding_error_handlerstrictoutput_encodingutf-8output_encoding_error_handlerj6error_encodingutf-8error_encoding_error_handlerbackslashreplace language_codeenrecord_dependenciesNconfigN id_prefixhauto_id_prefixid dump_settingsNdump_internalsNdump_transformsNdump_pseudo_xmlNexpose_internalsNstrict_visitorN_disable_configN_sourceh _destinationN _config_files]7/var/lib/git/docbuild/linux/Documentation/docutils.confafile_insertion_enabled raw_enabledKline_length_limitM'pep_referencesN pep_base_urlhttps://peps.python.org/pep_file_url_templatepep-%04drfc_referencesN rfc_base_url&https://datatracker.ietf.org/doc/html/ tab_widthKtrim_footnote_reference_spacesyntax_highlightlong smart_quotessmartquotes_locales]character_level_inline_markupdoctitle_xform docinfo_xformKsectsubtitle_xform image_loadinglinkembed_stylesheetcloak_email_addressessection_self_linkenvNubreporterNindirect_targets]substitution_defs}substitution_names}refnames}refids}nameids}(jjjjjrjoj ju nametypes}(jjjrj uh}(jhjj jojjjuu footnote_refs} citation_refs} autofootnotes]autofootnote_refs]symbol_footnotes]symbol_footnote_refs] footnotes] citations]autofootnote_startKsymbol_footnote_startK id_counter collectionsCounter}Rparse_messages]hsystem_message)}(hhh]h)}(heUnexpected possible title overline or transition. Treating it as ordinary text because it's so short.h]hgUnexpected possible title overline or transition. Treating it as ordinary text because it’s so short.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjubah}(h]h ]h"]h$]h&]levelKtypeINFOlineM sourcehuh1jhjdubatransform_messages] transformerN include_log] decorationNhhub.