Yocto Project - User contributions [en]

TipsAndTricks/UsingRPM

2018-03-15T17:52:23Z

Mhatle:

The RPM command allows for a number of query operations. The format of the query operations can be used for a number things, such as debugging a package or even exporting information into another format, such as XML.

First in order to perform a query, you want to tell the system to go into query mode:

''rpm -q''

You then need to add the option to tell it WHAT to query:

To query a single package that has been installed into the database, just add the package name, such as:

''rpm -q bash''

To query all of the installed packages in the system, add the '-a' option, such as:

''rpm -q -a''

To query a single package that is not yet installed, add '-p <package name>'

''rpm -q -p bash-3.0-r3.i386.rpm''

To query multiple packages, just list the packages after the -p:

''rpm -q -p bash-3.0-r3.i386.rpm libc6-7-r3.i386.rpm''

You can include lists of packages instead:

''echo "bash-3.0-r3.i386.rpm" > mymanifest.txt''
''echo "libc6-7-r3.i386.rpm" >> mymanifest.txt''
''rpm -q -p mymanifest.txt''

(Note: there is a minimum size of the file for RPM to determine this is a manifest file. So it's recommended if this is used in script to always include a header that says something like "# This is a manifest file".

The above operations simply control the 'what', by default the system will just print the package name. (Some versions will print the name and package architecture.)

In order to select the exact items you want to query, you want to use the '--queryformat' (or '--qf') to specify a format. Such as:

''rpm -q -p mymanifest.txt --qf "[%{NAME}\n]"''

The above duplicates the default. The special characters or parts being used are:

<nowiki>
[ ] - this indicates that it should be applied on each package or item (if the item being queried is an iterator, like a filelist.) Including '\n' inside of the brackets means adding a line feed at the end of every item that is queried.

%{...} -- this is how you specify the exact field to be queried. To get a list of valid options, you can run: 'rpm --querytags'.
</nowiki>

The format of %{...} also allows for select 'type' conversions. Some of the valid types are: octal, shescape, deptype, pgpsig, day, date, and others.

For instance, the typical, 'rpm -q bash --requires' is actually implemented as:

''rpm -q bash --qf "[%|VERBOSE?{%{REQUIREFLAGS:deptype}: }:{}|%{REQUIRENEVRS}\n]"''

The above indicate that based on the value 'VERBOSE', either %{REQUIREFLAGS:deptype} followed by either {} | %{REQUIRENEVRS}.

<nowiki>
| ? and other special operators exist to permit you to do some basic boolean cases. See: /usr/lib/rpm/rpmpopt-* for a bunch of examples.
</nowiki>

Another popular example is how to export the whole DB to XML:

''rpm -qa --qf "[%{*:xml}\n]"''

The '*' says to not only query the main thing, but also iterate over the matching entries (all of them), with the :xml indicating to dump the contents in XML format.

TipsAndTricks/UsingRPM

2018-03-15T17:51:17Z

Mhatle:

TipsAndTricks/UsingRPM

2018-03-15T17:48:49Z

Mhatle:

TipsAndTricks/UsingRPM

2018-03-15T17:48:14Z

Mhatle:

The RPM command allows for a number of query operations. The format of the query operations can be used for a number things, such as debugging a package or even exporting information into another format, such as XML.

First in order to perform a query, you want to tell the system to go into query mode:

''rpm -q''

You then need to add the option to tell it WHAT to query:

To query a single package that has been installed into the database, just add the package name, such as:

''rpm -q bash''

To query all of the installed packages in the system, add the '-a' option, such as:

''rpm -q -a''

To query a single package that is not yet installed, add '-p <package name>'

''rpm -q -p bash-3.0-r3.i386.rpm''

To query multiple packages, just list the packages after the -p:

''rpm -q -p bash-3.0-r3.i386.rpm libc6-7-r3.i386.rpm''

You can include lists of packages instead:

''echo "bash-3.0-r3.i386.rpm" > mymanifest.txt
echo "libc6-7-r3.i386.rpm" >> mymanifest.txt
rpm -q -p mymanifest.txt
''

(Note: there is a minimum size of the file for RPM to determine this is a manifest file. So it's recommended if this is used in script to always include a header that says something like "# This is a manifest file".

The above operations simply control the 'what', by default the system will just print the package name. (Some versions will print the name and package architecture.)

In order to select the exact items you want to query, you want to use the '--queryformat' (or '--qf') to specify a format. Such as:

''rpm -q -p mymanifest.txt --qf "[%{NAME}\n]"''

The above duplicates the default. The special characters or parts being used are:

<nowiki>
[ ] - this indicates that it should be applied on each package or item (if the item being queried is an iterator, like a filelist.) Including '\n' inside of the brackets means adding a line feed at the end of every item that is queried.

%{...} -- this is how you specify the exact field to be queried. To get a list of valid options, you can run: 'rpm --querytags'.
</nowiki>

The format of %{...} also allows for select 'type' conversions. Some of the valid types are: octal, shescape, deptype, pgpsig, day, date, and others.

For instance, the typical, 'rpm -q bash --requires' is actually implemented as:

''rpm -q bash --qf "[%|VERBOSE?{%{REQUIREFLAGS:deptype}: }:{}|%{REQUIRENEVRS}\n]"''

The above indicate that based on the value 'VERBOSE', either %{REQUIREFLAGS:deptype} followed by either {} | %{REQUIRENEVRS}.

<nowiki>
| ? and other special operators exist to permit you to do some basic boolean cases. See: /usr/lib/rpm/rpmpopt-* for a bunch of examples.
</nowiki>

Another popular example is how to export the whole DB to XML:

''rpm -qa --qf "[%{*:xml}\n]"''

The '*' says to not only query the main thing, but also iterate over the matching entries (all of them), with the :xml indicating to dump the contents in XML format.

TipsAndTricks/UsingRPM

2018-03-15T17:42:20Z

Mhatle: RPM usage tips and tricks

The RPM command allows for a number of query operations. The format of the query operations can be used for a number things, such as debugging a package or even exporting information into another format, such as XML.

First in order to perform a query, you want to tell the system to go into query mode:

rpm -q

You then need to add the option to tell it WHAT to query:

To query a single package that has been installed into the database, just add the package name, such as:

rpm -q bash

To query all of the installed packages in the system, add the '-a' option, such as:

rpm -q -a

To query a single package that is not yet installed, add '-p <package name>'

rpm -q -p bash-3.0-r3.i386.rpm

To query multiple packages, just list the packages after the -p:

rpm -q -p bash-3.0-r3.i386.rpm libc6-7-r3.i386.rpm

You can include lists of packages instead:

echo "bash-3.0-r3.i386.rpm" > mymanifest.txt
echo "libc6-7-r3.i386.rpm" >> mymanifest.txt

rpm -q -p mymanifest.txt

(Note: there is a minimum size of the file for RPM to determine this is a manifest file. So it's recommended if this is used in script to always include a header that says something like "# This is a manifest file".

The above operations simply control the 'what', by default the system will just print the package name. (Some versions will print the name and package architecture.)

In order to select the exact items you want to query, you want to use the '--queryformat' (or '--qf') to specify a format. Such as:

rpm -q -p mymanifest.txt --qf "[%{NAME}\n]"

The above duplicates the default. The special characters or parts being used are:

[ ] - this indicates that it should be applied on each package or item (if the item being queried is an iterator, like a filelist.) Including '\n' inside of the brackets means adding a line feed at the end of every item that is queried.

%{...} -- this is how you specify the exact field to be queried. To get a list of valid options, you can run: 'rpm --querytags'.

The format of %{...} also allows for select 'type' conversions. Some of the valid types are: octal, shescape, deptype, pgpsig, day, date, and others.

For instance, the typical, 'rpm -q bash --requires' is actually implemented as:

rpm -q bash --qf "[%|VERBOSE?{%{REQUIREFLAGS:deptype}: }:{}|%{REQUIRENEVRS}\n]"

The above indicate that based on the value 'VERBOSE', either %{REQUIREFLAGS:deptype} followed by either {} | %{REQUIRENEVRS}.

| ? and other special operators exist to permit you to do some basic boolean cases. See: /usr/lib/rpm/rpmpopt-* for a bunch of examples.

Another popular example is how to export the whole DB to XML:

rpm -qa --qf "[%{*:xml}\n]"

The '*' says to not only query the main thing, but also iterate over the matching entries (all of them), with the :xml indicating to dump the contents in XML format.

TipsAndTricks

2018-03-15T17:08:14Z

Mhatle: /* Articles in development */

== Background ==
This wiki page captures ideas for "Tips and tricks" articles that are aimed Yocto Project users that have a basic understanding of the core tools and want to extend their knowledge. Articles will written and published using the following process
* Articles must refer to the current (or earlier) release. They must not cover features in development in the master branch.
* Anyone can add entries to the '''Ideas for Articles''' section based on challenges they have encountered when using the Yocto Project
* More experienced developers can start to flesh out articles in the ''Ideas'' section move then to '''Articles in Development''' or contribute directly to this section.
* Approximately once a month an article ready for publishing will be chosen for publication by [mailto:jeffrey.osier-mixon@intel.com Jefro] and moved to the '''Finished Articles ''' section.

Please contact [mailto:henry.bruce@intel.com?Subject=Yocto%20Project%20Tips%20and%20Tricks Henry Bruce] with any questions.

== Ideas for Articles ==
* [[TipsAndTricks/GeneratingASDK]] (Ross, Paul help please...)
* [[TipsAndTricks/AddingALicense]] (Ross)
* [[TipsAndTricks/UsingBuildstatsDiff]] (Ross)
* [[TipsAndTricks/DevPyShell]] (Richard Purdie)
* [[TipsAndTricks/CreatingABSP]]. And what not to put in it.
* [[TipsAndTricks/Patchwork]]
* [[TipsAndTricks/Patchtest]] (Leo)
* [[TipsAndTricks/CreateNewLayer]] (Brendan)
* [[TipsAndTricks/JenkinsPipelinesForContinuousIntegration]] (Tim Orling)

== Articles in development ==
* [[TipsAndTricks/Building core-image-minimal on AWS]] (bavery)
* [[TipsAndTricks/Running YP Image On AWS]] (Amber Elliot)
* [[TipsAndTricks/DockerOnImage]] (bavery)
* [[TipsAndTricks/OnTargetWorkFlowLeveragingRPMPackagefeeds]] (bavery)
* [[TipsAndTricks/BuildingAndRunningClearContainersonTarget]] (bavery)
* [[TipsAndTricks/KernelDevelopmentWithEsdk]] (Todor Minchev, Henry Bruce)
* [[TipsAndTricks/DebugNativeRecipeWithGdb]] (Joshua Lock)
* [[TipsAndTricks/Netconsole]] (Ross Burton)
* [[TipsAndTricks/ParsingProfiling]] (Richard Purdie)
* [[TipsAndTricks/DemystifyingTheLinuxYoctoKernel]] (Tom Zanussi)
* [[TipsAndTricks/Patching the source for a recipe]] (Paul Eggleton)
* [[TipsAndTricks/Incorporating closed source components]] (Paul Eggleton)
* [[TipsAndTricks/DebuggingAvoidingRebuilds]] (Richard Purdie)
* [[TipsAndTricks/GitBisectABitbake]] (Ross)
* [[TipsAndTricks/RunningEclipseAgainstBuiltImage]] (bavery)
* [[TipsAndTricks/PrelinkSomePointersAndWorkarounds]] (bavery)
* [[TipsAndTricks/RunningQemuOnMacOSX]] (Stephano)
* [[TipsAndTricks/Understanding what changed (diffsigs etc)]] (Joshua)
* [[TipsAndTricks/CropsCLIContainers]] (bavery)
* [[TipsAndTricks/QuickAndDirtyKernelConfig]] (bavery)
* [[TipsAndTricks/TestingToasterWithContainers]] (bavery)
* [[TipsAndTricks/InvestigatingBuildTime]] (Leo Sandoval)
* [[TipsAndTricks/ResolvingLocaleIssues]] (bavery)
* [[TipsAndTricks/DebuggingBitbakeInPudb]] (bavery)
* [[TipsAndTricks/DebuggingBitbakeInWingIDE]] (bavery)
* [[TipsAndTricks/CliBuildsInToasterBuilddir]] (bavery)
* [[TipsAndTricks/BuildingZephyrImages]] (Henry)
* [[TipsAndTricks/Cmake,Eclipse, and SDKS]] (bavery)
* [[TipsAndTricks/LinuxKernelAndSDKs]] (bavery)
* [[TipsAndTricks/Running YP binaries on Ubuntu and Vice Versa]] (bavery)
* [[TipsAndTricks/LockSharedState]] (Stephano)
* [[TipsAndTricks/Building and booting for Joule or MinnowBoard]] (Cal)
* [[TipsAndTricks/EnablingAPackageFeed]] (Henry)
* [[TipsAndTricks/Creating Recipes for ROS modules]] (Henry)
* [[TipsAndTricks/TeamWorkflows]] (Joshua)
* [[TipsAndTricks/UseRamdisikToSpeedUpBuilds]] (Juro)
* [[TipsAndTricks/DebuggingHardQemuFailures]] (RP)
* [[TipsAndTricks/MiningPerformanceData]]
* [[TipsAndTricks/UsingRPM]] (fray)

== Finished Articles ==
* [[TipsAndTricks/Packaging Prebuilt Libraries | Packaging Prebuilt Libraries]] (Ross and Henry)
* [[TipsAndTricks/NPM | Packaging Node.js Projects]] (Brendan and Henry)

File:Yocto DevDay Advanced Class Prague.pdf

2017-10-26T07:48:24Z

Mhatle: Mhatle uploaded a new version of "File:Yocto DevDay Advanced Class Prague.pdf": Update fibonacci-lib and fibonacci-srv examples

Advanced Class Prague Slides in PDF

File:Yocto DevDay Advanced Class Prague.pptx

2017-10-26T07:47:09Z

Mhatle: Mhatle uploaded a new version of "File:Yocto DevDay Advanced Class Prague.pptx": Fix minor issues in fibonacci-lib and fibonacci-srv examples

Prague Advanced Class Slides - Initial Version

Member Technical Contacts

2016-11-14T17:58:24Z

Mhatle:

This page tracks the official technical contributors to the YP core from each of the Yocto Project's member organizations. Note that many organizations provide more resources than just one, particularly in terms of hardware or specific feature support, which is why the Yocto Project is a de facto standard for building Linux for embedded systems.

Gold Members

* Intel: Ross Burton <ross.burton@intel.com>
* Wind River: Robert Yang <liezhi.yang@windriver.com>; Mark Hatle <mark.hatle@windriver.com>; Bruce Ashfield <bruce.ashfield@windriver.com>
* Texas Instruments: Name <email>
* Juniper Networks: Name <email>
* Xilinx: Name <email>
* Mentor Graphics: Chris Larson <chris_larson@mentor.com>
* OpenEmbedded: Name <email>
* Long Term Support Initiative: Name <email>

Silver Members

* Renesas: Mr. Takamitsu Honda <takamitsu.honda.pv@renesas.com>
* Linaro: Koen Kooi <koen.kooi@linaro.org>; Nicolas Dechesne <nicolas.dechesne@linaro.org>; Fathi Boudra <fathi.boudra@linaro.org>
* MontaVista: Armin Kuster <akuster@mvista.com>
* Dell: Name <email>
* OS Systems: Fabio Berton <fabio.berton@ossystems.com.br>; Otavio Salvador <otavio@ossystems.com.br>
* Broadcom: Name <email>
* Enea: Name <email>
* AMD: Name <email>
* Timesys: Name <email>
* LG: Name <email>
* NXP: Name <email>
* Huawei: Name <email>

Smart

2012-10-31T19:29:19Z

Mhatle:

http://labix.org/smart/

Mark's smart contrib branch:

http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=mhatle/smart

(This is on top of OE-Core - cherry pick the patches on top of something else if you prefer - you'll probably need to revert the patch mentioned in [https://bugzilla.yoctoproject.org/show_bug.cgi?id=3371 bug 3371] as well).

To test this out querying a root filesystem on the host:

# Ensure you are using "package_rpm" in PACKAGE_CLASSES
# Comment out the line in core-image-minimal that removes the packaging data files
# <code>bitbake core-image-minimal</code>
# <code>bitbake python-smartpm-native</code>
# <code>bitbake -c devshell core-image-minimal</code>
# Within the devshell:
cd ../rootfs
export PATH=/path/to/native/sysroot/usr/bin/python-native:$PATH
export RPM_ETCRPM=$PWD/etc/rpm
smart --data-dir=$PWD/var/lib/smart channel --add rpmsys type=rpm-sys name="rpmsys"
smart --data-dir=$PWD/var/lib/smart config --set rpm-root=$PWD
smart --data-dir=$PWD/var/lib/smart config --set rpm-dbpath=/var/lib/rpm

You should now be able to query the packages installed into the rootfs e.g.
smart --data-dir=$PWD/var/lib/smart query

If you add an rpm-dir channel and run smart under pseudo you can install and uninstall packages:

smart --data-dir=$PWD/var/lib/smart channel --add test type=rpm-dir path=/path/to/tmp/deploy/rpm/i586
smart --data-dir=$PWD/var/lib/smart query # verify that the new channel is recognized
unset PSEUDO_DISABLED
unset PSEUDO_UNLOAD
export PSEUDO_LOCALSTATEDIR=$PWD/../pseudo
pseudo smart --data-dir=$PWD/var/lib/smart install zip # install 'zip' in the rootfs

Smart

2012-10-31T19:28:53Z

Mhatle:

Yocto 1.2 Features

2011-12-16T16:14:39Z

Mhatle: /* Unsorted */

== Potential Yocto Project 1.2 Features ==
Yocto Project 1.2 - Target release = April 2012

== Yocto Project 1.2 Themes ==
The topics below are the themes that some members of the team have started brainstorming for Yocto Project v1.2. These will be improved with community input.

=== Yocto Project 1.2 Objectives ===
The objectives of the Yocto 1.2 release are to increase adoption of the Yocto Project.

=== Yocto Project 1.2 Theme List ===
The Yocto Project 1.2 Themes towards the Objectives listed above are:

* Improved usability of the build system for new experienced users, new novice users and existing users.
*

== Process for Entering New Feature Requests ==

* Open a bug in the Yocto bugzilla setting the type of bug to be an "enhancement" request. The detail about the request should be included in the bugzilla report.
* Create a new entry in the appropriate feature table below (Poky, SDK, Hardware)
** Suggestion: start by copying an existing request as a template
* Give the feature a short, descriptive name
* Set the priority as appropriate (see the legend below)
* Set the Status to "Review"
* In the Source field, enter your name along with the origination of the request (e.g. OSV, OEM, Community) if applicable; provide as much detail here as you can
* In the Comments / Bugzilla field, provide any additional information for the request includind a link to a bugzilla entry
* Preview your Entry to make sure it looks ok and then save it

''Legend''

'''Priority:''' 1 = Must have, 2 = Nice to have but wouldn't block a release, 3 = Lower priority, desired, defined plan, 4 = Worthwhile ideas, no defined plan

'''Status:''' Accept = Engineering agreement to include in release, Review = Under Review for Inclusion in this release, Reject = Will not be included in this release

== Sample Table ==

This is a sample table to show how to submit features.

{| border="1"
||'''Feature Name''' ||'''Priority''' ||'''Status''' ||'''Source''' ||'''Comments / Bugzilla Links'''
|-
||Placeholder feature name || 1, 2, 3 or 4 || Review|| Name|| Comment + Link
|}

== Usability ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Build Appliance: Pre-configured VM Build image built by Yocto||1||Review||davest/tracey/RP||Saul (PRC)||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1557
|-
| Hob improvements||1||Review||davest/tracey/RP||Joshua/Jessica||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1559
|-
| Hob v2 - Interface updates? ||1||Review||davest/tracey/RP||Ke & PRC Team||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1588
|-
| Improve user experience under Windows||1||Review||davest/tracey/RP||Scott R.||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1586
|-
| Error Handling Improvements||1||Review||||Scott G||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1543
|-
| Firewall / Proxy handling in git||2||Review||davest/tracey/RP||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1585
|}

== Core/Bitbake ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Due'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Make BasicHash the default ||1||Review||RP||Lianhao(Jessica/RP)||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1555
|-
| Address git fetcher mirror issues||2||Review||RP||Richard||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1511
|-
| Recipe specific configuration (e.g. Gstreamer)||2||Resolved||||Richard / Resolved||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=923
|-
| Finish and enable PR server||2||Review||Lianhao||Lianhao||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1126
|-
| Host intrusion prevention/Swabber||2||Review||Joshua||Joshua||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1582
|-
| Yocto OOPS-type messages||2.5||Review||LCS||Paul to Investigate for 1.3 Feature||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1562
|-
| Recipe-specific sysroot||3||Review||from 1.0||Dongxiao||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1560
|-
| Handle old versions in WORKDIR||3||Review||from 1.0||Kai (WR)||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1561
|-
| Ability to build SRPM||3||Review||RP Notes||Jeff Polk/Mark||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1591
|-
| Binary package install class||3||Review||||Kai (WR)||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1592
|-
| Disk space monitoring||3||Review||RP and Robert||Robert (WR)||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1589
|-
| Ability to archive work dir||3||Review||LCS||Wenzong (WR)||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1590
|-
| Support for remote layers||3||Review||Community||Paul||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1598
|-
| Build Appliance: Pre-configured VM Build image (desktop Linux OS)||4||Review||LCS||||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1558
|-
| Depexp functionality without X||4||Review||Joshua||||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1658
|}

== QA Items ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Due'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Package History||1||Review||RP|||Paul||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1565
|-
| Package History Analysis Tool||1|||Review||RP|||Paul||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1566
|-
|QA Tests: Add recipe for LSB Tests and automate test||2||Review||||Yizhao||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1567
|-
|QA Tests: Add recipe for posix Tests and automate test||2||Review||||Jiajun||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1568
|-
|Open Source Test Cases||2||Review||QA||Jiajun (Song)||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1595
|-
| Collect data at build time to increase accuracy of estimation (hob)||2||Resolved||||Paul / Closed||1.2||Is this really Package History Now? http://bugzilla.yoctoproject.org/show_bug.cgi?id=1316
|-
|QA Tests: Add recipe for rt Tests and automate test||3||Review||||||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1569
|-
|QA Test improvements - consider fedora/gentoo runtime security tools||3||Review||Joshua||Jiajun||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1584
|-
| Automate BSP Testing||4||Review||Tom||||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1596
|-
| Test framework||4||Review||RP Notes||||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1594
|}

== Core Meta Data ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Due'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| build statistics reporting||2||Review||eflanagan||Beth||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1612
|-
| Sanity checks on per recipe basis||2||Review||RP Notes||Scott G||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=405
|-
| Package Documentation Audit: All recipes build||2||||Team||Scott G||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1619
|-
| Parallel Locale Generation ||2||Done||RP||RP - Resolved||1.2||Resolved? http://bugzilla.yoctoproject.org/show_bug.cgi?id=1554
|-
| Clean up warning messages||2||Review||||Saul||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1544
|-
| Multilib: Enhance gcc recipe to support multilibs||2||Review||RP||Nitin||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1549
|-
| Multilib: Complete recipe enablement||2||Review||RP||Dongxiao||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1563
|-
| Multilib: Drop MULTILIB_IMAGE_INSTALL||2||Review||RP||Dongxiao||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1564
|-
| Multilib: Document||2||Review||RP||Scott R||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1622
|-
| MeeGo GPLv2 Sync||2||Review||RP Notes||Saul||1.2|| http://bugzilla.yoctoproject.org/show_bug.cgi?id=1618
|-
| Finish Oracle/Sun Hotspot JDK/JRE support||2||Review||Tom||Nitin/Tom||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1620
|-
| Running post installs at rootfs gen time||2||Review||RP Notes||Dexuan||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1621
|-
| Fix Runtime POSIX Issue||2||Review||Team||Kai||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1623
|-
| License file cleanup ||2||Review||Beth||Beth||1.2||1 week http://bugzilla.yoctoproject.org/show_bug.cgi?id=1547
|-
| QEMU GL Enhancements||2||Review||Meta-data||Edwin||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1624
|-
| Init Selection as Distro Feature||2||Review||Joshua||Joshua w/Kai||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1625
|-
| Document multiple library versions co-existing||3||Review||Team||Scott R||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1548
|-
| Enhance TARGET_VENDOR field support||3||Review||RP||Ke||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1550
|-
| selinux patch integration||3||Review||Meta-data||ScottG w/WR||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1609
|-
| gtk+ sato filechooser patch||3||Review||RP Notes||Xiaofeng/Joshua||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1615
|-
| Investigate New UI||4||Review||Meta-data||Paul||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1606
|-
| Implement Factory reset||4||Review||Joshua||Joshua||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1593
|-
| Embedded java environment or even JDK support||4||Review||Team||Saul||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1613
|}

