Lines Matching refs:this

19 companion chip type, and CPU type. Looking at a tree view of this directory
92 In the first case, this is just a matter of making a directory for your
94 build system (more on this in the next section). However, for board families
97 Both the Solution Engine and the hp6xx boards are an example of this.
100 should also add a directory in include/asm-sh for headers localized to this
102 seamlessly with the build system, it's best to have this directory the same
104 a family, the build system has ways of dealing with this (via incdir-y
110 explain this, we use some examples for adding an imaginary board. For
112 get_system_type() and platform_setup(). For our imaginary board, this
130 	 * setup here. Though it's also sane to leave this empty
132 	 * this board.
192    this must be defined as something like:
220 next, this has to be added into arch/sh/Makefile. All boards require a
224 need to be listed). For our new board, this entry can look like:
231 be named the same. If this is not the case (as is the case with multiple
233 implicitly appended to incdir-y. The existing code manages this for the
238 list. The method for doing this is self explanatory, and so we won't waste
239 space restating it here. After this is done, you will be able to use
240 implicit checks for your board if you need this somewhere throughout the
253 way, other people who end up with this board can simply use this config
258 (assume arch/sh/configs/vapor_defconfig), you can also use this directly as a
275 which will in turn copy the defconfig for this board, run it through