nyuuzyou/wikis huggingface dataset:
Extensible SDK

This page is being continually updated with more content. Please bookmark and come back soon. Any questions, contact Henry Bruce
== Introduction ==
The Yocto Project Extensible SDK (eSDK) has tools that allow you to easily add new applications and libraries to an image, modify the source of an existing component and test changes on the target hardware. The main benefit over the standard SDK is improved team workflow due to tighter integration with the OpenEmbedded build system.
Want to learn more about the Extensible SDK? You've come to the right place.
== Documentation ==
To learn about using the Extensible SDK read the SDK manual. Information on building and customizing an eSDK can be found in Appendix B. Also see this eSDK talk and companion devtool talk.
== Pre-built Installers ==
The Yocto Project auto-builder creates core-image-minimal and core-image-0sato eSDK installers for machines defined in oe-core. Currently only full installers are built. See http://autobuilder.yoctoproject.org/pub/releases/yocto-2.2.1/toolchain/x86_64. As an example poky-glibc-x86_64-core-image-sato-core2-64-toolchain-ext-2.2.1.sh is the core-image-sato eSDK installer for machine genericx86-64.
== Tips and Tricks ==
* Add cmake to your eSDK
== Workflow ==
Details of the improved Yocto Project workflow enabled by using containers and the eSDK can be found on the Developer Workflow Improvements page.
== Presentations ==
=== ELC 2017 ===
* Henry Bruce's eSDK talk and video
* Tim Orling's devtool talk and video
* Randy Witt's container talk and video
== Releases ==
* First appeared as part of fido (1.8).
* Jethro (2.0) is beta release.
* Krogoth (2.1) is first usable release.
* Morty (2.2) brings "devtool finish" that generates patches to go with recipe
* Pyro (2.3) focuses on bug fixes
* Rocko (2.4) brings devtool (and underlying recipetool) enhancements
== Community ==
The eSDK is part of Openembedded Core. 
* Mailing list: openembedded-core@lists.openembedded.org
* Bugs: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=extensible%20sdk&list_id=592532
* Yocto Project SDK QuickStart: https://mender.io/resources/yocto-sdk-quickstart
Extensible SDK Debugging

The extensible SDK is effectively an encapsulated instance of the normal build system. Generally that shouldn't be touched directly, however sometimes you need to debug why it's not doing what you expect it to do, either at install time or runtime.
== Accessing the eSDK internals ==
Run the following commands:
cd /path/to/sdk/install
. ./environment-setup-<tab complete>
. ./layers/<core layer>/oe-init-build-env .
WARNING: don't miss out the " ." at the end of the last command - if you do, it will not work!
Now you can run bitbake as you would normally.
FAQ:How do I change and add startup scripts

Q: How do I change and add startup scripts?
A: Edit meta/recipes-sato/matchbox-sato/matchbox-session-sato/session. Of course, if you have your own meta-layer, append the matchbox-session-sato_0.1.bb recipe.
Disable 'matchbox-desktop' and 'matchbox-panel', however, do not disable 'exec matchbox-window-manager ...'
Don't forget to run your app as a background process
For example, the following code will start the fifteen game:
#matchbox-desktop &
# Lines containing feature-[foo] are removed at build time if the machine
# doesn't have the feature "foo".
#START_APPLETS=showdesktop,windowselector
#END_APPLETS=clock,battery,systray,startup-notify,notify
#END_APPLETS=openmoko-panel-gsm,$END_APPLETS # feature-phone
#matchbox-panel --titlebar --start-applets $START_APPLETS --end-applets $END_APPLETS &
/usr/games/fifteen &
exec matchbox-window-manager -theme Sato -use_desktop_mode decorated -use_cursor $SHOWCURSOR $@
Category:FAQ Category:FAQ-open
FAQ:How do I configure the kernel

Q: How do I configure the kernel?
A: The yocto mailing list gives the following answers:
 
