Lines Matching refs:specific

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
24 Board-specific code::
31     |           |   `-- board-specific files
33     |           |   `-- board-specific files
40 	    |   `-- board-specific headers
42 	    |   `-- board-specific headers
54 			`-- cchip-specific files
57 board-specific headers. Thus, include/asm-sh/hd64461 is home to all of the
58 hd64461-specific headers.
80 	    |   `-- SH-2 specific headers
82 	    |   `-- SH-3 specific headers
84 		`-- SH-4 specific headers
87 need to be dealt with by the CPU family specific code.
94 share the same board-specific code with minor differences.
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
174    any machine specific IO functions prefixed with the machine name, for
184    somewhere in the board-specific header. Any boards being ported that still
196    the machine specific io functions (if there are enough to warrant it).
202 board-specific code is in place, it's time to look at how to get the
259 Architecture specific targets (sh):