diff options
| -rw-r--r-- | MAINTAINERS | 44 | ||||
| -rw-r--r-- | README.md (renamed from README) | 26 | ||||
| -rw-r--r-- | common/README.md (renamed from common/README) | 3 | ||||
| -rw-r--r-- | meta-amdfalconx86/README | 20 | ||||
| -rw-r--r-- | meta-amdfalconx86/README.md | 15 | ||||
| -rw-r--r-- | meta-baldeagle/README | 20 | ||||
| -rw-r--r-- | meta-baldeagle/README.md | 15 | ||||
| -rw-r--r-- | meta-seattle/README.md (renamed from meta-seattle/README) | 68 | ||||
| -rw-r--r-- | meta-steppeeagle/README | 20 | ||||
| -rw-r--r-- | meta-steppeeagle/README.md | 15 |
10 files changed, 79 insertions, 167 deletions
diff --git a/MAINTAINERS b/MAINTAINERS deleted file mode 100644 index 85f55241..00000000 --- a/MAINTAINERS +++ /dev/null @@ -1,44 +0,0 @@ -This file contains a list of BSP maintainers for the BSPs contained in -the meta-amd repository. - -The purpose of this file is to provide contact information for -specific BSPs and other code contained within meta-amd. You should -address questions and patches for a particular BSP or other code to -the appropriate maintainer listed in this file, cc'ing the meta-amd -mailing list. This ensures that your question or patch will be -addressed by the appropriate person, and that it will be seen by other -users who may be facing similar problems or questions. - -Please see the top-level README file for guidelines relating to the -details of submitting patches, reporting problems, or asking questions -about any of the BSPs or other recipes contained within meta-amd. - -Descriptions of section entries: - - M: Mail patches to: FullName <address@domain> - F: Files and directories with wildcard patterns. - A trailing slash includes all files and subdirectory files. - F: meta-amd/ all files in and below meta-amd - F: meta-amd/* all files in meta-amd, but not below - One pattern per line. Multiple F: lines acceptable. - -Please keep this list in alphabetical order. - -Maintainers List (try to look for most precise areas first) - - ----------------------------------- -baldeagle -M: Drew Moseley<drew_moseley@mentor.com> -F: meta-baldeagle/ - -common -M: Drew Moseley<drew_moseley@mentor.com> -F: common/ - -steppeeagle -M: Drew Moseley<drew_moseley@mentor.com> -F: meta-steppeeagle/ - -seattle -M: Adrian Calianu <adrian.calianu@enea.com> -F: meta-seattle/ @@ -1,16 +1,15 @@ -meta-amd -========== +# meta-amd This is the location for AMD BSPs. Please see the README files contained in the individual BSP layers for -BSP-specific information. +BSP-specific information like dependencies etc. If you have problems with or questions about a particular BSP, please -contact the maintainer listed in the MAINTAINERS file directly (cc:ing -the Yocto mailing list puts it in the archive and helps other people -who might have the same questions in the future), but please try to do -the following first: +contact the maintainer of the particular layer as listed in the +MAINTAINERS section below directly (cc:ing the Yocto mailing list +puts it in the archive and helps other people who might have the same +questions in the future), but please try to do the following first: - look in the Yocto Project Bugzilla (http://bugzilla.yoctoproject.org/) to see if a problem has @@ -31,8 +30,7 @@ submit the bug against the most likely category for the problem - if you're wrong, it's not a big deal and the bug will be recategorized upon triage. -Guidelines for submitting patches -================================= +## Contributing Please submit any patches against meta-amd BSPs to the meta-amd mailing list (meta-amd@yoctoproject.org). Also, if your patches are @@ -82,3 +80,13 @@ The meta-amd maintainers will do their best to review and/or pull in a patch or patchset within 24 hours of the time it was posted. For larger and/or more involved patches and patchsets, the review process may take longer. + +## Maintainers + +The per layer gatekeepers are the following. + +- amdfalconx86: Drew Moseley, drew_moseley@mentor.com +- baldeagle: Drew Moseley, drew_moseley@mentor.com +- common: Drew Moseley, drew_moseley@mentor.com +- steppeeagle: Drew Moseley, drew_moseley@mentor.com +- seattle: Adrian Calianu, adrian.calianu@enea.com diff --git a/common/README b/common/README.md index f153f5d6..0fe68c20 100644 --- a/common/README +++ b/common/README.md @@ -1,5 +1,4 @@ -meta-amd/common -=============== +# meta-amd/common This layer contains metadata that is appropriate for all AMD-based platforms. diff --git a/meta-amdfalconx86/README b/meta-amdfalconx86/README deleted file mode 100644 index 45106d0b..00000000 --- a/meta-amdfalconx86/README +++ /dev/null @@ -1,20 +0,0 @@ -meta-amd/meta-amdfalconx86 -========================== - -This is the location for AMD Falcon Family BSP. - -Please see the README file contained in the root meta-amd directory -for general information and usage details. - -Dependencies -============ - -This layer depends on: - -URI: git://git.openembedded.org/bitbake - -URI: git://git.openembedded.org/openembedded-core -layers: meta - -URI: git://git.openembedded.org/meta-openembedded -layers: meta-oe diff --git a/meta-amdfalconx86/README.md b/meta-amdfalconx86/README.md new file mode 100644 index 00000000..0eb88b41 --- /dev/null +++ b/meta-amdfalconx86/README.md @@ -0,0 +1,15 @@ +# meta-amd/meta-amdfalconx86 + +This is the location for AMD Falcon Family BSP. + +Please see the README file contained in the root meta-amd directory +for general information and usage details. + +## Dependencies + +This layer depends on: + +[bitbake](https://github.com/openembedded/bitbake) layer, +[oe-core](https://github.com/openembedded/openembedded-core) layer, +[meta-oe](https://github.com/openembedded/meta-openembedded) layer, +meta-amd/common layer diff --git a/meta-baldeagle/README b/meta-baldeagle/README deleted file mode 100644 index cce5fa07..00000000 --- a/meta-baldeagle/README +++ /dev/null @@ -1,20 +0,0 @@ -meta-amd/meta-baldeagle -======================= - -This is the location for AMD Bald Eagle BSP. - -Please see the README file contained in the root meta-amd directory -for general information and usage details. - -Dependencies -============ - -This layer depends on: - -URI: git://git.openembedded.org/bitbake - -URI: git://git.openembedded.org/openembedded-core -layers: meta - -URI: git://git.openembedded.org/meta-openembedded -layers: meta-oe diff --git a/meta-baldeagle/README.md b/meta-baldeagle/README.md new file mode 100644 index 00000000..90cd98e7 --- /dev/null +++ b/meta-baldeagle/README.md @@ -0,0 +1,15 @@ +# meta-amd/meta-baldeagle + +This is the location for AMD Bald Eagle BSP. + +Please see the README file contained in the root meta-amd directory +for general information and usage details. + +## Dependencies + +This layer depends on: + +[bitbake](https://github.com/openembedded/bitbake) layer, +[oe-core](https://github.com/openembedded/openembedded-core) layer, +[meta-oe](https://github.com/openembedded/meta-openembedded) layer, +meta-amd/common layer diff --git a/meta-seattle/README b/meta-seattle/README.md index fd4d4610..d2e7ed88 100644 --- a/meta-seattle/README +++ b/meta-seattle/README.md @@ -1,59 +1,27 @@ -meta-seattle -============ +# meta-seattle -This is the location for AMD Seattle maintained BSP. +This is the location for AMD Seattle BSP. - -Overview of AMD 64-bit ARM-based processor ------------------------------------------- +## Overview of AMD 64-bit ARM-based processor The AMD Opteron A1100-Series features AMDs first 64-bit ARM-based processor, codenamed "Seattle". - -Yocto Project Compatible -======================== +## Yocto Project Compatible This BSP is compatible with the Yocto Project as per the requirements listed here: https://www.yoctoproject.org/webform/yocto-project-compatible-registration -Dependencies -============ +## 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/meta-amd - layers: common - branch: master - -Patches -======= - -Please submit any patches against this BSP to the maintainer and cc -the meta-amd mailing list (meta-amd@yoctoproject.org): +[bitbake](https://github.com/openembedded/bitbake) layer, +[oe-core](https://github.com/openembedded/openembedded-core) layer, +meta-amd/common layer -Maintainer: Adrian Calianu <adrian.calianu@enea.com> - - -Table of Contents -================= - - I. Building the meta-seattle BSP layer - II. Booting the images -III. How to Run 32-bit Applications on aarch64 - IV. Limitations - - -I. Building the meta-seattle BSP layer -======================================= +## Building the meta-seattle BSP layer The following instructions require a Poky installation (or equivalent). @@ -83,8 +51,7 @@ Once complete the images for the target machine will be available in the output directory 'tmp/deploy/images'. -II. Booting the images -===================================== +## Booting the images Booting the images using UEFI firmware @@ -119,8 +86,7 @@ References: 1) https://www.kernel.org/doc/Documentation/efi-stub.txt 2) http://www.uefi.org/specifications -III. How to Run 32-bit Applications on aarch64 -============================================== +## How to Run 32-bit Applications on aarch64 Since multilib is not yet available for aarch64, this BSP offers some alternatives in order to run 32-bit legacy applications on an aarch64. @@ -132,8 +98,7 @@ chroot and another one qemu installation. meta-seattle BSP includes two scripts that help you to setup environment for 32bit applications that can be found under following path meta-seattle/recipes-support/32b-env/ -III.1 Using chroot tool to run 32-bit applications on aarch64 -============================================================= +### Using chroot tool to run 32-bit applications on aarch64 This solution requires the chroot tool on the target, a 32b-built rootfs, and a build for the seattle machine. @@ -144,15 +109,14 @@ root@seattle:~# tar -zxf rootfs32.tar.gz root@seattle:~# set_32b_env_chroot.sh -r ./rootfs32 -# 32b environment started +- 32b environment started @seattle:~# ./hello32d Starting from this point, any 32-bit application can be executed, but not 64-bit applications which will fail due to wrong path to 32-bit libraries. To run a 64-bit application, chroot mode must be quit by using the "exit" command. -III.2 Using qemu to run 32-bit applications on aarch64 -====================================================== +### Using qemu to run 32-bit applications on aarch64 This example requires an existing 32b-built rootfs and a build for the seattle machine. It is also expected that qemu-arm is already installed!!! @@ -163,8 +127,8 @@ root@seattle:~# source /usr/bin/set_32b_env_qemu.sh -r ./rootfs32 Starting from this point, any 32-bit or 64-bit application can be executed. -IV. Limitations -=============== +## Limitations + In order to enable 32-bit support in the aarch64 kernel, COMPAT mode is enabled (CONFIG_COMPAT=y), page size set to 4K, and VirtualAddress set to 48-bit. diff --git a/meta-steppeeagle/README b/meta-steppeeagle/README deleted file mode 100644 index c731ebeb..00000000 --- a/meta-steppeeagle/README +++ /dev/null @@ -1,20 +0,0 @@ -meta-amd/meta-steppeeagle -========================= - -This is the location for AMD Steppe Eagle BSP. - -Please see the README file contained in the root meta-amd directory -for general information and usage details. - -Dependencies -============ - -This layer depends on: - -URI: git://git.openembedded.org/bitbake - -URI: git://git.openembedded.org/openembedded-core -layers: meta - -URI: git://git.openembedded.org/meta-openembedded -layers: meta-oe diff --git a/meta-steppeeagle/README.md b/meta-steppeeagle/README.md new file mode 100644 index 00000000..b6b40388 --- /dev/null +++ b/meta-steppeeagle/README.md @@ -0,0 +1,15 @@ +# meta-amd/meta-steppeeagle + +This is the location for AMD Steppe Eagle BSP. + +Please see the README file contained in the root meta-amd directory +for general information and usage details. + +## Dependencies + +This layer depends on: + +[bitbake](https://github.com/openembedded/bitbake) layer, +[oe-core](https://github.com/openembedded/openembedded-core) layer, +[meta-oe](https://github.com/openembedded/meta-openembedded) layer, +meta-amd/common layer |