1. Overview

  • Head: Meego

  • Summary: provide a MeeGo clone head that leverages the linaro base system and tools

  • Owner: Rajeev Kapoor

  • Driver: Alexander Sack

  • Seed: meego in lp:linaro-seeds

  • Image Config: meego/ in lp:linaro-image-configs

  • Downloads:

    Type

    Download URL

    Latest Daily

    put URL here

    Development Milestone

    put URL here

    Release

    put release URL here

2. Objectives

  • Proof of concept MeeGo-like (and based) UI running on several Linaro member platforms.

  • Prove the value of the Linaro ARM toolchain in delivering significant performance improvements over the stock 4.4.4 and 4.5 releases
  • Inputs to BSP consolidation efforts within the kernel consolidation working group
  • Inputs to proposed Graphics and Multimedia working groups
  • Video Playback over GST-OMX IL using Linaro as base and MeeGo as UI.

  • Migrate and execute QT graphics application / benchmark in MeeGo application.

3. Definitions

PPA: Personal Package Archive (https://help.launchpad.net/Packaging/PPA#Overview)

4. Structure

the MeeGo-based test head proposal is broken into a hardware enablement and software configuration components:

  1. Maintain the hardware independent user experience stack in linaro done referred to as Meego Core

  2. Board bring up and hardware acceleration packs for ST-E UH8500 done by the Meego Enablement - ST-E UH8500

  3. Board bring up and hardware acceleration packs for OMAP4 done by the Meego Enablement - OMAP4

While the user experience stack in general is hardware independent, a close working relationship between those two efforts ensures that both ends of the stack will be optimized for the intended targets.

5. Meego Core

This team focuses primarily on the hardware independent components of the MeeGo-based image

5.1. Proposed Scope

  1. Sync MeeGo-based packages all the way up to the middleware layer

  2. Package MeeGo-based handheld UI / netbook.

  3. Address conflicts with existing linaro software through upstreaming and consolidation
  4. Maintain MeeGo-based seed to produce bootable image profiles

  5. Write development tools that help track diffs from linaro to MeeGo.com and vice versa

  6. Fix bugs and push them upstream

5.2. Proposed Deliverables

The following deliverables are meant to be suggestions. they require further investigation, documentation and approval using the blueprints process

  • Phase 1 (aligned to 10.11):

    • Develop implementation plan
    • Setup MeeGo-based development PPA

    • Start initial packaging sync for parts of MeeGo-based middleware

    • Create seed and meta package comprising MeeGo-based package set

    • Review change of MeeGo and linaro stack up to the middleware layer

    • Focus on X11, Qt; with telephony and multimedia being opportunities
  • Phase 2 (probably aligned to 11.05):

    • Update MeeGo-based packages to full/recent/stable release

    • Updated change-tracking tool for tracking daily sync/merge work of the MeeGo Core Team

    • bootable MeeGo-based images

    • Proper graphics and multimedia acceleration integrated
    • Voice calls possible with proper hardware support pack

5.2.1. Risks

To be filled in by the team members upon the completion of the investigation phase

5.3. Suggested Resources

5.3.1. Phase 1

Role

Count (FTE)

Person

Committed

Enabler

0.25

Asac

PM and Planning

0.25

Rajeev

MeeGo Packager/Integrator

1

Sudip (0.5), Kunal (0.5)

Needed

Senior Platform Engineer

0.5

TBD

5.3.2. Phase 2

Role

Count (FTE)

Person

Committed

Technical Lead

0.25

Alexander Sack

PM And Planning

0.5

TBD

Needed

Senior Integration Engineer

1

TBD

Junior Integration Engineer

2

TBD

Sudip (0.5), Kunal (0.5)
Expected to do some QA ad hoc testing

Middleware Integrator

1

TBD

Ofono/Modem Engineer

1

TBD

Graphics Toolkit Engineer

0.5

TBD

6. Meego Enablement - ST-E UH8500

6.1. Proposed Scope

  • Enable board bringup (kernel/uboot)
  • Package, test and make available middleware drivers
    • Graphics: X11 support
    • Graphics: egl/ogles
    • Multimedia: codecs
    • (optional) telephony: ofono support; user space,

6.2. Proposed Deliverables

The following deliverables are meant to be suggestions. they require further investigation, documentation and approval using the blueprints process

  • Phase 1 (aligned to 10.11):

    • Packaged and usable u-boot in ppa or archive
    • Packaged kernel in ppa or archive
    • Boot installable headless image using linaro-media-create
    • Initiate manual grapics acceleration on X11 tests using the linaro headless image
  • Phase 2 (probably aligned to 11.05):

    • Hardware support pack fully enabling the UH8500 board
    • Enable full Graphics acceleration
    • Integrated complete Multimedia codecs
    • Codec <-> Xv brige optimization for zero copying

    • Full support for then current linaro image creation/installation tools

6.2.1. Assumptions:

  • BSP will be used as is.
  • Bugs and issues caused by the BSP are the responsibility of the Member and not Linaro.
  • BSP is NDA free
  • BSP and hardware enablement is re-distributable

6.2.2. Risks

Team members to fill in the risks once the investigation phase is complete

6.3. Suggested Resources

Role

Count (FTE)

Suggested Person

Committed

Technical Lead

0.25

Asac

PM and Planning

0.25

Rajeev

Board Enabler

1

Frederick (0.5), Sudip (0.5)

Middleware Enabler

2

Vishal (0.5), Sudip (0.5), TBD (1.0)

Kernel Packager

0.3

John Rigby (0.3)

Needed

TBD

TBD

TBD

6.4. Suggested Requirements Schedule

Deliverable

Owner

Date

Comments

2 ST-E HREF8500 Boards

Andrea Gallo

Delivered

critical requirement

2 ST-E HREF8500 Boards

Andrea Gallo

2010-08-06

critical requirement

4 ST-E HREF8500 Boards

Andrea Gallo

2010-08-20

critical requirement

ST-E BSP for HREF8500 boards

Frederyk?

2010-08-06

critical requirement

ST-E Graphics Drivers for EGL, GLES, and X-drivers (Kernel and user space)

Andrea Gallo

2010-08-20

critical requirement

7. Meego Enablement - PandaBoard or Blaze

7.1. Proposed Scope

It is assumed that the following scope of work is already addressed by the Canonical ARM team

  • Enable board bringup (kernel/uboot)
  • Package, test and make available middleware drivers
    • Graphics: X11 support
    • Graphics: egl/ogles
    • Multimedia: codecs
    • (optional) telephony: ofono support; user space,

7.2. Proposed Deliverables

The following proposed deliverables are to be done using the Canonical ARM team work as a basis

  • Codec <-> Xv brige optimization for zero copying

  • Full support for then current linaro image creation/installation tools

7.2.1. Assumptions:

  • BSP will be used as is
  • Bugs and issues caused by the BSP are the responsibility of the Member and not Linaro
  • BSP is NDA free
  • BSP and hardware enablement is re-distributable

7.2.2. Risks

Team members to fill in the risks once the investigation phase is complete

7.3. Suggested Resources

This table suggests a setup without Canonical ARM commitment after ubuntu 10.10 and needs refinement depending on it

Role

Count (FTE)

Suggested Person

Committed

Technincal Lead

0.25

Asac

Needed

PM and Planning

0.5

TBD

Board Enabler

1

TBD

Middleware Enabler

1

TBD

Kernel Packager

0.3

TBD

7.4. Suggested Requirements Schedule

Deliverable

Owner

Date

Comments

2 OMAP4 based boards (PandaBoard or Blaze)

Gokul Subramaniam

2010-08-13

critical requirement

2 OMAP4 based boards (PandaBoard or Blaze)

Gokul Subramaniam

2010-08-27

critical requirement

8. Work Progress

Fill in Work tables for the projects here

9. Test Plan / Status

It is important to note that all testing and evaluation is to be done by the assignees or by members QA teams.

10. Outstanding Issues

Platform/UserPlatforms/Heads/Meego (last modified 2010-08-23 09:53:21)