== Other Layer Meta Data ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Due'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| x32 Enhancements||2||Review||||Nitin||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1579
|-
| BSPs or layers for a specific category of devices ||2||Review||Dirk/Dave/Andy||Shane||1.2|| http://bugzilla.yoctoproject.org/show_bug.cgi?id=1626
|-
| Security layer||4||Review||Joshua||||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1597
|}

== Infrastructure ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Due'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| autobuilder layer support||need detail||2||Review||Beth||Beth||1.2|| 2 weeks, http://bugzilla.yoctoproject.org/show_bug.cgi?id=1628
|-
| buildstats memory measurements||need detail||2||Review||Beth||Beth||1.2||1 week and half, http://bugzilla.yoctoproject.org/show_bug.cgi?id=1629
|-
| autobuilder clean sstate option||||2||Review||Beth||Beth||1.2|| http://bugzilla.yoctoproject.org/show_bug.cgi?id=1627
|-
| Eval Patch management tools||||3||Review||RP Notes||||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1632
|-
| Bugzilla to Wiki||||2.5||Review||Darren||||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1631
|-
| Provide a click through license mechanism||||2||Review||Tom||Tom||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1630
|}

== BSPs ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Due'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Improve device management||[Need plan from Joshua]|| 2 ||Review||||Joshua/Darren||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1608
|-
| BSP update/intro||||2||Review||Bruce/Richard/team||Bruce||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1634
|-
|Drop Grub for Syslinux |||| 2 || Review || Darren || Darren || 1.2 ||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1635
|-
|Upgrade to EFI |||| 2 || Review || Darren || Darren || 1.2 ||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1636
|-
| replace qemuppc|||| 2 ||Review||||Bruce||1.2||http://bugzilla.pokylinux.org/show_bug.cgi?id=1638
|-
| streamline meta-intel kernel config options |||| 2 ||Review||Tom||Tom||1.2||http://bugzilla.pokylinux.org/show_bug.cgi?id=1661
|-
| add crownbay video acceleration |||| 2 ||Review||Tom||Tom||1.2||http://bugzilla.pokylinux.org/show_bug.cgi?id=1660
|}