* [ http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#changing-the-kernel-configuration ] Answer from Joshua Lock
* [ http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#dev-manual-bsp-appendix ] Answer from Tom Zanussi
Category:FAQ Category:FAQ-answered
FAQ:What do I need to do when I change my recipe to ensure that the changes make it to the image

Q: What do I need to do when I change my recipe to ensure that the changes make it in to the image?
A: Update the PR variable in your recipe.
Explanation: Every recipe has a variable PR that holds the current release version of this recipe. If you do modifications on the recipe you need to increase the PR variable as well. Example:
Before modification of your recipe:
PR = "r2"
After modification after modification:
PR = "r3"
Bitbake tracks the release versions of every recipe and if the version increases it rebuilds the package(s) for that recipe.
Category:FAQ Category:FAQ-answered
FLOSS License Compliance

==Introduction to Open Source License Compliance with Yocto==
One of the issues the Yocto Project and OE-Core have attempted to help solve is the proliferation of embedded devices that violate various FLOSS licensing. Our licensing system, discussed below, is but a part of that overall effort. This document will discuss the various ways to help avoid a compliance violation both through use of the tools that Yocto provides as well as give some tips and hints on good release practices when developing your embedded device. This document should not to be construed as legal advice. For further information on FLOSS compliance, you should contact an attorney.
==History of License Compliance==
During the initial phase of license compliance with Yocto, one of the goals was to look at it through the eyes of both the end user, legal and license compliance enforcement agencies. With this in mind, Yocto license compliance currently falls into a number of feature groups.
-- License sanity checks
-- Image manifests
-- Blacklists/Whitelists
-- Copyleft source archives.
These feature groups help an embedded developer know that the license the upstream provider includes in the tarball has not changed, give them detailed information about what an image contains, give them very fine grained control over what licenses are and are not allowed on the image and assist the developer in producing a source archive with all necessary source. This functionality is fairly simple to implement however, it is up to the developer to maintain good release practices in order to avoid a license violation.
===Recipe/Package Licensing===
Each bitbake recipe should have at least the following two fields. LICENSE and LIC_
====
==Technical Information==
===LICENSE Field Standard===
==Best Practices==
Firmware upgrade on Minnowmax with Dediprog 600

This tutorial explains how to upgrade firmware in a Minnowmax with Dediprog 600.
You must have a Dediprog 600 with the USB cable interface needed to establish communication between platform and PC.
 
The connection to the platform is via the 8 pin connector cable inserted right here:
 
Note the red line in the cable, this is the right way to connect the cable, oriented with the pin 1.
 
You need to download the Dediprog 600 engineering software and drivers from: 
http://www.dediprog.com/pd/spi-flash-solution/sf600
To install the software just need to go through the process:
 
 
Now, for the driver installation, you need to download and unzip the files in a folder, go to Control Panel > Device manager and look for the unrecognized device (SF600-ISP):
 
Right clic and update driver, set the path where you unzip the driver files and ok.
 
Now get the latest BIOS file .
Open the Dediprog application, if everything was well configured a screen like this will open:
 
 
Choose OK and a screen like this will open:
 
 
From this screen select the button named "File" it will open a Open File window to find the BIOS file:
 
 
And the next step is to press the "Batch" Button
 
 
When the process finish, you will see a message like this:
 
 
--Juan Ramos (talk) 14:31, 30 November 2016 (PST)
Frequently Asked Release Engineering Questions

=== Frequently Asked Questions (Release Engineering) ==
=== How often are these pages updated? Who updates them? ===
The main Release wiki pages will be reviewed by the Yocto Project release engineer, half way between each major release and immediately after a major release, to ensure that information is kept up to date. 
=== When is the next major release? When is the next X.X.x release? ===
We release major releases at a 6 month interval. Generally, odd numbered releases fall sometime in mid-late October, even releases fall mid-late April. The next major release is due out sometime around April 2014.
Point releases are released on an adhoc basis.
=== How long are point releases supported ===
We will produce point releases of prior major releases:
* to fix critical bugs and security issues (CVEs) for the first 6 months after release
* to fix security issues(CVEs) for the first year after release
From an autobuilder standpoint, we generally maintain autobuilder backwards compatibility for at least 5 major releases. This is slowly getting better, with the goal of being able to be backwards compatible for at least 3 years worth of releases.
=== Danny? Dylan? Denzil? How can I find out the name of the next Yocto Project major release? ===
We generally call the next major release by it's major.minor number up until about a month or so prior to the major release. 
In the spirit of full disclosure, we don't even know the name of the release until Richard Purdie comes up with it.
The https://wiki.yoctoproject.org/wiki/Releases page of the wiki has a nice list of release numbers past and 
present. See that site for information.
=== Where does the naming convention come from? ===
It's a secret!
=== How does the Yocto Project release software? ===
The Yocto Project's Release Process establishes the full process for both major and point releases.
=== How do I release my own board support package and put them up on the Yocto Project downloads site? ===
The Third Party BSP Release Process establishes the full process for BSP releases.
=== How do I maintain compliance with open source licenses? ===
Coming Soon
=== How do I release a product using the Yocto Project? ===
Coming Soon
=== meta-jarvis layer? kernel 0.98pl13? What is wrong with you people? ===
Every major release includes an easter egg or two within the Yocto Project's release notes.
Prior Easter Eggs included:
* Implementation of a magic smoke generator
* The meta-jarvis layer for the Iron Man suit
* The meta-yocto-classic layer, which includes mc.
Most of these are inside project jokes. For example, our community manager, Jeff "jefro" Osier-Mixon bears a resemblance to Robert Downey Jr. 
Richard Purdie has a love of mc. They're generally pretty obvious jokes, except when they're not.
Full Pass Specification

==== M2 Test Execution Plan ====
Since there are still some unclear requirements for Yocto project, currently it’s hard to define test plan to cover all future milestone/weekly testing. According to the suggestion from KangKang, I defined a test execution plan for M2 testing, which only covers tests for M2 requirement.
The fullpass test plan is here, M2 fullpass test plan. For each target, like qemux86, qemuarm, netbook, e-Menlow, etc, I define separate test plan for them, with sub-tests chosen from the fullpass test plan.
I setup a testlink page to track test case and test plan status, http://otc-qa.sh.intel.com/testlink_yocto/. You can use username/passwd: guest/guest, to browser test case and test plan.
Full Pass Test Report for Yocto 1.3.1 RC1 201302262 Build

=Testing data=
 
 Test type: Full Pass
 Branch: danny
 Milestone: 1.3.1
 Build name: 1.3.1 RC1
 poky commit: 98292d1ef1cb44cf96f0a28fbca6439eda55ce1b
 poky commit date: Thu Feb 21 15:23:35 2013 +0000
 meta-intel commit: d38b102cb9f3c269391d026d2022f10a6e1b1f11
 Eclipse Plugin commit: cb8a0eff776d2cbd1b5f596a94dce825860574ab
 Autobuilder images repository: http://autobuilder.yoctoproject.org/pub/nightly/20130226-2
 Distributions tested: Fedora 17 i686, Fedora 18, OpenSUSE 12.1, OpenSUSE 12.2, Ubuntu 12.10 x86-64, Ubuntu 12.04 x86-64 
=Summary Report=
==Core Build System==
Status:
Bugs:
==HOB==
Status:
Bugs:
==BSP & QEMU==
Status:
Bugs:
==Performance testing==
Status:
Bugs:
Performance Metrics
Performance data comparison
==Build-appliance==
Status:
Bugs:
==ADT & Eclipse Plugin==
Status:
Bugs:
=Detailed Report=
==Core Build System==
===Bitbake===
Status
Bugs
Agenda
===Meta-Yocyo===
Status
Bugs
Agenda
===OE-Core===
Status
Bugs
Agenda
==Hob==
Status
Bugs
Agenda
==BSP==
===Emenlow: core-image-sato-sdk===
Status
Bugs
Agenda
===Sugarbay: core-image-sato-sdk===
Status
Bugs
Agenda
===Jasperforest: core-image-sato-sdk===
Status
Bugs
Agenda
===Crownbay: core-image-sato-sdk-noemgd===
Status
Bugs
Agenda
===FRI2: core-image-sato-sdk===
Status
Bugs
Agenda
==Qemu==
===qemux86: core-image-sato-sdk===
Status
Bugs
Agenda
===qemux86-64: core-image-sato-sdk===
Status
Bugs
Agenda
===qemuarm: core-image-sato-sdk===
Status
Bugs
Agenda
===qemumips: core-image-sato-sdk===
Status
Bugs
Agenda
===qemuppc: core-image-sato-sdk===
Status
Bugs
Agenda
===Beagleboard: core-image-sato-sdk===
Status
Bugs
Agenda
===Routerstationpro: core-image-sato-sdk===
Status
Bugs
Agenda
===MPC8315e-rdb: core-image-sato-sdk===
Status
Bugs
Agenda
===P1022ds-rdb: core-image-sato-sdk===
Status
Bugs
Agenda
==Performance Testing==
Status
Bugs
Agenda
Performance Metrics
Performance data comparison
==Build-appliance==
Status
Bugs
Agenda
==ADT==
===ADT on: Fedora 17 i686===
Status
Bugs
Agenda
===ADT on: Ubuntu 12.10 x86-64===
Status
Bugs
Agenda
==Eclipse Plugin==
Status
Bugs
Agenda
Full Pass Test Report for Yocto 1.3.1 RC2 201303012 Build

=Testing data=
 
 Test type: Full Pass
 Branch: danny
 Milestone: 1.3.1
 Build name: 1.3.1 RC2
 poky commit: 955827af15f611189c66850fd077de344e1285c3
 poky commit date: Thu Feb 21 09:28:02 2013 -0800
 meta-intel commit: d38b102cb9f3c269391d026d2022f10a6e1b1f11
 Eclipse Plugin commit: cb8a0eff776d2cbd1b5f596a94dce825860574ab
 Autobuilder images repository: http://autobuilder.yoctoproject.org/pub/nightly/20130301-2
 Distributions tested: Fedora 17 i686, Fedora 18, OpenSUSE 12.1, OpenSUSE 12.2, Ubuntu 12.10 x86-64, Ubuntu 12.04 x86-64 
=Summary Report=
==Core Build System==
Status:
Bugs:
==HOB==
Status:
Bugs:
==BSP & QEMU==
Status:
Bugs:
==Performance testing==
Status:
Bugs:
Performance Metrics
Performance data comparison
==Build-appliance==
Status:
Bugs:
==ADT & Eclipse Plugin==
Status:
Bugs:
=Detailed Report=
==Core Build System==
===Bitbake===
Status
Bugs
Agenda
===Meta-Yocyo===
Status
Bugs
Agenda
===OE-Core===
Status
Bugs
Agenda
==Hob==
Status
Bugs
Agenda
==BSP==
===Emenlow: core-image-sato-sdk===
Status
Bugs
Agenda
===Sugarbay: core-image-sato-sdk===
Status
Bugs
Agenda
===Jasperforest: core-image-sato-sdk===
Status
Bugs
Agenda
===Crownbay: core-image-sato-sdk-noemgd===
Status
Bugs
Agenda
===FRI2: core-image-sato-sdk===
Status
Bugs
Agenda
===atom-pc: core-image-sato-sdk===
Status
Bugs
Agenda
==Qemu==
===qemux86: core-image-sato-sdk===
Status
Bugs
Agenda
===qemux86-64: core-image-sato-sdk===
Status
Bugs
Agenda
===qemuarm: core-image-sato-sdk===
Status
Bugs
Agenda
===qemumips: core-image-sato-sdk===
Status
Bugs
Agenda
===qemuppc: core-image-sato-sdk===
Status
Bugs
Agenda
===Beagleboard: core-image-sato-sdk===
Status
Bugs
Agenda
===Routerstationpro: core-image-sato-sdk===
Status
Bugs
Agenda
===MPC8315e-rdb: core-image-sato-sdk===
Status
Bugs
Agenda
===P1022ds-rdb: core-image-sato-sdk===
Status
Bugs
Agenda
==Performance Testing==
Status
Bugs
Agenda
Performance Metrics
Performance data comparison
==Build-appliance==
Status
Bugs
Agenda
==ADT==
===ADT on: Ubuntu 12.10 x86-64===
Status
Bugs
Agenda
==Eclipse Plugin==
Status
Bugs
Agenda
Full Pass Test Report for Yocto 1.3.2 RC1 201305163 Build

=Testing data=
 
 Test type: Full Pass
 Branch: danny
 Milestone: 1.3.2
 Build name: 1.3.2 RC1
 poky commit: 8450317a6cbcc0b3e5ec00b266608ee1740d906c
 poky commit date: Thu May 16 13:48:42 2013 +0000
 meta-intel commit: d44f005338012cc7111190122b2ab08a29c0e0e7
 Eclipse Plugin commit: ae28375759e6c9a6eef64f74b61d95e1cb00783d
 Autobuilder images repository: http://autobuilder.yoctoproject.org/pub/nightly/20130516-3
 Distributions tested: 
=Summary Report=
	
Performance Metrics 
=Detailed Report=
Full Pass Test Report for Yocto 1.4.1 RC1 20130612-5 build

=Testing data=
 
 Test type: Fullpass Test
 Branch: dylan
 Milestone: 1.4.1 RC1
 Build name: Fullpass
 poky commit: 73f103bf9b2cdf985464dc53bf4f1cfd71d4531f
 poky commit date: Tue Jun 11 18:00:03 2013 +0100
 eclipse-poky: dc9a609c68fe4a6bbbf34d418fd6611489c1d6f7
 Eclipse Plugin commit: Wed Apr 17 20:01:23 2013 +0300
 Autobuilder images repository: http://autobuilder.yoctoproject.org/pub/nightly/20130612-5
 Environments used for testing: Fedora 18 x86_64, Fedora 18 i686, Ubuntu 13.04 x86_64, Ubuntu 12.04 x86_64, openSUSE 12.3 x86_64, 
 Distributions tested: Fedora 17 x86_64, Fedora 18 x86_64, Ubuntu 12.10 x86_64, Ubuntu 12.04 x86_64, openSUSE 12.3 x86_64, openSUSE 12.2 x86_64, CentOS 6.3 x86_64 
=Summary Report=
	
=Detailed Report=
Full Pass Test Report for Yocto 1.4.2 RC1 2013-08-18 build

=Testing data=
 
 Test type: Full pass post release
 Branch: dylan
 Milestone: 1.4.2
 Build name: 2013-08-18
 poky commit: d734ab491a30078d43dee5440c03acce2d251425
 poky commit date: Fri Aug 16 12:22:25 2013 +0100
 Eclipse Plugin commit: dc9a609c68fe4a6bbbf34d418fd6611489c1d6f7
 Autobuilder images repository: http://autobuilder.yoctoproject.org/pub/releases/dylan-1.4.2.rc1
 Distributions tested: Fedora 19 32bit, Fedora 18 64bit, Ubuntu 13.04 64bit, Ubuntu 12.04 64bit, CentOS 6.4 64bit, Opensuse 12.3 64bit, opensuse 12.2 64bit
 
=Summary Report=
	
=Detailed Report=
Full Pass Test Report for Yocto 1.4 M4 RC1 201302202 Build

=Testing data=
 
 Test type: Full Pass
 Branch: master
 Milestone: 1.4 M4
 Build name: 1.4_M4_RC1
 poky commit: 7d22ef28e64de06b6238d0ef9b664c0bee6efa46
 poky commit date: 2013-02-19
 meta-intel commit: 150be7c8fb97ac88737f6017fdf9dd47b273bb3e
 Eclipse Plugin commit: d18c45e0f5367979f7402380ee123242da2b57d5 
 Autobuilder images repository: http://autobuilder.yoctoproject.org/pub/nightly/20130220-2/
 Distributions tested: Ubuntu 12.04 x86-64, Ubuntu 12.10 x86-64, Fedora 17, Fedora 18, OpenSUSE 12.1, OpenSUSE 12.2 
=Summary Report=
==Core Build System==
Status:
Bugs:
==HOB==
Status:
Bugs:
==BSP & QEMU==
Status:
Bugs:
==Performance testing==
Status:
Bugs:
==Build-appliance==
Status:
Bugs:
==ADT & Eclipse Plugin==
Status:
Bugs:
=Detailed Report=
==Core Build System==
===Bitbake===
Status
Bugs
Agenda
===Meta-Yocyo===
Status
Bugs
Agenda
===OE-Core===
Status
Bugs
Agenda
==Hob==
Status
Bugs
Agenda
==BSP==
===NUC: core-image-sato-sdk===
Status
Bugs
Agenda
===Emenlow: core-image-sato-sdk===
Status
Bugs
Agenda
===Sugarbay: core-image-sato-sdk===
Status
Bugs
Agenda
===Jasperforest: core-image-sato-sdk===
Status
Bugs
Agenda
===Crownbay: core-image-sato-sdk-noemgd===
Status
Bugs
Agenda
===FRI2: core-image-sato-sdk===
Status
Bugs
Agenda
==Qemu==
===qemux86: core-image-sato-sdk===
Status
Bugs
Agenda
===qemux86-64: core-image-sato-sdk===
Status
Bugs
Agenda
===qemuarm: core-image-sato-sdk===
Status
Bugs
Agenda
===qemumips: core-image-sato-sdk===
Status
Bugs
Agenda
===qemuppc: core-image-sato-sdk===
Status
Bugs
Agenda
===Beagleboard: core-image-sato-sdk===
Status
Bugs
Agenda
===Routerstationpro: core-image-sato-sdk===
Status
Bugs
Agenda
===MPC8315e-rdb: core-image-sato-sdk===
Status
Bugs
Agenda
===P1022ds-rdb: core-image-sato-sdk===
Status
Bugs
Agenda
==Performance Testing==
Status
Bugs
Agenda
Performance Metrics
Performance data comparison
==Build-appliance==
Status
Bugs
Agenda
==ADT==
===ADT on: Fedora 17 i686===
Status
Bugs
Agenda
===ADT on: Fedora 17 x86-64===
Status
Bugs
Agenda
===ADT on: Ubuntu 12.04 x86-64===
Status
Bugs
Agenda
===ADT on: OpenSUSE 12.2 x86-64===
Status
Bugs
Agenda
==Eclipse Plugin==
===Eclipse Plugin on Fedora 17 x86-64===
Status
Bugs
Agenda
Full Pass Test Report for Yocto 1.4 M5 RC2 201303271 Build

=Testing data=
 
 Test type: Full Pass post-release
 Branch: master
 Milestone: 1.4 M5
 Build name: 1.4 M5 RC2
 poky commit: bdca49274173153b1b0a72887de6321b4756b684
 poky commit date: Tue Mar 26 17:47:26 2013 +0000
 meta-intel commit: 2e8760d272aa2c62b41cbf768445c99569604c5e
 Eclipse Plugin commit: 5e20d3c32072ddd91dceb8b2b793ef13f25b915e
 Autobuilder images repository: http://autobuilder.yoctoproject.org/pub/nightly/20130327-1
 Environments used for testing: Ubuntu 12.04 x86-64, Ubuntu 12.10 x86-64, Fedora 17, Fedora 18, OpenSUSE 12.2 x86-64
 Distribution Testing was performed on: Ubuntu 12.04, Ubuntu 12.10, Fedora 17, Fedora 18, OpenSUse 12.1, OpenSuse 12.2, CentOS 6.3 
=Summary Report=
==Core Build System==
Status:
Bugs:
==HOB==
Status:
Bugs:
==BSP & QEMU==
Status:
Bugs:
==Performance testing==
Status:
Bugs:
Performance Metrics
1.4_M4 bitbake core-image-sato: 1:16:45
1.4_M5: bitbake core-image-sato: 1:15:46
Detailed results: Build performance metrics
==Build-appliance==
Status:
Bugs:
==ADT & Eclipse Plugin==
Status:
Bugs:
=Detailed Report=
==Core Build System==
===Bitbake===
Status
Bugs
Agenda
===Meta-Yocyo===
Status
Bugs
Agenda
===OE-Core===
Status
Bugs
Agenda
==Hob==
Status
Bugs
Agenda
==BSP==
===Atom-pc: core-image-sato-sdk===
Status
Bugs
Agenda
===NUC: core-image-sato-sdk===
Status
Bugs
Agenda
===Emenlow: core-image-sato-sdk===
Status
Bugs
Agenda
===Sugarbay: core-image-sato-sdk===
Status
Bugs
Agenda
===Jasperforest: core-image-sato-sdk===
Status
Bugs
Agenda
===Crownbay: core-image-sato-sdk===
Status
Bugs
Agenda
===Crownbay: core-image-sato-sdk-noemgd===
Status
Bugs
Agenda
===FRI2: core-image-sato-sdk===
Status
Bugs
Agenda
===Beagleboard: core-image-sato-sdk===
Status
Bugs
Agenda
===Routerstationpro: core-image-sato-sdk===
Status
Bugs
Agenda
===MPC8315e-rdb: core-image-sato-sdk===
Status
Bugs
Agenda
===P1022ds-rdb: core-image-sato-sdk===
Status
Bugs
Agenda
==Qemu==
===qemux86: core-image-sato-sdk===
Status
Bugs
Agenda
===qemux86-64: core-image-sato-sdk===
Status
Bugs
Agenda
===qemuarm: core-image-sato-sdk===
Status
Bugs
Agenda
===qemumips: core-image-sato-sdk===
Status
Bugs
Agenda
===qemuppc: core-image-sato-sdk===
Status
Bugs
Agenda
==Performance Testing==
Status
Bugs
Agenda
Performance Metrics 
Detailed result at: Build performance metrics
==Build-appliance==
Status
Bugs
Agenda
==ADT==
===ADT on: Fedora 17 x86-64===
Status
Bugs
Agenda
===ADT on: Fedora 17 i686===
Status
Bugs
Agenda
===ADT on: Ubuntu 12.04 x86-64===
Status
Bugs
Agenda
===ADT on: OpenSUSE 12.2 x86-64===
Status
Bugs
Agenda
==Eclipse Plugin==
Status
Bugs
Agenda