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
- 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
- Provide a one or two sentence brief description of the feature
- 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, such as 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.
| Feature Name |
Description |
Priority |
Status |
Source |
Comments / Bugzilla Links
|
| Placeholder feature name |
Placeholder description of the feature |
1, 2, or 3 |
Review |
name |
Comment
|
Usability
Core/Bitbake
QA Items
Core Meta Data
| Feature Name
|
Description
|
Priority
|
Status
|
Source
|
Owner
|
Due
|
Comments / Bugzilla Links
|
| Investigate New UI |
For demos, we would like need a reference UI that is not Sato. Investigate possibilities that the Yocto team won\'t need to maintain. OpenBox? Gnome-desktop? GP? LXDE? KDE Mobile? Refresh Sato? |
3 |
Review |
Meta-data |
|
1.2 |
Yocto 1.2
|
| selinux patch integration |
add SE Linux patches in a similar way to PAM |
3 |
Review |
Meta-data |
|
1.2 |
Yocto 1.2
|
| build statistics reporting |
As someone interested in how long it takes to build different images on different hardware configurations and other assorted build metrics, I would like a web based service, that takes output generated by an extended buildstats.bbclass and stores it, to compare against different machines. The end result should be a way to visualize the collected data. See: https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions |
2 |
M3, Sprint A |
eflanagan/Jay7/ka6sox |
Beth/Jay |
1.2 |
Yocto 1.2, from 1.1
|
| Document multiple library versions co-existing |
|
3 |
Review |
Team |
Saul (Dongxiao?) |
1.2 |
http://bugzilla.yoctoproject.org/show_bug.cgi?id=1548
|
| Embedded java environment or even JDK support |
|
3 |
Review |
Team |
|
1.2 |
Yocto 1.2
|
| Target module build |
Allow for building kernel modules on the target device |
2 |
Review |
RP Notes |
Darren |
1.2 |
Yocto 1.2, On Janitor\'s list
|
| gtk+ sato filechooser patch |
|
3 |
Review |
RP Notes |
|
1.2 |
Yocto 1.2
|
| Sanity checks on per recipe basis |
|
2 |
Accept |
RP Notes Bug#405 |
Saul (Scott G) |
1.2 |
Yocto 1.2, from 1.1
|
| perf scripting\' integration |
Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this. |
2 |
Dev |
Tom |
Jessica/Tom |
1.2 |
Yocto 1.2, from 1.1
|
| Package Documentation Audit: All recipes build |
31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. Those all need to build and we need to re-run a new package documentation audit. |
2 |
Accept |
Team |
Scott G |
1.2 |
Yocto 1.2, from 1.1
|
| Parallel Locale Generation |
|
2 |
Review |
RP |
|
|
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 |
|
RP |
Ke |
1.2 |
http://bugzilla.yoctoproject.org/show_bug.cgi?id=1549
|
| Multilib: Complete recipe enablement |
|
2 |
|
RP |
Ke |
1.2 |
http://bugzilla.yoctoproject.org/show_bug.cgi?id=1563
|
| Multilib: Drop MULTILIB_IMAGE_INSTALL |
|
2 |
|
RP |
Ke |
1.2 |
http://bugzilla.yoctoproject.org/show_bug.cgi?id=1564
|
| Enhance TARGET_VENDOR field support |
|
3 |
Review |
RP |
Ke |
1.2 |
http://bugzilla.yoctoproject.org/show_bug.cgi?id=1550
|
| MeeGo GPLv2 Sync |
compare with Yocto, sync any patches |
2 |
Accept |
RP Notes |
Saul (Ke) |
1.2 |
Yocto 1.2, from 1.1
|
| Finish Oracle/Sun Hotspot JDK/JRE support |
I created an initial hack of a recipe for this for the demo - finish it up (involves licensing issues (click-through license support would be a prerequisite) as well) |
2 |
Review |
Tom |
Tom |
1.2 |
50% done already
|
| running post installs at rootfs gen time |
|
2 |
Review |
RP Notes |
Saul (Dexuan) |
1.2 |
|
| Multi-lib - 6 |
Create some \"standard\" multilib configurations (x86 32+64 bit) |
1 |
Review |
RP |
Ke |
1.2 |
|
| POSIX support |
address POSIX failures found in 1.1 |
2 |
Review |
Team |
|
1.2 |
Yocto 1.2, On Janitor\'s list
|
| License file cleanup |
|
2 |
|
Beth |
Beth |
1.2 |
1 week http://bugzilla.yoctoproject.org/show_bug.cgi?id=1547
|
| QEMU GL Enhancements |
These include syncing sync qemugl with other projects (e.g. MeeGo?, Android?). Ideally we'd be working on a solution which could be submitted and accepted by upstream QEMU. Also need to consider GLES support. |
2 |
|
Meta-data |
Saul (Edwin) |
1.2 |
|
| Implement Factory reset |
|
4 |
Review |
Joshua |
|
1.2 |
http://bugzilla.yoctoproject.org/show_bug.cgi?id=1593
|
| Init |
Interest in systemd as a replacement for Sys V init is growing but it may not be appropriate for deeply embedded systems. I\'d like to investigate a crop of service based and process monitoring init systems and compare them on a variety of criteria as determined by the community. Furthermore I would like to investigate supporting multiple init systems, the current SysV system, systemd and possibly others. As part of this work, and because increasingly many upstreams support systemd (no doubt thanks to its adoption in Fedora) I would like to investigate implementing some infrastructure which translates from systemd units to the appropriate init format for the supported init systems. |
2 |
Review |
|
|
1.2 |
|
Other Layer Meta Data
Infrastructure
| Feature Name
|
Description
|
Priority
|
Status
|
Source
|
Owner
|
Due
|
Comments / Bugzilla Links
|
| autobuilder layer support |
|
2 |
|
Beth |
Beth |
1.2 |
2 weeks
|
| autobuilder split of nightly (really an M4 task) few days license.bbclass refactor |
|
2 |
|
Beth |
Beth |
1.2 |
1 week
|
| buildstats memory measurements |
|
2 |
|
Beth |
Beth |
1.2 |
1 week and half
|
| autobuilder release checkbox (running a yocto release right from the autobuilder) |
|
2 |
|
Beth |
Beth |
1.2 |
2 weeks
|
| Eval Patch management tools |
Consider patchwork, gerrit and others and see if they help. Any other alternatives? |
3 |
Review |
RP Notes |
|
1.2 |
Yocto 1.2
|
| Bugzilla to Wiki |
Create a script which automatically populates and updates the Wiki based on changes in bugzilla. |
2.5 |
Review |
Darren |
|
1.2 |
Yocto 1.2
|
| Provide a click through license mechanism |
Implement the mechanism described in Section 1.2. BSP \'Click-Through\' Licensing Procedure in the BSP Developer\'s Guide |
2 |
Review |
Tom |
Tom |
1.2 |
|
BSPs
| Feature Name
|
Description
|
Priority
|
Status
|
Source
|
Owner
|
Due
|
Comments / Bugzilla Links
|
| AMT driver integration |
incorporate Linux AMT into the Yocto BSPs |
|
|
|
|
1.2 |
Intel
|
| Zaurusd++ (devmand?) |
I keep seeing changes to toggle certain features for various boards (audio on the beagleboard, N450 and spring to mind), rather than writing lots of recipes for this perhaps we could resurrect zaurusd and evolve it to reflect the projects original goals as devmand; a daemon to handle hardware quirks across a range of boards and devices. |
|
|
|
|
1.2 |
Joshua
|
| BSP update/intro |
determine and integrate / create arch reference BSPs (e500, Cortex, ARM, MIPs) |
2 |
Dev |
Bruce/Richard/team |
Bruce |
1.2 |
Yocto 1.2, from 1.1
|
| Drop Grub for Syslinux |
Grub is considerably more complicated than we need for any of our current BSPs. Syslinux can be used in place of every known usage of Grub. For upcoming EFI BSPs, we can look to Efilinux. This will reduce our bootloader maintenance burden and simplify our images. |
2 |
Review |
Darren |
Darren |
1.2 |
|
| Integrate alsa-state |
Remove all the BSP specific $MACHINE-audio recipes in favor of the more generic alsa-state mechanism in use by OE already. |
1 |
Review |
Darren |
|
1.2 |
This possibly conflicts with the item to refresh zaurusd.
|
| Upgrade to EFI |
Where possible, update our existing BSPs to boot using EFI. This will support development of efilinux as well as help us prepare for the newer boards which will be EFI only. |
2 |
Review |
Darren |
Darren |
1.2 |
|
| BSP/kernel wrappers/wizards |
Create some simple scripts or 'wizards' that make it easy for users to start writing a new BSP and/or easily make simple kernel modifications to a BSP. Ideally, users shouldn't need to know anything low-level about the kernel, git, or the mechanics of appending config items to recipes in order to get a BSP up and running or to make the simple modifications needed to tweak or maintain it. |
2 |
Review |
tomz |
tomz |
1.2 |
|
| replace qemuppc |
|
|
|
|
Bruce |
1.2 |
Come from bug 414
|
ADT / Tools and Support
| Feature Name
|
Description
|
Priority
|
Status
|
Source
|
Owner
|
Due
|
Comments / Bugzilla Links
|
| Enhance the deploy part in remote debug |
|
2 |
Review |
Lianhao |
Jessica |
1.2 |
http://bugzilla.pokylinux.org/show_bug.cgi?id=1600
|
| Secure login |
|
2 |
Review |
ADT Team |
Jessica |
1.2 |
http://bugzilla.pokylinux.org/show_bug.cgi?id=1601
|
| Linux tools upstream integration |
|
2 |
Review |
ADT Team |
Jessica |
1.2 |
http://bugzilla.pokylinux.org/show_bug.cgi?id=1602
|
| Add recipe supporting autoconf-nativesdk and automake-nativesdk |
|
2 |
Review |
Lianhao |
|
1.2 |
http://bugzilla.pokylinux.org/show_bug.cgi?id=1603
|
| Eclipse BSP/Kernel Plugin |
Provide an Eclipse plugin to facilitate configuring new BSPs and streamlining the linuix-yocto development workflow. |
2 |
Review |
Darren |
|
1.2 |
|
| enhance the bitbake commander eclipse plugin |
By having the Eclipse as a frontend UI to bitbake server, eclipse may talk to bitbake server, enable the user to glimpse on the variables' values when editing the recipes, try out building the recipe being edited, etc. |
2 |
Review |
Dongxiao/Lianhao |
TBD |
TBD |
This requires new features both in eclipse plugin and bitbake server.
|
| Tracing: tuna, oscilloscope recipes |
This might be more useful with the increased importance of RT |
3 |
Review |
from 1.0 |
|
1.2 |
Yocto 1.2
|
| Tracing/profiling HOWTOs |
Create a document or extend the current Yocto tracing wiki page to explain in detail how to use all the tracing tools in Yocto. It should detail not only how to use each tool individually, but also how to use them in conjunction with each other, highlighting situations in which each is most useful. There should also be some extensive worked examples of real-life use-cases and how they could be investigated using the Yocto tracing/profiling tools. |
2 |
Accept |
Tom |
Tom |
1.2 |
Yocto 1.2, from 1.1
|
| Profiling: Valgrind tools in Eclipse |
|
2 |
Accept |
Dave/JZ |
|
1.2 |
http://bugzilla.yoctoproject.org/show_bug.cgi?id=1580
|
| Tracing: Systemtap usability in Yocto |
|
2 |
Accept |
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 |
Dev (50%) |
from 1.0 |
Tom |
1.2 |
http://bugzilla.yoctoproject.org/show_bug.cgi?id=1553
|
Documentation
| Feature Name
|
Description
|
Priority
|
Status
|
Source
|
Owner
|
Due
|
Comments / Bugzilla Links
|
| Various Demo Videos |
The idea here is to create screen-capture type tutorials similar to what exists for the ADT Eclipse Plug-in. However, we want to contract out some help for professional voice-over talent to be used with the images. These don\'t have to be limited to screen-capture material but could include well-done PPT decks - similar to how other business units in Intel create various training modules. For 1.1 it would be good to capture the script for the existing ADT Eclipse Plug-in module and have it voiced over. Also, for 1.1 it would be good to create a similar module for the Image Creator application. |
2 |
Not Started |
From ADT module and scratch |
ScottR |
1.2 |
Q3 at the earliest
|
Kernel
| Feature Name
|
Description
|
Priority
|
Status
|
Source
|
Owner
|
Due
|
Comments / Bugzilla Links
|
| Minimal Image unique |
make minimal image smaller |
3 |
Accept |
Team |
WR Distro Team |
1.2 |
Yocto 1.2, from 1.1
|
| Kernel Tools |
Implement plan for kernel tools |
2 |
Dev (20%) |
Bruce/Mark |
Bruce |
1.2 |
Yocto 1.2, from 1.1
|
| use cases |
BSP config streamlining, building the kernel standalone, yoctoization, meta data sharing |
1 |
Accept |
Bruce |
Bruce |
1.2 |
Yocto 1.2, from 1.1
|
| kernel bloat - development |
target = boot a minimal image in < 8M - development complete |
1 |
Dev |
Darren |
Darren |
1.2 |
Yocto 1.2, from 1.1, continuation needed?
|
| Fast boot time |
2 second boot time target |
1 |
Dev |
Team |
Darren |
1.2 |
Yocto 1.2, from 1.1, continuation needed?
|
| Upstream config fragments |
Work with John Stultz to upstream a Linux kernel config fragment manager and rework the yocto-kernel-tools to use it. This will simplify our tooling and increase our usage/test base. |
1 |
Review |
Darren |
|
1.2 |
|
| Real-time process-executed timers |
Timers currently run at the priority of the softirq that processes them and they are accounted to whichever task was preempted for them to run. This negatively impacts determinism and accounting accuracy. |
2 |
Review |
Darren |
|
1.2 |
|
| Define Kernel policy |
We need to clearly document kernel policy and make the config fragments reflect it. This will facilitate a more modular approach to building BSP kernel configs, as well as make it clear what can be expected to be supported when running a "linux-yocto kernel". |
1 |
Review |
Darren |
|
1.2 |
|
