summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2013-04-16 15:26:56 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-04-17 22:34:21 +0100
commite50ef9e9cf6009bdb79757121c37f06eb286564f (patch)
tree2af9346222db71b9e053aea0bac5c5dc2f91d0f8 /documentation
parentd9c3fef5fd6792268baf76b240b92ee82977a764 (diff)
downloadpoky-e50ef9e9cf6009bdb79757121c37f06eb286564f.tar.gz
bsp-guide: Minor edits
Applied "Metadata" for "metadata" Added a link to the section to help find maintainers. Some re-wording. (From yocto-docs rev: 7f40c4dac30d2f54cf09afeb51a5cc83ba0851e9) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
-rw-r--r--documentation/bsp-guide/bsp.xml18
1 files changed, 11 insertions, 7 deletions
diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml
index 1f04930b9f..aee30ae455 100644
--- a/documentation/bsp-guide/bsp.xml
+++ b/documentation/bsp-guide/bsp.xml
@@ -692,7 +692,7 @@
692 wiki page.</para></listitem> 692 wiki page.</para></listitem>
693 <listitem><para>The requirements for the BSP as it is made available to a developer 693 <listitem><para>The requirements for the BSP as it is made available to a developer
694 are completely independent of the released form of the BSP. 694 are completely independent of the released form of the BSP.
695 For example, the BSP metadata can be contained within a Git repository 695 For example, the BSP Metadata can be contained within a Git repository
696 and could have a directory structure completely different from what appears 696 and could have a directory structure completely different from what appears
697 in the officially released BSP layer.</para></listitem> 697 in the officially released BSP layer.</para></listitem>
698 <listitem><para>It is not required that specific packages or package 698 <listitem><para>It is not required that specific packages or package
@@ -741,12 +741,12 @@
741 recipes. 741 recipes.
742 The recipes themselves should follow the general guidelines 742 The recipes themselves should follow the general guidelines
743 for recipes used in the Yocto Project found in the 743 for recipes used in the Yocto Project found in the
744 <ulink url='https://wiki.yoctoproject.org/wiki/Recipe_%26_Patch_Style_Guide'>Yocto 744 "<ulink url='https://wiki.yoctoproject.org/wiki/Recipe_%26_Patch_Style_Guide'>Yocto Recipe and Patch Style Guide</ulink>".
745 Recipe and Patch Style Guide</ulink>.</para></listitem> 745 </para></listitem>
746 <listitem><para><emphasis>License File:</emphasis> 746 <listitem><para><emphasis>License File:</emphasis>
747 You must include a license file in the 747 You must include a license file in the
748 <filename>meta-&lt;bsp_name&gt;</filename> directory. 748 <filename>meta-&lt;bsp_name&gt;</filename> directory.
749 This license covers the BSP metadata as a whole. 749 This license covers the BSP Metadata as a whole.
750 You must specify which license to use since there is no 750 You must specify which license to use since there is no
751 default license if one is not specified. 751 default license if one is not specified.
752 See the 752 See the
@@ -775,11 +775,15 @@
775 For example, this information includes information on 775 For example, this information includes information on
776 special variables needed to satisfy a EULA, 776 special variables needed to satisfy a EULA,
777 or instructions on information needed to build or distribute 777 or instructions on information needed to build or distribute
778 binaries built from the BSP metadata.</para></listitem> 778 binaries built from the BSP Metadata.</para></listitem>
779 <listitem><para>The name and contact information for the 779 <listitem><para>The name and contact information for the
780 BSP layer maintainer. 780 BSP layer maintainer.
781 This is the person to whom patches and questions should 781 This is the person to whom patches and questions should
782 be sent.</para></listitem> 782 be sent.
783 For information on how to find the right person, see the
784 "<ulink url='&YOCTO_DOCS_DEV_URL;#how-to-submit-a-change'>How to Submit a Change</ulink>"
785 section in the Yocto Project Development Manual.
786 </para></listitem>
783 <listitem><para>Instructions on how to build the BSP using the BSP 787 <listitem><para>Instructions on how to build the BSP using the BSP
784 layer.</para></listitem> 788 layer.</para></listitem>
785 <listitem><para>Instructions on how to boot the BSP build from 789 <listitem><para>Instructions on how to boot the BSP build from
@@ -822,7 +826,7 @@
822 BSP layers for each target. 826 BSP layers for each target.
823 <note>It is completely possible for a developer to structure the 827 <note>It is completely possible for a developer to structure the
824 working repository as a conglomeration of unrelated BSP 828 working repository as a conglomeration of unrelated BSP
825 files, and to possibly generate specifically targeted 'release' BSPs 829 files, and to possibly generate BSPs targeted for release
826 from that directory using scripts or some other mechanism. 830 from that directory using scripts or some other mechanism.
827 Such considerations are outside the scope of this document.</note> 831 Such considerations are outside the scope of this document.</note>
828 </para></listitem> 832 </para></listitem>