diff options
Diffstat (limited to 'yocto-poky/scripts/lib/bsp/substrate/target/arch/common')
16 files changed, 0 insertions, 299 deletions
diff --git a/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/COPYING.MIT b/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/COPYING.MIT deleted file mode 100644 index fb950dc69..000000000 --- a/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/COPYING.MIT +++ /dev/null @@ -1,17 +0,0 @@ -Permission is hereby granted, free of charge, to any person obtaining a copy -of this software and associated documentation files (the "Software"), to deal -in the Software without restriction, including without limitation the rights -to use, copy, modify, merge, publish, distribute, sublicense, and/or sell -copies of the Software, and to permit persons to whom the Software is -furnished to do so, subject to the following conditions: - -The above copyright notice and this permission notice shall be included in -all copies or substantial portions of the Software. - -THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR -IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, -FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE -AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER -LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, -OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN -THE SOFTWARE. diff --git a/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/README b/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/README deleted file mode 100644 index 928659f30..000000000 --- a/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/README +++ /dev/null @@ -1,118 +0,0 @@ -This README file contains information on building the meta-{{=machine}} -BSP layer, and booting the images contained in the /binary directory. -Please see the corresponding sections below for details. - - -Dependencies -============ - -This layer depends on: - - URI: git://git.openembedded.org/bitbake - branch: master - - URI: git://git.openembedded.org/openembedded-core - layers: meta - branch: master - - URI: git://git.yoctoproject.org/xxxx - layers: xxxx - branch: master - - -Patches -======= - -Please submit any patches against this BSP to the Yocto mailing list -(yocto@yoctoproject.org) and cc: the maintainer: - -Maintainer: XXX YYYYYY <xxx.yyyyyy@zzzzz.com> - -Please see the meta-xxxx/MAINTAINERS file for more details. - - -Table of Contents -================= - - I. Building the meta-{{=machine}} BSP layer - II. Booting the images in /binary - - -I. Building the meta-{{=machine}} BSP layer -======================================== - ---- replace with specific instructions for your layer --- - -In order to build an image with BSP support for a given release, you -need to download the corresponding BSP tarball from the 'Board Support -Package (BSP) Downloads' page of the Yocto Project website. - -Having done that, and assuming you extracted the BSP tarball contents -at the top-level of your yocto build tree, you can build a -{{=machine}} image by adding the location of the meta-{{=machine}} -layer to bblayers.conf, along with any other layers needed (to access -common metadata shared between BSPs) e.g.: - - yocto/meta-xxxx \ - yocto/meta-xxxx/meta-{{=machine}} \ - -To enable the {{=machine}} layer, add the {{=machine}} MACHINE to local.conf: - - MACHINE ?= "{{=machine}}" - -You should then be able to build a {{=machine}} image as such: - - $ source oe-init-build-env - $ bitbake core-image-sato - -At the end of a successful build, you should have a live image that -you can boot from a USB flash drive (see instructions on how to do -that below, in the section 'Booting the images from /binary'). - -As an alternative to downloading the BSP tarball, you can also work -directly from the meta-xxxx git repository. For each BSP in the -'meta-xxxx' repository, there are multiple branches, one corresponding -to each major release starting with 'laverne' (0.90), in addition to -the latest code which tracks the current master (note that not all -BSPs are present in every release). Instead of extracting a BSP -tarball at the top level of your yocto build tree, you can -equivalently check out the appropriate branch from the meta-xxxx -repository at the same location. - - -II. Booting the images in /binary -================================= - ---- replace with specific instructions for your platform --- - -This BSP contains bootable live images, which can be used to directly -boot Yocto off of a USB flash drive. - -Under Linux, insert a USB flash drive. Assuming the USB flash drive -takes device /dev/sdf, use dd to copy the live image to it. For -example: - -# dd if=core-image-sato-{{=machine}}-20101207053738.hddimg of=/dev/sdf -# sync -# eject /dev/sdf - -This should give you a bootable USB flash device. Insert the device -into a bootable USB socket on the target, and power on. This should -result in a system booted to the Sato graphical desktop. - -If you want a terminal, use the arrows at the top of the UI to move to -different pages of available applications, one of which is named -'Terminal'. Clicking that should give you a root terminal. - -If you want to ssh into the system, you can use the root terminal to -ifconfig the IP address and use that to ssh in. The root password is -empty, so to log in type 'root' for the user name and hit 'Enter' at -the Password prompt: and you should be in. - ----- - -If you find you're getting corrupt images on the USB (it doesn't show -the syslinux boot: prompt, or the boot: prompt contains strange -characters), try doing this first: - -# dd if=/dev/zero of=/dev/sdf bs=1M count=512 diff --git a/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/README.sources b/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/README.sources deleted file mode 100644 index 3c4cb7b43..000000000 --- a/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/README.sources +++ /dev/null @@ -1,17 +0,0 @@ -The sources for the packages comprising the images shipped with this -BSP can be found at the following location: - -http://downloads.yoctoproject.org/mirror/sources/ - -The metadata used to generate the images shipped with this BSP, in -addition to the code contained in this BSP, can be found at the -following location: - -http://www.yoctoproject.org/downloads/yocto-1.1/poky-edison-6.0.tar.bz2 - -The metadata used to generate the images shipped with this BSP, in -addition to the code contained in this BSP, can also be found at the -following locations: - -git://git.yoctoproject.org/poky.git -git://git.yoctoproject.org/meta-xxxx diff --git a/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/binary/.gitignore b/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/binary/.gitignore deleted file mode 100644 index e69de29bb..000000000 --- a/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/binary/.gitignore +++ /dev/null diff --git a/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/conf/layer.conf b/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/conf/layer.conf deleted file mode 100644 index 5529f4595..000000000 --- a/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/conf/layer.conf +++ /dev/null @@ -1,10 +0,0 @@ -# We have a conf and classes directory, add to BBPATH -BBPATH .= ":${LAYERDIR}" - -# We have a recipes-* directories, add to BBFILES -BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \ - ${LAYERDIR}/recipes-*/*/*.bbappend" - -BBFILE_COLLECTIONS += "{{=machine}}" -BBFILE_PATTERN_{{=machine}} = "^${LAYERDIR}/" -BBFILE_PRIORITY_{{=machine}} = "6" diff --git a/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/recipes-bsp/formfactor/formfactor/machine.noinstall b/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/recipes-bsp/formfactor/formfactor/machine.noinstall deleted file mode 100644 index b442d02d5..000000000 --- a/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/recipes-bsp/formfactor/formfactor/machine.noinstall +++ /dev/null @@ -1 +0,0 @@ -# yocto-bsp-dirname {{=machine}} diff --git a/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/recipes-bsp/formfactor/formfactor/machine/machconfig b/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/recipes-bsp/formfactor/formfactor/machine/machconfig deleted file mode 100644 index 3b85d3821..000000000 --- a/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/recipes-bsp/formfactor/formfactor/machine/machconfig +++ /dev/null @@ -1,5 +0,0 @@ -# Assume a USB mouse and keyboard are connected -{{ input type:"boolean" name:"touchscreen" msg:"Does your BSP have a touchscreen? (y/n)" default:"n" }} -HAVE_TOUCHSCREEN={{=touchscreen}} -{{ input type:"boolean" name:"keyboard" msg:"Does your BSP have a keyboard? (y/n)" default:"y" }} -HAVE_KEYBOARD={{=keyboard}} diff --git a/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/recipes-bsp/formfactor/formfactor_0.0.bbappend b/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/recipes-bsp/formfactor/formfactor_0.0.bbappend deleted file mode 100644 index 6d4804d12..000000000 --- a/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/recipes-bsp/formfactor/formfactor_0.0.bbappend +++ /dev/null @@ -1,2 +0,0 @@ -FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" - diff --git a/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/recipes-kernel/linux/kernel-list.noinstall b/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/recipes-kernel/linux/kernel-list.noinstall deleted file mode 100644 index 663dddbb0..000000000 --- a/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/recipes-kernel/linux/kernel-list.noinstall +++ /dev/null @@ -1,26 +0,0 @@ -{{ if kernel_choice == "custom": }} -{{ input type:"boolean" name:"custom_kernel_remote" prio:"20" msg:"Is the custom kernel you'd like to use in a remote git repo? (y/n)" default:"y"}} - -{{ if kernel_choice == "custom" and custom_kernel_remote == "y": }} -{{ input type:"edit-git-repo" name:"custom_kernel_remote_path" prio:"20" msg:"Please enter the full URI to the remote git repo (the default corresponds to linux-stable v3.16.3)" default:"git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git"}} - -{{ if kernel_choice == "custom" and custom_kernel_remote == "n": }} -{{ input type:"edit-git-repo" name:"custom_kernel_local_path" prio:"20" msg:"You've indicated that you're not using a remote git repo. Please enter the full path to the local git repo you want to use (the default assumes a local linux-stable v3.16.3)" default:"/home/trz/yocto/kernels/linux-stable.git"}} - -{{ if kernel_choice == "custom": }} -{{ input type:"boolean" name:"custom_kernel_need_kbranch" prio:"20" msg:"Do you need to use a specific (non-master) branch? (y/n)" default:"n"}} - -{{ if kernel_choice == "custom" and custom_kernel_need_kbranch == "y": }} -{{ input type:"edit" name:"custom_kernel_kbranch" prio:"20" msg:"Please enter the branch you want to use (the default branch corresponds to the linux-stable 'linux-3.16.y' branch):" default:"linux-3.16.y"}} - -{{ if kernel_choice == "custom": }} -{{ input type:"edit" name:"custom_kernel_srcrev" prio:"20" msg:"Please enter the SRCREV (commit id) you'd like to use (use '${AUTOREV}' to track the current HEAD):" default:"${AUTOREV}"}} - -{{ if kernel_choice == "custom": }} -{{ input type:"edit" name:"custom_kernel_linux_version" prio:"20" msg:"Please enter the Linux version of the kernel you've specified:" default:"3.16.3"}} - -{{ if kernel_choice == "custom": }} -{{ input type:"edit" name:"custom_kernel_linux_version_extension" prio:"20" msg:"Please enter a Linux version extension if you want (it will show up at the end of the kernel name shown by uname):" default:"-custom"}} - -{{ if kernel_choice == "custom": }} -{{ input type:"edit-file" name:"custom_kernel_defconfig" prio:"20" msg:"It's recommended (but not required) that custom kernels be built using a defconfig. Please enter the full path to the defconfig for your kernel (NOTE: if you don't specify a defconfig the kernel probably won't build or boot):" default:""}} diff --git a/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/recipes-kernel/linux/linux-yocto-custom.bb b/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/recipes-kernel/linux/linux-yocto-custom.bb deleted file mode 100644 index fda955b5e..000000000 --- a/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/recipes-kernel/linux/linux-yocto-custom.bb +++ /dev/null @@ -1,57 +0,0 @@ -# yocto-bsp-filename {{ if kernel_choice == "custom": }} this -# This file was derived from the linux-yocto-custom.bb recipe in -# oe-core. -# -# linux-yocto-custom.bb: -# -# A yocto-bsp-generated kernel recipe that uses the linux-yocto and -# oe-core kernel classes to apply a subset of yocto kernel -# management to git managed kernel repositories. -# -# Warning: -# -# Building this kernel without providing a defconfig or BSP -# configuration will result in build or boot errors. This is not a -# bug. -# -# Notes: -# -# patches: patches can be merged into to the source git tree itself, -# added via the SRC_URI, or controlled via a BSP -# configuration. -# -# example configuration addition: -# SRC_URI += "file://smp.cfg" -# example patch addition: -# SRC_URI += "file://0001-linux-version-tweak.patch -# example feature addition: -# SRC_URI += "file://feature.scc" -# - -inherit kernel -require recipes-kernel/linux/linux-yocto.inc - -{{ if kernel_choice == "custom" and custom_kernel_remote == "y": }} -SRC_URI = "{{=custom_kernel_remote_path}};protocol=git;bareclone=1;branch=${KBRANCH}" -{{ if kernel_choice == "custom" and custom_kernel_remote == "n": }} -SRC_URI = "git://{{=custom_kernel_local_path}};protocol=file;bareclone=1;branch=${KBRANCH}" - -SRC_URI += "file://defconfig" - -SRC_URI += "file://{{=machine}}.scc \ - file://{{=machine}}.cfg \ - file://{{=machine}}-user-config.cfg \ - file://{{=machine}}-user-patches.scc \ - " - -{{ if kernel_choice == "custom" and custom_kernel_need_kbranch == "y" and custom_kernel_kbranch and custom_kernel_kbranch != "master": }} -KBRANCH = "{{=custom_kernel_kbranch}}" - -LINUX_VERSION ?= "{{=custom_kernel_linux_version}}" -LINUX_VERSION_EXTENSION ?= "{{=custom_kernel_linux_version_extension}}" - -SRCREV="{{=custom_kernel_srcrev}}" - -PV = "${LINUX_VERSION}+git${SRCPV}" - -COMPATIBLE_MACHINE_{{=machine}} = "{{=machine}}" diff --git a/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/recipes-kernel/linux/linux-yocto-custom.noinstall b/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/recipes-kernel/linux/linux-yocto-custom.noinstall deleted file mode 100644 index 017d206c2..000000000 --- a/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/recipes-kernel/linux/linux-yocto-custom.noinstall +++ /dev/null @@ -1 +0,0 @@ -# yocto-bsp-dirname {{ if kernel_choice == "custom": }} linux-yocto-custom diff --git a/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/recipes-kernel/linux/linux-yocto-custom/defconfig b/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/recipes-kernel/linux/linux-yocto-custom/defconfig deleted file mode 100644 index ceb0ffa30..000000000 --- a/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/recipes-kernel/linux/linux-yocto-custom/defconfig +++ /dev/null @@ -1,5 +0,0 @@ -# -# Placeholder for custom default kernel configuration. yocto-bsp will -# replace this file with a user-specified defconfig. -# -{{ if custom_kernel_defconfig: replace_file(of, custom_kernel_defconfig) }} diff --git a/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/recipes-kernel/linux/linux-yocto-custom/machine-user-config.cfg b/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/recipes-kernel/linux/linux-yocto-custom/machine-user-config.cfg deleted file mode 100644 index 922309d5a..000000000 --- a/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/recipes-kernel/linux/linux-yocto-custom/machine-user-config.cfg +++ /dev/null @@ -1,9 +0,0 @@ -# yocto-bsp-filename {{=machine}}-user-config.cfg -# -# Used by yocto-kernel to manage config options. -# -# yocto-kernel may change the contents of this file in any -# way it sees fit, including removing comments like this, -# so don't manually make any modifications you don't want -# to lose. -# diff --git a/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/recipes-kernel/linux/linux-yocto-custom/machine-user-patches.scc b/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/recipes-kernel/linux/linux-yocto-custom/machine-user-patches.scc deleted file mode 100644 index 6d1138f42..000000000 --- a/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/recipes-kernel/linux/linux-yocto-custom/machine-user-patches.scc +++ /dev/null @@ -1,9 +0,0 @@ -# yocto-bsp-filename {{=machine}}-user-patches.scc -# -# Used by yocto-kernel to manage patches. -# -# yocto-kernel may change the contents of this file in any -# way it sees fit, including removing comments like this, -# so don't manually make any modifications you don't want -# to lose. -# diff --git a/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/recipes-kernel/linux/linux-yocto-custom/machine.cfg b/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/recipes-kernel/linux/linux-yocto-custom/machine.cfg deleted file mode 100644 index 1ba8201f1..000000000 --- a/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/recipes-kernel/linux/linux-yocto-custom/machine.cfg +++ /dev/null @@ -1,4 +0,0 @@ -# yocto-bsp-filename {{=machine}}.cfg -# -# A convenient place to add config options, nothing more. -# diff --git a/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/recipes-kernel/linux/linux-yocto-custom/machine.scc b/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/recipes-kernel/linux/linux-yocto-custom/machine.scc deleted file mode 100644 index 0b6b41337..000000000 --- a/yocto-poky/scripts/lib/bsp/substrate/target/arch/common/recipes-kernel/linux/linux-yocto-custom/machine.scc +++ /dev/null @@ -1,18 +0,0 @@ -# yocto-bsp-filename {{=machine}}.scc -# -# The top-level 'feature' for the {{=machine}} custom kernel. -# -# Essentially this is a convenient top-level container or starting -# point for adding lower-level config fragements and features. -# - -# {{=machine}}.cfg in the linux-yocto-custom subdir is just a -# convenient place for adding random config fragments. - -kconf hardware {{=machine}}.cfg - -# These are used by yocto-kernel to add config fragments and features. -# Don't remove if you plan on using yocto-kernel with this BSP. - -kconf hardware {{=machine}}-user-config.cfg -include {{=machine}}-user-patches.scc |