Lines Matching refs:specific

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
22 Board-specific code:
29 |           |   `-- board-specific files
31 |           |   `-- board-specific files
38         |   `-- board-specific headers
40         |   `-- board-specific headers
51                     `-- cchip-specific files
54 board-specific headers. Thus, include/asm-sh/hd64461 is home to all of the
55 hd64461-specific headers.
76         |   `-- SH-2 specific headers
78         |   `-- SH-3 specific headers
80             `-- SH-4 specific headers
83 need to be dealt with by the CPU family specific code.
90 share the same board-specific code with minor differences.
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
178    any machine specific IO functions prefixed with the machine name, for
188    somewhere in the board-specific header. Any boards being ported that still
200    the machine specific io functions (if there are enough to warrant it).
206 board-specific code is in place, it's time to look at how to get the
263 Architecture specific targets (sh):