summaryrefslogtreecommitdiff
path: root/scripts
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2011-03-01 07:44:04 -0600
committerSaul Wold <sgw@linux.intel.com>2011-03-02 09:48:52 -0800
commit4c2dcb376b4be0778cab97138fefdb8a27a0e708 (patch)
treed1fcae6488755211bab8e875bc8af165c6b4e73a /scripts
parent982ff35cad0276eb74eae170d21ead0edd3a1072 (diff)
downloadopenembedded-core-4c2dcb376b4be0778cab97138fefdb8a27a0e708.tar.gz
openembedded-core-4c2dcb376b4be0778cab97138fefdb8a27a0e708.tar.bz2
openembedded-core-4c2dcb376b4be0778cab97138fefdb8a27a0e708.tar.xz
openembedded-core-4c2dcb376b4be0778cab97138fefdb8a27a0e708.zip
[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 <scott.m.rifenbark@intel.com>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions