mirror of
https://git.yoctoproject.org/poky
synced 2026-05-08 17:19:20 +00:00
bsp-guide: WIP Removing yocto-bsp
(From yocto-docs rev: 056cc0c1dab79df6911552a690ca6b4dc302cc8b) Signed-off-by: Kristi Rifenbark <kristi.rifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
committed by
Richard Purdie
parent
3716b1f51e
commit
4a71d17172
@@ -1612,46 +1612,34 @@
|
||||
<title>Creating a new BSP Layer Using the yocto-bsp Script</title>
|
||||
|
||||
<para>
|
||||
The <filename>yocto-bsp</filename> script creates a new
|
||||
<link linkend='bsp-layers'>BSP layer</link> for any architecture supported
|
||||
by the Yocto Project, as well as QEMU versions of the same.
|
||||
The default mode of the script's operation is to prompt you for information needed
|
||||
to generate the BSP layer.
|
||||
[SOMETHING ABOUT CREATING A GENERAL LAYER USING bitbake-layers SCRIPT]
|
||||
The [MODIFICATION NAME] sub-command creates a new
|
||||
<link linkend='bsp-layers'>BSP layer</link> for any architecture
|
||||
supported by the Yocto Project, as well as QEMU versions of the same.
|
||||
The default mode of the script's operation is to prompt you for
|
||||
information needed to generate the BSP layer.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
For the current set of BSPs, the script prompts you for various important
|
||||
parameters such as:
|
||||
For the current set of BSPs, the [SCRIPT] prompts you for various
|
||||
important parameters such as:
|
||||
<itemizedlist>
|
||||
<listitem><para>The kernel to use</para></listitem>
|
||||
<listitem><para>The branch of that kernel to use (or re-use)</para></listitem>
|
||||
<listitem><para>Whether or not to use X, and if so, which drivers to use</para></listitem>
|
||||
<listitem><para>Whether to turn on SMP</para></listitem>
|
||||
<listitem><para>Whether the BSP has a keyboard</para></listitem>
|
||||
<listitem><para>Whether the BSP has a touchscreen</para></listitem>
|
||||
<listitem><para>Remaining configurable items associated with the BSP</para></listitem>
|
||||
<listitem><para>[PAREMETER 1]</para></listitem>
|
||||
<listitem><para>[PARAMETER 2]</para></listitem>
|
||||
<listitem><para>[PARAMETER 3]</para></listitem>
|
||||
<listitem><para>[PARAMETER 4]</para></listitem>
|
||||
<listitem><para>[PARAMETER 5]</para></listitem>
|
||||
<listitem><para>[PARAMETER 6]</para></listitem>
|
||||
<listitem><para>[PARAMETER 7]</para></listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
You use the <filename>yocto-bsp create</filename> sub-command to create
|
||||
a new BSP layer.
|
||||
This command requires you to specify a particular kernel architecture
|
||||
(<filename>karch</filename>) on which to base the BSP.
|
||||
Assuming you have sourced the environment, you can use the
|
||||
<filename>yocto-bsp list karch</filename> sub-command to list the
|
||||
architectures available for BSP creation as follows:
|
||||
<literallayout class='monospaced'>
|
||||
$ yocto-bsp list karch
|
||||
Architectures available:
|
||||
powerpc
|
||||
x86_64
|
||||
i386
|
||||
arm
|
||||
qemu
|
||||
mips
|
||||
mips64
|
||||
</literallayout>
|
||||
[ASSUMING STEP ONE IS RUNNING bitbake-layers TO CREATE GENERIC LAYER - INTRO]
|
||||
For instructions on how to create a general layer using the
|
||||
<filename>bitbake-layers</filename> script see the
|
||||
"<ulink url='&YOCTO_DOCS_DEV_URL;#creating-a-general-layer-using-the-bitbake-layers-script'>Creating a General Layer Using the <filename>bitbake-layers</filename> Script</ulink>"
|
||||
section.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
@@ -1667,7 +1655,7 @@
|
||||
</para>
|
||||
|
||||
<para>
|
||||
As the <filename>yocto-bsp create</filename> command runs, default values for
|
||||
[ASSUMING SIMLILAR ACTION OCCURS]As the [SUBCOMMAND] command runs, default values for
|
||||
the prompts appear in brackets.
|
||||
Pressing enter without supplying anything on the command line or pressing enter
|
||||
with an invalid response causes the script to accept the default value.
|
||||
@@ -1681,39 +1669,10 @@
|
||||
<para>
|
||||
Following is the complete example:
|
||||
<literallayout class='monospaced'>
|
||||
$ yocto-bsp create myarm qemu
|
||||
Checking basic git connectivity...
|
||||
Done.
|
||||
|
||||
Which qemu architecture would you like to use? [default: i386]
|
||||
1) i386 (32-bit)
|
||||
2) x86_64 (64-bit)
|
||||
3) ARM (32-bit)
|
||||
4) PowerPC (32-bit)
|
||||
5) MIPS (32-bit)
|
||||
6) MIPS64 (64-bit)
|
||||
3
|
||||
Would you like to use the default (4.8) kernel? (y/n) [default: y]
|
||||
Do you need a new machine branch for this BSP (the alternative is to re-use an existing branch)? [y/n] [default: y]
|
||||
Getting branches from remote repo git://git.yoctoproject.org/linux-yocto-4.8.git...
|
||||
Please choose a machine branch to base this BSP on: [default: standard/base]
|
||||
1) standard/arm-versatile-926ejs
|
||||
2) standard/base
|
||||
3) standard/beaglebone
|
||||
4) standard/edgerouter
|
||||
5) standard/fsl-mpc8315e-rdb
|
||||
6) standard/mti-malta32
|
||||
7) standard/mti-malta64
|
||||
8) standard/qemuarm64
|
||||
9) standard/qemuppc
|
||||
1
|
||||
Would you like SMP support? (y/n) [default: y]
|
||||
Does your BSP have a touchscreen? (y/n) [default: n]
|
||||
Does your BSP have a keyboard? (y/n) [default: y]
|
||||
|
||||
New qemu BSP created in meta-myarm
|
||||
[INSERT EXAMPLE]
|
||||
</literallayout>
|
||||
Take a closer look at the example now:
|
||||
[UPDATE EXAMPLE STRUCTURE BASED ON NEW INSTRUCTIONS]
|
||||
<orderedlist>
|
||||
<listitem><para>For the QEMU architecture,
|
||||
the script first prompts you for which emulated architecture to use.
|
||||
@@ -1765,6 +1724,7 @@
|
||||
/usr/local/src/yocto/meta-myarm \
|
||||
"
|
||||
</literallayout>
|
||||
[YOCTO-KERNEL WILL BE REMOVED - THIS NEEDS UPDATED WITH NEW INFO]
|
||||
Adding the layer to this file allows the build system to build the BSP and
|
||||
the <filename>yocto-kernel</filename> tool to be able to find the layer and
|
||||
other Metadata it needs on which to operate.
|
||||
|
||||
Reference in New Issue
Block a user