Lines Matching refs:board

2                 Adding a new board to LinuxSH
16 of the board-specific code (with the exception of stboards) ended up
17 in arch/sh/kernel/ directly, with board-specific headers ending up in
18 include/asm-sh/. For the new kernel, things are broken out by board type,
29 |           |   `-- board-specific files
31 |           |   `-- board-specific files
38         |   `-- board-specific headers
40         |   `-- board-specific headers
54 board-specific headers. Thus, include/asm-sh/hd64461 is home to all of the
88 The first thing to determine is whether the board you are adding will be
90 share the same board-specific code with minor differences.
93 board in arch/sh/boards/ and adding rules to hook your board in with the
94 build system (more on this in the next section). However, for board families
101 board (if there are going to be more than one). In order to interoperate
103 as the arch/sh/boards/ directory name, though if your board is again part of
108 There are a few things that each board is required to have, both in the
110 explain this, we use some examples for adding an imaginary board. For
112 get_system_type() and platform_setup(). For our imaginary board, this
116  * arch/sh/boards/vapor/setup.c - Setup code for imaginary board
132 	 * this board.
149 Our new imaginary board will also have to tie into the machvec in order for it
159    particularly for allocating out of some board-specific SRAM for DMA
173 If the board-specific definitions are quite minimalistic, as is the case for
174 the vast majority of boards, simply having a single board-specific header is
188    somewhere in the board-specific header. Any boards being ported that still
191  - Add machine vector definitions to the board's setup.c. At a bare minimum,
206 board-specific code is in place, it's time to look at how to get the
222 the board directory as it appears in arch/sh/boards, even if it is in a
224 need to be listed). For our new board, this entry can look like:
240 implicit checks for your board if you need this somewhere throughout the
252 Now all that's left to do is providing a defconfig for your new board. This
253 way, other people who end up with this board can simply use this config
257 Also, as soon as you have copied over a sample .config for your new board
275 which will in turn copy the defconfig for this board, run it through
278 board.