summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2012-10-01 13:56:44 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-10-02 17:41:35 +0100
commitfd67c63d0d3e31cc1d44abc413cc9f7c19ab86d8 (patch)
tree1f09f0c513ebe1066aefa584ad1758495e5d9951
parent876a87ba1cf52a472a6171fb1c55d5fbd6129bdd (diff)
downloadpoky-fd67c63d0d3e31cc1d44abc413cc9f7c19ab86d8.tar.gz
documentation: dev-manual - Changes from Crown Bay to fri2
These changes are partial for converting the example for BSP creation from Crown Bay to Fish River Island 2. (From yocto-docs rev: c7fc78a8453ad363138764aa30e377b56ce49f2b) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/dev-manual/dev-manual-bsp-appendix.xml154
1 files changed, 87 insertions, 67 deletions
diff --git a/documentation/dev-manual/dev-manual-bsp-appendix.xml b/documentation/dev-manual/dev-manual-bsp-appendix.xml
index c5a6c92cad..27e4b48ea9 100644
--- a/documentation/dev-manual/dev-manual-bsp-appendix.xml
+++ b/documentation/dev-manual/dev-manual-bsp-appendix.xml
@@ -11,10 +11,10 @@
11 The example assumes the following: 11 The example assumes the following:
12 <itemizedlist> 12 <itemizedlist>
13 <listitem><para>No previous preparation or use of the Yocto Project.</para></listitem> 13 <listitem><para>No previous preparation or use of the Yocto Project.</para></listitem>
14 <listitem><para>Use of the Crown Bay Board Support Package (BSP) as a "base" BSP from 14 <listitem><para>Use of the Fish River Island 2 Board Support Package (BSP) as a "base" BSP from
15 which to work. 15 which to work.
16 The example begins with the Crown Bay BSP as the starting point 16 The example begins with the Fish River Island 2 BSP as the starting point
17 but ends by building a new 'atom-pc' BSP, which was based on the Crown Bay BSP. 17 but ends by building a new 'atom-pc' BSP, which was based on the Fish River Island 2 BSP.
18 </para></listitem> 18 </para></listitem>
19 <listitem><para>Shell commands assume <filename>bash</filename></para></listitem> 19 <listitem><para>Shell commands assume <filename>bash</filename></para></listitem>
20 <listitem><para>Example was developed on an Intel-based Core i7 platform running 20 <listitem><para>Example was developed on an Intel-based Core i7 platform running
@@ -113,10 +113,10 @@
113 <para> 113 <para>
114 For this example, the base BSP is the <trademark class='registered'>Intel</trademark> 114 For this example, the base BSP is the <trademark class='registered'>Intel</trademark>
115 <trademark class='trade'>Atom</trademark> Processor E660 with Intel Platform 115 <trademark class='trade'>Atom</trademark> Processor E660 with Intel Platform
116 Controller Hub EG20T Development Kit, which is otherwise referred to as "Crown Bay." 116 Controller Hub EG20T Development Kit, which is otherwise referred to as "Fish River Island 2."
117 The BSP layer is <filename>meta-crownbay</filename>. 117 The BSP layer is <filename>meta-fri2</filename>.
118 The base BSP is simply the BSP 118 The base BSP is simply the BSP
119 we will be using as a starting point, so don't worry if you don't actually have Crown Bay 119 we will be using as a starting point, so don't worry if you don't actually have Fish River Island 2
120 hardware. 120 hardware.
121 The remainder of the example transforms the base BSP into a BSP that should be 121 The remainder of the example transforms the base BSP into a BSP that should be
122 able to boot on generic atom-pc (netbook) hardware. 122 able to boot on generic atom-pc (netbook) hardware.
@@ -149,7 +149,7 @@
149 parent directory. 149 parent directory.
150 The following steps will automatically create the 150 The following steps will automatically create the
151 <filename>meta-intel</filename> directory and the contained 151 <filename>meta-intel</filename> directory and the contained
152 <filename>meta-crownbay</filename> starting point in both the Git and the tarball cases. 152 <filename>meta-fri2</filename> starting point in both the Git and the tarball cases.
153 </para> 153 </para>
154 154
155 <para> 155 <para>
@@ -160,16 +160,16 @@
160 $ git clone git://git.yoctoproject.org/meta-intel.git 160 $ git clone git://git.yoctoproject.org/meta-intel.git
161 $ cd meta-intel 161 $ cd meta-intel
162 </literallayout> 162 </literallayout>
163 Alternatively, you can start with the downloaded Crown Bay tarball. 163 Alternatively, you can start with the downloaded Fish River Island 2 tarball.
164 You can download the &DISTRO_NAME; version of the BSP tarball from the 164 You can download the &DISTRO_NAME; version of the BSP tarball from the
165 <ulink url='&YOCTO_HOME_URL;/download'>Downloads</ulink> page of the 165 <ulink url='&YOCTO_HOME_URL;/download'>Downloads</ulink> page of the
166 Yocto Project website. 166 Yocto Project website.
167 Here is the specific link for the tarball needed for this example: 167 Here is the specific link for the tarball needed for this example:
168 <ulink url='&YOCTO_MACHINES_DL_URL;/crownbay-noemgd/crownbay-noemgd-&DISTRO_NAME;-&POKYVERSION;.tar.bz2'></ulink>. 168 <ulink url='&YOCTO_MACHINES_DL_URL;/fri2-noemgd/fri2-noemgd-&DISTRO_NAME;-&POKYVERSION;.tar.bz2'></ulink>.
169 Again, be sure that you are already in the <filename>poky</filename> directory 169 Again, be sure that you are already in the <filename>poky</filename> directory
170 as described previously before installing the tarball: 170 as described previously before installing the tarball:
171 <literallayout class='monospaced'> 171 <literallayout class='monospaced'>
172 $ tar xfj crownbay-noemgd-&DISTRO_NAME;-&POKYVERSION;.tar.bz2 172 $ tar xfj fri2-noemgd-&DISTRO_NAME;-&POKYVERSION;.tar.bz2
173 $ cd meta-intel 173 $ cd meta-intel
174 </literallayout> 174 </literallayout>
175 </para> 175 </para>
@@ -199,7 +199,7 @@
199 <para> 199 <para>
200 Now that you have set up the Source Directory and included the base BSP files, you need to 200 Now that you have set up the Source Directory and included the base BSP files, you need to
201 create a new layer for your BSP. 201 create a new layer for your BSP.
202 To create your BSP layer, you simply copy the <filename>meta-crownbay</filename> 202 To create your BSP layer, you simply copy the <filename>meta-fri2</filename>
203 layer to a new layer. 203 layer to a new layer.
204 </para> 204 </para>
205 205
@@ -212,7 +212,7 @@
212 To start your new layer, just copy the new layer alongside the existing 212 To start your new layer, just copy the new layer alongside the existing
213 BSP layers in the <filename>meta-intel</filename> directory: 213 BSP layers in the <filename>meta-intel</filename> directory:
214 <literallayout class='monospaced'> 214 <literallayout class='monospaced'>
215 $ cp -a meta-crownbay/ meta-mymachine 215 $ cp -a meta-fri2/ meta-mymachine
216 </literallayout> 216 </literallayout>
217 </para> 217 </para>
218</section> 218</section>
@@ -222,7 +222,7 @@
222 222
223 <para> 223 <para>
224 Right now you have two identical BSP layers with different names: 224 Right now you have two identical BSP layers with different names:
225 <filename>meta-crownbay</filename> and <filename>meta-mymachine</filename>. 225 <filename>meta-fri2</filename> and <filename>meta-mymachine</filename>.
226 You need to change your configurations so that they work for your new BSP and 226 You need to change your configurations so that they work for your new BSP and
227 your particular hardware. 227 your particular hardware.
228 The following sections look at each of these areas of the BSP. 228 The following sections look at each of these areas of the BSP.
@@ -238,15 +238,15 @@
238 238
239 <para> 239 <para>
240 First, since in this example the new BSP will not support EMGD, we will get rid of the 240 First, since in this example the new BSP will not support EMGD, we will get rid of the
241 <filename>crownbay.conf</filename> file and then rename the 241 <filename>fri2.conf</filename> file and then rename the
242 <filename>crownbay-noemgd.conf</filename> file to <filename>mymachine.conf</filename>. 242 <filename>fri2-noemgd.conf</filename> file to <filename>mymachine.conf</filename>.
243 Much of what we do in the configuration directory is designed to help the OpenEmbedded 243 Much of what we do in the configuration directory is designed to help the OpenEmbedded
244 build system work with the new layer and to be able to find and use the right software. 244 build system work with the new layer and to be able to find and use the right software.
245 The following two commands result in a single machine configuration file named 245 The following two commands result in a single machine configuration file named
246 <filename>mymachine.conf</filename>. 246 <filename>mymachine.conf</filename>.
247 <literallayout class='monospaced'> 247 <literallayout class='monospaced'>
248 $ rm meta-mymachine/conf/machine/crownbay.conf 248 $ rm meta-mymachine/conf/machine/fri2.conf
249 $ mv meta-mymachine/conf/machine/crownbay-noemgd.conf \ 249 $ mv meta-mymachine/conf/machine/fri2-noemgd.conf \
250 meta-mymachine/conf/machine/mymachine.conf 250 meta-mymachine/conf/machine/mymachine.conf
251 </literallayout> 251 </literallayout>
252 </para> 252 </para>
@@ -254,10 +254,10 @@
254 <para> 254 <para>
255 Next, we need to make changes to the <filename>mymachine.conf</filename> itself. 255 Next, we need to make changes to the <filename>mymachine.conf</filename> itself.
256 The only changes we want to make for this example are to the comment lines. 256 The only changes we want to make for this example are to the comment lines.
257 Changing comments, of course, is never strictly necessary, but it's alway good form to make 257 Changing comments, of course, is never strictly necessary, but it's always good form to make
258 them reflect reality as much as possible. 258 them reflect reality as much as possible.
259 259
260 Here, simply substitute the Crown Bay name with an appropriate name for the BSP 260 Here, simply substitute the Fish River Island 2 name with an appropriate name for the BSP
261 (<filename>mymachine</filename> in this case) and change the description to 261 (<filename>mymachine</filename> in this case) and change the description to
262 something that describes your hardware. 262 something that describes your hardware.
263 </para> 263 </para>
@@ -267,7 +267,7 @@
267 <filename>PREFERRED_VERSION_linux-yocto</filename> statement. 267 <filename>PREFERRED_VERSION_linux-yocto</filename> statement.
268 This statement identifies the kernel that the BSP is going to use. 268 This statement identifies the kernel that the BSP is going to use.
269 In this case, the BSP is using <filename>linux-yocto</filename>, which is the 269 In this case, the BSP is using <filename>linux-yocto</filename>, which is the
270 current Yocto Project kernel based on the Linux 3.2 release. 270 current Yocto Project kernel based on the Linux 3.4 release.
271 </para> 271 </para>
272 272
273 <para> 273 <para>
@@ -281,18 +281,18 @@
281 </para> 281 </para>
282 282
283 <para> 283 <para>
284 The file contains these statements that reference the Crown Bay BSP: 284 The file contains these statements that reference the Fish River Island 2 BSP:
285 <literallayout class='monospaced'> 285 <literallayout class='monospaced'>
286 BBFILE_COLLECTIONS += "crownbay" 286 BBFILE_COLLECTIONS += "fri2"
287 BBFILE_PATTERN_crownbay := "^${LAYERDIR}/" 287 BBFILE_PATTERN_fri2 := "^${LAYERDIR}/"
288 BBFILE_PRIORITY_crownbay = "6" 288 BBFILE_PRIORITY_fri2 = "6"
289 289
290 LAYERDEPENDS_crownbay = "intel" 290 LAYERDEPENDS_fri2 = "intel"
291 </literallayout> 291 </literallayout>
292 </para> 292 </para>
293 293
294 <para> 294 <para>
295 Simply substitute the machine string name <filename>crownbay</filename> 295 Simply substitute the machine string name <filename>fri2</filename>
296 with the new machine name <filename>mymachine</filename> to get the following: 296 with the new machine name <filename>mymachine</filename> to get the following:
297 <literallayout class='monospaced'> 297 <literallayout class='monospaced'>
298 BBFILE_COLLECTIONS += "mymachine" 298 BBFILE_COLLECTIONS += "mymachine"
@@ -331,8 +331,8 @@
331 the remaining one that doesn't support EMGD. 331 the remaining one that doesn't support EMGD.
332 These commands take care of the <filename>recipes-bsp</filename> recipes: 332 These commands take care of the <filename>recipes-bsp</filename> recipes:
333 <literallayout class='monospaced'> 333 <literallayout class='monospaced'>
334 $ rm -rf meta-mymachine/recipes-bsp/formfactor/formfactor/crownbay 334 $ rm -rf meta-mymachine/recipes-bsp/formfactor/formfactor/fri2
335 $ mv meta-mymachine/recipes-bsp/formfactor/formfactor/crownbay-noemgd/ \ 335 $ mv meta-mymachine/recipes-bsp/formfactor/formfactor/fri2-noemgd/ \
336 meta-mymachine/recipes-bsp/formfactor/formfactor/mymachine 336 meta-mymachine/recipes-bsp/formfactor/formfactor/mymachine
337 </literallayout> 337 </literallayout>
338 </para> 338 </para>
@@ -347,8 +347,8 @@
347 be sure to rename remaining directories appropriately. 347 be sure to rename remaining directories appropriately.
348 The following commands clean up the <filename>recipes-graphics</filename> directory: 348 The following commands clean up the <filename>recipes-graphics</filename> directory:
349 <literallayout class='monospaced'> 349 <literallayout class='monospaced'>
350 $ rm -rf meta-mymachine/recipes-graphics/xorg-xserver/xserver-xf86-config/crownbay 350 $ rm -rf meta-mymachine/recipes-graphics/xorg-xserver/xserver-xf86-config/fri2
351 $ mv meta-mymachine/recipes-graphics/xorg-xserver/xserver-xf86-config/crownbay-noemgd \ 351 $ mv meta-mymachine/recipes-graphics/xorg-xserver/xserver-xf86-config/fri2-noemgd \
352 meta-mymachine/recipes-graphics/xorg-xserver/xserver-xf86-config/mymachine 352 meta-mymachine/recipes-graphics/xorg-xserver/xserver-xf86-config/mymachine
353 </literallayout> 353 </literallayout>
354 </para> 354 </para>
@@ -369,7 +369,7 @@
369 The recipe for that kernel is not located in the 369 The recipe for that kernel is not located in the
370 BSP layer but rather in the Source Directory at 370 BSP layer but rather in the Source Directory at
371 <filename>meta/recipes-kernel/linux</filename> and is 371 <filename>meta/recipes-kernel/linux</filename> and is
372 named <filename>linux-yocto_3.2.bb</filename>. 372 named <filename>linux-yocto_3.4.bb</filename>.
373 The <filename>SRCREV_machine</filename> and <filename>SRCREV_meta</filename> 373 The <filename>SRCREV_machine</filename> and <filename>SRCREV_meta</filename>
374 statements point to the exact commits used by the Yocto Project development team 374 statements point to the exact commits used by the Yocto Project development team
375 in their source repositories that identify the right kernel for our hardware. 375 in their source repositories that identify the right kernel for our hardware.
@@ -382,30 +382,38 @@
382 <para> 382 <para>
383 However, in the <filename>meta-mymachine</filename> layer in 383 However, in the <filename>meta-mymachine</filename> layer in
384 <filename>recipes-kernel/linux</filename> resides a <filename>.bbappend</filename> 384 <filename>recipes-kernel/linux</filename> resides a <filename>.bbappend</filename>
385 file named <filename>linux-yocto_3.2.bbappend</filename> that 385 file named <filename>linux-yocto_3.4.bbappend</filename> that
386 appends information to the recipe of the same name in <filename>meta/recipes-kernel/linux</filename>. 386 appends the information to the recipe of the same name
387 that is found in <filename>meta/recipes-kernel/linux</filename>.
387 Thus, the <filename>SRCREV</filename> statements in the append file override 388 Thus, the <filename>SRCREV</filename> statements in the append file override
388 the more general statements found in <filename>meta</filename>. 389 the more general statements found in <filename>meta</filename>.
389 </para> 390 </para>
390 391
391 <para> 392 <para>
392 The <filename>SRCREV</filename> statements in the append file currently identify 393 The <filename>SRCREV</filename> statements in the append file currently identify
393 the kernel that supports the Crown Bay BSP with and without EMGD support. 394 the kernel that supports the Fish River Island 2 BSP with and without EMGD support.
394 Here are the statements: 395 Here are the statements:
395 <note>The commit ID strings used in this manual might not match the actual commit 396 <note>The commit ID strings used in this manual might not match the actual commit
396 ID strings found in the <filename>linux-yocto_3.2.bbappend</filename> file. 397 ID strings found in the <filename>linux-yocto_3.4.bbappend</filename> file.
397 For the example, this difference does not matter.</note> 398 For the example, this difference does not matter.</note>
398 <literallayout class='monospaced'> 399 <literallayout class='monospaced'>
399 SRCREV_machine_pn-linux-yocto_crownbay ?= \ 400 SRCREV_machine_pn-linux-yocto_fri2 ?= \
400 "211fc7f4d10ec2b82b424286aabbaff9254b7cbd" 401 "59c3ff750831338d05ab67d5efd7fc101c451aff"
401 SRCREV_meta_pn-linux-yocto_crownbay ?= \ 402 #SRCREV_meta_pn-linux-yocto_fri2 ?= \
402 "514847185c78c07f52e02750fbe0a03ca3a31d8f" 403 "c5bddf8ea379406ffec550528e17b777a0eba24b"
403 404
404 SRCREV_machine_pn-linux-yocto_crownbay-noemgd ?= \ 405 SRCREV_machine_pn-linux-yocto_fri2-noemgd ?= \
405 "211fc7f4d10ec2b82b424286aabbaff9254b7cbd" 406 "59c3ff750831338d05ab67d5efd7fc101c451aff"
406 SRCREV_meta_pn-linux-yocto_crownbay-noemgd ?= \ 407 #SRCREV_meta_pn-linux-yocto_fir2-noemgd ?= \
407 "514847185c78c07f52e02750fbe0a03ca3a31d8f" 408 "c5bddf8ea379406ffec550528e17b777a0eba24b"
408 </literallayout> 409 </literallayout>
410 <note>The <filename>SRCREV_meta_pn-linux-yocto_fir2-noemgd</filename>
411 statements in the Fish River Island 2 append file are identical to those in the
412 general <filename>linux-yocto_3.4.bbappend</filename> recipe, which is
413 found in <filename>meta/recipes-kernel/linux</filename>.
414 For this reason they are commented out in the Fish River Island 2
415 append file.
416 In this case, there is no need to override the statements.</note>
409 </para> 417 </para>
410 418
411 <para> 419 <para>
@@ -415,11 +423,12 @@
415 The bottom pair identifies the kernel that we will use: 423 The bottom pair identifies the kernel that we will use:
416 <filename>linux-yocto</filename>. 424 <filename>linux-yocto</filename>.
417 At this point though, the unique commit strings all are still associated with 425 At this point though, the unique commit strings all are still associated with
418 Crown Bay and not <filename>meta-mymachine</filename>. 426 Fish River Island 2 and not <filename>meta-mymachine</filename>.
419 </para> 427 </para>
420 428
421 <para> 429 <para>
422 To fix this situation in <filename>linux-yocto_3.2.bbappend</filename>, 430 To fix this situation in <filename>linux-yocto_3.4.bbappend</filename>
431 for <filename>mymachine</filename>,
423 we delete the two <filename>SRCREV</filename> statements that support 432 we delete the two <filename>SRCREV</filename> statements that support
424 EMGD (the top pair). 433 EMGD (the top pair).
425 We also change the remaining pair to specify <filename>mymachine</filename> 434 We also change the remaining pair to specify <filename>mymachine</filename>
@@ -428,26 +437,34 @@
428 kernel. 437 kernel.
429 In this case, because we're working with the &DISTRO_NAME; branch of everything, we 438 In this case, because we're working with the &DISTRO_NAME; branch of everything, we
430 need to use the <filename>SRCREV</filename> values for the atom-pc branch 439 need to use the <filename>SRCREV</filename> values for the atom-pc branch
431 that are associated with the &DISTRO_NAME; release. 440 that are associated with the &DISTRO_NAME; release.
432 To find those values, we need to find the <filename>SRCREV</filename> 441 </para>
433 values that &DISTRO_NAME; uses for the atom-pc branch, which we find in the 442
434 <filename>poky/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_3.2.bbappend</filename> 443 <para>
444 To find the machine value, we need to find the <filename>SRCREV</filename>
445 value that &DISTRO_NAME; uses for the atom-pc branch, which we find in the
446 <filename>poky/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_3.4.bbappend</filename>
435 file. 447 file.
448 The machine <filename>SRCREV</filename> we want is in the
449 <filename>SRCREV_machine_atom-pc</filename> variable.
450 </para>
451
452 <para>
453 The meta <filename>SRCREV</filename> isn't specified in this file, so if you
454 needed it, you would find it in the base kernel recipe in the
455 <filename>poky/meta/recipes-kernel/linux/linux-yocto_3.4.bb</filename>.
456 Recall that for this example the commit ID's for the <filename>SRCREV</filename>
457 meta statements are identical and are do not have to be used in the
458 <filename>mymachine</filename> append file.
436 </para> 459 </para>
437 460
438 <para> 461 <para>
439 The machine <filename>SRCREV</filename> we want is in the
440 <filename>SRCREV_machine_atom-pc</filename> variable.
441 The meta <filename>SRCREV</filename> isn't specified in this file, so it must be
442 specified in the base kernel recipe in the
443 <filename>poky/meta/recipes-kernel/linux/linux-yocto_3.2.bb</filename>
444 file, in the <filename>SRCREV_meta</filename> variable found there.
445 Here are the final <filename>SRCREV</filename> statements: 462 Here are the final <filename>SRCREV</filename> statements:
446 <literallayout class='monospaced'> 463 <literallayout class='monospaced'>
447 SRCREV_machine_pn-linux-yocto_mymachine ?= \ 464 SRCREV_machine_pn-linux-yocto_mymachine ?= \
448 "f29531a41df15d74be5ad47d958e4117ca9e489e" 465 "0985844fa6235422c67ef269952fa4e765f252f9"
449 SRCREV_meta_pn-linux-yocto_mymachine ?= \ 466 #SRCREV_meta_pn-linux-yocto_mymachine ?= \
450 "b14a08f5c7b469a5077c10942f4e1aec171faa9d" 467 "463299bc2e533e1bd38b0053ae7b210980f269c3"
451 </literallayout> 468 </literallayout>
452 </para> 469 </para>
453 470
@@ -463,8 +480,8 @@
463 exact commit strings in the Yocto Project source repositories you need to change 480 exact commit strings in the Yocto Project source repositories you need to change
464 the <filename>SRCREV</filename> statements. 481 the <filename>SRCREV</filename> statements.
465 You can find all the <filename>machine</filename> and <filename>meta</filename> 482 You can find all the <filename>machine</filename> and <filename>meta</filename>
466 branch points (commits) for the <filename>linux-yocto-3.2</filename> kernel at 483 branch points (commits) for the <filename>linux-yocto-3.4</filename> kernel at
467 <ulink url='&YOCTO_GIT_URL;/cgit/cgit.cgi/linux-yocto-3.2'></ulink>. 484 <ulink url='&YOCTO_GIT_URL;/cgit/cgit.cgi/linux-yocto-3.4'></ulink>.
468 </para> 485 </para>
469 486
470 <para> 487 <para>
@@ -475,7 +492,7 @@
475 branch</para></listitem> 492 branch</para></listitem>
476 <listitem><para>Click on the commit column header to view the top commit</para></listitem> 493 <listitem><para>Click on the commit column header to view the top commit</para></listitem>
477 <listitem><para>Copy the commit string for use in the 494 <listitem><para>Copy the commit string for use in the
478 <filename>linux-yocto_3.2.bbappend</filename> file</para></listitem> 495 <filename>linux-yocto_3.4.bbappend</filename> file</para></listitem>
479 </orderedlist> 496 </orderedlist>
480 </para> 497 </para>
481 498
@@ -486,7 +503,7 @@
486 </para> 503 </para>
487 504
488 <para> 505 <para>
489 Also in the <filename>linux-yocto_3.2.bbappend</filename> file are 506 Also in the <filename>linux-yocto_3.4.bbappend</filename> file are
490 <ulink url='&YOCTO_DOCS_REF_URL;#var-COMPATIBLE_MACHINE'><filename>COMPATIBLE_MACHINE</filename></ulink>, 507 <ulink url='&YOCTO_DOCS_REF_URL;#var-COMPATIBLE_MACHINE'><filename>COMPATIBLE_MACHINE</filename></ulink>,
491 <ulink url='&YOCTO_DOCS_REF_URL;#var-KMACHINE'><filename>KMACHINE</filename></ulink>, 508 <ulink url='&YOCTO_DOCS_REF_URL;#var-KMACHINE'><filename>KMACHINE</filename></ulink>,
492 and 509 and
@@ -494,16 +511,19 @@
494 Two sets of these exist: one set supports EMGD and one set does not. 511 Two sets of these exist: one set supports EMGD and one set does not.
495 Because we are not interested in supporting EMGD those three can be deleted. 512 Because we are not interested in supporting EMGD those three can be deleted.
496 The remaining three must be changed so that <filename>mymachine</filename> replaces 513 The remaining three must be changed so that <filename>mymachine</filename> replaces
497 <filename>crownbay-noemgd</filename> and <filename>crownbay</filename>. 514 <filename>fri2-noemgd</filename> and <filename>fri2</filename>.
515 </para>
516
517 <para>
498 Because we are using the <filename>atom-pc</filename> branch for this new BSP, we can also find 518 Because we are using the <filename>atom-pc</filename> branch for this new BSP, we can also find
499 the exact branch we need for the <filename>KMACHINE</filename> 519 the exact branch we need for the <filename>KMACHINE</filename>
500 and <filename>KBRANCH</filename> variables in our new BSP from the value 520 and <filename>KBRANCH</filename> variables in our new BSP from the value
501 we find in the 521 we find in the
502 <filename>poky/meta-yocto/recipes-kernel/linux/linux-yocto_3.2.bbappend</filename> 522 <filename>poky/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_3.4.bbappend</filename>
503 file we looked at in a previous step. 523 file we looked at in a previous step.
504 In this case, the values we want are in the <filename>KMACHINE_atom-pc</filename> variable 524 In this case, the values we want are in the <filename>KMACHINE_atom-pc</filename> variable
505 and the <filename>KBRANCH_atom-pc</filename> variables in that file. 525 and the <filename>KBRANCH_atom-pc</filename> variables in that file.
506 Here is the final <filename>linux-yocto_3.2.bbappend</filename> file after all 526 Here is the final <filename>linux-yocto_3.4.bbappend</filename> file after all
507 the edits: 527 the edits:
508 <literallayout class='monospaced'> 528 <literallayout class='monospaced'>
509 FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" 529 FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
@@ -672,7 +692,7 @@
672 260538368 2012-04-27 01:44 core-image-sato-mymachine-20120427025051.hddimg 692 260538368 2012-04-27 01:44 core-image-sato-mymachine-20120427025051.hddimg
673 </literallayout> 693 </literallayout>
674 <note>The previous instructions are also present in the README that was copied 694 <note>The previous instructions are also present in the README that was copied
675 from meta-crownbay, which should also be updated to reflect the specifics of your 695 from meta-fri2, which should also be updated to reflect the specifics of your
676 new BSP. 696 new BSP.
677 That file and the <filename>README.hardware</filename> file in the top-level 697 That file and the <filename>README.hardware</filename> file in the top-level
678 <filename>poky</filename> directory 698 <filename>poky</filename> directory