== ADT / Tools and Support ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Due'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Enhance the deploy part in remote debug||||3||Review||Lianhao||Jessica||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1600
|-
| Secure login||||3||Review||ADT Team||Jessica||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1601
|-
| Linux tools upstream integration||||3||Review||ADT Team||Jessica||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1602
|-
| Add recipe supporting autoconf-nativesdk and automake-nativesdk ||||2||Review||Lianhao||Kai/Lianhao||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1603
|-
|Eclipse BSP/Kernel Plugin || This one is Jessica's, Tom's tracked elsewhere || 2 || Review || Darren || Jessica || 1.2 ||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1610
|-
| enhance the bitbake commander eclipse plugin ||||2||Review||Dongxiao/Lianhao||Jessica/Lianhao||1.2|| http://bugzilla.yoctoproject.org/show_bug.cgi?id=1611
|-
| Tracing: tuna, oscilloscope recipes||Need detail||3||Review||from 1.0||||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1639
|-
| Tracing/profiling HOWTOs||||2||Review||Tom||Tom||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1640
|-
| Profiling: Valgrind tools in Eclipse||||2||Review||Dave/JZ||Jessica||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1580
|-
| Tracing: Systemtap usability in Yocto||||2||Review||Tom||Tom||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1551
|-
| Tracing: create separate recipe for perf||||2||Review||Tom||Tom||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1552
|-
| Tracing: perf trace scripting support||||2||Review||from 1.0||Tom||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1553
|-
| 'perf scripts' integration||Can Jessica own this own after stap (1551) is done?||2||Review||Tom||Jessica/Tom||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1617
|-
|}

