Lines Matching refs:boards

8 for new boards to the LinuxSH port under the new 2.5 and 2.6 kernels. This
27 |       `-- boards
33 |           ... more boards here ...
42 	.. more boards here ...
89 isolated, or whether it will be part of a family of boards that can mostly
93 board in arch/sh/boards/ and adding rules to hook your board in with the
95 it makes more sense to have a common top-level arch/sh/boards/ directory
97 Both the Solution Engine and the hp6xx boards are an example of this.
99 After you have setup your new arch/sh/boards/ directory, remember that you
103 as the arch/sh/boards/ directory name, though if your board is again part of
109 arch/sh/boards and the include/asm-sh/ hierarchy. In order to better
116  * arch/sh/boards/vapor/setup.c - Setup code for imaginary board
150  - Consistent allocators (for boards that need special allocators,
159 unconditionally throughout most of the tree. Some boards have incredibly
166 the vast majority of boards, simply having a single board-specific header is
180    somewhere in the board-specific header. Any boards being ported that still
191  - finally add a file arch/sh/boards/vapor/io.c, which contains definitions of
212 next, this has to be added into arch/sh/Makefile. All boards require a
214 the board directory as it appears in arch/sh/boards, even if it is in a
215 sub-directory (in which case, all parent directories below arch/sh/boards/
220 provided that we've placed everything in the arch/sh/boards/vapor/ directory.
224 boards belonging to a common family), then the directory name needs to be
226 Solution Engine and hp6xx boards, so see these for an example.