Meego Wiki
Views

In-vehicle

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(→Roadmap)
Line 99: Line 99:
More details on the long term direction and short term Release plan may be found at [http://wiki.meego.com/In-vehicle/Roadmap Roadmap Details]
More details on the long term direction and short term Release plan may be found at [http://wiki.meego.com/In-vehicle/Roadmap Roadmap Details]
 +
 +
=== MeeGo IVI Weekly Builds ===
 +
Automated weekly MeeGo IVI repository and image builds are available on meego.com for testing and development baselining. Each build has a build version and date in its path. [http://wiki.meego.com/Release_Engineering/Release_Versioning MeeGo Release Versioning] explains the build version numbering scheme. For example '''1.1.80.xx''' is a 1.2 Alpha build, '''1.1.90.xx''' is a 1.2 Beta build, '''1.1.99.x''' is a 1.2 Release Candidate, and '''1.2.1''' is the first release update after the final 1.2 release.
 +
 +
[http://repo.meego.com/MeeGo/builds/trunk/ MeeGo weekly build repositories]
 +
 +
IVI live .iso images are found under the ''IVI'' link. A list of every package included a live image is found in the same directory as the image. RPM packages are found under the ''oss'' and ''non-oss'' links.
 +
 +
<u>'''MeeGo IVI 1.2 Feature Status'''</u>
 +
 +
[https://bugs.meego.com/report.cgi?x_axis_field=bug_status&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=MeeGo+Features&version=1.2&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&deadlinefrom=&deadlineto=&rep_platform=Automotive&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= Featurezilla status report of MeeGo 1.2 IVI features]
 +
 +
;February 12, 2011
 +
:IVI Home Screen Changes
 +
::The ''IVIHome'' screen has been updated to reduce the number of choices in the main menu.  Instead of a dozen or so choices in the main menu and two to three choices in sub-menus, now there are five to six choices in the main menu and about the same in sub-menus. We changed this to make menu choices easier and quicker. The IVI home screen has been designed to support driver interaction with the minimal amount of distraction. This is enhanced by the use of scrollwheel, Text to Speech and Speech Recognition, removing the need to look at or touch the display.
 +
:Nokia Terminal Mode
 +
::Packages implementing the Nokia Terminal Mode have been included in the build. There are two packages(libqterminalmode and qterminalmodeclient) must be installed from the ''oss'' repositories in order to try this code.  These packages currently only work with Nokia developer kit phone sets. [http://www.terminalmode.org/en/developer/developer-offering/ Terminal Mode Developer Offering] has more information about the software and how to get developer kits
 +
:WiFi Tethering
 +
::MeeGo IVI now includes the capability to act as a WiFi Access Point enabling data sharing between tethered WiFi devices [https://bugs.meego.com/show_bug.cgi?id=7696 MeeGo WiFi Tethering Feature]
 +
:EMGD
 +
::The Embedded Media Graphics Driver (EMGD) is now integrated with all IA32 builds and provides support for the Power-VR graphics core in Intel IVI platforms. The driver package is named <nowiki> "emgd-bin...."</nowiki> and can be found in the <nowiki>"non-oss"</nowiki> repository. This driver is considered ENGINEERING SAMPLE quality with NO guaranteed response to issues.  Anyone planning to use this driver in product should obtain production quality support from the EMGD team via http://edc.intel.com
 +
 +
<u>'''MeeGo IVI 1.2 Supported Platforms'''</u>
 +
 +
;IA32
 +
:There are now two IA32 images built every week. These images support the following platforms:
 +
{| border="1"
 +
! Image name
 +
! Platform name
 +
! Intel chipset
 +
! I/O Hub name
 +
! drivers included
 +
! status
 +
|-
 +
|meego-ivi-ia32
 +
|Congatec IVI Kit (Russellville)
 +
|Intel® Atom™ Processor Z5xx Series and Intel® System Controller Hub US15Wx (eMenlow)
 +
|Timberdale
 +
|GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, KS8842 GigE, EMGD, Video-in, SDHC, TSC2007, I2S, SDHC, ADV7180, BT, Radio
 +
|No known driver issues
 +
|-
 +
|meego-ivi-ia32
 +
|Crown Bay
 +
|Intel® Atom™ Processor E6xx Series for Embedded (Tunnel Creek)
 +
|Intel® Platform Controller Hub EG20T (Top Cliff)
 +
|GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, GigE, EMGD, PHUB, CAN
 +
|No known driver issues
 +
|-
 +
|meego-ivi-ia32-conx
 +
|Northville
 +
|Intel® Atom™ Processor E6xx Series for Embedded (Tunnel Creek)
 +
|ST Microelectronics ConneXt STA2x11
 +
|GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, GigE, EMGD, Video-in, MMC, CAN, USB-OTG, MSP, BT, FM-Radio
 +
|in development, needs TSC2007 patch
 +
|}
 +
 +
 +
;ARM
 +
:Jeremiah Foster and Jan-Simon Moeller are working on updates to enable automated weekly builds of MeeGo IVI images for the Beagleboard-XM.
=== Releases ===
=== Releases ===

Revision as of 02:25, 14 February 2011

Contents

In-vehicle Infotainment (IVI)

MeeGo IVI is setting the new standard for in-vehicle infotainment in cars, buses, airplanes, etc. MeeGo IVI is a Free and Open-Source Software (FOSS) OS distribution integrating the MeeGo Core for embedded systems leveraging and extending functionality known from mobile computers and handsets into vehicles. Building on the MeeGo OS Base and the MeeGo OS Middleware the MeeGo IVI software stack enables rich Internet and multimedia experiences to consumers while traveling.

Organization

The MeeGo IVI organization is composed of a Working Group and a Project Team. The Working Group is responsible for the definition of the roadmap and the MeeGo IVI Project Team executes the implementation through the partnering organizations using the best practices of open-source development. Through the collaboration of organizations and companies covering automotive, computer hardware, communications, and software industries this partnership enables jump-starting product development for rapid delivery allowing adopters to concentrate on their core competencies while benefiting from this extensive know-how and the open-source assets.

For a graphical representation of the organizational structure: Media:MeeGo_IVI_OrgStruct.pdf

Working Group

The Working Group is composed from the following members and roles:

  • Working Group Chair
    • Represents and promotes the Working Group.
    • Leads strategic discussions on requirements, direction, policies.
    • Commitment: full-time role.
    • Current Working Group Chair: Rudi Streif (Linux Foundation)
  • Working Group Representative (the number is not limited, others participants to be invited)
    • Represents his/her organization in the Working Group.
    • Collects, organizes, prioritizes, and contributes requirements from his/her organization.
    • Commitment: 20% - 50% dependent on how actively the organization wants to contribute requirements.
    • Current Working Group Representatives:
  • Product Manager (cross-function across Working Group and Project Team)
    • Unifies and prioritizes overall requirements set.
    • Owns the roadmap.
    • Leads the Project Team and defines the release schedule together with the Project Manager.
    • Accountable to the Working Group for delivery of agreed upon requirements.
    • Commitment: full-time role.
    • Full job description: Media:MeeGo_IVI_PDM.pdf
    • Current Product Manager:
  • Program Manager (cross-functional across Working Group and Project Team)
    • Works the Lead Architects and Lead Designers on effort estimates and schedules.
    • Leads the Project Team together with the Project Manager.
    • Accountable to the Working Group for deliverables and schedule.
    • Commitment: full-time role.
    • Full job description: Media:MeeGo_IVI_PJM.pdf
    • Current Program Manager: Joel Clark (Intel)

The Working Group meets regularly. Information on current and past meetings can be found on IVI Working Group.

Project Team

The Project Team has members with various roles that are subject to change according to the requirements of the current projects. The number of members and roles in the Project Team is not limited and grow as the team gains momentum and takes on larger tasks.

  • Lead Architect
    • Defines technical architecture to meet the requirements n terms of functionality, performance, etc.
    • Defines interfaces between modules and components together with other Lead Architects within the same and/or other Project Teams.
    • Performs feasibility studies and provides feedback to product manager on technical challenges, difficulties, “show stoppers”.
    • Commitment: > 50% dependent on sub-project complexity.
    • Current Lead Architect: Tom Counihan (Intel)
  • Lead Designer (multiple roles)
    • Responsible for the detailed implementation design of the architecture.
    • Estimates the effort necessary for implementation.
    • Leads implementation team comprised of engineering resources of his/her organization.
    • Commitment: full-time role.
    • Current Lead Designers
  • QA Lead (multiple roles)
    • Transforms requirements into functionality test plans.
    • Develops interface and compliance test procedures according to the architecture.
    • Implements black box and white box test tools through the resources of his/her organization.
    • Executes test plans and provides test reports.
    • Commitment: full-time role.
    • Current QA Leads:
  • Release Manager
    • Coordinates bug tracking, build and release with the design and QA leads.
    • Develops and manages build tools.
    • Leads build and release engineering team.
    • Commitment: full-time role.
    • Current Release Manager: Jeremiah Foster (Pelagicore)
  • Engineers for Development and QA (many roles)
    • Implement and test the required functionality.
    • Qualification varies with sub-project.
    • Commitment: full-time role.

Roadmap

The roadmap is always under discussion. But the important thing it that it is open and transparent - and you can contribute. The path to contribution begins on the MeeGo IVI mailing list. This list is the central communication point with all the MeeGo IVI stakeholders participating. Through this list you can contribute ideas, code, and other resources. You will also receive support and advice as well as pointers to other resources on this list, this is where the community comes together.

Before any new feature is committed to the Roadmap, a feature request is created in http://bugs.meego.com.

Submit new MeeGo IVI feature request

For a Feature Request to become part of the MeeGo IVI release plan, it needs to clearly define the engineering requirements and have resources working on development.

More details on the long term direction and short term Release plan may be found at Roadmap Details

MeeGo IVI Weekly Builds

Automated weekly MeeGo IVI repository and image builds are available on meego.com for testing and development baselining. Each build has a build version and date in its path. MeeGo Release Versioning explains the build version numbering scheme. For example 1.1.80.xx is a 1.2 Alpha build, 1.1.90.xx is a 1.2 Beta build, 1.1.99.x is a 1.2 Release Candidate, and 1.2.1 is the first release update after the final 1.2 release.

MeeGo weekly build repositories

IVI live .iso images are found under the IVI link. A list of every package included a live image is found in the same directory as the image. RPM packages are found under the oss and non-oss links.

MeeGo IVI 1.2 Feature Status

Featurezilla status report of MeeGo 1.2 IVI features

February 12, 2011
IVI Home Screen Changes
The IVIHome screen has been updated to reduce the number of choices in the main menu. Instead of a dozen or so choices in the main menu and two to three choices in sub-menus, now there are five to six choices in the main menu and about the same in sub-menus. We changed this to make menu choices easier and quicker. The IVI home screen has been designed to support driver interaction with the minimal amount of distraction. This is enhanced by the use of scrollwheel, Text to Speech and Speech Recognition, removing the need to look at or touch the display.
Nokia Terminal Mode
Packages implementing the Nokia Terminal Mode have been included in the build. There are two packages(libqterminalmode and qterminalmodeclient) must be installed from the oss repositories in order to try this code. These packages currently only work with Nokia developer kit phone sets. Terminal Mode Developer Offering has more information about the software and how to get developer kits
WiFi Tethering
MeeGo IVI now includes the capability to act as a WiFi Access Point enabling data sharing between tethered WiFi devices MeeGo WiFi Tethering Feature
EMGD
The Embedded Media Graphics Driver (EMGD) is now integrated with all IA32 builds and provides support for the Power-VR graphics core in Intel IVI platforms. The driver package is named "emgd-bin...." and can be found in the "non-oss" repository. This driver is considered ENGINEERING SAMPLE quality with NO guaranteed response to issues. Anyone planning to use this driver in product should obtain production quality support from the EMGD team via http://edc.intel.com

MeeGo IVI 1.2 Supported Platforms

IA32
There are now two IA32 images built every week. These images support the following platforms:
Image name Platform name Intel chipset I/O Hub name drivers included status
meego-ivi-ia32 Congatec IVI Kit (Russellville) Intel® Atom™ Processor Z5xx Series and Intel® System Controller Hub US15Wx (eMenlow) Timberdale GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, KS8842 GigE, EMGD, Video-in, SDHC, TSC2007, I2S, SDHC, ADV7180, BT, Radio No known driver issues
meego-ivi-ia32 Crown Bay Intel® Atom™ Processor E6xx Series for Embedded (Tunnel Creek) Intel® Platform Controller Hub EG20T (Top Cliff) GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, GigE, EMGD, PHUB, CAN No known driver issues
meego-ivi-ia32-conx Northville Intel® Atom™ Processor E6xx Series for Embedded (Tunnel Creek) ST Microelectronics ConneXt STA2x11 GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, GigE, EMGD, Video-in, MMC, CAN, USB-OTG, MSP, BT, FM-Radio in development, needs TSC2007 patch


ARM
Jeremiah Foster and Jan-Simon Moeller are working on updates to enable automated weekly builds of MeeGo IVI images for the Beagleboard-XM.

Releases

Resources

Retrieved from "http://wiki.meego.com/In-vehicle"
Personal tools