== Documentation ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Due'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Various Demo Videos||||2||Review||From ADT module and scratch||ScottR||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1641
|}

== Kernel ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Due'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Minimal Image Config Infrastructure||||3||Review||Team||WR Distro Team??? / Darren||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1642
|-
| Kernel Tools||need detail||2||Review||Bruce/Mark||Bruce||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1643
|-
| use cases||need detail||1||Review||Bruce||Bruce||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1644
|-
| kernel bloat - development||need detail||2||Review||Darren||Darren||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1645
|-
| Fast boot time||need detail||2||Review||Team||Darren||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1646
|-
|Upstream config fragments |||| 2 || Review || Darren || || 1.2 ||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1647
|-
|Real-time process-executed timers |||| 2 || Review || Darren || || 1.2 ||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1648
|-
|Define Kernel policy |||| 2 || Review || Darren || || 1.2 ||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1649
|-
| Target module build||||3||Review||RP Notes||Darren||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1614
|-
| linux-yocto-dev lock ||||1||Review||Bruce||Bruce||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1679
|-
| linux-yocto-dev stable update||||2||Review||Bruce||Bruce||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1680
|-
| Kernel usability scripts ||||2||Review||Tom||Tom||1.2||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1678
|-
|}

== Unsorted ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Due'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
|Way to determine what is about to happen (similar to a dry-run)||1||Review||WR||||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1659
|-
|debuginfo export||2||Review||WR||||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1657
|-
|Recipe creation/import script||2||Review||WR|||Kai (WR)||M2?||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1656
|-
|Export source package||3||Review||WR||Xiaofeng(WR)||?||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1655
|-
|Layer tooling: Tool to combine layers||2||Review||WR||||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1654
|-
|Recipe patch tooling/workflow||2||Review||WR||||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1652
|-
|Incremental image generation||2||Review||WR||Robert (WR)||M2?||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1651
|-
|Need documentation on contributing patches and code||1||Review||WR||||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1650
|-
| rebuild udev cache if the kernel version changes||2||ACCE||||tong.lin@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1147
|-
| Unpackaged files WARNING||2||NEW||||song.liu@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1545
|-
| Handled Releases with the PR server||2||NEW||||song.liu@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1556
|-
| Buildstats memory measurements||3||NEW||||song.liu@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1605
|-
| Use the per-file dependencies in deb and ipkg packages||2||NEW||||song.liu@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1662
|-
| Document invalidation of the sstate on a per class basis||3||ACCE||||scott.m.rifenbark@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1500
|-
| New santiy check for userspace packages||3||ACCE||||scott.a.garman@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1008
|-
| bitbake -b prints meaningless error when given an invalid recipe name||1||ACCE||||scott.a.garman@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1141
|-
| Remove python stack trace when do_patch fails||1||ACCE||||scott.a.garman@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1143
|-
| Need to change numeric user/groupids to names in device_table-minimal.txt||2||ACCE||||scott.a.garman@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1159
|-
| Make bitbake output less noisy for non-error cases||2||NEW||||scott.a.garman@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1145
|-
| QEMU won\'t run on a system that does not support tunctl||2||NEW||||scott.a.garman@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1474
|-
| Display a summary of warnings and errors at the end of a bitbake command||1||NEW||||scott.a.garman@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1540
|-
| Create better interface for metrics and status gathering||2||ACCE||||saul.wold@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=205
|-
| Improve syslog configurability||2||NEW||||saul.wold@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=717
|-
| Allow logrotate to use a different file system from the original logs||3||NEW||||saul.wold@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=718
|-
| qemu: when booting from live CD, X cannot be started||2||NEW||||saul.wold@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1487
|-
| Convert meta-toolchain to work as a poky install composed of staging/prebuild packages||3||ACCE||||richard.purdie@linuxfoundation.org||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=115
|-
| Qemu booting cost more time||3||ACCE||||richard.purdie@linuxfoundation.org||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=646
|-
| Enable swabber to be run for only specific recipes||3||ACCE||||richard.purdie@linuxfoundation.org||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=822
|-
| RRECOMMENDS...-dbg causes dependency failure if no ${PN} package exists||3||ACCE||||richard.purdie@linuxfoundation.org||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=824
|-
| Specify paths searched when failing to find a SRC_URI||2||ACCE||||richard.purdie@linuxfoundation.org||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1179
|-
| Drop PKGSUFFIX and have nativesdk use multilib technology||3||ACCE||||richard.purdie@linuxfoundation.org||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1508
|-
| Set default gcc-cross-canadian instruction generation to TARGET_ARCH||3||ACCE||||nitin.a.kamble@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=139
|-
| Zypper: Package dependency resolution does not know about hinting||3||NEED||||mark.hatle@windriver.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=821
|-
| Consider using PatchELF rather than chrpath for modifying the RPATH||3||NEW||||josh@linux.intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=806
|-
| Ensure Poky can be run on non-Linux Unices||4||NEW||||josh@linux.intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=823
|-
| Add build progress indicator||3||NEW||||josh@linux.intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1221
|-
| Should be easier to find and remove packages||3||NEW||||josh@linux.intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1241
|-
| Add more detailed data to the models used for hob state||3||NEW||||josh@linux.intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1293
|-
| Allow customize the dev packages when building a toolchain||3||NEW||||josh@linux.intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1303
|-
| Enable removal of packages||3||NEW||||josh@linux.intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1450
|-
| report on artifacts after image generation||3||NEW||||josh@linux.intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1572
|-
| make it clear how to run saved hob recipes from command line||3||NEW||||josh@linux.intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1573
|-
| add additional dialogs/config for u-boot/kernel||3||NEW||||josh@linux.intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1574
|-
| configure runtime services from gui||3||NEW||||josh@linux.intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1575
|-
| configure network settings from hob gui||3||NEW||||josh@linux.intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1576
|-
| configure users and default passwords from hob gui||3||NEW||||josh@linux.intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1577
|-
| Enable customisation of image drop down||3||NEW||||josh@linux.intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1581
|-
| Provide interface for user the install Yocto SDK through IDE||3||ACCE||||jessica.zhang@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=191
|-
| native packages should use siteinfo files||3||ACCE||||jeff.polk@windriver.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=270
|-
| [AutoBuilder/FEAT] Set Bug to Fixed automatically when building in AutoBuilder||3||REOP||||elizabeth.flanagan@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=874
|-
| Put a uname and ab name in stdio||2||ACCE||||elizabeth.flanagan@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1461
|-
| License file WARNING messages||2||ACCE||||elizabeth.flanagan@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1546
|-
| Autobuilder Layer support||2||ACCE||||elizabeth.flanagan@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1604
|-
| autobuilder clean sstate checkbox||3||ACCE||||elizabeth.flanagan@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1607
|-
| Close button doesn\'t obey Fitt\'s Law||3||ACCE||||edwin.zhai@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=35
|-
| sato-icon-theme lacks generic / unknown icon||3||ACCE||||edwin.zhai@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=37
|-
| I/O schedule isn\'t no-op on flash based devices||3||NEED||||dvhart@linux.intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=66
|-
| Create a power users tips and tricks document||3||ACCE||||dvhart@linux.intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1033
|-
| Support \'~\' in version strings||3||Wait||||dongxiao.xu@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=256
|-
| Pull alsa-state into oe-core (from oe)||2|||ACCE||||dongxiao.xu@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1176
|-
| kernel: support standalone kernel builds||2||ACCE||||bruce.ashfield@windriver.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=843
|-
| mpc8315\'s tune file: \"tune-ppc603e.inc\"||3||ACCE||||bruce.ashfield@windriver.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1192
|-
| [multilib] Triggering building a 64 bit kernel with a 32 bit userspace||3||ACCE||||song.liu@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1525
|-
| Yocto website should include a glossary||2||NEED||||scott.m.rifenbark@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=557
|-
| Yocto project website should include a simplified walk-through||3||NEED||||scott.m.rifenbark@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=558
|-
| Bug reporting guide||2||ACCE||||scott.m.rifenbark@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=237
|-
| Improve SDK sysroot extensibility and workflow||3||ACCE||||scott.m.rifenbark@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=545
|-
| add documentation for swabber||3||ACCE||||scott.m.rifenbark@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=635
|-
| need a doc for qemu usage||3||ACCE||||scott.m.rifenbark@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=641
|-
| QEMU fails to launch using unfs with rpcbind installed - must have portmap.||2||ACCE||||scott.m.rifenbark@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=655- maybe resolved?
|-
| Need centralized documentation on BitBake class usage||2||ACCE||||scott.m.rifenbark@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1467
|-
| bitbake \"NoProvider\" message doesn\'t aid in resolving the problem||2||ACCE||||scott.a.garman@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=542
|-
| Improve the error reporting when SkipPackage error is raised||2||ACCE||||scott.a.garman@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1127
|-
| sstate code doesn\'t detect overwriting files||3||ACCE||||richard.purdie@linuxfoundation.org||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=238
|-
| Add a mechanism to do pre-build sanity based on specific configurations||3||ACCE||||richard.purdie@linuxfoundation.org||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=405
|-
| Usability: How to find specific variables and settings?||2||ACCE||||richard.purdie@linuxfoundation.org||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=407
|-
| TCF RSE plug-in not handle the situation if the remote agent does NOT support terminal service||3||Wait||||liping.ke@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=107
|-
| cdt.launch.remote issues on a non-canonical terminal||3||Wait||||liping.ke@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=188
|-
| Need a generic xorg.conf package that all the xservers can use.||3||ACCE||||ke.yu@intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1175
|-
| Show contents of images & tasks||2||NEW||||josh@linux.intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=991
|-
| Show more information about packages||3||NEW||||josh@linux.intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=992
|-
| Preference Package Format only support one selection at a time||3||NEW||||josh@linux.intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1272
|-
| Need guidance choosing \'Base image\'||2||NEW||||josh@linux.intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1277
|-
| Built toolchain doesn\'t include development packages for image||2||NEW||||josh@linux.intel.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1302
|-
| On qemuarm, the command \'poweroff/shutdown\' can\'t close the qemu completely and exit to host console with Laverne build 20110121||3||ACCE||||bruce.ashfield@windriver.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=684
|-
| gtk+ over directfb ||3||ACCE||||xiaofeng.yan@windriver.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1674
|-
| make an lsb image to meet LSB requirement for version 1.2 ||2||ACCE||||xiaofeng.yan@windriver.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1675
|-
| A scripts to clean obsolote sstate cache files ||3||NEW||||liezhi.yang@windriver.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1682
|-
| bitbake-runtask doesn't work in both 1.0.1 and 1.1 ||2||NEW||||liezhi.yang@windriver.com||||http://bugzilla.yoctoproject.org/show_bug.cgi?id=1229
|-
|}

