Lines Matching refs:sh

5                Paul Mundt <lethal@linux-sh.org>
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,
26 |   `-- sh
36     `-- asm-sh
47     `-- sh
54 board-specific headers. Thus, include/asm-sh/hd64461 is home to all of the
60 |   `-- sh
74     `-- asm-sh
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
99 After you have setup your new arch/sh/boards/ directory, remember that you
100 should also add a directory in include/asm-sh for headers localized to this
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
163 consult include/asm-sh/machvec.h for the current state of the machvec.
177  - add a new file include/asm-sh/vapor.h which contains prototypes for
199  - finally add a file arch/sh/boards/vapor/io.c, which contains definitions of
212 The first thing to do is to add an entry to arch/sh/Kconfig, under the
220 next, this has to be added into arch/sh/Makefile. All boards require a
222 the board directory as it appears in arch/sh/boards, even if it is in a
223 sub-directory (in which case, all parent directories below arch/sh/boards/
228 provided that we've placed everything in the arch/sh/boards/vapor/ directory.
230 Next, the build system assumes that your include/asm-sh directory will also
237 This is done by adding an entry to the end of the arch/sh/tools/mach-types
258 (assume arch/sh/configs/vapor_defconfig), you can also use this directly as a
263 Architecture specific targets (sh):
264   zImage                  - Compressed kernel image (arch/sh/boot/zImage)
273 $ make ARCH=sh CROSS_COMPILE=sh4-linux- vapor_defconfig vmlinux