From d3ae37234cf0df758e97c6690fb8de9ef2eb3f9c Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Tue, 1 Mar 2011 07:44:04 -0600 Subject: [BUGID# 553] - documentation/bsp-guide/bsp.xml: Re-write of click-through [BUGID# 553] - In the 'BSP Click-Through Licensing Procedure' section, which is shared between the BSP Guide and the Poky Reference Manual, there were three links to 'pokylinux.org' sites. These links were intended to help a user get a license for encumbered BSPs. However, the links never did work. The section also had some wording that described a propsed naming convention for BSP tarballs that were encumbered and non-encumbered. The naming convention is a good idea but has not been followed so far. I removed the links and replaced them with general instructions on how to get through the licensing situation. Also removed the hard-line naming rules and replaces with a more general explanation of how we are naming BSP (e.g. Crown Bay). Signed-off-by: Scott Rifenbark --- documentation/bsp-guide/bsp.xml | 59 ++++++++++++++++++++++++----------------- 1 file changed, 34 insertions(+), 25 deletions(-) (limited to 'documentation') diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml index 076c08cf60..ea9b0017f3 100644 --- a/documentation/bsp-guide/bsp.xml +++ b/documentation/bsp-guide/bsp.xml @@ -533,19 +533,22 @@ FILESEXTRAPATHS := "${THISDIR}/${PN}" - For cases where you can substitute something and still maintain functionality, the Poky website will make - available a 'de-featured' BSP completely free of the encumbered IP. - In that case you can use the substitution directly and without any further licensing requirements. - If present, this fully 'de-featured' BSP will be named meta-<bsp_name> (i.e. the - normal default naming convention). - If available, this is the simplest the most preferred option. + For cases where you can substitute something and still maintain functionality, + the Yocto Project website at + + will make available a 'de-featured' BSP completely free of the encumbered IP. + In that case you can use the substitution directly and without any further licensing + requirements. + If present, this fully 'de-featured' BSP will be named appropiately different + than the normal encumbered BSP. + If available, this substitution is the simplest and most preferred option. This, of course, assumes the resulting functionality meets requirements. - If however, a non-encumbered version is unavailable or the 'free' version would provide unsuitable - functionality or quality, an encumbered version can be used. - Encumbered versions of a BSP are given names of the form meta-<bsp_name>-nonfree. + If however, a non-encumbered version is unavailable or the 'free' version + would provide unsuitable functionality or quality, you can use + an encumbered version. @@ -559,14 +562,23 @@ FILESEXTRAPATHS := "${THISDIR}/${PN}" Get a license key (or keys) for the encumbered BSP by visiting + a website and providing the name of the BSB and your email address + through a web form. + + + + After agreeing to any applicable license terms, the BSP key(s) will be immediately sent to the address @@ -609,7 +621,8 @@ FILESEXTRAPATHS := "${THISDIR}/${PN}" encumbered BSP. These prompts usually take the form of instructions needed to manually fetch the encumbered package(s) - and md5 sums into the required directory (e.g. the poky/build/downloads) + and md5 sums into the required directory + (e.g. the poky/build/downloads). Once the manual package fetch has been completed, restart the build to continue where it left off. @@ -619,25 +632,21 @@ FILESEXTRAPATHS := "${THISDIR}/${PN}" - Get a full-featured BSP recipe rather than a key, by - visiting - https://pokylinux.org/bsps.html. - Accepting the license agreement(s) presented will - subsequently allow you to download a tarball - containing a full-featured BSP that is legally cleared for - your use by the just-given license agreement(s). - This method will also allow the encumbered image to - be built with no change at all to the normal build - process. - + Get a full-featured BSP recipe rather than a key. + You can do this by visiting the applicable BSP download page from the Yocto + Project website at + . + BSP tarballs that have proprietary information can be downloaded after agreeing + to licensing requirements as part of the download process. + Obtaining the code this way allows you to build an encumbered image with + no changes at all as compared to the normal build. + Note that the third method is also the only option available - when downloading pre-compiled images generated from - non-free BSPs. - Those images are likewise available at - https://pokylinux.org/bsps.html. + when downloading pre-compiled images generated from non-free BSPs. + Those images are likewise available at from the Yocto Project website. -- cgit v1.2.3-54-g00ecf