Yocto 1.1 Schedule

2011-03-17T02:33:15Z

Mhatle: /* M2 (May 30 to Jul 25 -- Design Complete Jun 6, Dev Complete Jul 4, Stabilize Complete Jul 18, Release Complete Jul 25) */

= October 2011 (release date: October 6, 2011) =
----
The detailed milestone map for the October 2011 release of Yocto is as below.

== pre-M1 (March 14 to April 18 -- Feature List and Schedule Defined April 18) ==
* Features Submitted to web - by April 1st
* Features prioritized and added to schedule - by April 18th

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==

{|border="1"
|| '''Group''' || '''Feature Name''' || '''Description''' || '''Priority''' || '''Status''' || '''Owner''' || '''Source''' || '''Comments / Bugzilla Links'''
|-
|| Architecture || OE Core || Restructuring, renaming, rebranding || 1 || Review || Richard || Architect ||
|-
|| 1.0 Carryover || multi-lib || multi-lib support for 32-bit & 64-bit and capable of being installed at the same time || 1 || Review || Richard || 1.0 Carryover ||
|-
|| Meta-Data || OE Comparison || Compare Yocto core set against integration work in OE and other distributions looking for bug fixes, (relevant) feature enhancements, and integration/policy hints. || 1 || Accept || Mark || Meta-data ||
|-
|| BSPs || Support for AVX as in kernel 2.6.30. - Already in 1.0 || Any toolchain support needed? || 1 || Review || Saul || Jay ||
|-
|| Misc || User creation at post-install || || 1 || Accept || Mark || Architect ||
|}

== M2 (May 30 to Jul 25 -- Design Complete Jun 6, Dev Complete Jul 4, Stabilize Complete Jul 18, Release Complete Jul 25) ==

