Lines Matching refs:boards

10 for new boards to the LinuxSH port under the new 2.5 and 2.6 kernels. This
29     |       `-- boards
35     |           ... more boards here ...
44 	    .. more boards here ...
93 isolated, or whether it will be part of a family of boards that can mostly
97 board in arch/sh/boards/ and adding rules to hook your board in with the
99 it makes more sense to have a common top-level arch/sh/boards/ directory
101 Both the Solution Engine and the hp6xx boards are an example of this.
103 After you have setup your new arch/sh/boards/ directory, remember that you
107 as the arch/sh/boards/ directory name, though if your board is again part of
113 arch/sh/boards and the include/asm-sh/ hierarchy. In order to better
120     * arch/sh/boards/vapor/setup.c - Setup code for imaginary board
154  - Consistent allocators (for boards that need special allocators,
163 unconditionally throughout most of the tree. Some boards have incredibly
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
195  - finally add a file arch/sh/boards/vapor/io.c, which contains definitions of
216 next, this has to be added into arch/sh/Makefile. All boards require a
218 the board directory as it appears in arch/sh/boards, even if it is in a
219 sub-directory (in which case, all parent directories below arch/sh/boards/
224 provided that we've placed everything in the arch/sh/boards/vapor/ directory.
228 boards belonging to a common family), then the directory name needs to be
230 Solution Engine and hp6xx boards, so see these for an example.