Lines Matching full:board

4 Adding a new board to LinuxSH
18 of the board-specific code (with the exception of stboards) ended up
19 in arch/sh/kernel/ directly, with board-specific headers ending up in
20 include/asm-sh/. For the new kernel, things are broken out by board type,
24 Board-specific code::
31     |           |   `-- board-specific files
33     |           |   `-- board-specific files
40 	    |   `-- board-specific headers
42 	    |   `-- board-specific headers
57 board-specific headers. Thus, include/asm-sh/hd64461 is home to all of the
89 2. Adding a New Board
92 The first thing to determine is whether the board you are adding will be
94 share the same board-specific code with minor differences.
97 board in arch/sh/boards/ and adding rules to hook your board in with the
98 build system (more on this in the next section). However, for board families
105 board (if there are going to be more than one). In order to interoperate
107 as the arch/sh/boards/ directory name, though if your board is again part of
112 There are a few things that each board is required to have, both in the
114 explain this, we use some examples for adding an imaginary board. For
116 get_system_type() and platform_setup(). For our imaginary board, this
120     * arch/sh/boards/vapor/setup.c - Setup code for imaginary board
135 	    * this board.
145 Our new imaginary board will also have to tie into the machvec in order for it
155    particularly for allocating out of some board-specific SRAM for DMA
169 If the board-specific definitions are quite minimalistic, as is the case for
170 the vast majority of boards, simply having a single board-specific header is
184    somewhere in the board-specific header. Any boards being ported that still
187  - Add machine vector definitions to the board's setup.c. At a bare minimum,
202 board-specific code is in place, it's time to look at how to get the
218 the board directory as it appears in arch/sh/boards, even if it is in a
220 need to be listed). For our new board, this entry can look like::
236 implicit checks for your board if you need this somewhere throughout the
248 Now all that's left to do is providing a defconfig for your new board. This
249 way, other people who end up with this board can simply use this config
253 Also, as soon as you have copied over a sample .config for your new board
274 which will in turn copy the defconfig for this board, run it through
277 board.