{|border="1"
|| '''Group''' || '''Feature Name''' || '''Description''' || '''Priority''' || '''Status''' || '''Owner''' || '''Source''' || '''Comments / Bugzilla Links'''
|-
|| 1.0 Carryover || Image Creator || finish the Image Creator to add features pushed out from 1.0 || 1 || Accept || Joshua + Jessica || 1.0 Carryover ||
|-
|| Architecture || Layer Tooling || This includes the architectural work plus implementing the changes || 1 || Review || Richard || Architect ||
|-
|| Meta-data || Upstream our patches || Placeholder for time for the team to upstream patches || 1 || Review || Saul || Meta-Data Team||
|-
|| Meta-data|| Error handling in bitbake || add additional error handling to bitbake || 1 || Review || Saul || Architect ||
|-
|| ADT || Changes for Image Creator || Eclipse changes pending Image Creator || 1 || Review || Jessica || ADT Team||
|-
|| BSP || Tutorials || Create tutorials and documentation on how to create a BSP || 1 || Review || Tom, Scott || Team||
|-
|| Kernel|| Fast Boot Time || 2 second boot time target || 1 || Accept || Darren|| Team ||
|-
|| Misc || adding eglibc config control || this goes with the package config options || 1.5 || Accept || Mark || Architect ||
|-
|| Misc || Directory Ownership || || 1.5 || Accept || Mark || Architect || a bit concerned this will take longer then expected
|}

== M3 (Jul 11 to Aug 15 -- Design Complete Jul 18, Dev Complete Jul 25, Stabilize Complete Aug 8, Release Complete Aug 15) ==

{|border="1"
|| '''Group''' || '''Feature Name''' || '''Description''' || '''Priority''' || '''Status''' || '''Owner''' || '''Source''' || '''Comments / Bugzilla Links'''
|-
|| X || X|| X || 1 || Review || X || X ||
|}

== M4 (Aug 15 to Oct 6 -- Stabilize Complete Aug 29, Release Complete Oct 3) ==

{|border="1"
|| '''Group''' || '''Feature Name''' || '''Description''' || '''Priority''' || '''Status''' || '''Owner''' || '''Source''' || '''Comments / Bugzilla Links'''
|-
|| X || X|| X || 1 || Review || X || X ||
|}

Yocto 1.1 Schedule

2011-03-17T02:31:29Z

Mhatle: /* M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) */

= October 2011 (release date: October 6, 2011) =
----
The detailed milestone map for the October 2011 release of Yocto is as below.

== pre-M1 (March 14 to April 18 -- Feature List and Schedule Defined April 18) ==
* Features Submitted to web - by April 1st
* Features prioritized and added to schedule - by April 18th

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==

{|border="1"
|| '''Group''' || '''Feature Name''' || '''Description''' || '''Priority''' || '''Status''' || '''Owner''' || '''Source''' || '''Comments / Bugzilla Links'''
|-
|| Architecture || OE Core || Restructuring, renaming, rebranding || 1 || Review || Richard || Architect ||
|-
|| 1.0 Carryover || multi-lib || multi-lib support for 32-bit & 64-bit and capable of being installed at the same time || 1 || Review || Richard || 1.0 Carryover ||
|-
|| Meta-Data || OE Comparison || Compare Yocto core set against integration work in OE and other distributions looking for bug fixes, (relevant) feature enhancements, and integration/policy hints. || 1 || Accept || Mark || Meta-data ||
|-
|| BSPs || Support for AVX as in kernel 2.6.30. - Already in 1.0 || Any toolchain support needed? || 1 || Review || Saul || Jay ||
|-
|| Misc || User creation at post-install || || 1 || Accept || Mark || Architect ||
|}

== M2 (May 30 to Jul 25 -- Design Complete Jun 6, Dev Complete Jul 4, Stabilize Complete Jul 18, Release Complete Jul 25) ==

{|border="1"
|| '''Group''' || '''Feature Name''' || '''Description''' || '''Priority''' || '''Status''' || '''Owner''' || '''Source''' || '''Comments / Bugzilla Links'''
|-
|| 1.0 Carryover || Image Creator || finish the Image Creator to add features pushed out from 1.0 || 1 || Accept || Joshua + Jessica || 1.0 Carryover ||
|-
|| Architecture || Layer Tooling || This includes the architectural work plus implementing the changes || 1 || Review || Richard || Architect ||
|-
|| Meta-data || Upstream our patches || Placeholder for time for the team to upstream patches || 1 || Review || Saul || Meta-Data Team||
|-
|| Meta-data|| Error handling in bitbake || add additional error handling to bitbake || 1 || Review || Saul || Architect ||
|-
|| ADT || Changes for Image Creator || Eclipse changes pending Image Creator || 1 || Review || Jessica || ADT Team||
|-
|| BSP || Tutorials || Create tutorials and documentation on how to create a BSP || 1 || Review || Tom, Scott || Team||
|-
|| Kernel|| Fast Boot Time || 2 second boot time target || 1 || Accept || Darren|| Team ||
|-
|| Misc || adding eglibc config control || this goes with the package config options || 1.5 || Review || Mark || Architect ||
|-
|| Misc || Directory Ownership || || 1.5 || Review || Mark || Architect ||
|}

== M3 (Jul 11 to Aug 15 -- Design Complete Jul 18, Dev Complete Jul 25, Stabilize Complete Aug 8, Release Complete Aug 15) ==

{|border="1"
|| '''Group''' || '''Feature Name''' || '''Description''' || '''Priority''' || '''Status''' || '''Owner''' || '''Source''' || '''Comments / Bugzilla Links'''
|-
|| X || X|| X || 1 || Review || X || X ||
|}

== M4 (Aug 15 to Oct 6 -- Stabilize Complete Aug 29, Release Complete Oct 3) ==

{|border="1"
|| '''Group''' || '''Feature Name''' || '''Description''' || '''Priority''' || '''Status''' || '''Owner''' || '''Source''' || '''Comments / Bugzilla Links'''
|-
|| X || X|| X || 1 || Review || X || X ||
|}

Yocto 1.1 Schedule

2011-03-17T02:30:58Z

Mhatle: /* M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) */

= October 2011 (release date: October 6, 2011) =
----
The detailed milestone map for the October 2011 release of Yocto is as below.

== pre-M1 (March 14 to April 18 -- Feature List and Schedule Defined April 18) ==
* Features Submitted to web - by April 1st
* Features prioritized and added to schedule - by April 18th

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==

{|border="1"
|| '''Group''' || '''Feature Name''' || '''Description''' || '''Priority''' || '''Status''' || '''Owner''' || '''Source''' || '''Comments / Bugzilla Links'''
|-
|| Architecture || OE Core || Restructuring, renaming, rebranding || 1 || Review || Richard || Architect ||
|-
|| 1.0 Carryover || multi-lib || multi-lib support for 32-bit & 64-bit and capable of being installed at the same time || 1 || Review || Richard || 1.0 Carryover ||
|-
|| Meta-Data || OE Comparison || Compare Yocto core set against integration work in OE and other distributions looking for bug fixes, (relevant) feature enhancements, and integration/policy hints. || 1 || Approved || Mark || Meta-data ||
|-
|| BSPs || Support for AVX as in kernel 2.6.30. - Already in 1.0 || Any toolchain support needed? || 1 || Review || Saul || Jay ||
|-
|| Misc || User creation at post-install || || 1 || Approved || Mark || Architect ||
|}

== M2 (May 30 to Jul 25 -- Design Complete Jun 6, Dev Complete Jul 4, Stabilize Complete Jul 18, Release Complete Jul 25) ==

{|border="1"
|| '''Group''' || '''Feature Name''' || '''Description''' || '''Priority''' || '''Status''' || '''Owner''' || '''Source''' || '''Comments / Bugzilla Links'''
|-
|| 1.0 Carryover || Image Creator || finish the Image Creator to add features pushed out from 1.0 || 1 || Accept || Joshua + Jessica || 1.0 Carryover ||
|-
|| Architecture || Layer Tooling || This includes the architectural work plus implementing the changes || 1 || Review || Richard || Architect ||
|-
|| Meta-data || Upstream our patches || Placeholder for time for the team to upstream patches || 1 || Review || Saul || Meta-Data Team||
|-
|| Meta-data|| Error handling in bitbake || add additional error handling to bitbake || 1 || Review || Saul || Architect ||
|-
|| ADT || Changes for Image Creator || Eclipse changes pending Image Creator || 1 || Review || Jessica || ADT Team||
|-
|| BSP || Tutorials || Create tutorials and documentation on how to create a BSP || 1 || Review || Tom, Scott || Team||
|-
|| Kernel|| Fast Boot Time || 2 second boot time target || 1 || Accept || Darren|| Team ||
|-
|| Misc || adding eglibc config control || this goes with the package config options || 1.5 || Review || Mark || Architect ||
|-
|| Misc || Directory Ownership || || 1.5 || Review || Mark || Architect ||
|}

