dev-manual: Changed GummiBootTarget to GummibootTarget.

(From yocto-docs rev: 0d870778d87dcbb38d1ce577f38b84c8fca0e464)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
2014-04-18 07:39:13 -07:00
committed by Richard Purdie
parent e0999660a8
commit a3dcfa6a6a

View File

@@ -5781,7 +5781,7 @@
For QEMU, you do not have to change anything, the default
value is "QemuTarget".
For running tests on hardware, two options exist:
"SimpleRemoteTarget" and "GummiBootTarget".
"SimpleRemoteTarget" and "GummibootTarget".
<itemizedlist>
<listitem><para><emphasis>"SimpleRemoteTarget":</emphasis>
Choose "SimpleRemoteTarget" if you are going to
@@ -5793,8 +5793,8 @@
within a separately started QEMU or any
other virtual machine manager.
</para></listitem>
<listitem><para><emphasis>"GummiBootTarget":</emphasis>
Choose "GummiBootTarget" if your hardware is
<listitem><para><emphasis>"GummibootTarget":</emphasis>
Choose "GummibootTarget" if your hardware is
an EFI-based machine with
<filename>gummiboot</filename> as bootloader and
<filename>core-image-testmaster</filename>
@@ -5808,7 +5808,7 @@
<para>
If you set <filename>TEST_TARGET</filename> to
"GummiBootTarget", you also need to perform a one-time
"GummibootTarget", you also need to perform a one-time
setup of your master image by doing the following:
<orderedlist>
<listitem><para><emphasis>Set <filename>EFI_PROVIDER</filename>:</emphasis>
@@ -5832,7 +5832,7 @@
<para>
The final thing you need to do when setting
<filename>TEST_TARGET</filename> to "GummiBootTarget" is
<filename>TEST_TARGET</filename> to "GummibootTarget" is
to set up the test image:
<orderedlist>
<listitem><para><emphasis>Set up your <filename>local.conf</filename> file:</emphasis>