== M3 (Jul 11 to Aug 15 -- Design Complete Jul 18, Dev Complete Jul 25, Stabilize Complete Aug 8, Release Complete Aug 15) ==

{|border="1"
|| '''Group''' || '''Feature Name''' || '''Description''' || '''Priority''' || '''Status''' || '''Owner''' || '''Source''' || '''Comments / Bugzilla Links'''
|-
|| X || X|| X || 1 || Review || X || X ||
|}

== M4 (Aug 15 to Oct 6 -- Stabilize Complete Aug 29, Release Complete Oct 3) ==

{|border="1"
|| '''Group''' || '''Feature Name''' || '''Description''' || '''Priority''' || '''Status''' || '''Owner''' || '''Source''' || '''Comments / Bugzilla Links'''
|-
|| X || X|| X || 1 || Review || X || X ||
|}

OpenEmbedded-Core

2011-03-02T23:28:13Z

Mhatle:

The OpenEmbedded-Core is a base layer, of recipes, classes and associated files that is meant to be common amount many different Open Embedded derived systems. While not all systems will use every piece of the OpenEmbedded-Core, it will provide a self contained example that can be used to prove basic functionality.

----

Getting Started

1) Download the repository

git clone git://git.openembedded.org/openembedded-core oe-core
cd oe-core
git clone git://git.openembedded.org/bitbake bitbake

1.5) Temporary workaround (as of 2011-03-02)

Edit the file scripts/poky-env-internal

Add to the end:

export BBFETCH2=True

2) Setup the environment, and build directory

. ./poky-init-build-env [<build directory>]

The optional build directory may be specified, otherwise it is assumed you want to use the directory named "build".

3) First time configuration

The first time you run poky-init-build-env, it will setup the directory for you. You should at least review the settings within the conf/local.conf file.

4) Build something

bitbake <rule>

A good simple place to start is "bitbake poky-image-minimal". This will run through a simple build and do basic system sanity checks. If your system needs additional software installed, or other environment settings it will tell you what is needed.

RPM5-Uprev

2011-01-11T16:22:32Z

Mhatle: Created page with 'The following is a summary of the RPM5 Uprev and related. This will be expanded to include a future roadmap as possible. The RPM5 work includes both rpm5.org and Zypper related…'

The following is a summary of the RPM5 Uprev and related. This will be expanded to include a future roadmap as possible.

The RPM5 work includes both rpm5.org and Zypper related sources and dependencies.

* RPM5
* Uprev RPM5 to latest version (5.4.0)
* Include package separation based on upstream SPEC file
* Consider also supporting previous stable release (5.3.7)

* Zypper
* Dependent upon the RPM5 uprev
* Sync up API usage with current RPM5 work
* Change Zypper to support variable arch as implemented by RPM5

* Rootfs creation
* Sync to latest RPM5 as necessary
* Create install repository for Zypper
* Create rootfs using Zypper, if possible

Goal in the end is to be able to have a more modern version of RPM5. A newer and/or better integrated version of Zypper. This newer version needs to hopefully use Poky's understanding of "arch" instead of it's own. A simple mechanism to construct a Zypper package repository structure. And to use that structure to generate a filesystem.

----

Roadmap:

Jan 6:
* Uprev RPM5 to 5.4.0 (in Poky Contrib)

Jan 7
* Rootfs creation with RPM5 5.4.0

Jan 13
* Final RPM5 uprev and integration, including package seperation
* Initial Zypper API integration and sync to RPM5

Jan 17-21
* RPM5 arch enhancement
* Zypper repository (createrepo) support

?
* Zypper used to create rootfs (may not happen for 1.0)

User:Mhatle

2011-01-11T16:12:25Z

Mhatle:

Name: Mark Hatle

email: mark.hatle at windriver dot com

freenode IRC: fray

----

I'm responsible for some of the userspace integration, especially around dependency generation, packaging, rootfs generation and related components.

I am the maintainer for the [[Cross-Prelink]] project.

I've started a page to attempt to document the [[Architecture-ABI]] that are in common use in embedded Linux designs.

RPM uprev and roadmap information [[RPM5-Uprev]].

User:Mhatle

2011-01-11T16:12:17Z

Mhatle:

Architecture-ABI

2010-11-04T19:42:41Z

Mhatle: /* Processor Variants */

== Introduction ==

There are currently many official and unofficial ABI -- Application Binary Interfaces -- in use within embedded Linux projects. The following is an attempt to lightly document what the individual architecture ABI consist of, without going into too many details..

Many of the following ABIs have grown organically based on specific processor designs and optimization levels. For the most part the processor optimizations are ignored in these descriptions, unless otherwise mentioned.

Additional references, CPU optimization compatibility and suggested canonical architecture namings may be provided.

== ABI Summary ==

The following is a list of ABIs that are in common usage. Some of the ABIs discussed in the following sections will not appear in this table if they are legacy.

{| border="1"
|'''Arch'''||'''ABI'''||'''Endian'''||'''Compatibility'''
|-
|ARM||EABI||Big Endian||
|-
|ARM||EABI||Little Endian||
|}

== ARM ==

=== ABI ===

apcs-gnu a.k.a. OABI - The original ARM ABI.

It has two variants, an emulated hardware floating point, and a soft floating point variant. The legacy ABI should no longer be used in embedded projects and has more or less disappeared. The legacy ABI is not compatible with the EABI.

You can detect the ABI if the result of objdump -x contains [APCS-32]

The legacy abi can be enabled by using "-mabi=apcs-gnu"

----

EABI - The new "Embedded" ABI by ARM ltd. This is otherwise known as "the ABI for the ARM Architecture".

The new EABI specifies a single ABI that works in various hardware floating point and software floating point configurations as well as Thumb interworking. Overall structure packing is better, a more efficient syscall convention is provided.

You can detect the ABI if the result of objdump -x contains [Version4 EABI]

=== Processor Variants ===

The gnu-canonical architecture for arm is in the format:

armv<version><capabilities>-os-linux-gnu-eabi

The gnu-eabi indicates that it is the newer EABI ABI.

The ARM core versions include:

* armv4
* armv5
* armv6
* armv7

The ARM processor capabilities indicate:

* el - little endian (optional)
* eb - big endian
* t - thumb/thumb2
* j - java

This would result in something similar to: armv7teb, for an ARM 7 core, with thumb capabilities, running in big endian mode.

In addition processors may include specific optimizations that change which CPUs a compiled program will run on, these include:

* VFP instructions
* NEON
* Thumb/Thumb-2 instructions

== IA32 ==

== MIPS ==

== Power ==

Architecture-ABI

2010-11-04T19:25:25Z

Mhatle: /* ABI Summary */

Architecture-ABI

2010-11-04T19:25:00Z

Mhatle: /* ABI */

== Introduction ==

There are currently many official and unofficial ABI -- Application Binary Interfaces -- in use within embedded Linux projects. The following is an attempt to lightly document what the individual architecture ABI consist of, without going into too many details..

Many of the following ABIs have grown organically based on specific processor designs and optimization levels. For the most part the processor optimizations are ignored in these descriptions, unless otherwise mentioned.

Additional references, CPU optimization compatibility and suggested canonical architecture namings may be provided.

== ABI Summary ==

The following is a list of ABIs that are in common usage. Some of the ABIs discussed in the following sections will not appear in this table if they are legacy.

{| border="1"
|'''Arch'''||'''ABI'''||'''Endian'''||'''Compatibility'''
|-
|ARM||ARM EABI||Big Endian||
|-
|ARM||ARM EABI||Little Endian||
|}

== ARM ==

=== ABI ===

apcs-gnu a.k.a. OABI - The original ARM ABI.

It has two variants, an emulated hardware floating point, and a soft floating point variant. The legacy ABI should no longer be used in embedded projects and has more or less disappeared. The legacy ABI is not compatible with the EABI.

You can detect the ABI if the result of objdump -x contains [APCS-32]

The legacy abi can be enabled by using "-mabi=apcs-gnu"

----

EABI - The new "Embedded" ABI by ARM ltd. This is otherwise known as "the ABI for the ARM Architecture".

The new EABI specifies a single ABI that works in various hardware floating point and software floating point configurations as well as Thumb interworking. Overall structure packing is better, a more efficient syscall convention is provided.

You can detect the ABI if the result of objdump -x contains [Version4 EABI]

=== Processor Variants ===

== IA32 ==

== MIPS ==

== Power ==

Architecture-ABI

2010-11-04T19:21:57Z

Mhatle: /* Introduction */

Architecture-ABI

2010-11-04T19:20:19Z

Mhatle: /* ARM */

Architecture-ABI

2010-11-04T19:17:53Z

Mhatle: /* Architecture ABI */

Architecture-ABI

2010-11-04T19:13:53Z

Mhatle: Created page with '== Architecture ABI == There are currently many official and unofficial ABI -- Application Binary Interfaces -- in use within embedded Linux projects. The following is an attem…'

== Architecture ABI ==

There are currently many official and unofficial ABI -- Application Binary Interfaces -- in use within embedded Linux projects. The following is an attempt to lightly document what the individual architecture ABI consist of, without going into too many details..

Many of the following ABIs have grown organically based on specific processor designs and optimization levels. For the most part the processor optimizations are ignored in these descriptions, unless otherwise mentioned.

== ARM ==

apcs-gnu a.k.a. OABI - The original ARM ABI.

It has two variants, an emulated hardware floating point, and a soft floating point variant. The legacy ABI should no longer be used in embedded projects and has more or less disappeared. The legacy ABI is not compatible with the EABI.

It can be detected by:

From: http://wiki.debian.org/ArmEabiPort

objdump -x contains [APCS-32]

The legacy abi can be enabled by using "-mabi=apcs-gnu"

----

EABI - The new "Embedded" ABI by ARM ltd.

The new EABI specifies a single ABI that works in various hardware floating point and software floating point configurations as well as Thumb interworking. Overall structure packing is better, a more efficient syscall convention is provided.

----

ARM Processors are available in both Big Endian and Little Endian varieties. Each variety impacts the ABI and specifies the endian bit and byte order.

The following table lists the current ARM ABIs in common usage:

{| border="1"
|'''ABI'''||'''Endian'''||'''Compatibility'''
|-
|EABI||Big Endian||
|-
|EABI||Little Endian||
|}

== IA32 ==

== MIPS ==

== Power ==

User:Mhatle

2010-11-04T18:51:44Z

Mhatle:

Cross-Prelink

2010-10-30T11:32:58Z

Mhatle: /* Yocto Project Prelink */

== Project Background ==

The upstream prelink project was founded by Jakub Jelinek at Red Hat. The upstream project is primarily focused on self-hosted configurations and does not support prelinking a target filesystem in a cross-development environment.

This limitation is due to the prelink software requiring the runtime linker to be available in order to resolve linking dependencies.

The cross prelink patches began at MontaVista around 2003 in order to work around this limitation. The original patches added the ability to emulate a runtime linker, as well as enabled a sysroot option. Over time, this work was continued by MontaVista, Wind River and Code Sourcery. Unfortunately, while all of the patches had been made public in one fashion or another, there was no central location that gathered and offered to manage these changes. Starting with the Yocto Project we have decided to put together these patches and make them available as a single unit, with a clear upstream that will happily accept patches.

== Upstream Prelink ==

The upstream prelink project is located at sourceware.org.

For mailing lists, see: http://sourceware.org/ml/prelink/

For SVN access to the upstream tree, see: svn://sourceware.org/svn/prelink/

== Yocto Project Prelink ==

See the http://yoctoproject.org/projects/cross-prelink page on the website for more information on this project.

Mark Hatle -- [[User:Mhatle]] is the project maintainer for the cross-prelink component of the Yocto Project.

Cross-Prelink

2010-10-30T11:32:26Z

Mhatle: /* Yocto Project Prelink */

== Project Background ==

The upstream prelink project was founded by Jakub Jelinek at Red Hat. The upstream project is primarily focused on self-hosted configurations and does not support prelinking a target filesystem in a cross-development environment.

This limitation is due to the prelink software requiring the runtime linker to be available in order to resolve linking dependencies.

The cross prelink patches began at MontaVista around 2003 in order to work around this limitation. The original patches added the ability to emulate a runtime linker, as well as enabled a sysroot option. Over time, this work was continued by MontaVista, Wind River and Code Sourcery. Unfortunately, while all of the patches had been made public in one fashion or another, there was no central location that gathered and offered to manage these changes. Starting with the Yocto Project we have decided to put together these patches and make them available as a single unit, with a clear upstream that will happily accept patches.

== Upstream Prelink ==

The upstream prelink project is located at sourceware.org.

For mailing lists, see: http://sourceware.org/ml/prelink/

For SVN access to the upstream tree, see: svn://sourceware.org/svn/prelink/

== Yocto Project Prelink ==

See the http://yoctoproject.org/projects/cross-prelink page on the website for more information on this project.

[[User:Mhatle]] is the project maintainer fro the cross-prelink component of the Yocto Project.

Cross-Prelink

2010-10-30T11:31:45Z

Mhatle: /* Yocto Project Prelink */

== Project Background ==

The upstream prelink project was founded by Jakub Jelinek at Red Hat. The upstream project is primarily focused on self-hosted configurations and does not support prelinking a target filesystem in a cross-development environment.

This limitation is due to the prelink software requiring the runtime linker to be available in order to resolve linking dependencies.

The cross prelink patches began at MontaVista around 2003 in order to work around this limitation. The original patches added the ability to emulate a runtime linker, as well as enabled a sysroot option. Over time, this work was continued by MontaVista, Wind River and Code Sourcery. Unfortunately, while all of the patches had been made public in one fashion or another, there was no central location that gathered and offered to manage these changes. Starting with the Yocto Project we have decided to put together these patches and make them available as a single unit, with a clear upstream that will happily accept patches.

== Upstream Prelink ==

The upstream prelink project is located at sourceware.org.

For mailing lists, see: http://sourceware.org/ml/prelink/

For SVN access to the upstream tree, see: svn://sourceware.org/svn/prelink/

== Yocto Project Prelink ==

See the http://yoctoproject.org/projects/cross-prelink page on the website for more information on this project.

[[Mhatle]] is the project maintainer fro the cross-prelink component of the Yocto Project.

User:Mhatle

2010-10-30T11:30:31Z

Mhatle: Created page with 'Name: Mark Hatle email: mark.hatle at windriver dot com freenode IRC: fray ---- I'm responsible for some of the userspace integration, especially around dependency generation…'

Cross-Prelink

2010-10-30T11:21:55Z

Mhatle: /* Project Background */

Cross-Prelink

2010-10-30T11:13:12Z

Mhatle:

== Project Background ==

The upstream prelink project was founded by Jakub Jelinek at Red Hat. The upstream project is primarily focused on self-hosted configurations and does not support prelinking a target filesystem in a cross-development environment.

This limitation is due to the prelink software requiring the runtime linker to be available in order to resolve linking dependencies.

The cross prelink patches began at MontaVista around 2003 in order to work around this limitation. The original patches added the ability to emulate a runtime linker, as well as enabled a sysroot option. This work was continued by MontaVista, Wind River and Code Sourcery. Unfortunately, while all of the patches had been made public in one fashion or another, there was no central location that gathered and offered to manage these changes. Starting with the Yocto Project we have decided to put together these patches and make them available as a single unit, with a clear upstream that will happily accept patches.

== Upstream Prelink ==

The upstream prelink project is located at sourceware.org.

For mailing lists, see: http://sourceware.org/ml/prelink/

For SVN access to the upstream tree, see: svn://sourceware.org/svn/prelink/

== Yocto Project Prelink ==

See the http://yoctoproject.org/projects/cross-prelink page on the website for more information on this project.

Cross-Link

2010-10-30T11:00:36Z

Mhatle: moved Cross-Link to Cross-Prelink: incorrect project tile.

#REDIRECT [[Cross-Prelink]]

Cross-Prelink

2010-10-30T11:00:36Z

Mhatle: moved Cross-Link to Cross-Prelink: incorrect project tile.

See the http://yoctoproject.org/projects/cross-prelink page on the website for more information on this project.

Projects

2010-10-30T11:00:01Z

Mhatle: /* Welcome to the Projects Page */

== Welcome to the Projects Page ==
* [[AutoBuilder]]
* [[Poky]]
* [[SDK Generator]]
* [[Eclipse Plug-in]]
* [[Anjuta Plug-in]]
* [[Psuedo]]
* [[Swabber]]
* [[Cross-Prelink]]
* [[QA]]
* [[Documentation]]
* [[Boards]]