MeeGo wiki - User contributions [en]

IVI Images for ConneXt IOH

2011-11-18T16:40:17Z

Joel:

= IVI Images for ConneXt IOH =

The Stephenville/Crossville platform with the ST Microelectronics ConneXt STA2x11 IO Hub is not supported in the MeeGo 1.2.0 release. These drivers are available on [http://sourceforge.net/projects/sta2x11/files/ Sourceforge] and are part of the 1.3 development in the current 1.2.80 Trunk builds on MeeGo. In order to support Stephenville customers with this platform, the Stephenville team is also providing MeeGo images with the latest ST Microelectronics drivers built in.

We currently have an image with MeeGo 1.2.0 release with the May 27th ConneXt drivers, posted below. Our plans are to create additional images when a new release of MeeGo is available and when new driver updates are available.

== Available Images ==

=== Breaking News Nov. 17, 2011: New images for Crossville platforms with ConneXt STA2x11===

[http://repo.meego.com/MeeGo/updates/1.2.0/images/ MeeGo 1.2.0 Update 4 images]

meego-ivi-ia32-conx is for Crossville platforms with the "Cut1" version of ConneXt STA2x11

meego-ivi-ia32-conx2 is for Crossville platforms with the "Cut2" version of ConneXt STA2x11

[https://meego.com/devices/in-vehicle/installing-meego-your-intel-ivi-system Installation instructions for installing .img files]

=== MeeGo 1.2.0 with May 27th drivers ===

[ftp://ftp.intel.com/pub/sites/ASD/ConneXt_IOH_Images/meego-conx-1.2.0-05.27.tar.gz meego-conx-1.2.0.5.27.tar.gz]is a tar zip archive contains an image with the ST Microelectronics drivers posted on [http://sourceforge.net/projects/sta2x11/files/2.6.37/20110527/ Sourceforge May 27th].

==== Instructions ====
* Download the tar archive
* Extract the archive
** on Linux extract by
***tar xzfv meego-conx-1.2.0-05.27.tar.gz
** on Windows winzip will extract
* Install with the live image (meego-ivi-ia32-conx-1.2.0-WRSI-05.27-1.iso listed below) following the procedure from [https://meego.com/devices/in-vehicle/installing-meego-your-intel-ivi-system#linux-instructions Installing MeeGo on your Intel IVI system]
==== Archive contents ====
* Checksum for the files
** CHECKSUMS.md5
* Kernel rpms from the [http://repo.meego.com/MeeGo/builds/1.2.80/1.2.80.6.0.20110614.7/repos/oss/ia32/packages/i586/ June 14th build of MeeGo]
** kernel-adaptation-connext-2.6.37.6-10.1.i586.rpm
** kernel-adaptation-connext-debugsource-2.6.37.6-10.1.i586.rpm
** kernel-adaptation-connext-devel-2.6.37.6-10.1.i586.rpm
* Kernel source rpm from the [http://repo.meego.com/MeeGo/builds/1.2.80/1.2.80.6.0.20110614.7/repos/oss/source/ June 14th build of MeeGo]
** kernel-adaptation-connext-2.6.37.6-10.1.src.rpm
*Kickstart file
** meego-ivi-ia32-conx-1.2.0.ks
* Live image
** meego-ivi-ia32-conx-1.2.0-WRSI-05.27-1.iso
*Package list
** meego-ivi-ia32-conx-1.2.0-WRSI-05.27-1-pkgs.txt

==== Known ConneXt Issues ====
* [https://bugs.meego.com/show_bug.cgi?id=20045 20045] Ethernet interface speed change failure
* [https://bugs.meego.com/show_bug.cgi?id=20044 20044] EHCI crashes
* [https://bugs.meego.com/show_bug.cgi?id=20043 20043] Crossville-ST CUT1 Radio playback/recording failure
* [https://bugs.meego.com/show_bug.cgi?id=18916 18916] GUI Installer hangs when a storage device partition table cannot be read
* [https://bugs.meego.com/show_bug.cgi?id=18006 18006] Radio and bluetooth firmware is loaded by an init script.
* [https://bugs.meego.com/show_bug.cgi?id=17510 17510] stmmac of the connext kernel stack traces and stops working
* [https://bugs.meego.com/show_bug.cgi?id=17349 17349] Connext kernel fails to enter suspend
* [https://bugs.meego.com/show_bug.cgi?id=17347 17347] Connext frame grabber has a hardcoded reset sequence of ADV7180 in it, which breaks MMC3
* [https://bugs.meego.com/show_bug.cgi?id=17346 17346] Connext SDIO driver crashes on cleanup
* [https://bugs.meego.com/show_bug.cgi?id=16002 16002] IVI/Northville:dmesg error after plugin SD card into middle SD slot(CN5)
* [https://bugs.meego.com/show_bug.cgi?id=15157 15157] Northville/CrossvilleST: Bluetooth initialization time out with speed other than 115200
* [https://bugs.meego.com/show_bug.cgi?id=15117 15117] IVI/Northville: Bluetooth not enabled by default
* [https://bugs.meego.com/show_bug.cgi?id=14834 14834] IVI/Northville: tsc2007: probe of 1-0048 failed with error -110
* [https://bugs.meego.com/show_bug.cgi?id=14831 14831] CrossvilleST: sta2x11_msp 0000:06:00.7: Interrupt: Receive Overrun Error
* [https://bugs.meego.com/show_bug.cgi?id=14830 14830] IVI/Northville: speech recognition does not work
* [https://bugs.meego.com/show_bug.cgi?id=14797 14797] IVI/Northville/CrossvilleST: installation by text mode failed to be completed, hangs after running post scripts
* [https://bugs.meego.com/show_bug.cgi?id=14684 14684] IVI/Northville: Failed to display via VGA
* [https://bugs.meego.com/show_bug.cgi?id=14570 14570] IVI/Northville:mmci-pci: probe of 0000:05:00.3/4 failed with error -22
* [https://bugs.meego.com/show_bug.cgi?id=13359 13359] IVI/Northville: i2c-sta2x11: probe of 0000:04:00.4 failed with error -22
* [https://bugs.meego.com/show_bug.cgi?id=13358 13358] IVI/Northville: ehci_hcd: probe of 0000:03:00.2 failed with error -22

Packaging/Guidelines

2011-07-27T20:36:07Z

Joel:

= Packaging Guidelines =

Guidelines below were adapted for MeeGo from Moblin, OpenSUSE, Fedora and other distributions.

== Maintaining a Package ==
Every package in MeeGo needs a maintainer (AKA owner, bug owner). Any package without an owner will automatically be nominated for deletion from MeeGo. A package maintainer is responsible for making sure that
* packages are up to date with latest upstream
* packages consistently build in the MeeGo build system and fix build failures when they occur
* package meta data in the RPM spec file is accurate
* the license of the package is correct
* she/he follow upstream for any critical security issues and fix them ASAP
* she/he Provides information about major changes to other packagers and maintainer to allow enough time for fixing compatibility issues

Since the data about ownership of packages is not maintained anywhere right now we are starting to use available meta data fields in the build system to track ownership. This will be better integrated and managed at a later point, but to be able to start somewhere MeeGo will use the bugowner key available for every package. We will start adding the metadata about maintainers (bugowners) in the build system and we will have a grace period for this data to be supplied and added to the build system. After the grace period, packages without a maintainer will be reviewed and any packages without a maintainer will be nominated for deletion.

To add yourself as a bugowner of a package, please follow the steps below:
* Update to the most recent osc version (0.131) from the MeeGo tools repository. Note: this is essential, since the needed options are not released upstream yet. Tools: http://repo.meego.com/MeeGo/tools/repos/
* Identify the packages of which you are the ultimate maintainer
* Do the following for every package you maintain in the Trunk:* projects:
<code>
osc reqms --role bugowner <project> <package> -m "I want to own this because I love this package"
</code>
* Your request will be sent and someone in release engineering will approve it

The current status can be seen here: [[Packaging/Maintainers]]

== Package Naming ==
* Dash '-' must be used as the delimiter for name parts.
* Do NOT use an underscore '_', a plus '+', or a period '.' as a delimiter.
* The spec file should be named using the %{name}.spec scheme which should also correspond to the package name within a project in the build system.

== Version and Release ==

Package Versions look like : X.Y.Z-R.B
* X.Y.Z is the 'Version' number - determined by the source package.
* R is the 'Release' number which is automatically incremented by OBS whenever a source/packaging changes (eg a check-in or request acceptance)
* B is the build number which is incremented when the package is rebuilt due to a dependency change.

=== Version ===

The Version field in the spec file is where you should put the current version of the software being packaged.
There are four cases where the version contains non-numeric characters:

* Pre-release packages: Packages released as "pre-release" versions, prior to a "final" version. Example tags include "alpha", "beta", "rc", "cvs", "git", "svn", etc... Details can be found below: Non-Numeric Version.
* Post-release packages: Packages released after a "final" version. These packages contain the same numeric version as the "final" version, but have an additional non-numeric identifier. This mechanism may also be used for packaging only changes to an upstream package.
* Snapshot packages: Packages built from SCM snapshots. These packages could be either "pre" or "post" release packages.

==== Non-Numeric Version ====

We can use letters and tilde into the version tag. We do not use the Release field for this.

Example:
<pre>
Let's assume the following Qt versions:
Qt 4.7.0~beta1
Qt 4.7.0~beta1+git1
Qt 4.7.0~beta2
Qt 4.7.0

rpmdev-vercmp is a rpm version comparison checker, belongs to package rpmdevtools,
you need to install it first through zypper.

Version comparison results:
$ rpmdev-vercmp 4.7.0~beta1 4.7.0~beta1+git1
0:4.7.0~beta1+git1-None is newer

$ rpmdev-vercmp 4.7.0~beta1+git2 4.7.0~beta2
0:4.7.0~beta2-None is newer

$ rpmdev-vercmp 4.7.0~beta2 4.7.0
0:4.7.0-None is newer

Conclusion:
4.7.0~beta1 < 4.7.0~beta1+git1 < 4.7.0~beta2 < 4.7.0
</pre>

Note that the ~ comparison order is specific to MeeGo rpm (http://rpm.org/ticket/56).

=== Release ===

This field is handled by the build system to be able to manage automated builds. The initial setting in the spec file is used by the build system but in many cases it does not need to be changed.

There is no need for the %{dist} macro in the release field. This is also handled directly by the build system.

The release number is set to zero with any version update. It is increased by one with any change in the package.

We can put letters into the version tag, so we do not use the Release field for this. Details can be found above.

If you build the package outside of the OBS or if you copy a package then you will of course not get the correct Release or Build values.

== Tags ==
*The ''Packager'' tag should not be used in spec files. The identities of the packagers are evident from the changelog entries. By not using the ''Packager'' tag, you also avoid seeing bad binaries rebuilt by someone else with your name in the header. See also the '''Maximum RPM definition of the Packager tag''' at [http://www.rpm.org/max-rpm/s1-rpm-inside-tags.html#S3-RPM-INSIDE-PACKAGER-TAG www.rpm.org] . If you need to include information about the packager in the rpms ''you'' built, use <code>%packager</code> in your <code>~/.rpmmacros</code> instead.
*The ''Vendor'' tag should not be used. It is set automatically by the build system.

*Usually, the ''Pre<code></code>Req'' tag should be replaced by plain ''Requires''. For more info, see Maximum RPM snapshot's [http://www.rpm.org/max-rpm-snapshot/s1-rpm-depend-manual-dependencies.html#S3-RPM-DEPEND-FINE-GRAINED fine grained dependencies chapter] .
* The ''Source'' tag documents where to find the upstream sources for the rpm. In most cases this should be a complete URL to the upstream tarball.
=== Summary Tag ===
The summary is a single line string describing the package. The maximum length is 80 characters. It should fit all standard situations and not assume any special context. It should be helpful alone, in alphabetically sorted or unsorted lists of some selected packages, and in alphabetically sorted or unsorted lists of all packages.

It should describe the package's main function and point out any special properties of the package to support the user comparing similar packages. For example, the two words "Web Browser" summarize any web browser, but using additional adjectives (like minimalistic, complex, GNOME, KDE, text-based, fast, or author's) helps characterize a specific package.

The RPM spec file contains only the English version to keep the RPM database small.

*The ''Summary'' tag value should not end in a period. If this bothers you from a grammatical point of view, sit down, take a deep breath, and get over it.

=== Group Tag ===

The group tag is used to group packages by the types of functionality they provide. In MeeGo the latest group tag are defined in package sepctacle, you can check out in file /usr/share/spectacle/GROUPS.

Valid RPM Groups are:
<pre>
Amusements/Games
Amusements/Graphics
Applications/Archiving
Applications/Communications
Applications/Databases
Applications/Editors
Applications/Emulators
Applications/Engineering
Applications/File
Applications/Internet
Applications/Multimedia
Applications/Productivity
Applications/Publishing
Applications/System
Applications/Text
Development/Debuggers
Development/Languages
Development/Libraries
Development/System
Development/Tools
Documentation
System/Boot
System/Console
System/I18n/Chinese
System/I18n/Japanese
System/I18n/Korean
System/Packages
System/Base
System/Daemons
System/Kernel
System/Libraries
System/Shells
System/X11
System/X11/Fonts
System/X11/Icons
System/GUI/XFCE
System/GUI/Other
System/GUI/GNOME
</pre>

==== Domain/Subsystem based RPM Groups ====

Following the new architecture and the new [http://meego.com/developers/meego-architecture/meego-architecture-domain-view domain view], RPM groups (The Group tag in the RPM) for core packages will be changed to match the domains and any package in the core that is part of one of the domain will have a corresponding group that matches the architecture.

{|
! Domain
! Subsystem
!Groupname
|-
| Communications || Cellular Adaptation || Communications/Cellular Adaptation
|-
| Communications || Cellular Framework || Communications/Cellular Framework
|-
| Communications || Telephony and IM || Communications/Telephony and IM
|-
| Communications || Bluetooth || Communications/Bluetooth
|-
| Communications || Connectivity Adaptation || Communications/Connectivity Adaptation
|-
| Communications || ConnMan || Communications/ConnMan
|-
| Data Management || Content Framework || Data Management/Content Framework
|-
| Development Platform || Platform SDK || Development Platform/Platform SDK
|-
| Essentials || Base Essentials || Essentials/Base Essentials
|-
| Graphics || Font Management || Graphics/Font Management
|-
| Graphics || Display and Graphics Adaptation || Graphics/Display and Graphics Adaptation
|-
| Graphics || Input Adaptation || Graphics/Input Adaptation
|-
| Graphics || Open GL ES || Graphics/Open GL ES
|-
| Graphics || X11 || Graphics/X11
|-
| Kernel || Linux Kernel || Kernel/Linux Kernel
|-
| Location || Location Framework || Location/Location Framework
|-
| Location || Location Adaptation || Location/Location Adaptation
|-
| Multimedia || Audio Adaptation || Multimedia/Audio Adaptation
|-
| Multimedia || Camera Adaptation || Multimedia/Camera Adaptation
|-
| Multimedia || Gstreamer || Multimedia/Gstreamer
|-
| Multimedia || Imaging and Video Adaptation || Multimedia/Imaging and Video Adaptation
|-
| Multimedia || Imaging Codecs || Multimedia/Imaging Codecs
|-
| Multimedia || PulseAudio || Multimedia/PulseAudio
|-
| Multimedia || Sharing || Multimedia/Sharing
|-
| Multimedia || UPnP || Multimedia/UPnP
|-
| Personal Information Management || Backup Framework || Personal Information Management/Backup Framework
|-
| Personal Information Management || Calendar Engine || Personal Information Management/Calendar Engine
|-
| Personal Information Management || Contacts Engine || Personal Information Management/Contacts Engine
|-
| Personal Information Management || Email Engine || Personal Information Management/Email Engine
|-
| Personal Information Management || Synchronization Framework || Personal Information Management/Synchronization Framework
|-
| Qt || Qt || Qt/Qt
|-
| Qt || Qt Mobility || Qt/Qt Mobility
|-
| Qt || Qt WebKit || Qt/Qt WebKit
|-
| Security || Accounts || Security/Accounts
|-
| Security || Certificate Manager || Security/Certificate Manager
|-
| Security || Integrity Protection Framework || Security/Integrity Protection Framework
|-
| Security || Access Control Framework || Security/Access Control Framework
|-
| Security || Single Sign-On || Security/Single Sign-On
|-
| Security || SW Distribution Security || Security/SW Distribution Security
|-
| Security || Security Adaptation || Security/Security Adaptation
|-
| Software Management || Package Manager || Software Management/Package Manager
|-
| System || Context Framework || System/Context Framework
|-
| System || NGF || System/NGF
|-
| System || Resource Policy || System/Resource Policy
|-
| System || Sensor Adaptation || System/Sensor Adaptation
|-
| System || Sensor Framework || System/Sensor Framework
|-
| System || Startup Services || System/Startup Services
|-
| System || System Control || System/System Control
|-
| System || Device Mode Adaptation || System/Device Mode Adaptation
|-
| System || Vibra and Haptics Adaptation || System/Vibra and Haptics Adaptation
|-

|}

=== BuildRoot tag ===
The ''BuildRoot'' value MUST be below <code>%{_tmppath}/</code> and MUST contain at least <code>%{name}</code>, <code>%{version}</code> and <code>%{release}</code>.

The ''recommended'' values for the ''BuildRoot'' tag are (in descending order of preference) :
<pre>
%{_tmppath}/%{name}-%{version}-%{release}-root
</pre>

The BuildRoot tag can be omitted in packages targeting MeeGo only and is handled directly by rpm in MeeGo, for packages that need to run on other distros with older rpm it should be added for backward compatibility.

=== PreReq ===

Packages should not use the PreReq tag. Once upon a time, in dependency loops PreReq used to "win" over the conventional Requires when RPM determined the installation order in a transaction. This is no longer the case.

=== Explicit Requires ===
Packages must not contain explicit ''Requires'' on libraries except when absolutely
necessary. When explicit library ''Requires'' are necessary, there should be a spec file comment justifying it.

We generally rely on rpmbuild to automatically add dependencies on library SONAMEs.
Modern package management tools are capable of resolving such dependencies to determine
the required packages. Explicit dependencies on specific package names may aid the
inexperienced user, who attempts at installing RPM packages manually, however, history
has shown that such dependencies add confusion when library/files are moved from one
package to another, when packages get renamed, when one out of multiple alternative
packages would suffice, and when versioned explicit dependencies become out-of-date and
inaccurate. Additionally, in some cases, old explicit dependencies on package names
require unnecessary updates/rebuilds.

Exemplary rationale for a versioned explicit dependency:
<pre>
# The automatic dependency on libfubar.so.1 is insufficient,
# as we strictly need at least the release that fixes two segfaults.
Requires: libfubar >= 0:1.2.3-7
</pre>

Packagers should revisit an explicit dependency as appropriate to avoid
it becoming inaccurate and superfluous.

=== BuildRequires ===

In package development and testing, please verify that your package is not missing any necessary build dependencies. Having proper build requirements saves the time of all developers and testers as well as build systems because they will not need to search for missing build requirements manually. It is also a safety feature that prevents builds with that would not otherwise fail, but would be missing crucial features. For example, a graphical application may exclude PNG support after its '''configure''' script detects that libpng is not installed.

Before adding Build<code></code>Requires to any package, please be comfortable with [[#Explicit Requires| Requires]] .

=== Patches ===
Each problem should be solved in a separate patch. To allow easy maintenance of patches, every patch should have a header providing the following information:

* Authors' names
* [http://meego.com/about/contribution-guidelines/signed-process Signed-off-by] tag
* Detailed description of the fixed problem
* URL of the original source of the patch if any

The name of a patch file consists of:

* The name and version of the source tarball from which the patched file is derived
* Some words that characterize the patch content
* The filename suffix <code class="filename">.patch</code>

Patches are in the unified format ('''diff -u''') and should be applied with 1 strip level in the spec file ('''%patch -p1'''). The only exceptions are the patches obtained from an another primary source site. The original name, suffix, and format is preserved in this case.

Each patch should be compressed with '''bzip2''' if its size is greater than 100kB. The macros <code class="systemitem">%name</code> and <code class="systemitem">%version</code> should be used whenever possible.

Example:

Source: %{name}-%{version}.tar.bz2
Patch0: %{name}-%{version}-autoconf.patch
Patch1: %{name}-%{version}-gcc31.patch

For the patches to be applied, the patches should be mentioned under %setup. For the above example, this could be done as

%setup -q
%patch0 -p1
%patch1 -p1

Patches have to be marked as such in the spec file and should be applied using the internal patch routines available in rpm. Use of alternate patch management system not supported by rpm is not allowed.

=== %clean ===

The %clean section is not required for MeeGo 1.1 and above. Each package for MeeGo 1.0 MUST have a %clean section, which contains rm -rf %{buildroot} (or $RPM_BUILD_ROOT).

== Documentation ==
Any relevant documentation included in the source distribution should be included in the package. Irrelevant documentation include build instructions, the omnipresent ''INSTALL'' file containing generic build instructions, for example, and documentation for non-Linux systems, e.g. ''README.MSDOS''. Pay also attention about which subpackage you include documentation in, for example API documentation belongs in the -devel subpackage, not the main one. Or if there's a lot of documentation, consider putting it into a subpackage. In this case, it is recommended to use <code>*-doc</code> as the subpackage name, and <code>Documentation</code> as the value of the <code>Group</code> tag.

Also, if a package includes something as <code>%doc</code>, it must not affect the runtime of the application. To summarize: If it is in <code>%doc</code>, the program must run properly if it is not present.

== Devel Packages ==
If the software being packaged contains files intended solely for development, those files should be put in a -devel subpackage. The following are examples of file types which should be in -devel:
* Header files (such as .h files)
* Unversioned shared libraries (such as libfoo.so). Versioned shared libraries (such as libfoo.so.3, libfoo.so.3.0.0) should not be in -devel.

A good rule of thumb is if the file is used for development and not needed for the base package to run properly, it should go in -devel.

=== Requiring Base Package ===
Devel packages must require the base package using a fully versioned dependency: <code>Requires: %{name} = %{version}-%{release}</code>.
Usually, subpackages other than -devel should also require the base package using a fully versioned dependency.

=== Pkgconfig Files ===
The placement of pkgconfig(.pc) files depends on their usecase. Since they are almost always used for development purposes, they should be placed in a -devel package.
A reasonable exception is when the main package itself is a development tool not installed in a user runtime, such as gcc or gdb.

== Test Packages ==
Tests should be included in -test subpackage or separate package according to the following guidelines.

[http://wiki.meego.com/Test_Packaging Test Packaging Guidelines]

== Shared Libraries ==
Whenever possible (and feasible), MeeGo Packages containing libraries should build them as shared libraries. In addition, every binary RPM package which contains shared library files (not just symlinks) in any of the dynamic linker's default paths, must call ldconfig in <code>%post</code> and <code>%postun</code>. If the package has multiple subpackages with libraries, each subpackage should also have a <code>%post/%postun</code> section that calls <code>/sbin/ldconfig</code>. An example of the correct syntax for this is:
<pre>
%post -p /sbin/ldconfig

%postun -p /sbin/ldconfig
</pre>
Note that this specific syntax only works if <code>/sbin/ldconfig</code> is the only call in <code>%post</code> and <code>%postun</code>. If you have additional commands to run during the scriptlet, call <code>/sbin/ldconfig</code> at the beginning of the scriptlet, like this:
<pre>
%post
/sbin/ldconfig
/usr/bin/foo --add

%postun
/sbin/ldconfig
/usr/bin/foo --remove
</pre>

== Configuration files ==

Configuration files must be marked as such in packages.

As a rule of thumb, use <code>%config(noreplace)</code> instead of plain <code>%config</code> unless your best, educated guess is that doing so will break things. In other words, think hard before overwriting local changes in configuration files on package upgrades. An example case when /not/ to use <code>noreplace</code> is when a package's configuration file changes so that the new package revision wouldn't work with the config file from the previous package revision. Whenever plain <code>%config</code> is used, add a brief comment to the specfile explaining why.

Don't use %config or %config(noreplace) under /usr. /usr is deemed to not contain configuration files in MeeGo.

== Initscripts ==

In MeeGo 1.2 and previous version SystemV-style initscripts are supported.

In MeeGo 1.3 we use [http://en.wikipedia.org/wiki/Systemd Systemd] as system and service manager.

== Desktop files ==

If a package contains a GUI application, then it needs to also include a properly installed .desktop file. For the purposes of these guidelines, a GUI application is defined as any application which draws an X window and runs from within that window. Installed .desktop files MUST follow the [http://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html desktop-entry-spec] , paying particular attention to validating correct usage of Name, GenericName, [http://standards.freedesktop.org/menu-spec/latest/apa.html Categories] ,
[http://www.freedesktop.org/Standards/startup-notification-spec StartupNotify]
entries.

=== Icon tag in Desktop Files ===
The icon tag can be specified in two ways:

* Full path to specific icon file:
<code> Icon=/usr/share/pixmaps/comical.png </code>

* Short name without file extension:
<code> Icon=comical </code>

The short name without file extension is preferred, because it allows for icon theming (it assumes .png by default, then tries .svg and finally .xpm), but either method is acceptable.

=== .desktop file creation ===
If the package doesn't already include and install its own .desktop file, you need to make your own. You can do this by including a .desktop file you create as a Source: (such as Source3: %{name}.desktop) or generating it in the spec file. Here are the contents of a sample .desktop file (comical.desktop):

<pre>
[Desktop Entry]
Name=Comical
GenericName=Comic Archive Reader
Comment=Open .cbr & .cbz files
Exec=comical
Icon=comical
Terminal=false
Type=Application
Categories=Graphics;
</pre>

=== Localizing .desktop files ===
The values of Name or GenericName are displayed as captions to the graphical desktop icon, so they should be localized according to the [http://standards.freedesktop.org/desktop-entry-spec/latest/ar01s04.html Desktop Entry Specification]. Most of the time, only ''language'' codes or ''language/country'' codes are needed to select the intended system locale. For example:

<pre>
[Desktop Entry]
Type=Application
Name=Clocks
Name[de]=Uhrzeit
Name[es]=Relojes
Name[fr]=Horloges
Name[pt_BR]=Relógios
Name[zh_CN]=时钟
Icon=meego-app-clocks
Exec=meego-qml-launcher --opengl --fullscreen --app meego-app-clocks
</pre>

In the above .desktop file, <tt>[de]</tt> specifies the German language locale, covering any German-speaking locale, such as <tt>de_DE</tt> or <tt>de_AT</tt>.

'''Note:''' Since a ''language/country'' code (e.g. <tt>pt_BR</tt>) is more specific than a ''language'' code (e.g. <tt>pt</tt>), a string for the <tt>pt_BR</tt> locale will '''not''' be used for the Portuguese language locale (<tt>pt</tt>). If a string is appropriate for every Portuguese locale, you can use "<tt>Name[pt]</tt>" instead.

=== desktop-file-install usage ===
It is not simply enough to just include the .desktop file in the package, one MUST run <code>desktop-file-install</code> OR <code>desktop-file-validate</code> in <code>%install</code> (and have <code>BuildRequires: desktop-file-utils</code>), to help ensure .desktop file safety and spec-compliance. <code>desktop-file-install</code> MUST be used if the package does not install the file or there are changes desired to the .desktop file (such as add/removing categories, etc). <code>desktop-file-validate</code> MAY be used instead if the .desktop file's content/location does not need modification. Here are some examples of
usage:

<pre>
desktop-file-install \
--dir=${RPM_BUILD_ROOT}%{_datadir}/applications \
%{SOURCE3}
</pre>

<pre>
desktop-file-install \
--add-category="AudioVideo" \
--delete-original \
--dir=%{buildroot}%{_datadir}/applications \
%{buildroot}/%{_datadir}/foo.desktop
</pre>

<pre>
desktop-file-validate %{buildroot}/%{_datadir}/applications/foo.desktop
</pre>

=== .desktop file post-install ===

After installing a .desktop file, it's typical to touch the file and the folder so that the UX will detect the change. Otherwise, the new file will not be detected until reboot. I.e.

%post
touch %{_datadir}/applications/foo.desktop
touch %{_datadir}/applications

...will update the time-stamp of the folder and the .desktop file.

== Macros ==
=== Using %{buildroot} and %{optflags} vs $RPM_BUILD_ROOT and $RPM_OPT_FLAGS ===
There are two styles of defining the rpm Build Root and Optimization Flags in a spec file:

{| border="1"
|-
| ||macro style || variable style
|-
|Build Root||%{buildroot}||$RPM_BUILD_ROOT
|-
|Opt. Flags||%{optflags}||$RPM_OPT_FLAGS
|}

There is very little value in choosing one style over the other, since they will resolve to the same values in all scenarios. You should pick a style and use it consistently throughout your packaging.

Mixing the two styles, while valid, is bad from a QA and usability point of view, and should not be done in MeeGo packages.

== Handling Locale Files ==

If the package includes translations, add
<pre>
BuildRequires: gettext
</pre>
If you don't, your package could fail to generate translation files in the buildroot.

MeeGo includes an rpm macro called <code>%find_lang</code>. This macro will locate all of the locale files that belong to your package (by name), and put this list in a file. You can then use that file to include all of the locales. <code>%find_lang</code> should be run in the %install section of your spec file, after all of the files have been installed into the buildroot. The correct syntax for <code>%find_lang</code> is usually:
<pre>
%find_lang %{name}
</pre>
In some cases, the application may use a different "name" for its locales. You may have to look at the locale files and see what they are named. If they are named <code>myapp.mo</code>, then you will need to pass <code>myapp</code> to <code>%find_lang</code> instead of <code>%{name</code>}.
After <code>%find_lang</code> is run, it will generate a file in the active directory (by default, the top level of the source dir). This file will be named based on what you passed as the option to the <code>%find_lang</code> macro. Usually, it will be named <code>%{name}.lang</code>. You should then use this file in the <code>%files</code> list to include the locales detected by <code>%find_lang</code>. To do this, you should include it with the -f parameter to <code>%files</code>.
<pre>
%files -f %{name}.lang
%defattr(-,root,root,-)
%{_bindir}/foobar
...
</pre>
If you are already using the -f parameter for the <code>%files</code> section where the locales should live, just append the contents of <code>%{name}.lang</code> to the end of the file that you are already using with -f. (Note that only one file may be used with <code>%files -f</code>.)

Here is an example of proper usage of <code>%find_lang</code>, in <code>foo.spec</code>:

<pre>
...
%prep
%setup -q

%build
%configure --with-cheese
make %{?_smp_mflags}

%install
make DESTDIR=%{buildroot} install
%find_lang %{name}

%clean
rm -rf %{buildroot}

%files -f %{name}.lang
%defattr(-,root,root,-)
%doc LICENSE README
%{_bindir}/foobar

</pre>

=== Why do we need to use %find_lang? ===

Using <code>%find_lang</code> helps keep the spec file simple, and helps avoid several other packaging mistakes.

* Packages that use <code>%{_datadir}/*</code> to grab all the locale files in one line also grab ownership of the locale directories, which is not permitted.
* Most packages that have locales have lots of locales. Using <code>%find_lang</code> is much easier in the spec file than having to do:
<pre>
%{_datadir}/locale/ar/LC_MESSAGES/%{name}.mo
%{_datadir}/locale/be/LC_MESSAGES/%{name}.mo
%{_datadir}/locale/cs/LC_MESSAGES/%{name}.mo
%{_datadir}/locale/de/LC_MESSAGES/%{name}.mo
%{_datadir}/locale/es/LC_MESSAGES/%{name}.mo
...
</pre>
* As new locale files appear in later package revisions, <code>%find_lang</code> will automatically include them when it is run, preventing you from having to update the spec any more than is necessary.

Keep in mind that usage of <code>%find_lang</code> in packages containing locales is a MUST.

== Scriptlets ==
Great care should be taken when using scriptlets in MeeGo packages. If scriptlets are used, those scriptlets must be sane.

=== Scriptlets requirements ===
Do not use the <code>Requires(pre,post)</code> style notation for scriptlet dependencies, because of two bugs in RPM. Instead, they should be split like this:
<pre>
Requires(pre): ...
Requires(post): ...
</pre>
For more information, see [http://www.redhat.com/archives/fedora-devel-list/2004-April/msg00674.html www.redhat.com] .

=== Running scriptlets only in certain situations ===
When the rpm command executes the scriptlets in a package it indicates if the action preformed is an install, erase, upgrade or reinstall by passing an integer argument to the script in question according to the following:
<pre>
install erase upgrade reinstall
%pre 1 - 2 2
%post 1 - 2 2
%preun - 0 1 -
%postun - 0 1 -
</pre>
This means that for example a package that installs an init script with the <code>chkconfig</code> command should uninstall it only on erase and not upgrade with the following snippet:
<pre>
%preun
if [ $1 -eq 0 ] ; then
/sbin/chkconfig --del %{name}
fi
</pre>
See also <code>/usr/share/doc/rpm-*/triggers</code>, which gives a more formal, generalized definition about the integer value(s) passed to various scripts.

=== Scriplets are only allowed to write in certain directories ===
Build scripts of packages (%prep, %build, %install, %check and %clean) may only alter files (create, modify, delete) under %{buildroot}, %{_builddir} and valid temporary locations like /tmp, /var/tmp (or $TMPDIR or %{_tmppath} as set by the rpmbuild process) according to the following matrix

{| border="1"
|-
| || /tmp, /var/tmp, $TMPDIR, %{_tmppath} || %{_builddir} || %{buildroot}
|-
|%prep || yes || yes || no
|-
|%build || yes || yes || no
|-
|%install || yes || yes || yes
|-
|%check || yes || yes || no
|-
|%clean || yes || yes || yes
|}

Further clarification: That should hold true irrespective of the builder's uid.

== Use of Epochs ==
The Epoch tag in RPM is to be used only as a last resort, and should be avoided whenever possible. However, it is sometimes necessary to use an Epoch to handle upstream versioning changes or to ease transition from third party repositories.

== Writing a package from scratch ==

See [[Spectacle]]

Spectacle is a great tool for straightforward packages, and we have many of those, hundreds, many of those packages already have been using spectacle happily for a while now. Generally, the 80/20 rule applies here, almost 80% of packages in MeeGo can be converted to this format, probably around 20% will need to stay as is for various reasons.

Spectacle in general helps a lot when you have a package that does:
* configure
* make
* make install

and especially useful when for example you have to manage many build dependencies and patches or for common packaging of perl/python/X packages that usually follows the same packaging work flow. We have plans to add lots of nice features to make packaging easier and more fun with spectacle.

While spectacle has many advanced options to cover all kind of corner cases, it should not be used for complex packages that would require lots of customization, especially now that we support multiple architectures and where we need to apply code and custom scripts to support different scenarios.

Spectacle provides scripts to convert spec files to spectacle, those try to do their best but you SHOULD never just take the output as is and rely on the script, a review of the output is necessary, otherwise you might end up with lots of duplication in the spec file. This is the most common mistake, developers are relying on the output of the conversion script, basically picking some spec file from another distro and converting it. This can lead to major disasters in some cases.

So to summarize:
* It is NOT mandatory to use spectacle
* If you try to convert and find yourself spending more than a few minutes on a package, then probably there is something wrong and you should not be using that or you should RTFM.
* Use it with care, especially when you first import the data from existing spec files or when you first create your YAML file
* Your distro maintainer might send you a note that certain packages you are maintaining could be converted to spectacle easily, but she/he should not reject your package because it does not use spectacle.
* If you find yourself forced to edit the spec file manually for some reason, then either:
** your package is not suitable to be used with spectacle
** or you might want to ask for a feature to support that special case
* packager should not change packaging format randomly.
** You need to be the main maintainer
** If a package is already using the yaml format, you need to have a valid reason why not to use the yaml format

== Modifying existing Packages ==

If you base a new package on an existing non-MeeGo package, make sure you verify its correctness of the package and the spec file and to understand exactly what has been done to package the software exactly. Do not submit a package without knowing what those strange, but innocent-looking commands do.

In particular, you should

* ensure that original tarballs are self-contained pristine tarballs. The tarball should not contain symlinks that reference outside the tarball root directory
* verify any sources and patches and remove patches or sources that:
** are related to platforms we do not support (example: sparc, ia64, ppc, ...)
** Implement features we do not support (example: selinux)
** Read every patch and understand what it does, if it is needed, put an explanation in the header justifying why the patch is needed.
* verify that the license stated in the spec file matches the actual license of the software,
* skim the summary and description for typos and oddities (see Summary and description ),
* make sure that the correct build root is used,
* ensure that macro usage is consistent and that the macros are available in MeeGo (see Macros ).

Keep old changelog entries to credit the original authors. Entries that are several years old or refer to ancient versions of the software may be erased. If you end up doing radical changes and re-write most of the spec file anyway, feel free to start the changelog from scratch. In other words, use your best judgement.

== Changelogs ==

This section describes the MeeGo policy for RPM changelogs. (Original changelogs included in the original source are not affected by this policy.)

Please consider that a "normal end user with some technical skills" should be able to read and understand an RPM changelog. Changelog entries have to be in reverse chronological order: newer change log entries are listed above older entries, with the first entry being the most recent.

Please bear in mind that MeeGo changelogs will be automatically parsed to prepare distribution release notes and to report on bugs and CVEs and malformed entries may not be read correctly.

=== General information ===

* MeeGo uses a separate file for package changes which is similar to a debian changelog file. This file is named as the spec file, but ends in *.changes instead of *.spec. The %changelog% section must not be used in the .spec file.
* Entries in the changes file should have the following structure:
<pre>
* dow mmm dd yyyy Name Goes Here <your@email.com> - [version]
- comment
- comment

</pre>

Note the following exceptions are noted through observation:
* version is often omitted (such as: alsa-utils 1.0.15-1 -> 1.0.16-1)
* there are multiple changelog entries per version (such as: alsa-utils 1.0.19)
* the hyphen between email and version is often omitted (such as: alsa-utils)
* spaces between name and <email> are omitted (such as: Zhang, Qiang Z<qiang.z.zhang@intel.com> nano)
* name is sometimes omitted (such as: bitstream-vera-fonts nicolas.mailhot at laposte.net)
* <email> is sometimes omitted (such as: binutils Jim Kingdon)
This wide variation in formats makes automation tasks harder than they should be. Please use the correct format.

=== External References ===

Each external reference (bug numbers etc) should be of the form:
"(" + external reference code + bug number +")"

Currently defined:
* MeeGo Bugs : BMC#
* MeeGo Features: FEA#
* Common Vulnerability / Exposure : CVE
* BOO: A few references to BOO (as in BOO#9145) have been entered into BMC reports and MeeGo build system "submit" requests. BOO refers to an access controlled product oriented bugzilla database. References to BOO in BMC are inappropriate because of the access control to BOO. Patch submittals justified by a reference to a BOO report should be rejected and replaced with a reference to a BMC report.

==== Bug Numbers in the change log ====

During maintenance of a distribution, every change has to be marked with the correct bug number. Normally this has to be an number from https://bugzilla.meego.com/. Add an entry with bugzilla number and a short description of the bug-summary. For example:
- Removed invalid desktop Category "Application" (BMC#4654).
- Symlink icon to pixmaps dir (BMC#2108)
- Added gnome-ui-properties to control-center (BMC#1960).

New packages related to new features will refer to the corresponding bug number in bugzilla, preceded with an FEA. For example:
- Adding Qt Contacts support FEA#8011

==== CVE numbers in change log ====

As with bug numbers: Add a short description (normally the CVE summary should be enough), the Bugzilla and the CVE number to the changelog entry. Examples:
- Add gdk-pixbuf-226710.patch (BMC#226710), and (CVE-2007-0010).
- More XPM fixes: (CVE-2005-2975) xpm too many colors DoS (BMC#129642)
- fix ~/.dmrc symlink attack (BMC#180704), (CVE-2006-2449)

=== Spec File changes ===
Be as precise as possible! This is especially important if you remove something from the spec file.

* Removing original source code must be declared in spec file with a comment ("useful for FreeBSD only" for example) - not necessary to repeat the comment in specfile.
* Extra commands (for example during %install) can be illustrated with a short comment in spec file
* Adding/Removing packages from Requires/Provides must be described in the changelog

=== Source Code changes ===

Document the most important changes but limit verbosity.

* look into the source changelog and pick up the most important changes for the distribution (changes for other operation systems are not important). What has changed in the new version, usually in the level of detail of a NEWS file, the change log files are usually too long. More than '''10-15 lines''' shouldn't be necessary to describe the most important changes.
* arrange the original changes behind the version update information. Example:
- Update to 1.3.2:
+ fixes memory leak in import function
+ new API command: unlock_client()
+ the following bugs are closed by this new upstream release:
++ ............ [MGN:332]
++ .............[MGN:337]
- split of devel package
* If upstream does not provide a meaningful change log, then only do best effort. Don't waste too much time over it.
* If the upstream tarball really has not changed except for the version number, just the version number in the change log would be fine. Same goes for packages just containing some graphics or theming (unless upstream already provides something that fits). If the upstream changes just consists of "updated translation" or "several bug fixes" even that can be sufficient for a changelog entry (unless these bug fixes contain something you find worth mentioning).

== Packaging Static Libraries ==
Packages including libraries should exclude static libs as far as possible (eg by configuring with ''--disable-static''). Static libraries should only be included in exceptional circumstances. Applications linking against libraries should as far as possible link against shared libraries not static versions.

Libtool archives, ''foo.la'' files, should not be included. Packages using libtool will install these by default even if you configure with ''--disable-static'', so they may need to be removed before packaging. Due to bugs in older versions of libtool or bugs in programs that use it, there are times when it is not always possible to remove *.la files without modifying the program. In most cases it is fairly easy to work with upstream to fix these issues. Note that if you are updating a library in a stable release (not devel) and the package already contains *.la files, removing the *.la files should be treated as an API/ABI change -- ie: Removing them changes the interface that the library gives to the rest of the world and should not be undertaken lightly.

=== Packaging Static Libraries ===
* In general, packagers are strongly encouraged not to ship static libs unless a compelling reason exists.

* We want to be able to track which packages are using static libraries (so we can find which packages need to be rebuilt if a security flaw in a static library is fixed, for instance). There are two scenarios in which static libraries are packaged:
# '''Static libraries and shared libraries.''' In this case, the static libraries must be placed in a ''*-static'' subpackage. Separating the static libraries from the other development files in ''*-devel'' allow us to track this usage by checking which packages <code>BuildRequire</code> the ''*-static'' package. The intent is that whenever possible, packages will move away from using these static libraries, to the shared libraries.
# '''Static libraries only.''' When a package only provides static libraries you can place all the static library files in the ''*-devel'' subpackage. When doing this you also must have a virtual Provide for the ''*-static'' package:
<pre>%package devel
Provides: foo-static = %{version}-%{release}</pre>

Packages which explicitly need to link against the static version must <code>BuildRequire: foo-static</code>, so that the usage can be tracked.

* If (and only if) a package has shared libraries which require static libraries to be functional, the static libraries can be included in the ''*-devel'' subpackage. The devel subpackage must have a virtual Provide for the ''*-static'' package, and packages dependent on it must <code>BuildRequire</code> the ''*-static'' package.

=== Staticly Linking Executables ===
* Static linkage is a special exception and should be decided on a case-by-case basis. The packager must provide rationale for linking statically, including precedences where available, to release engineering for approval.

[[Category:Packaging]]

In-vehicle

2011-07-22T17:24:13Z

Joel: /* Weekly Builds */

= 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: '''[http://meego.com/users/RudolfStreif 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:
*** Intel: '''[http://meego.com/users/jahoffmann Joel Hoffmann]'''
*** LG Electronics: '''[https://meego.com/users/hyungjin Hyungjin Jeon]'''
*** Nokia: '''[http://meego.com/users/alistair Alistair Adams]'''
*** Pelagicore: '''[http://meego.com/users/mikael Mikael Soderberg]'''
*** Visteon: '''[http://meego.com/users/PavelKonopelko Pavel Konopelko]'''

* Product Manager (cross-function across Working Group and Project Team)
** Unifies and prioritizes overall requirements set.
** Owns the roadmap.
** co-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 with the Lead Architects and Lead Designers on effort estimates and schedules.
** co-leads the Project Team together with the Product 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: '''[http://meego.com/users/joel Joel Clark (Intel)]'''

==== Working Group Meetings and Minutes ====
The Working Group meets regularly. Information on current and past meetings can be found on [[in-vehicle/working-group|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: '''[http://meego.com/users/tomcounihan 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: '''[http://meego.com/users/jeremiah 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.

== Shipping MeeGo IVI Products ==

* [http://news.softpedia.com/news/MeeGo-Powered-In-Vehicle-Information-System-Makes-Appearance-at-MWC-2011-184651.shtml Hawtai B11]
* [http://www.allaboutmeego.com/news/item/12918_Red_Flag_Software_announces_Me.php Geely EC8]
* iKarPC [http://files.icp-deutschland.de/produkte2/124273/web/icp/IKARPC-W08A-datasheet-20110222.pdf datasheet] and [http://www.contradata.it/cataloghi/IEI_2011_In_Vehicle_PC.pdf catalog page]

== MeeGo IVI Demos ==

* MeeGo IVI UI from ICS: [http://www.youtube.com/watch?v=ZWbfGzyLoh8 video] and [http://www.ics.com/services/qtquick info], including source code

== MeeGo IVI UI (HMI)==

MeeGo IVI includes a Sample UI. This UI is sample only because it has always been stolen from some other MeeGo device project and ported with little change to the IVI builds. Also the underlaying UI framework and the UI applications have changed in every version of MeeGo so far.

The MeeGo IVI 1.2.0 UI is primarily based on a collection of QML based applications designed for MeeGo Tablet. It has a IVI specific taskbar app launcher that adds support for scrollwheel and voice command imputs.

* [[In-vehicle/IVIHome_Guide | MeeGo IVI 1.2.0 IVI home screen / taskbar User Guide ]]

The MeeGo IVI Home screen / taskbar is tested with a Contour ShuttleExpress Scrollweel.

* [http://www.amazon.com/Contour-Design-00496-0-Shuttle-Xpress/dp/B0032Y0OH0/ref=sr_1_2?ie=UTF8&qid=1309555207&sr=8-2 Contour ShuttleXpress infromation ]

==== Other Scroll Wheels ====
Other scrollwheels that have been used by the MeeGo IVI community

* [[3Dconnexion|3Dconnexion SpaceNavigator ]]

== 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.

The roadmap pages are the central collaboration point on laying out the future of MeeGo IVI. Here architecture details, system diagrams, use cases, etc. are shared.

[[In-vehicle/Roadmap|View the Roadmap]]

Before any new feature is committed to the Roadmap, a feature request is created in http://bugs.meego.com. Current MeeGo IVI feature requests can be found [https://bugs.meego.com/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=MeeGo+IVI+Features&content= here]

[https://bugs.meego.com/enter_bug.cgi?product=MeeGo%20IVI%20Features 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 in the [[In-vehicle/Roadmap|IVI roadmap]].

== 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. [[Release Engineering/Release Versioning|MeeGo Release Versioning]] explains the build version numbering scheme. For example '''1.2.80.xx''' is a 1.3 Alpha build, '''1.2.90.xx''' is a 1.3 Beta build, '''1.2.99.x''' is a 1.3 Release Candidate.

* [http://repo.meego.com/MeeGo/builds/trunk/ MeeGo weekly build repositories]

The first MeeGo 1.2 release was named version 1.2.0 which allows an opportunity for some additional application and User Experience development to be released on MeeGo 1.2 core with future versions such as 1.2.1, and 1.2.2 etc. With this version naming 1.2.0.90 is the pre-cursor to MeeGo 1.2.1. Updates to MeeGo 1.2.0 will either be called 1.2.0 Update or perhaps 1.2.0.1. Each weekly build directory is named with a version number and date. IVI live .iso images are found under the ''images'' link in each weekly build directory. 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 under ''repos'' in the weekly build directory.

* [http://repo.meego.com/MeeGo/updates/ MeeGo update repositories ]

==Upcoming Releases==
===Meego 1.2.0 Update ===

;Update release dates
{| border="1"
! Update name
! Code Freeze
! Release
|-
|Update 1
|June 30
|July 15
|-
|Update 2
|August 11
|August 18
|-
|Update 3
|Sept 22
|Sept 29
|}

====Links====
When the first MeeGo 1.2.0 update is released July 7, 2011, the updated packages will show up in the following repository:
* [http://repo.meego.com/MeeGo/updates/1.2.0/repos/ MeeGo 1.2.0 Update Repositories]

* [https://bugs.meego.com/buglist.cgi?emailtype2=substring&field0-0-0=flagtypes.name&classification=MeeGo%20Platform&emailcc2=1&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&email2=ivi-bugs&version=1.2.0&type0-0-0=anywordssubstr&value0-0-0=meego_update_release_blocker%2B&known_name=ivibugs_1.2.0Update%2B MeeGo IVI 1.2.0 Update approved bugs ]

* [https://bugs.meego.com/buglist.cgi?emailtype2=substring&field0-0-0=flagtypes.name&classification=MeeGo%20Platform&emailcc2=1&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&email2=ivi-bugs&version=1.2.0&type0-0-0=anywordssubstr&value0-0-0=meego_update_release_blocker%3F&known_name=ivibugs_1.2.0Update%3F MeeGo IVI 1.2.0 Update proposed bugs ]

* [[ Quality/IVI 1.2 Update | IVI 1.2.0 Update bug fix status]]

===Meego 1.3===

;MeeGo 1.3 milestones
{| border="1"
! Milestone
! Date
|-
|New Package Planning complete ||June 30
|-
|Core Package integration ||July 26
|-
|IVI Package integration / version freeze ||August 12
|-
|1.3 branch and Release Candidate 1 ||October 4
|-
|1.3 final release ||October 27
|}

==Platforms==
===MeeGo IVI Platforms Supported in Releases===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! Releases
! Plan
! status
! price/availability
|-
|meego-ivi-ia32
|Congatec IVI Kit (Russellville)
|Intel Atom Z5xx Series and Intel System Controller Hub US15Wx (eMenlow)
|Timberdale
|GPIO, DMA, SPI, I2C, UART, USB, IDE, Audio, KS8842 GigE, EMGD, Video-in, SDHC, TSC2007, I2S, SDHC, ADV7180, BT, Radio
|1.0.1, 1.1, 1.2
|EOL
|No known driver issues
|unavailable 5/11
|-
|meego-ivi-ia32
|Crown Bay
|Intel Atom 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
|1.2
|1.3
|No known driver issues
|
|-
|meego-ivi-ia32
|Stephenville/Crossville
|Intel Atom E6xx Series for Embedded (Tunnel Creek)
|Oki Semiconductors ML7213 IVI IOH
|GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, EMGD, SD/SDIO/MMC, USB-OTG, TDM, sDVO
|1.2
|1.3
|[https://bugs.meego.com/buglist.cgi?short_desc=oki&classification=MeeGo%20Platform&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&version=1.2&version=1.3&short_desc_type=allwordssubstr&component=Kernel%20and%20drivers%20%28generic%29&product=MeeGo%20IVI CV-ML7213 bugs ]
|
|}

===MeeGo IVI Trunk Prototype Platforms===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! status
|-
|meego-ivi-ia32-conx
|Stephenville/Northville/Crossville
|Intel Atom 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, several issues open, visit [[IVI Images for ConneXt IOH]] for more information
|}

;ARM
:Jeremiah Foster and Jan-Simon Moeller are working on updates to enable automated weekly builds of MeeGo IVI images for the Beagleboard-XM.
:The suggested reference platform is the Beagleboard xM. The [[ARM/OMAP4_Panda|PandaBoard]] and [[ARM/Snowball|Snowball]] most likely will be supported in the future.
{| border="1"
! Image name
! Platform name
! chipset
! status
|-
| meego-ivi-armv7l
| Beagleboard xM
| OMAP 3
| Not yet smoke tested. No QA
|-
| meego-ivi-armv7l
| Tegra2
| ARM v7 rev 0
| Not yet smoke tested. No QA
|-
|}

===[http://sf2011.meego.com/sites/all/files/slides/meegocon2011developmentboardbofslides.pdf MeeGo IVI Development Boards]===

;IA32
{| border="1"
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! price/availability as of 5/11
! tested with MeeGo?
|-
|Intel Embedded Development Board 1-N450/1-D510
|N450 or D510
|Intel 82801HM
|SSD, WiFi, SATA, USB, SPI, GPIO, PCIe, UART, GigE, Audio, IEGD, DMA, I2C
|[http://edc.intel.com/Platforms/Atom-N450-D410-D510/Development-Board/#bd1-content=bd1-toggle~~visible-content $149 for registered users]
|[http://wiki.meego.com/Devices/Ideapad yes]
|}

;ARM

Per Stskeeps on meego-arm IRC on 6/2/2011, Nokia-provided N900 SGX530 drivers with hardfp extensions are known to work with SGX530 revisions 121 and 125. Which OMAP3 SoCs have revision 121 and 125 is not always straightforward to determine. dm8tbr reports problems with N900 hardfp drivers on Beagleboard xM. Stskeeps reports success with these drivers on Beagleboard C4. Tripzero reports success with hardfp drivers on old build of IGEPv2 that had the Cortex A8 processor.

{| border="1"
! Platform name
! Processor
! GPU; [[http://wiki.meego.com/ARM/hardfp hardfp?]]
! Memory
! Features
! price/availability as of 5/11
! tested with MeeGo?
|-
|[http://www.igloocommunity.org/ Snowball] (usable in end products)
|Cortex A-9 Dual-Core Nova A9500 1 GHz
|ARM Mali 400, [http://igloocommunity.org/news/ promised; no GPU support in 6/11 BSP]
|1 GB
|HDMI, WiFi b/g/n, Bluetooth, GPS, USB OTG, FSMC, HSI, Audio, MiPi CSI / Camera, LCD, MiPi DSI, UART, SPI, I2C, GPIO, SD/MMC, accelerometer, magnetometer, gyrometer, pressure sensor [[ARM/Snowball|(complete specs)]]
| [https://shop.strato.com/epages/61428605.sf/en_GB/?ObjectPath=/Shops/61428605/Products/905-00024-B11 160€]
| [[ARM/Snowball|yes]]
|-
|[http://www.igep.es/index.php?option=com_content&view=article&id=46&Itemid=55 IGEPv2]
|[http://www.igep.es/public_docs/IGEPv2/HW_User_Manuals/MAN-PR-IGEP.0020.HW_USER_MANUAL.pdf DM3730 1 GHz]
|Imagination Technologies SGX530, yes? (tested by IGES with both TI and Nokia drivers)
|512 MB
|GigE, WiFi b/g, Bluetooth, USB OTG, USB Host, DVI-D, audio, SPI, UART, LCD, serial; [http://shop.igep.es/index.php?main_page=product_info&cPath=1&products_id=49 expansion board] with GSM, VGA, video in, camera, '''CAN'''
| 116.0€ and up plus 152.0€ for expansion board
| yes, but with older Cortex A8 build
|-
|[http://www.variscite.com/products/item/35-var-am35customboard Variscite VAR-AM3517 CustomBoard]
|[http://www.variscite.com/images/stories/DataSheets/VAR-SOM-AM35_1_15.pdf Cortex A-8 Sitara 600 MHz]
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|DMA, QCIF, LCD, SDTV, S-Video, USB, USB OTG, I2C, McSPI, GPIO, MMC, JTAG, '''CAN'''
|$1150 plus shipping
| no
|-
|[http://www.origenboard.org Samsung Origen]
|Samsung Exynos 4210 Cortex A-9 1 GHz
|ARM Mali 400, [http://forums.arm.com/index.php?/topic/14236-mali-gpus-linux-device-drivers-r2p0-05rel0-source-code-released/ reuse Snowball drivers?]
|1 GB
|HMDI, SD, WiFi, Bluetooth, audio, LCD, JTAG, camera
|[http://www.insignal.co.kr "sub-$200", June 25]
|no
|-
|[http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=IMX53QSB i.MX53 Quick Start Board]
|Cortex A-8 1 GHz
|Freescale GPUv3, [http://imxcommunity.org/profiles/blogs/ubuntu-rebuilt-with-hardfp yes]
|1 GB
|LVDS, LCD, HDMI, SPDIF, I2C, SSI, SPI, SD/MMC, microSD, SATA, GigE, USB, USB OTG, JTAG, UART, accelerometer
|$149
|[http://www.youtube.com/watch?feature=player_embedded&v=osDlTdl5lAk yes, similar HW]
|-
|[http://pandaboard.org/ Pandaboard]
|Cortex A-9 Dual-Core OMAP 4430 1 GHz
|Imagination Technologies SGX540, [http://article.gmane.org/gmane.comp.embedded.pandaboard/1771/match=hardfp not yet]
|1 GB
|SD/MMC, UART, Camera connector, USB OTG, Audio, GiGE, LCD connector, HDMI, WiFi, Bluetooth, JTAG, SPI, GPIO, I2C, McBSP
|[http://pandaboard.org/content/buy $179]
|[[ARM/OMAP4_Panda|yes]]
|-
|[http://beagle.s3.amazonaws.com/design/xM-A/BB_xM_SRM_A2_01.pdf Beagleboard Xm]
|Cortex A-8 DM3730 1GHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|512 MB
|uSD, USB, USB OTG, UART, McBSP, JTAG, GiGE, Audio, DVI-D, Camera connector, McBSP, I2C, GPIO, MMC2/3, ADC, LCD connector
|[http://beagleboard.org/buy $149]
|[[ARM/Meego_on_Beagleboard_from_scratch|yes]]
|-
|[http://beagleboard.org/static/BBSRM_latest.pdf Beagleboard C4]
|Cortex A-8 OMAP3530 720 MHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|I2C, I2S, SPI, MMC, USB, UART, USB OTG, S-Video, Audio, LCD, JTAG, GiGE
|[http://beagleboard.org/buy $125]
|[[ARM/Meego_IVI_on_Beagle|yes]]
|}

=== IVI Ports to Consumer Devices ===

* ia32 Atom processors

* ARM v7 processors
** [[ARM/TEGRA2|Trimslice Tegra2]]
** [[MeeGo_IVI_on ExoPC|ExoPC]]

== Releases ==
* [[MeeGo IVI 1.2 | MeeGo IVI 1.2]]
* [http://meego.com/downloads/releases/1.1/meego-v1.1-in-vehicle-infotainment-ivi MeeGo IVI 1.1]
* [http://meego.com/downloads/releases/1.0/meego-v1.0-in-vehicle-infotainment-ivi MeeGo IVI 1.0]

== Resources ==
* IRC irc.freenode.org #meego-ivi
* Mailing list sign-up: http://lists.meego.com/listinfo/meego-ivi
* Mailing list archive: http://lists.meego.com/pipermail/meego-ivi/
* [[Presentations_about_meego-ivi#Presentations_and_Articles_about_MeeGo_IVI|Presentations and articles about meego-ivi]]
* [[In-vehicle/IVI for users and developers|IVI for users and developers]]
* [[IVITopic|Topics]]

[[Category:IVI]]

In-vehicle

2011-07-15T05:10:59Z

Joel: /* Meego 1.2.0 Update */

= 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: '''[http://meego.com/users/RudolfStreif 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:
*** Intel: '''[http://meego.com/users/jahoffmann Joel Hoffmann]'''
*** LG Electronics: '''[https://meego.com/users/hyungjin Hyungjin Jeon]'''
*** Nokia: '''[http://meego.com/users/alistair Alistair Adams]'''
*** Pelagicore: '''[http://meego.com/users/mikael Mikael Soderberg]'''
*** Visteon: '''[http://meego.com/users/PavelKonopelko Pavel Konopelko]'''

* Product Manager (cross-function across Working Group and Project Team)
** Unifies and prioritizes overall requirements set.
** Owns the roadmap.
** co-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 with the Lead Architects and Lead Designers on effort estimates and schedules.
** co-leads the Project Team together with the Product 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: '''[http://meego.com/users/joel Joel Clark (Intel)]'''

==== Working Group Meetings and Minutes ====
The Working Group meets regularly. Information on current and past meetings can be found on [[in-vehicle/working-group|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: '''[http://meego.com/users/tomcounihan 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: '''[http://meego.com/users/jeremiah 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.

== Shipping MeeGo IVI Products ==

* [http://news.softpedia.com/news/MeeGo-Powered-In-Vehicle-Information-System-Makes-Appearance-at-MWC-2011-184651.shtml Hawtai B11]
* [http://www.allaboutmeego.com/news/item/12918_Red_Flag_Software_announces_Me.php Geely EC8]
* iKarPC [http://files.icp-deutschland.de/produkte2/124273/web/icp/IKARPC-W08A-datasheet-20110222.pdf datasheet] and [http://www.contradata.it/cataloghi/IEI_2011_In_Vehicle_PC.pdf catalog page]

== MeeGo IVI Demos ==

* MeeGo IVI UI from ICS: [http://www.youtube.com/watch?v=ZWbfGzyLoh8 video] and [http://www.ics.com/services/qtquick info], including source code

== MeeGo IVI UI (HMI)==

MeeGo IVI includes a Sample UI. This UI is sample only because it has always been stolen from some other MeeGo device project and ported with little change to the IVI builds. Also the underlaying UI framework and the UI applications have changed in every version of MeeGo so far.

The MeeGo IVI 1.2.0 UI is primarily based on a collection of QML based applications designed for MeeGo Tablet. It has a IVI specific taskbar app launcher that adds support for scrollwheel and voice command imputs.

* [[In-vehicle/IVIHome_Guide | MeeGo IVI 1.2.0 IVI home screen / taskbar User Guide ]]

The MeeGo IVI Home screen / taskbar is tested with a Contour ShuttleExpress Scrollweel.

* [http://www.amazon.com/Contour-Design-00496-0-Shuttle-Xpress/dp/B0032Y0OH0/ref=sr_1_2?ie=UTF8&qid=1309555207&sr=8-2 Contour ShuttleXpress infromation ]

==== Other Scroll Wheels ====
Other scrollwheels that have been used by the MeeGo IVI community

* [[3Dconnexion|3Dconnexion SpaceNavigator ]]

== 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.

The roadmap pages are the central collaboration point on laying out the future of MeeGo IVI. Here architecture details, system diagrams, use cases, etc. are shared.

[[In-vehicle/Roadmap|View the Roadmap]]

Before any new feature is committed to the Roadmap, a feature request is created in http://bugs.meego.com. Current MeeGo IVI feature requests can be found [https://bugs.meego.com/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=MeeGo+IVI+Features&content= here]

[https://bugs.meego.com/enter_bug.cgi?product=MeeGo%20IVI%20Features 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 in the [[In-vehicle/Roadmap|IVI roadmap]].

== 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. [[Release Engineering/Release Versioning|MeeGo Release Versioning]] explains the build version numbering scheme. For example '''1.3.80.xx''' is a 1.3 Alpha build, '''1.3.90.xx''' is a 1.3 Beta build, '''1.3.99.x''' is a 1.3 Release Candidate.

* [http://repo.meego.com/MeeGo/builds/trunk/ MeeGo weekly build repositories]

The first MeeGo 1.2 release was named version 1.2.0 which allows an opportunity for some additional application and User Experience development to be released on MeeGo 1.2 core with future versions such as 1.2.1, and 1.2.2 etc. With this version naming 1.2.0.90 is the pre-cursor to MeeGo 1.2.1. Updates to MeeGo 1.2.0 will either be called 1.2.0 Update or perhaps 1.2.0.1. Each weekly build directory is named with a version number and date. IVI live .iso images are found under the ''images'' link in each weekly build directory. 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 under ''repos'' in the weekly build directory.

* [http://repo.meego.com/MeeGo/updates/ MeeGo update repositories ]

==Upcoming Releases==
===Meego 1.2.0 Update ===

;Update release dates
{| border="1"
! Update name
! Code Freeze
! Release
|-
|Update 1
|June 30
|July 15
|-
|Update 2
|August 11
|August 18
|-
|Update 3
|Sept 22
|Sept 29
|}

====Links====
When the first MeeGo 1.2.0 update is released July 7, 2011, the updated packages will show up in the following repository:
* [http://repo.meego.com/MeeGo/updates/1.2.0/repos/ MeeGo 1.2.0 Update Repositories]

* [https://bugs.meego.com/buglist.cgi?emailtype2=substring&field0-0-0=flagtypes.name&classification=MeeGo%20Platform&emailcc2=1&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&email2=ivi-bugs&version=1.2.0&type0-0-0=anywordssubstr&value0-0-0=meego_update_release_blocker%2B&known_name=ivibugs_1.2.0Update%2B MeeGo IVI 1.2.0 Update approved bugs ]

* [https://bugs.meego.com/buglist.cgi?emailtype2=substring&field0-0-0=flagtypes.name&classification=MeeGo%20Platform&emailcc2=1&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&email2=ivi-bugs&version=1.2.0&type0-0-0=anywordssubstr&value0-0-0=meego_update_release_blocker%3F&known_name=ivibugs_1.2.0Update%3F MeeGo IVI 1.2.0 Update proposed bugs ]

* [[ Quality/IVI 1.2 Update | IVI 1.2.0 Update bug fix status]]

===Meego 1.3===

;MeeGo 1.3 milestones
{| border="1"
! Milestone
! Date
|-
|New Package Planning complete ||June 30
|-
|Core Package integration ||July 26
|-
|IVI Package integration / version freeze ||August 12
|-
|1.3 branch and Release Candidate 1 ||October 4
|-
|1.3 final release ||October 27
|}

==Platforms==
===MeeGo IVI Platforms Supported in Releases===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! Releases
! Plan
! status
! price/availability
|-
|meego-ivi-ia32
|Congatec IVI Kit (Russellville)
|Intel Atom Z5xx Series and Intel System Controller Hub US15Wx (eMenlow)
|Timberdale
|GPIO, DMA, SPI, I2C, UART, USB, IDE, Audio, KS8842 GigE, EMGD, Video-in, SDHC, TSC2007, I2S, SDHC, ADV7180, BT, Radio
|1.0.1, 1.1, 1.2
|EOL
|No known driver issues
|unavailable 5/11
|-
|meego-ivi-ia32
|Crown Bay
|Intel Atom 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
|1.2
|1.3
|No known driver issues
|
|-
|meego-ivi-ia32
|Stephenville/Crossville
|Intel Atom E6xx Series for Embedded (Tunnel Creek)
|Oki Semiconductors ML7213 IVI IOH
|GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, EMGD, SD/SDIO/MMC, USB-OTG, TDM, sDVO
|1.2
|1.3
|[https://bugs.meego.com/buglist.cgi?short_desc=oki&classification=MeeGo%20Platform&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&version=1.2&version=1.3&short_desc_type=allwordssubstr&component=Kernel%20and%20drivers%20%28generic%29&product=MeeGo%20IVI CV-ML7213 bugs ]
|
|}

===MeeGo IVI Trunk Prototype Platforms===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! status
|-
|meego-ivi-ia32-conx
|Stephenville/Northville/Crossville
|Intel Atom 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, several issues open, visit [[IVI Images for ConneXt IOH]] for more information
|}

;ARM
:Jeremiah Foster and Jan-Simon Moeller are working on updates to enable automated weekly builds of MeeGo IVI images for the Beagleboard-XM.
:The suggested reference platform is the Beagleboard xM. The [[ARM/OMAP4_Panda|PandaBoard]] and [[ARM/Snowball|Snowball]] most likely will be supported in the future.
{| border="1"
! Image name
! Platform name
! chipset
! status
|-
| meego-ivi-armv7l
| Beagleboard xM
| OMAP 3
| Not yet smoke tested. No QA
|-
| meego-ivi-armv7l
| Tegra2
| ARM v7 rev 0
| Not yet smoke tested. No QA
|-
|}

===[http://sf2011.meego.com/sites/all/files/slides/meegocon2011developmentboardbofslides.pdf MeeGo IVI Development Boards]===

;IA32
{| border="1"
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! price/availability as of 5/11
! tested with MeeGo?
|-
|Intel Embedded Development Board 1-N450/1-D510
|N450 or D510
|Intel 82801HM
|SSD, WiFi, SATA, USB, SPI, GPIO, PCIe, UART, GigE, Audio, IEGD, DMA, I2C
|[http://edc.intel.com/Platforms/Atom-N450-D410-D510/Development-Board/#bd1-content=bd1-toggle~~visible-content $149 for registered users]
|[http://wiki.meego.com/Devices/Ideapad yes]
|}

;ARM

Per Stskeeps on meego-arm IRC on 6/2/2011, Nokia-provided N900 SGX530 drivers with hardfp extensions are known to work with SGX530 revisions 121 and 125. Which OMAP3 SoCs have revision 121 and 125 is not always straightforward to determine. dm8tbr reports problems with N900 hardfp drivers on Beagleboard xM. Stskeeps reports success with these drivers on Beagleboard C4. Tripzero reports success with hardfp drivers on old build of IGEPv2 that had the Cortex A8 processor.

{| border="1"
! Platform name
! Processor
! GPU; [[http://wiki.meego.com/ARM/hardfp hardfp?]]
! Memory
! Features
! price/availability as of 5/11
! tested with MeeGo?
|-
|[http://www.igloocommunity.org/ Snowball] (usable in end products)
|Cortex A-9 Dual-Core Nova A9500 1 GHz
|ARM Mali 400, [http://igloocommunity.org/news/ promised; no GPU support in 6/11 BSP]
|1 GB
|HDMI, WiFi b/g/n, Bluetooth, GPS, USB OTG, FSMC, HSI, Audio, MiPi CSI / Camera, LCD, MiPi DSI, UART, SPI, I2C, GPIO, SD/MMC, accelerometer, magnetometer, gyrometer, pressure sensor [[ARM/Snowball|(complete specs)]]
| [https://shop.strato.com/epages/61428605.sf/en_GB/?ObjectPath=/Shops/61428605/Products/905-00024-B11 160€]
| [[ARM/Snowball|yes]]
|-
|[http://www.igep.es/index.php?option=com_content&view=article&id=46&Itemid=55 IGEPv2]
|[http://www.igep.es/public_docs/IGEPv2/HW_User_Manuals/MAN-PR-IGEP.0020.HW_USER_MANUAL.pdf DM3730 1 GHz]
|Imagination Technologies SGX530, yes? (tested by IGES with both TI and Nokia drivers)
|512 MB
|GigE, WiFi b/g, Bluetooth, USB OTG, USB Host, DVI-D, audio, SPI, UART, LCD, serial; [http://shop.igep.es/index.php?main_page=product_info&cPath=1&products_id=49 expansion board] with GSM, VGA, video in, camera, '''CAN'''
| 116.0€ and up plus 152.0€ for expansion board
| yes, but with older Cortex A8 build
|-
|[http://www.variscite.com/products/item/35-var-am35customboard Variscite VAR-AM3517 CustomBoard]
|[http://www.variscite.com/images/stories/DataSheets/VAR-SOM-AM35_1_15.pdf Cortex A-8 Sitara 600 MHz]
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|DMA, QCIF, LCD, SDTV, S-Video, USB, USB OTG, I2C, McSPI, GPIO, MMC, JTAG, '''CAN'''
|$1150 plus shipping
| no
|-
|[http://www.origenboard.org Samsung Origen]
|Samsung Exynos 4210 Cortex A-9 1 GHz
|ARM Mali 400, [http://forums.arm.com/index.php?/topic/14236-mali-gpus-linux-device-drivers-r2p0-05rel0-source-code-released/ reuse Snowball drivers?]
|1 GB
|HMDI, SD, WiFi, Bluetooth, audio, LCD, JTAG, camera
|[http://www.insignal.co.kr "sub-$200", June 25]
|no
|-
|[http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=IMX53QSB i.MX53 Quick Start Board]
|Cortex A-8 1 GHz
|Freescale GPUv3, [http://imxcommunity.org/profiles/blogs/ubuntu-rebuilt-with-hardfp yes]
|1 GB
|LVDS, LCD, HDMI, SPDIF, I2C, SSI, SPI, SD/MMC, microSD, SATA, GigE, USB, USB OTG, JTAG, UART, accelerometer
|$149
|[http://www.youtube.com/watch?feature=player_embedded&v=osDlTdl5lAk yes, similar HW]
|-
|[http://pandaboard.org/ Pandaboard]
|Cortex A-9 Dual-Core OMAP 4430 1 GHz
|Imagination Technologies SGX540, [http://article.gmane.org/gmane.comp.embedded.pandaboard/1771/match=hardfp not yet]
|1 GB
|SD/MMC, UART, Camera connector, USB OTG, Audio, GiGE, LCD connector, HDMI, WiFi, Bluetooth, JTAG, SPI, GPIO, I2C, McBSP
|[http://pandaboard.org/content/buy $179]
|[[ARM/OMAP4_Panda|yes]]
|-
|[http://beagle.s3.amazonaws.com/design/xM-A/BB_xM_SRM_A2_01.pdf Beagleboard Xm]
|Cortex A-8 DM3730 1GHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|512 MB
|uSD, USB, USB OTG, UART, McBSP, JTAG, GiGE, Audio, DVI-D, Camera connector, McBSP, I2C, GPIO, MMC2/3, ADC, LCD connector
|[http://beagleboard.org/buy $149]
|[[ARM/Meego_on_Beagleboard_from_scratch|yes]]
|-
|[http://beagleboard.org/static/BBSRM_latest.pdf Beagleboard C4]
|Cortex A-8 OMAP3530 720 MHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|I2C, I2S, SPI, MMC, USB, UART, USB OTG, S-Video, Audio, LCD, JTAG, GiGE
|[http://beagleboard.org/buy $125]
|[[ARM/Meego_IVI_on_Beagle|yes]]
|}

== Releases ==
* [[MeeGo IVI 1.2 | MeeGo IVI 1.2]]
* [http://meego.com/downloads/releases/1.1/meego-v1.1-in-vehicle-infotainment-ivi MeeGo IVI 1.1]
* [http://meego.com/downloads/releases/1.0/meego-v1.0-in-vehicle-infotainment-ivi MeeGo IVI 1.0]

== Resources ==
* IRC irc.freenode.org #meego-ivi
* Mailing list sign-up: http://lists.meego.com/listinfo/meego-ivi
* Mailing list archive: http://lists.meego.com/pipermail/meego-ivi/
* [[Presentations_about_meego-ivi#Presentations_and_Articles_about_MeeGo_IVI|Presentations and articles about meego-ivi]]
* [[In-vehicle/IVI for users and developers|IVI for users and developers]]
* [[IVITopic|Topics]]

[[Category:IVI]]

In-vehicle

2011-07-06T06:15:38Z

Joel: /* Weekly Builds */

= 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: '''[http://meego.com/users/RudolfStreif 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:
*** Intel: '''[http://meego.com/users/jahoffmann Joel Hoffmann]'''
*** LG Electronics: '''[https://meego.com/users/hyungjin Hyungjin Jeon]'''
*** Nokia: '''[http://meego.com/users/alistair Alistair Adams]'''
*** Pelagicore: '''[http://meego.com/users/mikael Mikael Soderberg]'''
*** Visteon: '''[http://meego.com/users/PavelKonopelko Pavel Konopelko]'''

* Product Manager (cross-function across Working Group and Project Team)
** Unifies and prioritizes overall requirements set.
** Owns the roadmap.
** co-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 with the Lead Architects and Lead Designers on effort estimates and schedules.
** co-leads the Project Team together with the Product 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: '''[http://meego.com/users/joel Joel Clark (Intel)]'''

==== Working Group Meetings and Minutes ====
The Working Group meets regularly. Information on current and past meetings can be found on [[in-vehicle/working-group|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: '''[http://meego.com/users/tomcounihan 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: '''[http://meego.com/users/jeremiah 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.

== Shipping MeeGo IVI Products ==

* [http://news.softpedia.com/news/MeeGo-Powered-In-Vehicle-Information-System-Makes-Appearance-at-MWC-2011-184651.shtml Hawtai B11]
* [http://www.allaboutmeego.com/news/item/12918_Red_Flag_Software_announces_Me.php Geely EC8]
* iKarPC [http://files.icp-deutschland.de/produkte2/124273/web/icp/IKARPC-W08A-datasheet-20110222.pdf datasheet] and [http://www.contradata.it/cataloghi/IEI_2011_In_Vehicle_PC.pdf catalog page]

== MeeGo IVI Demos ==

* MeeGo IVI UI from ICS: [http://www.youtube.com/watch?v=ZWbfGzyLoh8 video] and [http://www.ics.com/services/qtquick info], including source code

== MeeGo IVI UI (HMI)==

MeeGo IVI includes a Sample UI. This UI is sample only because it has always been stolen from some other MeeGo device project and ported with little change to the IVI builds. Also the underlaying UI framework and the UI applications have changed in every version of MeeGo so far.

The MeeGo IVI 1.2.0 UI is primarily based on a collection of QML based applications designed for MeeGo Tablet. It has a IVI specific taskbar app launcher that adds support for scrollwheel and voice command imputs.

* [[In-vehicle/IVIHome_Guide | MeeGo IVI 1.2.0 IVI home screen / taskbar User Guide ]]

The MeeGo IVI Home screen / taskbar is tested with a Contour ShuttleExpress Scrollweel.

* [http://www.amazon.com/Contour-Design-00496-0-Shuttle-Xpress/dp/B0032Y0OH0/ref=sr_1_2?ie=UTF8&qid=1309555207&sr=8-2 Contour ShuttleXpress infromation ]

==== Other Scroll Wheels ====
Other scrollwheels that have been used by the MeeGo IVI community

* [[3Dconnexion|3Dconnexion SpaceNavigator ]]

== 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.

The roadmap pages are the central collaboration point on laying out the future of MeeGo IVI. Here architecture details, system diagrams, use cases, etc. are shared.

[[In-vehicle/Roadmap|View the Roadmap]]

Before any new feature is committed to the Roadmap, a feature request is created in http://bugs.meego.com. Current MeeGo IVI feature requests can be found [https://bugs.meego.com/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=MeeGo+IVI+Features&content= here]

[https://bugs.meego.com/enter_bug.cgi?product=MeeGo%20IVI%20Features 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 in the [[In-vehicle/Roadmap|IVI roadmap]].

== 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. [[Release Engineering/Release Versioning|MeeGo Release Versioning]] explains the build version numbering scheme. For example '''1.3.80.xx''' is a 1.3 Alpha build, '''1.3.90.xx''' is a 1.3 Beta build, '''1.3.99.x''' is a 1.3 Release Candidate.

* [http://repo.meego.com/MeeGo/builds/trunk/ MeeGo weekly build repositories]

The first MeeGo 1.2 release was named version 1.2.0 which allows an opportunity for some additional application and User Experience development to be released on MeeGo 1.2 core with future versions such as 1.2.1, and 1.2.2 etc. With this version naming 1.2.0.90 is the pre-cursor to MeeGo 1.2.1. Updates to MeeGo 1.2.0 will either be called 1.2.0 Update or perhaps 1.2.0.1. Each weekly build directory is named with a version number and date. IVI live .iso images are found under the ''images'' link in each weekly build directory. 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 under ''repos'' in the weekly build directory.

* [http://repo.meego.com/MeeGo/updates/ MeeGo update repositories ]

==Upcoming Releases==
===Meego 1.2.0 Update ===

;Update release dates
{| border="1"
! Update name
! Code Freeze
! Release
|-
|Update 1
|June 30
|July 7
|-
|Update 2
|August 11
|August 18
|-
|Update 3
|Sept 22
|Sept 29
|}

====Links====
When the first MeeGo 1.2.0 update is released July 7, 2011, the updated packages will show up in the following repository:
* [http://repo.meego.com/MeeGo/updates/1.2.0/repos/ MeeGo 1.2.0 Update Repositories]

* [https://bugs.meego.com/buglist.cgi?emailtype2=substring&field0-0-0=flagtypes.name&classification=MeeGo%20Platform&emailcc2=1&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&email2=ivi-bugs&version=1.2.0&type0-0-0=anywordssubstr&value0-0-0=meego_update_release_blocker%2B&known_name=ivibugs_1.2.0Update%2B MeeGo IVI 1.2.0 Update approved bugs ]

* [https://bugs.meego.com/buglist.cgi?emailtype2=substring&field0-0-0=flagtypes.name&classification=MeeGo%20Platform&emailcc2=1&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&email2=ivi-bugs&version=1.2.0&type0-0-0=anywordssubstr&value0-0-0=meego_update_release_blocker%3F&known_name=ivibugs_1.2.0Update%3F MeeGo IVI 1.2.0 Update proposed bugs ]

* [[ Quality/IVI 1.2 Update | IVI 1.2.0 Update bug fix status]]

===Meego 1.3===

;MeeGo 1.3 milestones
{| border="1"
! Milestone
! Date
|-
|New Package Planning complete ||June 30
|-
|Core Package integration ||July 26
|-
|IVI Package integration / version freeze ||August 12
|-
|1.3 branch and Release Candidate 1 ||October 4
|-
|1.3 final release ||October 27
|}

==Platforms==
===MeeGo IVI Platforms Supported in Releases===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! Releases
! Plan
! status
! price/availability
|-
|meego-ivi-ia32
|Congatec IVI Kit (Russellville)
|Intel Atom Z5xx Series and Intel System Controller Hub US15Wx (eMenlow)
|Timberdale
|GPIO, DMA, SPI, I2C, UART, USB, IDE, Audio, KS8842 GigE, EMGD, Video-in, SDHC, TSC2007, I2S, SDHC, ADV7180, BT, Radio
|1.0.1, 1.1, 1.2
|EOL
|No known driver issues
|unavailable 5/11
|-
|meego-ivi-ia32
|Crown Bay
|Intel Atom 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
|1.2
|1.3
|No known driver issues
|
|-
|meego-ivi-ia32
|Stephenville/Crossville
|Intel Atom E6xx Series for Embedded (Tunnel Creek)
|Oki Semiconductors ML7213 IVI IOH
|GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, EMGD, SD/SDIO/MMC, USB-OTG, TDM, sDVO
|1.2
|1.3
|[https://bugs.meego.com/buglist.cgi?short_desc=oki&classification=MeeGo%20Platform&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&version=1.2&version=1.3&short_desc_type=allwordssubstr&component=Kernel%20and%20drivers%20%28generic%29&product=MeeGo%20IVI CV-ML7213 bugs ]
|
|}

===MeeGo IVI Trunk Prototype Platforms===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! status
|-
|meego-ivi-ia32-conx
|Stephenville/Northville/Crossville
|Intel Atom 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, several issues open, visit [[IVI Images for ConneXt IOH]] for more information
|}

;ARM
:Jeremiah Foster and Jan-Simon Moeller are working on updates to enable automated weekly builds of MeeGo IVI images for the Beagleboard-XM.
:The suggested reference platform is the Beagleboard xM. The [[ARM/OMAP4_Panda|PandaBoard]] and [[ARM/Snowball|Snowball]] most likely will be supported in the future.
{| border="1"
! Image name
! Platform name
! chipset
! status
|-
| meego-ivi-armv7l
| Beagleboard xM
| OMAP 3
| Not yet smoke tested. No QA
|-
| meego-ivi-armv7l
| Tegra2
| ARM v7 rev 0
| Not yet smoke tested. No QA
|-
|}

===[http://sf2011.meego.com/sites/all/files/slides/meegocon2011developmentboardbofslides.pdf MeeGo IVI Development Boards]===

;IA32
{| border="1"
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! price/availability as of 5/11
! tested with MeeGo?
|-
|Intel Embedded Development Board 1-N450/1-D510
|N450 or D510
|Intel 82801HM
|SSD, WiFi, SATA, USB, SPI, GPIO, PCIe, UART, GigE, Audio, IEGD, DMA, I2C
|[http://edc.intel.com/Platforms/Atom-N450-D410-D510/Development-Board/#bd1-content=bd1-toggle~~visible-content $149 for registered users]
|[http://wiki.meego.com/Devices/Ideapad yes]
|}

;ARM

Per Stskeeps on meego-arm IRC on 6/2/2011, Nokia-provided N900 SGX530 drivers with hardfp extensions are known to work with SGX530 revisions 121 and 125. Which OMAP3 SoCs have revision 121 and 125 is not always straightforward to determine. dm8tbr reports problems with N900 hardfp drivers on Beagleboard xM. Stskeeps reports success with these drivers on Beagleboard C4. Tripzero reports success with hardfp drivers on old build of IGEPv2 that had the Cortex A8 processor.

{| border="1"
! Platform name
! Processor
! GPU; [[http://wiki.meego.com/ARM/hardfp hardfp?]]
! Memory
! Features
! price/availability as of 5/11
! tested with MeeGo?
|-
|[http://www.igloocommunity.org/ Snowball] (usable in end products)
|Cortex A-9 Dual-Core Nova A9500 1 GHz
|ARM Mali 400, [http://igloocommunity.org/news/ promised; no GPU support in 6/11 BSP]
|1 GB
|HDMI, WiFi b/g/n, Bluetooth, GPS, USB OTG, FSMC, HSI, Audio, MiPi CSI / Camera, LCD, MiPi DSI, UART, SPI, I2C, GPIO, SD/MMC, accelerometer, magnetometer, gyrometer, pressure sensor [[ARM/Snowball|(complete specs)]]
| [https://shop.strato.com/epages/61428605.sf/en_GB/?ObjectPath=/Shops/61428605/Products/905-00024-B11 160€]
| [[ARM/Snowball|yes]]
|-
|[http://www.igep.es/index.php?option=com_content&view=article&id=46&Itemid=55 IGEPv2]
|[http://www.igep.es/public_docs/IGEPv2/HW_User_Manuals/MAN-PR-IGEP.0020.HW_USER_MANUAL.pdf DM3730 1 GHz]
|Imagination Technologies SGX530, yes? (tested by IGES with both TI and Nokia drivers)
|512 MB
|GigE, WiFi b/g, Bluetooth, USB OTG, USB Host, DVI-D, audio, SPI, UART, LCD, serial; [http://shop.igep.es/index.php?main_page=product_info&cPath=1&products_id=49 expansion board] with GSM, VGA, video in, camera, '''CAN'''
| 116.0€ and up plus 152.0€ for expansion board
| yes, but with older Cortex A8 build
|-
|[http://www.variscite.com/products/item/35-var-am35customboard Variscite VAR-AM3517 CustomBoard]
|[http://www.variscite.com/images/stories/DataSheets/VAR-SOM-AM35_1_15.pdf Cortex A-8 Sitara 600 MHz]
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|DMA, QCIF, LCD, SDTV, S-Video, USB, USB OTG, I2C, McSPI, GPIO, MMC, JTAG, '''CAN'''
|$1150 plus shipping
| no
|-
|[http://www.origenboard.org Samsung Origen]
|Samsung Exynos 4210 Cortex A-9 1 GHz
|ARM Mali 400, [http://forums.arm.com/index.php?/topic/14236-mali-gpus-linux-device-drivers-r2p0-05rel0-source-code-released/ reuse Snowball drivers?]
|1 GB
|HMDI, SD, WiFi, Bluetooth, audio, LCD, JTAG, camera
|[http://www.insignal.co.kr "sub-$200", June 25]
|no
|-
|[http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=IMX53QSB i.MX53 Quick Start Board]
|Cortex A-8 1 GHz
|Freescale GPUv3, [http://imxcommunity.org/profiles/blogs/ubuntu-rebuilt-with-hardfp yes]
|1 GB
|LVDS, LCD, HDMI, SPDIF, I2C, SSI, SPI, SD/MMC, microSD, SATA, GigE, USB, USB OTG, JTAG, UART, accelerometer
|$149
|[http://www.youtube.com/watch?feature=player_embedded&v=osDlTdl5lAk yes, similar HW]
|-
|[http://pandaboard.org/ Pandaboard]
|Cortex A-9 Dual-Core OMAP 4430 1 GHz
|Imagination Technologies SGX540, [http://article.gmane.org/gmane.comp.embedded.pandaboard/1771/match=hardfp not yet]
|1 GB
|SD/MMC, UART, Camera connector, USB OTG, Audio, GiGE, LCD connector, HDMI, WiFi, Bluetooth, JTAG, SPI, GPIO, I2C, McBSP
|[http://pandaboard.org/content/buy $179]
|[[ARM/OMAP4_Panda|yes]]
|-
|[http://beagle.s3.amazonaws.com/design/xM-A/BB_xM_SRM_A2_01.pdf Beagleboard Xm]
|Cortex A-8 DM3730 1GHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|512 MB
|uSD, USB, USB OTG, UART, McBSP, JTAG, GiGE, Audio, DVI-D, Camera connector, McBSP, I2C, GPIO, MMC2/3, ADC, LCD connector
|[http://beagleboard.org/buy $149]
|[[ARM/Meego_on_Beagleboard_from_scratch|yes]]
|-
|[http://beagleboard.org/static/BBSRM_latest.pdf Beagleboard C4]
|Cortex A-8 OMAP3530 720 MHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|I2C, I2S, SPI, MMC, USB, UART, USB OTG, S-Video, Audio, LCD, JTAG, GiGE
|[http://beagleboard.org/buy $125]
|[[ARM/Meego_IVI_on_Beagle|yes]]
|}

== Releases ==
* [[MeeGo IVI 1.2 | MeeGo IVI 1.2]]
* [http://meego.com/downloads/releases/1.1/meego-v1.1-in-vehicle-infotainment-ivi MeeGo IVI 1.1]
* [http://meego.com/downloads/releases/1.0/meego-v1.0-in-vehicle-infotainment-ivi MeeGo IVI 1.0]

== Resources ==
* IRC irc.freenode.org #meego-ivi
* Mailing list sign-up: http://lists.meego.com/listinfo/meego-ivi
* Mailing list archive: http://lists.meego.com/pipermail/meego-ivi/
* [[Presentations_about_meego-ivi#Presentations_and_Articles_about_MeeGo_IVI|Presentations and articles about meego-ivi]]
* [[In-vehicle/IVI for users and developers|IVI for users and developers]]
* [[IVITopic|Topics]]

[[Category:IVI]]

In-vehicle

2011-07-06T06:14:16Z

Joel: /* Weekly Builds */

= 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: '''[http://meego.com/users/RudolfStreif 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:
*** Intel: '''[http://meego.com/users/jahoffmann Joel Hoffmann]'''
*** LG Electronics: '''[https://meego.com/users/hyungjin Hyungjin Jeon]'''
*** Nokia: '''[http://meego.com/users/alistair Alistair Adams]'''
*** Pelagicore: '''[http://meego.com/users/mikael Mikael Soderberg]'''
*** Visteon: '''[http://meego.com/users/PavelKonopelko Pavel Konopelko]'''

* Product Manager (cross-function across Working Group and Project Team)
** Unifies and prioritizes overall requirements set.
** Owns the roadmap.
** co-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 with the Lead Architects and Lead Designers on effort estimates and schedules.
** co-leads the Project Team together with the Product 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: '''[http://meego.com/users/joel Joel Clark (Intel)]'''

==== Working Group Meetings and Minutes ====
The Working Group meets regularly. Information on current and past meetings can be found on [[in-vehicle/working-group|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: '''[http://meego.com/users/tomcounihan 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: '''[http://meego.com/users/jeremiah 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.

== Shipping MeeGo IVI Products ==

* [http://news.softpedia.com/news/MeeGo-Powered-In-Vehicle-Information-System-Makes-Appearance-at-MWC-2011-184651.shtml Hawtai B11]
* [http://www.allaboutmeego.com/news/item/12918_Red_Flag_Software_announces_Me.php Geely EC8]
* iKarPC [http://files.icp-deutschland.de/produkte2/124273/web/icp/IKARPC-W08A-datasheet-20110222.pdf datasheet] and [http://www.contradata.it/cataloghi/IEI_2011_In_Vehicle_PC.pdf catalog page]

== MeeGo IVI Demos ==

* MeeGo IVI UI from ICS: [http://www.youtube.com/watch?v=ZWbfGzyLoh8 video] and [http://www.ics.com/services/qtquick info], including source code

== MeeGo IVI UI (HMI)==

MeeGo IVI includes a Sample UI. This UI is sample only because it has always been stolen from some other MeeGo device project and ported with little change to the IVI builds. Also the underlaying UI framework and the UI applications have changed in every version of MeeGo so far.

The MeeGo IVI 1.2.0 UI is primarily based on a collection of QML based applications designed for MeeGo Tablet. It has a IVI specific taskbar app launcher that adds support for scrollwheel and voice command imputs.

* [[In-vehicle/IVIHome_Guide | MeeGo IVI 1.2.0 IVI home screen / taskbar User Guide ]]

The MeeGo IVI Home screen / taskbar is tested with a Contour ShuttleExpress Scrollweel.

* [http://www.amazon.com/Contour-Design-00496-0-Shuttle-Xpress/dp/B0032Y0OH0/ref=sr_1_2?ie=UTF8&qid=1309555207&sr=8-2 Contour ShuttleXpress infromation ]

==== Other Scroll Wheels ====
Other scrollwheels that have been used by the MeeGo IVI community

* [[3Dconnexion|3Dconnexion SpaceNavigator ]]

== 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.

The roadmap pages are the central collaboration point on laying out the future of MeeGo IVI. Here architecture details, system diagrams, use cases, etc. are shared.

[[In-vehicle/Roadmap|View the Roadmap]]

Before any new feature is committed to the Roadmap, a feature request is created in http://bugs.meego.com. Current MeeGo IVI feature requests can be found [https://bugs.meego.com/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=MeeGo+IVI+Features&content= here]

[https://bugs.meego.com/enter_bug.cgi?product=MeeGo%20IVI%20Features 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 in the [[In-vehicle/Roadmap|IVI roadmap]].

== 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. [[Release Engineering/Release Versioning|MeeGo Release Versioning]] explains the build version numbering scheme. For example '''1.3.80.xx''' is a 1.3 Alpha build, '''1.3.90.xx''' is a 1.3 Beta build, '''1.3.99.x''' is a 1.3 Release Candidate.

* [http://repo.meego.com/MeeGo/builds/trunk/ MeeGo weekly build repositories]

The first MeeGo 1.2 release was named version 1.2.0 which allows an opportunity for some additional application and User Experience development to be released on MeeGo 1.2 core with future versions such as 1.2.1, and 1.2.2 etc. With this version naming 1.2.0.90 is the pre-cursor to MeeGo 1.2.1. Updates to MeeGo 1.2.0 will either be called 1.2.0 Update or perhaps 1.2.0.1. Each weekly build directory is named with a version number and date. IVI live .iso images are found under the ''images'' link in each weekly build directory. 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 under ''repos'' in the weekly build directory.

==Upcoming Releases==
===Meego 1.2.0 Update ===

;Update release dates
{| border="1"
! Update name
! Code Freeze
! Release
|-
|Update 1
|June 30
|July 7
|-
|Update 2
|August 11
|August 18
|-
|Update 3
|Sept 22
|Sept 29
|}

====Links====
When the first MeeGo 1.2.0 update is released July 7, 2011, the updated packages will show up in the following repository:
* [http://repo.meego.com/MeeGo/updates/1.2.0/repos/ MeeGo 1.2.0 Update Repositories]

* [https://bugs.meego.com/buglist.cgi?emailtype2=substring&field0-0-0=flagtypes.name&classification=MeeGo%20Platform&emailcc2=1&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&email2=ivi-bugs&version=1.2.0&type0-0-0=anywordssubstr&value0-0-0=meego_update_release_blocker%2B&known_name=ivibugs_1.2.0Update%2B MeeGo IVI 1.2.0 Update approved bugs ]

* [https://bugs.meego.com/buglist.cgi?emailtype2=substring&field0-0-0=flagtypes.name&classification=MeeGo%20Platform&emailcc2=1&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&email2=ivi-bugs&version=1.2.0&type0-0-0=anywordssubstr&value0-0-0=meego_update_release_blocker%3F&known_name=ivibugs_1.2.0Update%3F MeeGo IVI 1.2.0 Update proposed bugs ]

* [[ Quality/IVI 1.2 Update | IVI 1.2.0 Update bug fix status]]

===Meego 1.3===

;MeeGo 1.3 milestones
{| border="1"
! Milestone
! Date
|-
|New Package Planning complete ||June 30
|-
|Core Package integration ||July 26
|-
|IVI Package integration / version freeze ||August 12
|-
|1.3 branch and Release Candidate 1 ||October 4
|-
|1.3 final release ||October 27
|}

==Platforms==
===MeeGo IVI Platforms Supported in Releases===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! Releases
! Plan
! status
! price/availability
|-
|meego-ivi-ia32
|Congatec IVI Kit (Russellville)
|Intel Atom Z5xx Series and Intel System Controller Hub US15Wx (eMenlow)
|Timberdale
|GPIO, DMA, SPI, I2C, UART, USB, IDE, Audio, KS8842 GigE, EMGD, Video-in, SDHC, TSC2007, I2S, SDHC, ADV7180, BT, Radio
|1.0.1, 1.1, 1.2
|EOL
|No known driver issues
|unavailable 5/11
|-
|meego-ivi-ia32
|Crown Bay
|Intel Atom 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
|1.2
|1.3
|No known driver issues
|
|-
|meego-ivi-ia32
|Stephenville/Crossville
|Intel Atom E6xx Series for Embedded (Tunnel Creek)
|Oki Semiconductors ML7213 IVI IOH
|GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, EMGD, SD/SDIO/MMC, USB-OTG, TDM, sDVO
|1.2
|1.3
|[https://bugs.meego.com/buglist.cgi?short_desc=oki&classification=MeeGo%20Platform&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&version=1.2&version=1.3&short_desc_type=allwordssubstr&component=Kernel%20and%20drivers%20%28generic%29&product=MeeGo%20IVI CV-ML7213 bugs ]
|
|}

===MeeGo IVI Trunk Prototype Platforms===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! status
|-
|meego-ivi-ia32-conx
|Stephenville/Northville/Crossville
|Intel Atom 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, several issues open, visit [[IVI Images for ConneXt IOH]] for more information
|}

;ARM
:Jeremiah Foster and Jan-Simon Moeller are working on updates to enable automated weekly builds of MeeGo IVI images for the Beagleboard-XM.
:The suggested reference platform is the Beagleboard xM. The [[ARM/OMAP4_Panda|PandaBoard]] and [[ARM/Snowball|Snowball]] most likely will be supported in the future.
{| border="1"
! Image name
! Platform name
! chipset
! status
|-
| meego-ivi-armv7l
| Beagleboard xM
| OMAP 3
| Not yet smoke tested. No QA
|-
| meego-ivi-armv7l
| Tegra2
| ARM v7 rev 0
| Not yet smoke tested. No QA
|-
|}

===[http://sf2011.meego.com/sites/all/files/slides/meegocon2011developmentboardbofslides.pdf MeeGo IVI Development Boards]===

;IA32
{| border="1"
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! price/availability as of 5/11
! tested with MeeGo?
|-
|Intel Embedded Development Board 1-N450/1-D510
|N450 or D510
|Intel 82801HM
|SSD, WiFi, SATA, USB, SPI, GPIO, PCIe, UART, GigE, Audio, IEGD, DMA, I2C
|[http://edc.intel.com/Platforms/Atom-N450-D410-D510/Development-Board/#bd1-content=bd1-toggle~~visible-content $149 for registered users]
|[http://wiki.meego.com/Devices/Ideapad yes]
|}

;ARM

Per Stskeeps on meego-arm IRC on 6/2/2011, Nokia-provided N900 SGX530 drivers with hardfp extensions are known to work with SGX530 revisions 121 and 125. Which OMAP3 SoCs have revision 121 and 125 is not always straightforward to determine. dm8tbr reports problems with N900 hardfp drivers on Beagleboard xM. Stskeeps reports success with these drivers on Beagleboard C4. Tripzero reports success with hardfp drivers on old build of IGEPv2 that had the Cortex A8 processor.

{| border="1"
! Platform name
! Processor
! GPU; [[http://wiki.meego.com/ARM/hardfp hardfp?]]
! Memory
! Features
! price/availability as of 5/11
! tested with MeeGo?
|-
|[http://www.igloocommunity.org/ Snowball] (usable in end products)
|Cortex A-9 Dual-Core Nova A9500 1 GHz
|ARM Mali 400, [http://igloocommunity.org/news/ promised; no GPU support in 6/11 BSP]
|1 GB
|HDMI, WiFi b/g/n, Bluetooth, GPS, USB OTG, FSMC, HSI, Audio, MiPi CSI / Camera, LCD, MiPi DSI, UART, SPI, I2C, GPIO, SD/MMC, accelerometer, magnetometer, gyrometer, pressure sensor [[ARM/Snowball|(complete specs)]]
| [https://shop.strato.com/epages/61428605.sf/en_GB/?ObjectPath=/Shops/61428605/Products/905-00024-B11 160€]
| [[ARM/Snowball|yes]]
|-
|[http://www.igep.es/index.php?option=com_content&view=article&id=46&Itemid=55 IGEPv2]
|[http://www.igep.es/public_docs/IGEPv2/HW_User_Manuals/MAN-PR-IGEP.0020.HW_USER_MANUAL.pdf DM3730 1 GHz]
|Imagination Technologies SGX530, yes? (tested by IGES with both TI and Nokia drivers)
|512 MB
|GigE, WiFi b/g, Bluetooth, USB OTG, USB Host, DVI-D, audio, SPI, UART, LCD, serial; [http://shop.igep.es/index.php?main_page=product_info&cPath=1&products_id=49 expansion board] with GSM, VGA, video in, camera, '''CAN'''
| 116.0€ and up plus 152.0€ for expansion board
| yes, but with older Cortex A8 build
|-
|[http://www.variscite.com/products/item/35-var-am35customboard Variscite VAR-AM3517 CustomBoard]
|[http://www.variscite.com/images/stories/DataSheets/VAR-SOM-AM35_1_15.pdf Cortex A-8 Sitara 600 MHz]
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|DMA, QCIF, LCD, SDTV, S-Video, USB, USB OTG, I2C, McSPI, GPIO, MMC, JTAG, '''CAN'''
|$1150 plus shipping
| no
|-
|[http://www.origenboard.org Samsung Origen]
|Samsung Exynos 4210 Cortex A-9 1 GHz
|ARM Mali 400, [http://forums.arm.com/index.php?/topic/14236-mali-gpus-linux-device-drivers-r2p0-05rel0-source-code-released/ reuse Snowball drivers?]
|1 GB
|HMDI, SD, WiFi, Bluetooth, audio, LCD, JTAG, camera
|[http://www.insignal.co.kr "sub-$200", June 25]
|no
|-
|[http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=IMX53QSB i.MX53 Quick Start Board]
|Cortex A-8 1 GHz
|Freescale GPUv3, [http://imxcommunity.org/profiles/blogs/ubuntu-rebuilt-with-hardfp yes]
|1 GB
|LVDS, LCD, HDMI, SPDIF, I2C, SSI, SPI, SD/MMC, microSD, SATA, GigE, USB, USB OTG, JTAG, UART, accelerometer
|$149
|[http://www.youtube.com/watch?feature=player_embedded&v=osDlTdl5lAk yes, similar HW]
|-
|[http://pandaboard.org/ Pandaboard]
|Cortex A-9 Dual-Core OMAP 4430 1 GHz
|Imagination Technologies SGX540, [http://article.gmane.org/gmane.comp.embedded.pandaboard/1771/match=hardfp not yet]
|1 GB
|SD/MMC, UART, Camera connector, USB OTG, Audio, GiGE, LCD connector, HDMI, WiFi, Bluetooth, JTAG, SPI, GPIO, I2C, McBSP
|[http://pandaboard.org/content/buy $179]
|[[ARM/OMAP4_Panda|yes]]
|-
|[http://beagle.s3.amazonaws.com/design/xM-A/BB_xM_SRM_A2_01.pdf Beagleboard Xm]
|Cortex A-8 DM3730 1GHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|512 MB
|uSD, USB, USB OTG, UART, McBSP, JTAG, GiGE, Audio, DVI-D, Camera connector, McBSP, I2C, GPIO, MMC2/3, ADC, LCD connector
|[http://beagleboard.org/buy $149]
|[[ARM/Meego_on_Beagleboard_from_scratch|yes]]
|-
|[http://beagleboard.org/static/BBSRM_latest.pdf Beagleboard C4]
|Cortex A-8 OMAP3530 720 MHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|I2C, I2S, SPI, MMC, USB, UART, USB OTG, S-Video, Audio, LCD, JTAG, GiGE
|[http://beagleboard.org/buy $125]
|[[ARM/Meego_IVI_on_Beagle|yes]]
|}

== Releases ==
* [[MeeGo IVI 1.2 | MeeGo IVI 1.2]]
* [http://meego.com/downloads/releases/1.1/meego-v1.1-in-vehicle-infotainment-ivi MeeGo IVI 1.1]
* [http://meego.com/downloads/releases/1.0/meego-v1.0-in-vehicle-infotainment-ivi MeeGo IVI 1.0]

== Resources ==
* IRC irc.freenode.org #meego-ivi
* Mailing list sign-up: http://lists.meego.com/listinfo/meego-ivi
* Mailing list archive: http://lists.meego.com/pipermail/meego-ivi/
* [[Presentations_about_meego-ivi#Presentations_and_Articles_about_MeeGo_IVI|Presentations and articles about meego-ivi]]
* [[In-vehicle/IVI for users and developers|IVI for users and developers]]
* [[IVITopic|Topics]]

[[Category:IVI]]

In-vehicle

2011-07-01T21:27:04Z

Joel: /* MeeGo IVI UI (HMI) */

= 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: '''[http://meego.com/users/RudolfStreif 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:
*** Intel: '''[http://meego.com/users/jahoffmann Joel Hoffmann]'''
*** LG Electronics: '''[https://meego.com/users/hyungjin Hyungjin Jeon]'''
*** Nokia: '''[http://meego.com/users/alistair Alistair Adams]'''
*** Pelagicore: '''[http://meego.com/users/mikael Mikael Soderberg]'''
*** Visteon: '''[http://meego.com/users/PavelKonopelko Pavel Konopelko]'''

* Product Manager (cross-function across Working Group and Project Team)
** Unifies and prioritizes overall requirements set.
** Owns the roadmap.
** co-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 with the Lead Architects and Lead Designers on effort estimates and schedules.
** co-leads the Project Team together with the Product 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: '''[http://meego.com/users/joel Joel Clark (Intel)]'''

==== Working Group Meetings and Minutes ====
The Working Group meets regularly. Information on current and past meetings can be found on [[in-vehicle/working-group|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: '''[http://meego.com/users/tomcounihan 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: '''[http://meego.com/users/jeremiah 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.

== Shipping MeeGo IVI Products ==

* [http://news.softpedia.com/news/MeeGo-Powered-In-Vehicle-Information-System-Makes-Appearance-at-MWC-2011-184651.shtml Hawtai B11]
* [http://www.allaboutmeego.com/news/item/12918_Red_Flag_Software_announces_Me.php Geely EC8]
* iKarPC [http://files.icp-deutschland.de/produkte2/124273/web/icp/IKARPC-W08A-datasheet-20110222.pdf datasheet] and [http://www.contradata.it/cataloghi/IEI_2011_In_Vehicle_PC.pdf catalog page]

== MeeGo IVI Demos ==

* MeeGo IVI UI from ICS: [http://www.youtube.com/watch?v=ZWbfGzyLoh8 video] and [http://www.ics.com/services/qtquick info], including source code

== MeeGo IVI UI (HMI)==

MeeGo IVI includes a Sample UI. This UI is sample only because it has always been stolen from some other MeeGo device project and ported with little change to the IVI builds. Also the underlaying UI framework and the UI applications have changed in every version of MeeGo so far.

The MeeGo IVI 1.2.0 UI is primarily based on a collection of QML based applications designed for MeeGo Tablet. It has a IVI specific taskbar app launcher that adds support for scrollwheel and voice command imputs.

* [[In-vehicle/IVIHome_Guide | MeeGo IVI 1.2.0 IVI home screen / taskbar User Guide ]]

The MeeGo IVI Home screen / taskbar is tested with a Contour ShuttleExpress Scrollweel.

* [http://www.amazon.com/Contour-Design-00496-0-Shuttle-Xpress/dp/B0032Y0OH0/ref=sr_1_2?ie=UTF8&qid=1309555207&sr=8-2 Contour ShuttleXpress infromation ]

==== Other Scroll Wheels ====
Other scrollwheels that have been used by the MeeGo IVI community

* [http://tech.ikt.intel.com/wiki/3Dspacenavigator.#xinput 3D SpaceNavigator ]

== 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.

The roadmap pages are the central collaboration point on laying out the future of MeeGo IVI. Here architecture details, system diagrams, use cases, etc. are shared.

[[In-vehicle/Roadmap|View the Roadmap]]

Before any new feature is committed to the Roadmap, a feature request is created in http://bugs.meego.com. Current MeeGo IVI feature requests can be found [https://bugs.meego.com/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=MeeGo+IVI+Features&content= here]

[https://bugs.meego.com/enter_bug.cgi?product=MeeGo%20IVI%20Features 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 in the [[In-vehicle/Roadmap|IVI roadmap]].

== 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. [[Release Engineering/Release Versioning|MeeGo Release Versioning]] explains the build version numbering scheme. For example '''1.2.80.xx''' is a 1.2 Alpha build, '''1.2.90.xx''' is a 1.2 Beta build, '''1.2.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]

Each weekly build directory is named with a version number and date. IVI live .iso images are found under the ''images'' link in each weekly build directory. 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 under ''repos'' in the weekly build directory.

==Upcoming Releases==
===Meego 1.2.0 Update ===

;Update release dates
{| border="1"
! Update name
! Code Freeze
! Release
|-
|Update 1
|June 30
|July 7
|-
|Update 2
|August 11
|August 18
|-
|Update 3
|Sept 22
|Sept 29
|}

====Links====
When the first MeeGo 1.2.0 update is released July 7, 2011, the updated packages will show up in the following repository:
* [http://repo.meego.com/MeeGo/updates/1.2.0/repos/ MeeGo 1.2.0 Update Repositories]

* [https://bugs.meego.com/buglist.cgi?emailtype2=substring&field0-0-0=flagtypes.name&classification=MeeGo%20Platform&emailcc2=1&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&email2=ivi-bugs&version=1.2.0&type0-0-0=anywordssubstr&value0-0-0=meego_update_release_blocker%2B&known_name=ivibugs_1.2.0Update%2B MeeGo IVI 1.2.0 Update approved bugs ]

* [https://bugs.meego.com/buglist.cgi?emailtype2=substring&field0-0-0=flagtypes.name&classification=MeeGo%20Platform&emailcc2=1&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&email2=ivi-bugs&version=1.2.0&type0-0-0=anywordssubstr&value0-0-0=meego_update_release_blocker%3F&known_name=ivibugs_1.2.0Update%3F MeeGo IVI 1.2.0 Update proposed bugs ]

* [[ Quality/IVI 1.2 Update | IVI 1.2.0 Update bug fix status]]

===Meego 1.3===

;MeeGo 1.3 milestones
{| border="1"
! Milestone
! Date
|-
|New Package Planning complete ||June 30
|-
|Core Package integration ||July 26
|-
|IVI Package integration / version freeze ||August 12
|-
|1.3 branch and Release Candidate 1 ||October 4
|-
|1.3 final release ||October 27
|}

==Platforms==
===MeeGo IVI Platforms Supported in Releases===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! Releases
! Plan
! status
! price/availability
|-
|meego-ivi-ia32
|Congatec IVI Kit (Russellville)
|Intel Atom Z5xx Series and Intel System Controller Hub US15Wx (eMenlow)
|Timberdale
|GPIO, DMA, SPI, I2C, UART, USB, IDE, Audio, KS8842 GigE, EMGD, Video-in, SDHC, TSC2007, I2S, SDHC, ADV7180, BT, Radio
|1.0.1, 1.1, 1.2
|EOL
|No known driver issues
|unavailable 5/11
|-
|meego-ivi-ia32
|Crown Bay
|Intel Atom 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
|1.2
|1.3
|No known driver issues
|
|-
|meego-ivi-ia32
|Stephenville/Crossville
|Intel Atom E6xx Series for Embedded (Tunnel Creek)
|Oki Semiconductors ML7213 IVI IOH
|GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, EMGD, SD/SDIO/MMC, USB-OTG, TDM, sDVO
|1.2
|1.3
|[https://bugs.meego.com/buglist.cgi?short_desc=oki&classification=MeeGo%20Platform&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&version=1.2&version=1.3&short_desc_type=allwordssubstr&component=Kernel%20and%20drivers%20%28generic%29&product=MeeGo%20IVI CV-ML7213 bugs ]
|
|}

===MeeGo IVI Trunk Prototype Platforms===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! status
|-
|meego-ivi-ia32-conx
|Stephenville/Northville/Crossville
|Intel Atom 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, several issues open, visit [[IVI Images for ConneXt IOH]] for more information
|}

;ARM
:Jeremiah Foster and Jan-Simon Moeller are working on updates to enable automated weekly builds of MeeGo IVI images for the Beagleboard-XM.
:The suggested reference platform is the Beagleboard xM. The [[ARM/OMAP4_Panda|PandaBoard]] and [[ARM/Snowball|Snowball]] most likely will be supported in the future.
{| border="1"
! Image name
! Platform name
! chipset
! status
|-
| meego-ivi-armv7l
| Beagleboard xM
| OMAP 3
| Not yet smoke tested. No QA
|-
| meego-ivi-armv7l
| Tegra2
| ARM v7 rev 0
| Not yet smoke tested. No QA
|-
|}

===[http://sf2011.meego.com/sites/all/files/slides/meegocon2011developmentboardbofslides.pdf MeeGo IVI Development Boards]===

;IA32
{| border="1"
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! price/availability as of 5/11
! tested with MeeGo?
|-
|Intel Embedded Development Board 1-N450/1-D510
|N450 or D510
|Intel 82801HM
|SSD, WiFi, SATA, USB, SPI, GPIO, PCIe, UART, GigE, Audio, IEGD, DMA, I2C
|[http://edc.intel.com/Platforms/Atom-N450-D410-D510/Development-Board/#bd1-content=bd1-toggle~~visible-content $149 for registered users]
|[http://wiki.meego.com/Devices/Ideapad yes]
|}

;ARM

Per Stskeeps on meego-arm IRC on 6/2/2011, Nokia-provided N900 SGX530 drivers with hardfp extensions are known to work with SGX530 revisions 121 and 125. Which OMAP3 SoCs have revision 121 and 125 is not always straightforward to determine. dm8tbr reports problems with N900 hardfp drivers on Beagleboard xM. Stskeeps reports success with these drivers on Beagleboard C4. Tripzero reports success with hardfp drivers on old build of IGEPv2 that had the Cortex A8 processor.

{| border="1"
! Platform name
! Processor
! GPU; [[http://wiki.meego.com/ARM/hardfp hardfp?]]
! Memory
! Features
! price/availability as of 5/11
! tested with MeeGo?
|-
|[http://www.igloocommunity.org/ Snowball] (usable in end products)
|Cortex A-9 Dual-Core Nova A9500 1 GHz
|ARM Mali 400, [http://igloocommunity.org/news/ promised; no GPU support in 6/11 BSP]
|1 GB
|HDMI, WiFi b/g/n, Bluetooth, GPS, USB OTG, FSMC, HSI, Audio, MiPi CSI / Camera, LCD, MiPi DSI, UART, SPI, I2C, GPIO, SD/MMC, accelerometer, magnetometer, gyrometer, pressure sensor [[ARM/Snowball|(complete specs)]]
| [https://shop.strato.com/epages/61428605.sf/en_GB/?ObjectPath=/Shops/61428605/Products/905-00024-B11 148€]
| [[ARM/Snowball|yes]]
|-
|[http://www.igep.es/index.php?option=com_content&view=article&id=46&Itemid=55 IGEPv2]
|[http://www.igep.es/public_docs/IGEPv2/HW_User_Manuals/MAN-PR-IGEP.0020.HW_USER_MANUAL.pdf DM3730 1 GHz]
|Imagination Technologies SGX530, yes? (tested by IGES with both TI and Nokia drivers)
|512 MB
|GigE, WiFi b/g, Bluetooth, USB OTG, USB Host, DVI-D, audio, SPI, UART, LCD, serial; [http://shop.igep.es/index.php?main_page=product_info&cPath=1&products_id=49 expansion board] with GSM, VGA, video in, camera, '''CAN'''
| 116.0€ and up plus 152.0€ for expansion board
| yes, but with older Cortex A8 build
|-
|[http://www.variscite.com/products/item/35-var-am35customboard Variscite VAR-AM3517 CustomBoard]
|[http://www.variscite.com/images/stories/DataSheets/VAR-SOM-AM35_1_15.pdf Cortex A-8 Sitara 600 MHz]
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|DMA, QCIF, LCD, SDTV, S-Video, USB, USB OTG, I2C, McSPI, GPIO, MMC, JTAG, '''CAN'''
|$1150 plus shipping
| no
|-
|[http://www.origenboard.org Samsung Origen]
|Samsung Exynos 4210 Cortex A-9 1 GHz
|ARM Mali 400, [http://forums.arm.com/index.php?/topic/14236-mali-gpus-linux-device-drivers-r2p0-05rel0-source-code-released/ reuse Snowball drivers?]
|1 GB
|HMDI, SD, WiFi, Bluetooth, audio, LCD, JTAG, camera
|[http://www.insignal.co.kr "sub-$200", June 25]
|no
|-
|[http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=IMX53QSB i.MX53 Quick Start Board]
|Cortex A-8 1 GHz
|Freescale GPUv3, [http://imxcommunity.org/profiles/blogs/ubuntu-rebuilt-with-hardfp yes]
|1 GB
|LVDS, LCD, HDMI, SPDIF, I2C, SSI, SPI, SD/MMC, microSD, SATA, GigE, USB, USB OTG, JTAG, UART, accelerometer
|$149
|[http://www.youtube.com/watch?feature=player_embedded&v=osDlTdl5lAk yes, similar HW]
|-
|[http://pandaboard.org/ Pandaboard]
|Cortex A-9 Dual-Core OMAP 4430 1 GHz
|Imagination Technologies SGX540, [http://article.gmane.org/gmane.comp.embedded.pandaboard/1771/match=hardfp not yet]
|1 GB
|SD/MMC, UART, Camera connector, USB OTG, Audio, GiGE, LCD connector, HDMI, WiFi, Bluetooth, JTAG, SPI, GPIO, I2C, McBSP
|[http://pandaboard.org/content/buy $179]
|[[ARM/OMAP4_Panda|yes]]
|-
|[http://beagle.s3.amazonaws.com/design/xM-A/BB_xM_SRM_A2_01.pdf Beagleboard Xm]
|Cortex A-8 DM3730 1GHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|512 MB
|uSD, USB, USB OTG, UART, McBSP, JTAG, GiGE, Audio, DVI-D, Camera connector, McBSP, I2C, GPIO, MMC2/3, ADC, LCD connector
|[http://beagleboard.org/buy $149]
|[[ARM/Meego_on_Beagleboard_from_scratch|yes]]
|-
|[http://beagleboard.org/static/BBSRM_latest.pdf Beagleboard C4]
|Cortex A-8 OMAP3530 720 MHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|I2C, I2S, SPI, MMC, USB, UART, USB OTG, S-Video, Audio, LCD, JTAG, GiGE
|[http://beagleboard.org/buy $125]
|[[ARM/Meego_IVI_on_Beagle|yes]]
|}

== Releases ==
* [[MeeGo IVI 1.2 | MeeGo IVI 1.2]]
* [http://meego.com/downloads/releases/1.1/meego-v1.1-in-vehicle-infotainment-ivi MeeGo IVI 1.1]
* [http://meego.com/downloads/releases/1.0/meego-v1.0-in-vehicle-infotainment-ivi MeeGo IVI 1.0]

== Resources ==
* IRC irc.freenode.org #meego-ivi
* Mailing list sign-up: http://lists.meego.com/listinfo/meego-ivi
* Mailing list archive: http://lists.meego.com/pipermail/meego-ivi/
* [[Presentations_about_meego-ivi#Presentations_and_Articles_about_MeeGo_IVI|Presentations and articles about meego-ivi]]
* [[In-vehicle/IVI for users and developers|IVI for users and developers]]
* [[IVITopic|Topics]]

[[Category:IVI]]

In-vehicle

2011-07-01T21:25:50Z

Joel: /* MeeGo IVI UI (HMI) */

= 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: '''[http://meego.com/users/RudolfStreif 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:
*** Intel: '''[http://meego.com/users/jahoffmann Joel Hoffmann]'''
*** LG Electronics: '''[https://meego.com/users/hyungjin Hyungjin Jeon]'''
*** Nokia: '''[http://meego.com/users/alistair Alistair Adams]'''
*** Pelagicore: '''[http://meego.com/users/mikael Mikael Soderberg]'''
*** Visteon: '''[http://meego.com/users/PavelKonopelko Pavel Konopelko]'''

* Product Manager (cross-function across Working Group and Project Team)
** Unifies and prioritizes overall requirements set.
** Owns the roadmap.
** co-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 with the Lead Architects and Lead Designers on effort estimates and schedules.
** co-leads the Project Team together with the Product 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: '''[http://meego.com/users/joel Joel Clark (Intel)]'''

==== Working Group Meetings and Minutes ====
The Working Group meets regularly. Information on current and past meetings can be found on [[in-vehicle/working-group|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: '''[http://meego.com/users/tomcounihan 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: '''[http://meego.com/users/jeremiah 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.

== Shipping MeeGo IVI Products ==

* [http://news.softpedia.com/news/MeeGo-Powered-In-Vehicle-Information-System-Makes-Appearance-at-MWC-2011-184651.shtml Hawtai B11]
* [http://www.allaboutmeego.com/news/item/12918_Red_Flag_Software_announces_Me.php Geely EC8]
* iKarPC [http://files.icp-deutschland.de/produkte2/124273/web/icp/IKARPC-W08A-datasheet-20110222.pdf datasheet] and [http://www.contradata.it/cataloghi/IEI_2011_In_Vehicle_PC.pdf catalog page]

== MeeGo IVI Demos ==

* MeeGo IVI UI from ICS: [http://www.youtube.com/watch?v=ZWbfGzyLoh8 video] and [http://www.ics.com/services/qtquick info], including source code

== MeeGo IVI UI (HMI)==

MeeGo IVI includes a Sample UI. This UI is sample only because it has always been stolen from some other MeeGo device project and ported with little change to the IVI builds. Also the underlaying UI framework and the UI applications have changed in every version of MeeGo so far.

The MeeGo IVI 1.2.0 UI is primarily based on a collection of QML based applications designed for MeeGo Tablet. It has a IVI specific taskbar app launcher that adds support for scrollwheel and voice command imputs.

* [[In-vehicle/IVIHome_Guide | MeeGo IVI 1.2.0 IVI home screen / taskbar User Guide ]]

The MeeGo IVI Home screen / taskbar is tested with a Contour ShuttleExpress Scrollweel.

* [http://www.amazon.com/Contour-Design-00496-0-Shuttle-Xpress/dp/B0032Y0OH0/ref=sr_1_2?ie=UTF8&qid=1309555207&sr=8-2 Contour ShuttleXpress infromation ]

==== Other Scroll Wheels ====
Other scrollwheels that have been used by the MeeGo IVI community

[ http://tech.ikt.intel.com/wiki/3Dspacenavigator.#xinput 3D SpaceNavigator

== 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.

The roadmap pages are the central collaboration point on laying out the future of MeeGo IVI. Here architecture details, system diagrams, use cases, etc. are shared.

[[In-vehicle/Roadmap|View the Roadmap]]

Before any new feature is committed to the Roadmap, a feature request is created in http://bugs.meego.com. Current MeeGo IVI feature requests can be found [https://bugs.meego.com/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=MeeGo+IVI+Features&content= here]

[https://bugs.meego.com/enter_bug.cgi?product=MeeGo%20IVI%20Features 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 in the [[In-vehicle/Roadmap|IVI roadmap]].

== 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. [[Release Engineering/Release Versioning|MeeGo Release Versioning]] explains the build version numbering scheme. For example '''1.2.80.xx''' is a 1.2 Alpha build, '''1.2.90.xx''' is a 1.2 Beta build, '''1.2.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]

Each weekly build directory is named with a version number and date. IVI live .iso images are found under the ''images'' link in each weekly build directory. 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 under ''repos'' in the weekly build directory.

==Upcoming Releases==
===Meego 1.2.0 Update ===

;Update release dates
{| border="1"
! Update name
! Code Freeze
! Release
|-
|Update 1
|June 30
|July 7
|-
|Update 2
|August 11
|August 18
|-
|Update 3
|Sept 22
|Sept 29
|}

====Links====
When the first MeeGo 1.2.0 update is released July 7, 2011, the updated packages will show up in the following repository:
* [http://repo.meego.com/MeeGo/updates/1.2.0/repos/ MeeGo 1.2.0 Update Repositories]

* [https://bugs.meego.com/buglist.cgi?emailtype2=substring&field0-0-0=flagtypes.name&classification=MeeGo%20Platform&emailcc2=1&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&email2=ivi-bugs&version=1.2.0&type0-0-0=anywordssubstr&value0-0-0=meego_update_release_blocker%2B&known_name=ivibugs_1.2.0Update%2B MeeGo IVI 1.2.0 Update approved bugs ]

* [https://bugs.meego.com/buglist.cgi?emailtype2=substring&field0-0-0=flagtypes.name&classification=MeeGo%20Platform&emailcc2=1&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&email2=ivi-bugs&version=1.2.0&type0-0-0=anywordssubstr&value0-0-0=meego_update_release_blocker%3F&known_name=ivibugs_1.2.0Update%3F MeeGo IVI 1.2.0 Update proposed bugs ]

* [[ Quality/IVI 1.2 Update | IVI 1.2.0 Update bug fix status]]

===Meego 1.3===

;MeeGo 1.3 milestones
{| border="1"
! Milestone
! Date
|-
|New Package Planning complete ||June 30
|-
|Core Package integration ||July 26
|-
|IVI Package integration / version freeze ||August 12
|-
|1.3 branch and Release Candidate 1 ||October 4
|-
|1.3 final release ||October 27
|}

==Platforms==
===MeeGo IVI Platforms Supported in Releases===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! Releases
! Plan
! status
! price/availability
|-
|meego-ivi-ia32
|Congatec IVI Kit (Russellville)
|Intel Atom Z5xx Series and Intel System Controller Hub US15Wx (eMenlow)
|Timberdale
|GPIO, DMA, SPI, I2C, UART, USB, IDE, Audio, KS8842 GigE, EMGD, Video-in, SDHC, TSC2007, I2S, SDHC, ADV7180, BT, Radio
|1.0.1, 1.1, 1.2
|EOL
|No known driver issues
|unavailable 5/11
|-
|meego-ivi-ia32
|Crown Bay
|Intel Atom 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
|1.2
|1.3
|No known driver issues
|
|-
|meego-ivi-ia32
|Stephenville/Crossville
|Intel Atom E6xx Series for Embedded (Tunnel Creek)
|Oki Semiconductors ML7213 IVI IOH
|GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, EMGD, SD/SDIO/MMC, USB-OTG, TDM, sDVO
|1.2
|1.3
|[https://bugs.meego.com/buglist.cgi?short_desc=oki&classification=MeeGo%20Platform&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&version=1.2&version=1.3&short_desc_type=allwordssubstr&component=Kernel%20and%20drivers%20%28generic%29&product=MeeGo%20IVI CV-ML7213 bugs ]
|
|}

===MeeGo IVI Trunk Prototype Platforms===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! status
|-
|meego-ivi-ia32-conx
|Stephenville/Northville/Crossville
|Intel Atom 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, several issues open, visit [[IVI Images for ConneXt IOH]] for more information
|}

;ARM
:Jeremiah Foster and Jan-Simon Moeller are working on updates to enable automated weekly builds of MeeGo IVI images for the Beagleboard-XM.
:The suggested reference platform is the Beagleboard xM. The [[ARM/OMAP4_Panda|PandaBoard]] and [[ARM/Snowball|Snowball]] most likely will be supported in the future.
{| border="1"
! Image name
! Platform name
! chipset
! status
|-
| meego-ivi-armv7l
| Beagleboard xM
| OMAP 3
| Not yet smoke tested. No QA
|-
| meego-ivi-armv7l
| Tegra2
| ARM v7 rev 0
| Not yet smoke tested. No QA
|-
|}

===[http://sf2011.meego.com/sites/all/files/slides/meegocon2011developmentboardbofslides.pdf MeeGo IVI Development Boards]===

;IA32
{| border="1"
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! price/availability as of 5/11
! tested with MeeGo?
|-
|Intel Embedded Development Board 1-N450/1-D510
|N450 or D510
|Intel 82801HM
|SSD, WiFi, SATA, USB, SPI, GPIO, PCIe, UART, GigE, Audio, IEGD, DMA, I2C
|[http://edc.intel.com/Platforms/Atom-N450-D410-D510/Development-Board/#bd1-content=bd1-toggle~~visible-content $149 for registered users]
|[http://wiki.meego.com/Devices/Ideapad yes]
|}

;ARM

Per Stskeeps on meego-arm IRC on 6/2/2011, Nokia-provided N900 SGX530 drivers with hardfp extensions are known to work with SGX530 revisions 121 and 125. Which OMAP3 SoCs have revision 121 and 125 is not always straightforward to determine. dm8tbr reports problems with N900 hardfp drivers on Beagleboard xM. Stskeeps reports success with these drivers on Beagleboard C4. Tripzero reports success with hardfp drivers on old build of IGEPv2 that had the Cortex A8 processor.

{| border="1"
! Platform name
! Processor
! GPU; [[http://wiki.meego.com/ARM/hardfp hardfp?]]
! Memory
! Features
! price/availability as of 5/11
! tested with MeeGo?
|-
|[http://www.igloocommunity.org/ Snowball] (usable in end products)
|Cortex A-9 Dual-Core Nova A9500 1 GHz
|ARM Mali 400, [http://igloocommunity.org/news/ promised; no GPU support in 6/11 BSP]
|1 GB
|HDMI, WiFi b/g/n, Bluetooth, GPS, USB OTG, FSMC, HSI, Audio, MiPi CSI / Camera, LCD, MiPi DSI, UART, SPI, I2C, GPIO, SD/MMC, accelerometer, magnetometer, gyrometer, pressure sensor [[ARM/Snowball|(complete specs)]]
| [https://shop.strato.com/epages/61428605.sf/en_GB/?ObjectPath=/Shops/61428605/Products/905-00024-B11 148€]
| [[ARM/Snowball|yes]]
|-
|[http://www.igep.es/index.php?option=com_content&view=article&id=46&Itemid=55 IGEPv2]
|[http://www.igep.es/public_docs/IGEPv2/HW_User_Manuals/MAN-PR-IGEP.0020.HW_USER_MANUAL.pdf DM3730 1 GHz]
|Imagination Technologies SGX530, yes? (tested by IGES with both TI and Nokia drivers)
|512 MB
|GigE, WiFi b/g, Bluetooth, USB OTG, USB Host, DVI-D, audio, SPI, UART, LCD, serial; [http://shop.igep.es/index.php?main_page=product_info&cPath=1&products_id=49 expansion board] with GSM, VGA, video in, camera, '''CAN'''
| 116.0€ and up plus 152.0€ for expansion board
| yes, but with older Cortex A8 build
|-
|[http://www.variscite.com/products/item/35-var-am35customboard Variscite VAR-AM3517 CustomBoard]
|[http://www.variscite.com/images/stories/DataSheets/VAR-SOM-AM35_1_15.pdf Cortex A-8 Sitara 600 MHz]
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|DMA, QCIF, LCD, SDTV, S-Video, USB, USB OTG, I2C, McSPI, GPIO, MMC, JTAG, '''CAN'''
|$1150 plus shipping
| no
|-
|[http://www.origenboard.org Samsung Origen]
|Samsung Exynos 4210 Cortex A-9 1 GHz
|ARM Mali 400, [http://forums.arm.com/index.php?/topic/14236-mali-gpus-linux-device-drivers-r2p0-05rel0-source-code-released/ reuse Snowball drivers?]
|1 GB
|HMDI, SD, WiFi, Bluetooth, audio, LCD, JTAG, camera
|[http://www.insignal.co.kr "sub-$200", June 25]
|no
|-
|[http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=IMX53QSB i.MX53 Quick Start Board]
|Cortex A-8 1 GHz
|Freescale GPUv3, [http://imxcommunity.org/profiles/blogs/ubuntu-rebuilt-with-hardfp yes]
|1 GB
|LVDS, LCD, HDMI, SPDIF, I2C, SSI, SPI, SD/MMC, microSD, SATA, GigE, USB, USB OTG, JTAG, UART, accelerometer
|$149
|[http://www.youtube.com/watch?feature=player_embedded&v=osDlTdl5lAk yes, similar HW]
|-
|[http://pandaboard.org/ Pandaboard]
|Cortex A-9 Dual-Core OMAP 4430 1 GHz
|Imagination Technologies SGX540, [http://article.gmane.org/gmane.comp.embedded.pandaboard/1771/match=hardfp not yet]
|1 GB
|SD/MMC, UART, Camera connector, USB OTG, Audio, GiGE, LCD connector, HDMI, WiFi, Bluetooth, JTAG, SPI, GPIO, I2C, McBSP
|[http://pandaboard.org/content/buy $179]
|[[ARM/OMAP4_Panda|yes]]
|-
|[http://beagle.s3.amazonaws.com/design/xM-A/BB_xM_SRM_A2_01.pdf Beagleboard Xm]
|Cortex A-8 DM3730 1GHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|512 MB
|uSD, USB, USB OTG, UART, McBSP, JTAG, GiGE, Audio, DVI-D, Camera connector, McBSP, I2C, GPIO, MMC2/3, ADC, LCD connector
|[http://beagleboard.org/buy $149]
|[[ARM/Meego_on_Beagleboard_from_scratch|yes]]
|-
|[http://beagleboard.org/static/BBSRM_latest.pdf Beagleboard C4]
|Cortex A-8 OMAP3530 720 MHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|I2C, I2S, SPI, MMC, USB, UART, USB OTG, S-Video, Audio, LCD, JTAG, GiGE
|[http://beagleboard.org/buy $125]
|[[ARM/Meego_IVI_on_Beagle|yes]]
|}

== Releases ==
* [[MeeGo IVI 1.2 | MeeGo IVI 1.2]]
* [http://meego.com/downloads/releases/1.1/meego-v1.1-in-vehicle-infotainment-ivi MeeGo IVI 1.1]
* [http://meego.com/downloads/releases/1.0/meego-v1.0-in-vehicle-infotainment-ivi MeeGo IVI 1.0]

== Resources ==
* IRC irc.freenode.org #meego-ivi
* Mailing list sign-up: http://lists.meego.com/listinfo/meego-ivi
* Mailing list archive: http://lists.meego.com/pipermail/meego-ivi/
* [[Presentations_about_meego-ivi#Presentations_and_Articles_about_MeeGo_IVI|Presentations and articles about meego-ivi]]
* [[In-vehicle/IVI for users and developers|IVI for users and developers]]
* [[IVITopic|Topics]]

[[Category:IVI]]

In-vehicle

2011-07-01T21:24:18Z

Joel: /* MeeGo IVI Demos */

= 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: '''[http://meego.com/users/RudolfStreif 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:
*** Intel: '''[http://meego.com/users/jahoffmann Joel Hoffmann]'''
*** LG Electronics: '''[https://meego.com/users/hyungjin Hyungjin Jeon]'''
*** Nokia: '''[http://meego.com/users/alistair Alistair Adams]'''
*** Pelagicore: '''[http://meego.com/users/mikael Mikael Soderberg]'''
*** Visteon: '''[http://meego.com/users/PavelKonopelko Pavel Konopelko]'''

* Product Manager (cross-function across Working Group and Project Team)
** Unifies and prioritizes overall requirements set.
** Owns the roadmap.
** co-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 with the Lead Architects and Lead Designers on effort estimates and schedules.
** co-leads the Project Team together with the Product 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: '''[http://meego.com/users/joel Joel Clark (Intel)]'''

==== Working Group Meetings and Minutes ====
The Working Group meets regularly. Information on current and past meetings can be found on [[in-vehicle/working-group|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: '''[http://meego.com/users/tomcounihan 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: '''[http://meego.com/users/jeremiah 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.

== Shipping MeeGo IVI Products ==

* [http://news.softpedia.com/news/MeeGo-Powered-In-Vehicle-Information-System-Makes-Appearance-at-MWC-2011-184651.shtml Hawtai B11]
* [http://www.allaboutmeego.com/news/item/12918_Red_Flag_Software_announces_Me.php Geely EC8]
* iKarPC [http://files.icp-deutschland.de/produkte2/124273/web/icp/IKARPC-W08A-datasheet-20110222.pdf datasheet] and [http://www.contradata.it/cataloghi/IEI_2011_In_Vehicle_PC.pdf catalog page]

== MeeGo IVI Demos ==

* MeeGo IVI UI from ICS: [http://www.youtube.com/watch?v=ZWbfGzyLoh8 video] and [http://www.ics.com/services/qtquick info], including source code

== MeeGo IVI UI (HMI)==

MeeGo IVI includes a Sample UI. This UI is sample only because it has always been stolen from some other MeeGo device project and ported with little change to the IVI builds. Also the underlaying UI framework and the UI applications have changed in every version of MeeGo so far.

The MeeGo IVI 1.2.0 UI is primarily based on a collection of QML based applications designed for MeeGo Tablet. It has a IVI specific taskbar app launcher that adds support for scrollwheel and voice command imputs.

* [[In-vehicle/IVIHome_Guide MeeGo | IVI 1.2.0 IVI home screen / taskbar User Guide ]]

The MeeGo IVI Home screen / taskbar is tested with a Contour ShuttleExpress Scrollweel.

* [http://www.amazon.com/Contour-Design-00496-0-Shuttle-Xpress/dp/B0032Y0OH0/ref=sr_1_2?ie=UTF8&qid=1309555207&sr=8-2 Contour ShuttleXpress infromation ]

==== Other Scroll Wheels ====
Other scrollwheels that have been used by the MeeGo IVI community

[ http://tech.ikt.intel.com/wiki/3Dspacenavigator.#xinput 3D SpaceNavigator

== 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.

The roadmap pages are the central collaboration point on laying out the future of MeeGo IVI. Here architecture details, system diagrams, use cases, etc. are shared.

[[In-vehicle/Roadmap|View the Roadmap]]

Before any new feature is committed to the Roadmap, a feature request is created in http://bugs.meego.com. Current MeeGo IVI feature requests can be found [https://bugs.meego.com/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=MeeGo+IVI+Features&content= here]

[https://bugs.meego.com/enter_bug.cgi?product=MeeGo%20IVI%20Features 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 in the [[In-vehicle/Roadmap|IVI roadmap]].

== 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. [[Release Engineering/Release Versioning|MeeGo Release Versioning]] explains the build version numbering scheme. For example '''1.2.80.xx''' is a 1.2 Alpha build, '''1.2.90.xx''' is a 1.2 Beta build, '''1.2.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]

Each weekly build directory is named with a version number and date. IVI live .iso images are found under the ''images'' link in each weekly build directory. 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 under ''repos'' in the weekly build directory.

==Upcoming Releases==
===Meego 1.2.0 Update ===

;Update release dates
{| border="1"
! Update name
! Code Freeze
! Release
|-
|Update 1
|June 30
|July 7
|-
|Update 2
|August 11
|August 18
|-
|Update 3
|Sept 22
|Sept 29
|}

====Links====
When the first MeeGo 1.2.0 update is released July 7, 2011, the updated packages will show up in the following repository:
* [http://repo.meego.com/MeeGo/updates/1.2.0/repos/ MeeGo 1.2.0 Update Repositories]

* [https://bugs.meego.com/buglist.cgi?emailtype2=substring&field0-0-0=flagtypes.name&classification=MeeGo%20Platform&emailcc2=1&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&email2=ivi-bugs&version=1.2.0&type0-0-0=anywordssubstr&value0-0-0=meego_update_release_blocker%2B&known_name=ivibugs_1.2.0Update%2B MeeGo IVI 1.2.0 Update approved bugs ]

* [https://bugs.meego.com/buglist.cgi?emailtype2=substring&field0-0-0=flagtypes.name&classification=MeeGo%20Platform&emailcc2=1&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&email2=ivi-bugs&version=1.2.0&type0-0-0=anywordssubstr&value0-0-0=meego_update_release_blocker%3F&known_name=ivibugs_1.2.0Update%3F MeeGo IVI 1.2.0 Update proposed bugs ]

* [[ Quality/IVI 1.2 Update | IVI 1.2.0 Update bug fix status]]

===Meego 1.3===

;MeeGo 1.3 milestones
{| border="1"
! Milestone
! Date
|-
|New Package Planning complete ||June 30
|-
|Core Package integration ||July 26
|-
|IVI Package integration / version freeze ||August 12
|-
|1.3 branch and Release Candidate 1 ||October 4
|-
|1.3 final release ||October 27
|}

==Platforms==
===MeeGo IVI Platforms Supported in Releases===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! Releases
! Plan
! status
! price/availability
|-
|meego-ivi-ia32
|Congatec IVI Kit (Russellville)
|Intel Atom Z5xx Series and Intel System Controller Hub US15Wx (eMenlow)
|Timberdale
|GPIO, DMA, SPI, I2C, UART, USB, IDE, Audio, KS8842 GigE, EMGD, Video-in, SDHC, TSC2007, I2S, SDHC, ADV7180, BT, Radio
|1.0.1, 1.1, 1.2
|EOL
|No known driver issues
|unavailable 5/11
|-
|meego-ivi-ia32
|Crown Bay
|Intel Atom 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
|1.2
|1.3
|No known driver issues
|
|-
|meego-ivi-ia32
|Stephenville/Crossville
|Intel Atom E6xx Series for Embedded (Tunnel Creek)
|Oki Semiconductors ML7213 IVI IOH
|GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, EMGD, SD/SDIO/MMC, USB-OTG, TDM, sDVO
|1.2
|1.3
|[https://bugs.meego.com/buglist.cgi?short_desc=oki&classification=MeeGo%20Platform&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&version=1.2&version=1.3&short_desc_type=allwordssubstr&component=Kernel%20and%20drivers%20%28generic%29&product=MeeGo%20IVI CV-ML7213 bugs ]
|
|}

===MeeGo IVI Trunk Prototype Platforms===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! status
|-
|meego-ivi-ia32-conx
|Stephenville/Northville/Crossville
|Intel Atom 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, several issues open, visit [[IVI Images for ConneXt IOH]] for more information
|}

;ARM
:Jeremiah Foster and Jan-Simon Moeller are working on updates to enable automated weekly builds of MeeGo IVI images for the Beagleboard-XM.
:The suggested reference platform is the Beagleboard xM. The [[ARM/OMAP4_Panda|PandaBoard]] and [[ARM/Snowball|Snowball]] most likely will be supported in the future.
{| border="1"
! Image name
! Platform name
! chipset
! status
|-
| meego-ivi-armv7l
| Beagleboard xM
| OMAP 3
| Not yet smoke tested. No QA
|-
| meego-ivi-armv7l
| Tegra2
| ARM v7 rev 0
| Not yet smoke tested. No QA
|-
|}

===[http://sf2011.meego.com/sites/all/files/slides/meegocon2011developmentboardbofslides.pdf MeeGo IVI Development Boards]===

;IA32
{| border="1"
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! price/availability as of 5/11
! tested with MeeGo?
|-
|Intel Embedded Development Board 1-N450/1-D510
|N450 or D510
|Intel 82801HM
|SSD, WiFi, SATA, USB, SPI, GPIO, PCIe, UART, GigE, Audio, IEGD, DMA, I2C
|[http://edc.intel.com/Platforms/Atom-N450-D410-D510/Development-Board/#bd1-content=bd1-toggle~~visible-content $149 for registered users]
|[http://wiki.meego.com/Devices/Ideapad yes]
|}

;ARM

Per Stskeeps on meego-arm IRC on 6/2/2011, Nokia-provided N900 SGX530 drivers with hardfp extensions are known to work with SGX530 revisions 121 and 125. Which OMAP3 SoCs have revision 121 and 125 is not always straightforward to determine. dm8tbr reports problems with N900 hardfp drivers on Beagleboard xM. Stskeeps reports success with these drivers on Beagleboard C4. Tripzero reports success with hardfp drivers on old build of IGEPv2 that had the Cortex A8 processor.

{| border="1"
! Platform name
! Processor
! GPU; [[http://wiki.meego.com/ARM/hardfp hardfp?]]
! Memory
! Features
! price/availability as of 5/11
! tested with MeeGo?
|-
|[http://www.igloocommunity.org/ Snowball] (usable in end products)
|Cortex A-9 Dual-Core Nova A9500 1 GHz
|ARM Mali 400, [http://igloocommunity.org/news/ promised; no GPU support in 6/11 BSP]
|1 GB
|HDMI, WiFi b/g/n, Bluetooth, GPS, USB OTG, FSMC, HSI, Audio, MiPi CSI / Camera, LCD, MiPi DSI, UART, SPI, I2C, GPIO, SD/MMC, accelerometer, magnetometer, gyrometer, pressure sensor [[ARM/Snowball|(complete specs)]]
| [https://shop.strato.com/epages/61428605.sf/en_GB/?ObjectPath=/Shops/61428605/Products/905-00024-B11 148€]
| [[ARM/Snowball|yes]]
|-
|[http://www.igep.es/index.php?option=com_content&view=article&id=46&Itemid=55 IGEPv2]
|[http://www.igep.es/public_docs/IGEPv2/HW_User_Manuals/MAN-PR-IGEP.0020.HW_USER_MANUAL.pdf DM3730 1 GHz]
|Imagination Technologies SGX530, yes? (tested by IGES with both TI and Nokia drivers)
|512 MB
|GigE, WiFi b/g, Bluetooth, USB OTG, USB Host, DVI-D, audio, SPI, UART, LCD, serial; [http://shop.igep.es/index.php?main_page=product_info&cPath=1&products_id=49 expansion board] with GSM, VGA, video in, camera, '''CAN'''
| 116.0€ and up plus 152.0€ for expansion board
| yes, but with older Cortex A8 build
|-
|[http://www.variscite.com/products/item/35-var-am35customboard Variscite VAR-AM3517 CustomBoard]
|[http://www.variscite.com/images/stories/DataSheets/VAR-SOM-AM35_1_15.pdf Cortex A-8 Sitara 600 MHz]
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|DMA, QCIF, LCD, SDTV, S-Video, USB, USB OTG, I2C, McSPI, GPIO, MMC, JTAG, '''CAN'''
|$1150 plus shipping
| no
|-
|[http://www.origenboard.org Samsung Origen]
|Samsung Exynos 4210 Cortex A-9 1 GHz
|ARM Mali 400, [http://forums.arm.com/index.php?/topic/14236-mali-gpus-linux-device-drivers-r2p0-05rel0-source-code-released/ reuse Snowball drivers?]
|1 GB
|HMDI, SD, WiFi, Bluetooth, audio, LCD, JTAG, camera
|[http://www.insignal.co.kr "sub-$200", June 25]
|no
|-
|[http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=IMX53QSB i.MX53 Quick Start Board]
|Cortex A-8 1 GHz
|Freescale GPUv3, [http://imxcommunity.org/profiles/blogs/ubuntu-rebuilt-with-hardfp yes]
|1 GB
|LVDS, LCD, HDMI, SPDIF, I2C, SSI, SPI, SD/MMC, microSD, SATA, GigE, USB, USB OTG, JTAG, UART, accelerometer
|$149
|[http://www.youtube.com/watch?feature=player_embedded&v=osDlTdl5lAk yes, similar HW]
|-
|[http://pandaboard.org/ Pandaboard]
|Cortex A-9 Dual-Core OMAP 4430 1 GHz
|Imagination Technologies SGX540, [http://article.gmane.org/gmane.comp.embedded.pandaboard/1771/match=hardfp not yet]
|1 GB
|SD/MMC, UART, Camera connector, USB OTG, Audio, GiGE, LCD connector, HDMI, WiFi, Bluetooth, JTAG, SPI, GPIO, I2C, McBSP
|[http://pandaboard.org/content/buy $179]
|[[ARM/OMAP4_Panda|yes]]
|-
|[http://beagle.s3.amazonaws.com/design/xM-A/BB_xM_SRM_A2_01.pdf Beagleboard Xm]
|Cortex A-8 DM3730 1GHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|512 MB
|uSD, USB, USB OTG, UART, McBSP, JTAG, GiGE, Audio, DVI-D, Camera connector, McBSP, I2C, GPIO, MMC2/3, ADC, LCD connector
|[http://beagleboard.org/buy $149]
|[[ARM/Meego_on_Beagleboard_from_scratch|yes]]
|-
|[http://beagleboard.org/static/BBSRM_latest.pdf Beagleboard C4]
|Cortex A-8 OMAP3530 720 MHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|I2C, I2S, SPI, MMC, USB, UART, USB OTG, S-Video, Audio, LCD, JTAG, GiGE
|[http://beagleboard.org/buy $125]
|[[ARM/Meego_IVI_on_Beagle|yes]]
|}

== Releases ==
* [[MeeGo IVI 1.2 | MeeGo IVI 1.2]]
* [http://meego.com/downloads/releases/1.1/meego-v1.1-in-vehicle-infotainment-ivi MeeGo IVI 1.1]
* [http://meego.com/downloads/releases/1.0/meego-v1.0-in-vehicle-infotainment-ivi MeeGo IVI 1.0]

== Resources ==
* IRC irc.freenode.org #meego-ivi
* Mailing list sign-up: http://lists.meego.com/listinfo/meego-ivi
* Mailing list archive: http://lists.meego.com/pipermail/meego-ivi/
* [[Presentations_about_meego-ivi#Presentations_and_Articles_about_MeeGo_IVI|Presentations and articles about meego-ivi]]
* [[In-vehicle/IVI for users and developers|IVI for users and developers]]
* [[IVITopic|Topics]]

[[Category:IVI]]

Quality/IVI 1.2 Update

2011-07-01T21:08:01Z

Joel: /* Kernel&Drivers */

== Bug List ==

{| border="1"
! LEGEND
! Comment
|-
| style="background: #33CC33"| || SRs completed, QA verified
|-
| style="background: #ee2222"| || Patch ready but still need SRs(accepted) and QA's verification
|}

=== Generic ===
{| border="1"
! ID(1.2.0)
! Status
! Resolution
! Flag
! ID(1.2)
! Status
! Resolution
! Summary
! Comment
|-
| 17502 || NEW || || U+ || 18913 || NEW || || [IVI] boot time is too long ~35 seconds ||
|}

=== Graphics ===
{| border="1"
! ID(1.2.0)
! Status
! Resolution
! Flag
! ID(1.2)
! Status
! Resolution
! Summary
! Comment
|- style="background: gray"
| 14641 || VERIFIED || WONTFIX || U? || 18976 || VERIFIED || WONTFIX || [IVI] Dual Head display support for Russellville/Northville ||
|-
| 16929 || NEW || || U? || 18978 || NEW || || IVI/Russellville: hang when switch from command line to X ||
|-
| 17177 || NEW || || U? || 18979 || NEW || ||[IVI]tear/black screen showed sometimes on LVDS'13 || Still reproduced with emgd-bin-2027
|- style="background: #33cc33"
| 17851 || RELEASED || FIXED || U+ || 18919 || RESOLVED || FIXED ||[IVI] EMGD returns 24-bit XRGB visual when a 32-bit ARGB visual is needed for EGL support of QT|| Accepted SR#21749 into 1.2.0:Update. Accepted SR#21631 into 1.2 branch and verified fixed.
|- style="background: #33cc33"
| 18707 || RESOLVED || FIXED || U+ || 18918 || RELEASED || FIXED || [IVI] EMGD-bin: meego-ux-daemon crashes QT at various times (lock screen, task switcher, when idle) || Accepted SR#21749 into 1.2.0:Update. Accepted SR#21631 into 1.2 branch and verified fixed.[Workaround for BMC# 16997]
|- style="background: #33cc33"
| 19087 || RESOLVED || FIXED || U+ || 20194 || RESOLVED || FIXED || [IVI] X init failed if emgd update to 2001-4|| Accepted SR#21749 into 1.2.0:Update. Accepted SR#21631 into 1.2 branch and verified fixed.
|- style="background: #33cc33"
| 19386 || RESOLVED || FIXED || U+ || 20195 || RESOLVED || FIXED || [IVI][REG] Lock screen not rendered on top of IVI desktop with emgd-bin-2001-4 || Accepted SR#21749 into 1.2.0:Update. Accepted SR#21631 into 1.2 branch and verified fixed.
|-
| || || || || 19377 || RESOLVED || FIXED || [IVI][REG] App switcher show black frame for launched app icons with emgd-2001 || '''Not reproduced with emgd-2027''' 
|}

=== Installation ===
{| border="1"
! ID(1.2.0)
! Status
! Resolution
! Flag
! ID(1.2)
! Status
! Resolution
! Summary
! Comment
|- style="background: #33ee33"
| 11781 || RELEASED || FIXED || U+ || 18915 || RESOLVED || FIXED || [IVI] Failed to install the meego ivi with text installation when the hdd is new brand || Accepted SR#21802 into 1.2.0 update. Accepted SR into 1.2 branch. '''Need verification by bug reporter.''' 
|-
| 15443 || NEW || || U+ || 18916 || NEW || || GUI Installer hangs when a storage device partition table cannot be read ||
|-
| 16876 || NEW || || U+ || 18917 || NEW || || [IVI] RV: GUI Installer takes a long time to launch ||
|}

=== Kernel&Drivers ===
{| border="1"
! ID(1.2.0)
! Status
! Resolution
! Flag
! ID(1.2)
! Status
! Resolution
! Summary
! Comment
|- style="background: #ee2222"
| 17135 || RELEASED || FIXED || U+ || 18981 || RESOLVED || FIXED || CrossvilleOKI: ioh_video_in initialize failed || Accepted SR#21938 into 1.2.0 update. New SR#21937 into 1.2 branch. Pending verification.
|-
| 17467 || NEW || || U? || 18982 || NEW || || IVI/Crossville-OKI: touchscreen NOT function ||
|- style="background: #33CC33"
| 18980 || RELEASED || FIXED || U+ || 15611 || RELEASED || FIXED || Wrong driver is loading on Crown Bay's EG20T serial port ( same will occur on ML7213) || Available in 1.2.0.0.1.20110629.1 Accepted in MeeGo:1.2:oss Accepted in Trunk:
|- style="background: #33CC33"
| 18988 || RELEASED || FIXED || U+ || 17042 || RELEASED || FIXED || Turn off expensive debug config options for release || Available in 1.2.0.0.1.20110629.1 Accepted in MeeGo:1.2:oss Accepted in Trunk:

|- style="background: #33CC33"
| 18991 || RELEASED || FIXED || U+ || 17774 || RELEASED || FIXED || xen missing from kernel-adaptation-intel-automotive-devel || Available in 1.2.0.0.1.20110629.1 Accepted in MeeGo:1.2:oss Accepted in Trunk:

|- style="background: #33CC33"
| 16760 || RELEASED || FIXED || U+ || 18977 || RELEASED || FIXED || [IVI] Russellville: /dev/radio0 not found || Available in 1.2.0.0.1.20110629.1. Accepted in MeeGo:1.2:oss ''' Not promoted to Trunk yet'''
|} 

=== meego-ux-ivi ===
{| border="1"
! ID(1.2.0)
! Status
! Resolution
! Flag
! ID(1.2)
! Status
! Resolution
! Summary
! Comment
|-
| 17391 || REOPENED || || U? || 18985 || NEW || || [IVI]screen lock function will kill running app ||
|- style="background: #33CC33"
| 18987 || RELEASED || FIXED || U+ || 16941 || RELEASED || FIXED || [IVI] no prompt give out when open deleted apps on desktop menu || Available in 1.2.0.0.1.20110629.1
|- style="background: #33CC33"
| 18989 || RELEASED || FIXED || U+ || 17184 || RELEASED || FIXED || [VoiceCommand] failed to launch task menu by "Tasks" || Available in 1.2.0.0.1.20110629.1
|- style="background: #33CC33"
| 18990 || RELEASED || FIXED || U+ || 17438 || RELEASED || FIXED || [IVI][VoiceCommand] failed to open apps directly || Available in 1.2.0.0.1.20110629.1
|- style="background: #ee2222"
| 17393 || RELEASED || FIXED || U+ || 20198 || NEW || || [IVI] screen should not lock when navigating || Accepted SR#22034 into 1.2.0:Update. No SR into 1.2 branch.
|- style="background: #ee2222"
| 19052 || RELEASED || FIXED || U+ || 20200 || NEW || || [IVI]: IVI UX should be visible at all times by default || Accepted SR#22034 into 1.2.0:Update. No SR into 1.2 branch.
|} 

=== Qt&QtContacts ===
{| border="1"
! ID(1.2.0)
! Status
! Resolution
! Flag
! ID(1.2)
! Status
! Resolution
! Summary
! Comment
|-
|18845 || NEW || || U+ || 18914 || NEW || || [IVI] Qt EGL graphics selects wrong "visual id" for secondary screen and crashes ||
|-
|18986 || NEW || || U? || 16997 || REOPENED || || meego-ux-daemon crashes QT at various times (lock screen, task switcher, when idle) || Workaround BMC#18707
|-
|18983 || NEW || || U? || 15948 || REOPENED || || [REG]Fail to run ut_qtcontacts_trackerplugin || qtcontacts-tracker is going to be replaced with qtcontacts-eds
|} 

=== Other Candidates ===
{| border="1"
! ID(1.2.0)
! Status
! Resolution
! Flag
! ID(1.2)
! Status
! Resolution
! Summary
! Comment
|-
| || || || || 17460 || NEW || || [IVI][REG] screen flickers when hovering cursors on the active buttons/text input box of Manage Apps ||
|-
| || || || R+, U+ || 19764 || NEEDINFO || || kernel-adaptation-intel-automotive source RPM fails to build ||
|-
| || || || R+, U+ || 10420 || NEW || || Failed to switch between X and console after kernel updated ||
|- style="background: #ee2222"
| 20276 || NEW || || U+ || 19353 || RELEASED || FIXED || Tracker fail to find the media files from USB disk. || No SR into 1.2.0 update. SR accepted into 1.2 branch.
|}

In-vehicle

2011-06-30T00:34:37Z

Joel: /* Meego 1.3 */

= 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: '''[http://meego.com/users/RudolfStreif 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:
*** Intel: '''[http://meego.com/users/jahoffmann Joel Hoffmann]'''
*** LG Electronics: '''[https://meego.com/users/hyungjin Hyungjin Jeon]'''
*** Nokia: '''[http://meego.com/users/alistair Alistair Adams]'''
*** Pelagicore: '''[http://meego.com/users/mikael Mikael Soderberg]'''
*** Visteon: '''[http://meego.com/users/PavelKonopelko Pavel Konopelko]'''

* Product Manager (cross-function across Working Group and Project Team)
** Unifies and prioritizes overall requirements set.
** Owns the roadmap.
** co-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 with the Lead Architects and Lead Designers on effort estimates and schedules.
** co-leads the Project Team together with the Product 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: '''[http://meego.com/users/joel Joel Clark (Intel)]'''

==== Working Group Meetings and Minutes ====
The Working Group meets regularly. Information on current and past meetings can be found on [[in-vehicle/working-group|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: '''[http://meego.com/users/tomcounihan 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: '''[http://meego.com/users/jeremiah 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.

== Shipping MeeGo IVI Products ==

* [http://news.softpedia.com/news/MeeGo-Powered-In-Vehicle-Information-System-Makes-Appearance-at-MWC-2011-184651.shtml Hawtai B11]
* [http://www.allaboutmeego.com/news/item/12918_Red_Flag_Software_announces_Me.php Geely EC8]
* iKarPC [http://files.icp-deutschland.de/produkte2/124273/web/icp/IKARPC-W08A-datasheet-20110222.pdf datasheet] and [http://www.contradata.it/cataloghi/IEI_2011_In_Vehicle_PC.pdf catalog page]

== MeeGo IVI Demos ==

* MeeGo IVI UI from ICS: [http://www.youtube.com/watch?v=ZWbfGzyLoh8 video] and [http://www.ics.com/services/qtquick info], including source code

== 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.

The roadmap pages are the central collaboration point on laying out the future of MeeGo IVI. Here architecture details, system diagrams, use cases, etc. are shared.

[[In-vehicle/Roadmap|View the Roadmap]]

Before any new feature is committed to the Roadmap, a feature request is created in http://bugs.meego.com. Current MeeGo IVI feature requests can be found [https://bugs.meego.com/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=MeeGo+IVI+Features&content= here]

[https://bugs.meego.com/enter_bug.cgi?product=MeeGo%20IVI%20Features 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 in the [[In-vehicle/Roadmap|IVI roadmap]].

== 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. [[Release Engineering/Release Versioning|MeeGo Release Versioning]] explains the build version numbering scheme. For example '''1.2.80.xx''' is a 1.2 Alpha build, '''1.2.90.xx''' is a 1.2 Beta build, '''1.2.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]

Each weekly build directory is named with a version number and date. IVI live .iso images are found under the ''images'' link in each weekly build directory. 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 under ''repos'' in the weekly build directory.

==Upcoming Releases==
===Meego 1.2.0 Update ===

;Update release dates
{| border="1"
! Update name
! Code Freeze
! Release
|-
|Update 1
|June 30
|July 7
|-
|Update 2
|August 11
|August 18
|-
|Update 3
|Sept 22
|Sept 29
|}

====Links====
When the first MeeGo 1.2.0 update is released July 7, 2011, the updated packages will show up in the following repository:
* [http://repo.meego.com/MeeGo/updates/1.2.0/repos/ MeeGo 1.2.0 Update Repositories]

* [https://bugs.meego.com/buglist.cgi?emailtype2=substring&field0-0-0=flagtypes.name&classification=MeeGo%20Platform&emailcc2=1&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&email2=ivi-bugs&version=1.2.0&type0-0-0=anywordssubstr&value0-0-0=meego_update_release_blocker%2B&known_name=ivibugs_1.2.0Update%2B MeeGo IVI 1.2.0 Update approved bugs ]

* [https://bugs.meego.com/buglist.cgi?emailtype2=substring&field0-0-0=flagtypes.name&classification=MeeGo%20Platform&emailcc2=1&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&email2=ivi-bugs&version=1.2.0&type0-0-0=anywordssubstr&value0-0-0=meego_update_release_blocker%3F&known_name=ivibugs_1.2.0Update%3F MeeGo IVI 1.2.0 Update proposed bugs ]

* [[ Quality/IVI 1.2 Update | IVI 1.2.0 Update bug fix status]]

===Meego 1.3===

;MeeGo 1.3 milestones
{| border="1"
! Milestone
! Date
|-
|New Package Planning complete ||June 30
|-
|Core Package integration ||July 26
|-
|IVI Package integration / version freeze ||August 12
|-
|1.3 branch and Release Candidate 1 ||October 4
|-
|1.3 final release ||October 27
|}

==Platforms==
===MeeGo IVI Platforms Supported in Releases===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! Releases
! Plan
! status
! price/availability
|-
|meego-ivi-ia32
|Congatec IVI Kit (Russellville)
|Intel Atom Z5xx Series and Intel System Controller Hub US15Wx (eMenlow)
|Timberdale
|GPIO, DMA, SPI, I2C, UART, USB, IDE, Audio, KS8842 GigE, EMGD, Video-in, SDHC, TSC2007, I2S, SDHC, ADV7180, BT, Radio
|1.0.1, 1.1, 1.2
|EOL
|No known driver issues
|unavailable 5/11
|-
|meego-ivi-ia32
|Crown Bay
|Intel Atom 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
|1.2
|1.3
|No known driver issues
|
|-
|meego-ivi-ia32
|Stephenville/Crossville
|Intel Atom E6xx Series for Embedded (Tunnel Creek)
|Oki Semiconductors ML7213 IVI IOH
|GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, EMGD, SD/SDIO/MMC, USB-OTG, TDM, sDVO
|1.2
|1.3
|[https://bugs.meego.com/buglist.cgi?short_desc=oki&classification=MeeGo%20Platform&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&version=1.2&version=1.3&short_desc_type=allwordssubstr&component=Kernel%20and%20drivers%20%28generic%29&product=MeeGo%20IVI CV-ML7213 bugs ]
|
|}

===MeeGo IVI Trunk Prototype Platforms===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! status
|-
|meego-ivi-ia32-conx
|Stephenville/Northville/Crossville
|Intel Atom 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, several issues open, visit [[IVI Images for ConneXt IOH]] for more information
|}

;ARM
:Jeremiah Foster and Jan-Simon Moeller are working on updates to enable automated weekly builds of MeeGo IVI images for the Beagleboard-XM.
:The suggested reference platform is the Beagleboard xM. The [[ARM/OMAP4_Panda|PandaBoard]] and [[ARM/Snowball|Snowball]] most likely will be supported in the future.
{| border="1"
! Image name
! Platform name
! chipset
! status
|-
| meego-ivi-armv7l
| Beagleboard xM
| OMAP 3
| Not yet smoke tested. No QA
|-
| meego-ivi-armv7l
| Tegra2
| ARM v7 rev 0
| Not yet smoke tested. No QA
|-
|}

===[http://sf2011.meego.com/sites/all/files/slides/meegocon2011developmentboardbofslides.pdf MeeGo IVI Development Boards]===

;IA32
{| border="1"
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! price/availability as of 5/11
! tested with MeeGo?
|-
|Intel Embedded Development Board 1-N450/1-D510
|N450 or D510
|Intel 82801HM
|SSD, WiFi, SATA, USB, SPI, GPIO, PCIe, UART, GigE, Audio, IEGD, DMA, I2C
|[http://edc.intel.com/Platforms/Atom-N450-D410-D510/Development-Board/#bd1-content=bd1-toggle~~visible-content $149 for registered users]
|[http://wiki.meego.com/Devices/Ideapad yes]
|}

;ARM

Per Stskeeps on meego-arm IRC on 6/2/2011, Nokia-provided N900 SGX530 drivers with hardfp extensions are known to work with SGX530 revisions 121 and 125. Which OMAP3 SoCs have revision 121 and 125 is not always straightforward to determine. dm8tbr reports problems with N900 hardfp drivers on Beagleboard xM. Stskeeps reports success with these drivers on Beagleboard C4. Tripzero reports success with hardfp drivers on old build of IGEPv2 that had the Cortex A8 processor.

{| border="1"
! Platform name
! Processor
! GPU; [[http://wiki.meego.com/ARM/hardfp hardfp?]]
! Memory
! Features
! price/availability as of 5/11
! tested with MeeGo?
|-
|[http://www.igloocommunity.org/ Snowball] (usable in end products)
|Cortex A-9 Dual-Core Nova A9500 1 GHz
|ARM Mali 400, [[ARM/Snowball|yes]]
|1 GB
|HDMI, WiFi b/g/n, Bluetooth, GPS, USB OTG, FSMC, HSI, Audio, MiPi CSI / Camera, LCD, MiPi DSI, UART, SPI, I2C, GPIO, SD/MMC, accelerometer, magnetometer, gyrometer, pressure sensor [[ARM/Snowball|(complete specs)]]
| [[ARM/Snowball|June]]
| [[ARM/Snowball|yes]]
|-
|[http://www.igep.es/index.php?option=com_content&view=article&id=46&Itemid=55 IGEPv2]
|[http://www.igep.es/public_docs/IGEPv2/HW_User_Manuals/MAN-PR-IGEP.0020.HW_USER_MANUAL.pdf DM3730 1 GHz]
|Imagination Technologies SGX530, yes? (tested by IGES with both TI and Nokia drivers)
|512 MB
|GigE, WiFi b/g, Bluetooth, USB OTG, USB Host, DVI-D, audio, SPI, UART, LCD, serial; [http://shop.igep.es/index.php?main_page=product_info&cPath=1&products_id=49 expansion board] with GSM, VGA, video in, camera, '''CAN'''
| 116.0€ and up plus 152.0€ for expansion board
| yes, but with older Cortex A8 build
|-
|[http://www.variscite.com/products/item/35-var-am35customboard Variscite VAR-AM3517 CustomBoard]
|[http://www.variscite.com/images/stories/DataSheets/VAR-SOM-AM35_1_15.pdf Cortex A-8 Sitara 600 MHz]
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|DMA, QCIF, LCD, SDTV, S-Video, USB, USB OTG, I2C, McSPI, GPIO, MMC, JTAG, '''CAN'''
|$1150 plus shipping
| no
|-
|[http://www.origenboard.org Samsung Origen]
|Samsung Exynos 4210 Cortex A-9 1 GHz
|ARM Mali 400, [http://forums.arm.com/index.php?/topic/14236-mali-gpus-linux-device-drivers-r2p0-05rel0-source-code-released/ reuse Snowball drivers?]
|1 GB
|HMDI, SD, WiFi, Bluetooth, audio, LCD, JTAG, camera
|[http://www.insignal.co.kr "sub-$200", June 25]
|no
|-
|[http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=IMX53QSB i.MX53 Quick Start Board]
|Cortex A-8 1 GHz
|Freescale GPUv3, [http://imxcommunity.org/profiles/blogs/ubuntu-rebuilt-with-hardfp yes]
|1 GB
|LVDS, LCD, HDMI, SPDIF, I2C, SSI, SPI, SD/MMC, microSD, SATA, GigE, USB, USB OTG, JTAG, UART, accelerometer
|$149
|[http://www.youtube.com/watch?feature=player_embedded&v=osDlTdl5lAk yes, similar HW]
|-
|[http://pandaboard.org/ Pandaboard]
|Cortex A-9 Dual-Core OMAP 4430 1 GHz
|Imagination Technologies SGX540, [http://article.gmane.org/gmane.comp.embedded.pandaboard/1771/match=hardfp not yet]
|1 GB
|SD/MMC, UART, Camera connector, USB OTG, Audio, GiGE, LCD connector, HDMI, WiFi, Bluetooth, JTAG, SPI, GPIO, I2C, McBSP
|[http://pandaboard.org/content/buy $179]
|[[ARM/OMAP4_Panda|yes]]
|-
|[http://beagle.s3.amazonaws.com/design/xM-A/BB_xM_SRM_A2_01.pdf Beagleboard Xm]
|Cortex A-8 DM3730 1GHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|512 MB
|uSD, USB, USB OTG, UART, McBSP, JTAG, GiGE, Audio, DVI-D, Camera connector, McBSP, I2C, GPIO, MMC2/3, ADC, LCD connector
|[http://beagleboard.org/buy $149]
|[[ARM/Meego_on_Beagleboard_from_scratch|yes]]
|-
|[http://beagleboard.org/static/BBSRM_latest.pdf Beagleboard C4]
|Cortex A-8 OMAP3530 720 MHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|I2C, I2S, SPI, MMC, USB, UART, USB OTG, S-Video, Audio, LCD, JTAG, GiGE
|[http://beagleboard.org/buy $125]
|[[ARM/Meego_IVI_on_Beagle|yes]]
|}

== Releases ==
* [[MeeGo IVI 1.2 | MeeGo IVI 1.2]]
* [http://meego.com/downloads/releases/1.1/meego-v1.1-in-vehicle-infotainment-ivi MeeGo IVI 1.1]
* [http://meego.com/downloads/releases/1.0/meego-v1.0-in-vehicle-infotainment-ivi MeeGo IVI 1.0]

== Resources ==
* IRC irc.freenode.org #meego-ivi
* Mailing list sign-up: http://lists.meego.com/listinfo/meego-ivi
* Mailing list archive: http://lists.meego.com/pipermail/meego-ivi/
* [[Presentations_about_meego-ivi#Presentations_and_Articles_about_MeeGo_IVI|Presentations and articles about meego-ivi]]
* [[In-vehicle/IVI for users and developers|IVI for users and developers]]
* [[IVITopic|Topics]]

[[Category:IVI]]

Quality/IVI 1.2 Update

2011-06-29T18:28:32Z

Joel: /* Kernel&Drivers */

== Bug List ==

{| border="1"
! LEGEND
! Comment
|-
| style="background: #33CC33"| || SRs completed, QA verified
|-
| style="background: #ee2222"| || Patch ready but still need SRs(accepted) and QA's verification
|}

=== Generic ===
{| border="1"
! ID(1.2.0)
! Status
! Resolution
! Flag
! ID(1.2)
! Status
! Resolution
! Summary
! Comment
|-
| 17502 || NEW || || U+ || 18913 || NEW || || [IVI] boot time is too long ~35 seconds ||
|}

=== Graphics ===
{| border="1"
! ID(1.2.0)
! Status
! Resolution
! Flag
! ID(1.2)
! Status
! Resolution
! Summary
! Comment
|- style="background: gray"
| 14641 || VERIFIED || WONTFIX || U? || 18976 || VERIFIED || WONTFIX || [IVI] Dual Head display support for Russellville/Northville ||
|-
| 16929 || NEW || || U? || 18978 || NEW || || IVI/Russellville: hang when switch from command line to X ||
|-
| 17177 || NEW || || U? || 18979 || NEW || ||[IVI]tear/black screen showed sometimes on LVDS'13 || Still reproduced with emgd-bin-2027
|- style="background: #ee2222"
| 17851 || RESOLVED || FIXED || U+ || 18919 || RESOLVED || FIXED ||[IVI] EMGD returns 24-bit XRGB visual when a 32-bit ARGB visual is needed for EGL support of QT|| NEW SR#21749 into 1.2.0:Update. Accepted SR#21631 into 1.2 branch and verified fixed.
|- style="background: #ee2222"
| 18707 || REOPENED || || U+ || 18918 || RELEASED || FIXED || [IVI] EMGD-bin: meego-ux-daemon crashes QT at various times (lock screen, task switcher, when idle) || NEW SR#21749 into 1.2.0:Update. Accepted SR#21631 into 1.2 branch and verified fixed.[Workaround for BMC# 16997]
|- style="background: #ee2222"
| 19087 || NEW || || U+ || 20194 || RESOLVED || FIXED || [IVI] X init failed if emgd update to 2001-4|| NEW SR#21749 into 1.2.0:Update. Accepted SR#21631 into 1.2 branch and verified fixed.
|- style="background: #ee2222"
| 19386 || RESOLVED || FIXED || U+ || 20195 || RESOLVED || FIXED || [IVI][REG] Lock screen not rendered on top of IVI desktop with emgd-bin-2001-4 || NEW SR#21749 into 1.2.0:Update. Accepted SR#21631 into 1.2 branch and verified fixed.
|}

=== Installation ===
{| border="1"
! ID(1.2.0)
! Status
! Resolution
! Flag
! ID(1.2)
! Status
! Resolution
! Summary
! Comment
|- style="background: #ee2222"
| 11781 || REOPENED || || U+ || 18915 || RESOLVED || FIXED || [IVI] Failed to install the meego ivi with text installation when the hdd is new brand || checking with Chengwei about SR
|-
| 15443 || NEW || || U+ || 18916 || NEW || || GUI Installer hangs when a storage device partition table cannot be read ||
|-
| 16876 || NEW || || U+ || 18917 || NEW || || [IVI] RV: GUI Installer takes a long time to launch ||
|}

=== Kernel&Drivers ===
{| border="1"
! ID(1.2.0)
! Status
! Resolution
! Flag
! ID(1.2)
! Status
! Resolution
! Summary
! Comment
|-
| 17135 || NEW || || U? || 18981 || NEW || || CrossvilleOKI: ioh_video_in initialize failed ||
|-
| 17467 || NEW || || U? || 18982 || NEW || || IVI/Crossville-OKI: touchscreen NOT function ||
|- style="background: #33CC33"
| 18980 || RELEASED || FIXED || U+ || 15611 || RELEASED || FIXED || Wrong driver is loading on Crown Bay's EG20T serial port ( same will occur on ML7213) ||
|- style="background: #33CC33"
| 18988 || RELEASED || FIXED || U+ || 17042 || RELEASED || FIXED || Turn off expensive debug config options for release ||
|- style="background: #33CC33"
| 18991 || RELEASED || FIXED || U+ || 17774 || RELEASED || FIXED || xen missing from kernel-adaptation-intel-automotive-devel ||
|- style="background: #33CC33"
| 16760 || RELEASED || FIXED || U+ || 18977 || RELEASED || FIXED || [IVI] Russellville: /dev/radio0 not found ||not in Trunk
|} 

=== meego-ux-ivi ===
{| border="1"
! ID(1.2.0)
! Status
! Resolution
! Flag
! ID(1.2)
! Status
! Resolution
! Summary
! Comment
|-
| 17391 || REOPENED || || U? || 18985 || NEW || || [IVI]screen lock function will kill running app ||
|- style="background: #33CC33"
| 18987 || RELEASED || FIXED || U+ || 16941 || RELEASED || FIXED || [IVI] no prompt give out when open deleted apps on desktop menu ||
|- style="background: #33CC33"
| 18989 || RELEASED || FIXED || U+ || 17184 || RELEASED || FIXED || [VoiceCommand] failed to launch task menu by "Tasks" ||
|- style="background: #33CC33"
| 18990 || RELEASED || FIXED || U+ || 17438 || RELEASED || FIXED || [IVI][VoiceCommand] failed to open apps directly ||
|- style="background: #ee2222"
| 17393 || ASSIGNED || || U+ || 20198 || NEW || || [IVI] screen should not lock when navigating || NEW SR#21784(partly fixed) into 1.2.0:Update. No SR into 1.2 branch.
|- style="background: #ee2222"
| 19052 || ASSIGNED || || U+ || 20200 || NEW || || [IVI]: IVI UX should be visible at all times by default || NEW SR#21784(partly fixed) into 1.2.0:Update. No SR into 1.2 branch.
|} 

=== Qt&QtContacts ===
{| border="1"
! ID(1.2.0)
! Status
! Resolution
! Flag
! ID(1.2)
! Status
! Resolution
! Summary
! Comment
|-
|18845 || NEW || || U+ || 18914 || NEW || || [IVI] Qt EGL graphics selects wrong "visual id" for secondary screen and crashes ||
|-
|18986 || NEW || || U? || 16997 || REOPENED || || meego-ux-daemon crashes QT at various times (lock screen, task switcher, when idle) || Workaround BMC#18707
|-
|18983 || NEW || || U? || 15948 || ASSIGNED || || [REG]Fail to run ut_qtcontacts_trackerplugin ||
|} 

=== Other Candidates ===
{| border="1"
! ID(1.2.0)
! Status
! Resolution
! Flag
! ID(1.2)
! Status
! Resolution
! Summary
! Comment
|-
| || || || || 17460 || NEW || || [IVI][REG] screen flickers when hovering cursors on the active buttons/text input box of Manage Apps ||
|-
| || || || || 19377 || NEW || || [IVI][REG] App switcher show black frame for launched app icons with emgd-2001 || '''Not reproduced with emgd-2027''' 
|-
| || || || R+, U+ || 19764 || NEEDINFO || || kernel-adaptation-intel-automotive source RPM fails to build ||
|-
| || || || R+, U+ || 10420 || NEW || || Failed to switch between X and console after kernel updated ||
|- style="background: #ee2222"
| 20276 || NEW || || U+ || 19353 || RELEASED || FIXED || Tracker fail to find the media files from USB disk. || No SR into 1.2.0 update. SR accepted into 1.2 branch.
|}

In-vehicle

2011-06-29T05:27:18Z

Joel: /* Links */

= 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: '''[http://meego.com/users/RudolfStreif 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:
*** Intel: '''[http://meego.com/users/jahoffmann Joel Hoffmann]'''
*** LG Electronics: '''[https://meego.com/users/hyungjin Hyungjin Jeon]'''
*** Nokia: '''[http://meego.com/users/alistair Alistair Adams]'''
*** Pelagicore: '''[http://meego.com/users/mikael Mikael Soderberg]'''
*** Visteon: '''[http://meego.com/users/PavelKonopelko Pavel Konopelko]'''

* Product Manager (cross-function across Working Group and Project Team)
** Unifies and prioritizes overall requirements set.
** Owns the roadmap.
** co-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 with the Lead Architects and Lead Designers on effort estimates and schedules.
** co-leads the Project Team together with the Product 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: '''[http://meego.com/users/joel Joel Clark (Intel)]'''

==== Working Group Meetings and Minutes ====
The Working Group meets regularly. Information on current and past meetings can be found on [[in-vehicle/working-group|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: '''[http://meego.com/users/tomcounihan 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: '''[http://meego.com/users/jeremiah 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.

== Shipping MeeGo IVI Products ==

* [http://news.softpedia.com/news/MeeGo-Powered-In-Vehicle-Information-System-Makes-Appearance-at-MWC-2011-184651.shtml Hawtai B11]
* [http://www.allaboutmeego.com/news/item/12918_Red_Flag_Software_announces_Me.php Geely EC8]
* iKarPC [http://files.icp-deutschland.de/produkte2/124273/web/icp/IKARPC-W08A-datasheet-20110222.pdf datasheet] and [http://www.contradata.it/cataloghi/IEI_2011_In_Vehicle_PC.pdf catalog page]

== MeeGo IVI Demos ==

* MeeGo IVI UI from ICS: [http://www.youtube.com/watch?v=ZWbfGzyLoh8 video] and [http://www.ics.com/services/qtquick info], including source code

== 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.

The roadmap pages are the central collaboration point on laying out the future of MeeGo IVI. Here architecture details, system diagrams, use cases, etc. are shared.

[[In-vehicle/Roadmap|View the Roadmap]]

Before any new feature is committed to the Roadmap, a feature request is created in http://bugs.meego.com. Current MeeGo IVI feature requests can be found [https://bugs.meego.com/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=MeeGo+IVI+Features&content= here]

[https://bugs.meego.com/enter_bug.cgi?product=MeeGo%20IVI%20Features 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 in the [[In-vehicle/Roadmap|IVI roadmap]].

== 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. [[Release Engineering/Release Versioning|MeeGo Release Versioning]] explains the build version numbering scheme. For example '''1.2.80.xx''' is a 1.2 Alpha build, '''1.2.90.xx''' is a 1.2 Beta build, '''1.2.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]

Each weekly build directory is named with a version number and date. IVI live .iso images are found under the ''images'' link in each weekly build directory. 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 under ''repos'' in the weekly build directory.

==Upcoming Releases==
===Meego 1.2.0 Update ===

;Update release dates
{| border="1"
! Update name
! Code Freeze
! Release
|-
|Update 1
|June 30
|July 7
|-
|Update 2
|August 11
|August 18
|-
|Update 3
|Sept 22
|Sept 29
|}

====Links====
When the first MeeGo 1.2.0 update is released July 7, 2011, the updated packages will show up in the following repository:
* [http://repo.meego.com/MeeGo/updates/1.2.0/repos/ MeeGo 1.2.0 Update Repositories]

* [https://bugs.meego.com/buglist.cgi?emailtype2=substring&field0-0-0=flagtypes.name&classification=MeeGo%20Platform&emailcc2=1&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&email2=ivi-bugs&version=1.2.0&type0-0-0=anywordssubstr&value0-0-0=meego_update_release_blocker%2B&known_name=ivibugs_1.2.0Update%2B MeeGo IVI 1.2.0 Update approved bugs ]

* [https://bugs.meego.com/buglist.cgi?emailtype2=substring&field0-0-0=flagtypes.name&classification=MeeGo%20Platform&emailcc2=1&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&email2=ivi-bugs&version=1.2.0&type0-0-0=anywordssubstr&value0-0-0=meego_update_release_blocker%3F&known_name=ivibugs_1.2.0Update%3F MeeGo IVI 1.2.0 Update proposed bugs ]

* [[ Quality/IVI 1.2 Update | IVI 1.2.0 Update bug fix status]]

===Meego 1.3===

;MeeGo 1.3 milestones
* New Package Planning complete: June 30
* Core Package integration / version freeze: July 15
* IVI Package integration / version freeze: August 5
* 1.3 branch and Release Candidate 1: September 16
* 1.3 final build: October 20
* 1.3 final release: October 28

==Platforms==
===MeeGo IVI Platforms Supported in Releases===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! Releases
! Plan
! status
! price/availability
|-
|meego-ivi-ia32
|Congatec IVI Kit (Russellville)
|Intel Atom Z5xx Series and Intel System Controller Hub US15Wx (eMenlow)
|Timberdale
|GPIO, DMA, SPI, I2C, UART, USB, IDE, Audio, KS8842 GigE, EMGD, Video-in, SDHC, TSC2007, I2S, SDHC, ADV7180, BT, Radio
|1.0.1, 1.1, 1.2
|EOL
|No known driver issues
|unavailable 5/11
|-
|meego-ivi-ia32
|Crown Bay
|Intel Atom 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
|1.2
|1.3
|No known driver issues
|
|-
|meego-ivi-ia32
|Stephenville/Crossville
|Intel Atom E6xx Series for Embedded (Tunnel Creek)
|Oki Semiconductors ML7213 IVI IOH
|GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, EMGD, SD/SDIO/MMC, USB-OTG, TDM, sDVO
|1.2
|1.3
|[https://bugs.meego.com/buglist.cgi?short_desc=oki&classification=MeeGo%20Platform&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&version=1.2&version=1.3&short_desc_type=allwordssubstr&component=Kernel%20and%20drivers%20%28generic%29&product=MeeGo%20IVI CV-ML7213 bugs ]
|
|}

===MeeGo IVI Trunk Prototype Platforms===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! status
|-
|meego-ivi-ia32-conx
|Stephenville/Northville/Crossville
|Intel Atom 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, several issues open, visit [[IVI Images for ConneXt IOH]] for more information
|}

;ARM
:Jeremiah Foster and Jan-Simon Moeller are working on updates to enable automated weekly builds of MeeGo IVI images for the Beagleboard-XM.
:The suggested reference platform is the Beagleboard xM. The [[ARM/OMAP4_Panda|PandaBoard]] and [[ARM/Snowball|Snowball]] most likely will be supported in the future.
{| border="1"
! Image name
! Platform name
! chipset
! status
|-
| meego-ivi-armv7l
| Beagleboard xM
| OMAP 3
| Not yet smoke tested. No QA
|-
| meego-ivi-armv7l
| Tegra2
| ARM v7 rev 0
| Not yet smoke tested. No QA
|-
|}

===[http://sf2011.meego.com/sites/all/files/slides/meegocon2011developmentboardbofslides.pdf MeeGo IVI Development Boards]===

;IA32
{| border="1"
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! price/availability as of 5/11
! tested with MeeGo?
|-
|Intel Embedded Development Board 1-N450/1-D510
|N450 or D510
|Intel 82801HM
|SSD, WiFi, SATA, USB, SPI, GPIO, PCIe, UART, GigE, Audio, IEGD, DMA, I2C
|[http://edc.intel.com/Platforms/Atom-N450-D410-D510/Development-Board/#bd1-content=bd1-toggle~~visible-content $149 for registered users]
|[http://wiki.meego.com/Devices/Ideapad yes]
|}

;ARM

Per Stskeeps on meego-arm IRC on 6/2/2011, Nokia-provided N900 SGX530 drivers with hardfp extensions are known to work with SGX530 revisions 121 and 125. Which OMAP3 SoCs have revision 121 and 125 is not always straightforward to determine. dm8tbr reports problems with N900 hardfp drivers on Beagleboard xM. Stskeeps reports success with these drivers on Beagleboard C4. Tripzero reports success with hardfp drivers on old build of IGEPv2 that had the Cortex A8 processor.

{| border="1"
! Platform name
! Processor
! GPU; [[http://wiki.meego.com/ARM/hardfp hardfp?]]
! Memory
! Features
! price/availability as of 5/11
! tested with MeeGo?
|-
|[http://www.igloocommunity.org/ Snowball] (usable in end products)
|Cortex A-9 Dual-Core Nova A9500 1 GHz
|ARM Mali 400, [[ARM/Snowball|yes]]
|1 GB
|HDMI, WiFi b/g/n, Bluetooth, GPS, USB OTG, FSMC, HSI, Audio, MiPi CSI / Camera, LCD, MiPi DSI, UART, SPI, I2C, GPIO, SD/MMC, accelerometer, magnetometer, gyrometer, pressure sensor [[ARM/Snowball|(complete specs)]]
| [[ARM/Snowball|June]]
| [[ARM/Snowball|yes]]
|-
|[http://www.igep.es/index.php?option=com_content&view=article&id=46&Itemid=55 IGEPv2]
|[http://www.igep.es/public_docs/IGEPv2/HW_User_Manuals/MAN-PR-IGEP.0020.HW_USER_MANUAL.pdf DM3730 1 GHz]
|Imagination Technologies SGX530, yes? (tested by IGES with both TI and Nokia drivers)
|512 MB
|GigE, WiFi b/g, Bluetooth, USB OTG, USB Host, DVI-D, audio, SPI, UART, LCD, serial; [http://shop.igep.es/index.php?main_page=product_info&cPath=1&products_id=49 expansion board] with GSM, VGA, video in, camera, '''CAN'''
| 116.0€ and up plus 152.0€ for expansion board
| yes, but with older Cortex A8 build
|-
|[http://www.variscite.com/products/item/35-var-am35customboard Variscite VAR-AM3517 CustomBoard]
|[http://www.variscite.com/images/stories/DataSheets/VAR-SOM-AM35_1_15.pdf Cortex A-8 Sitara 600 MHz]
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|DMA, QCIF, LCD, SDTV, S-Video, USB, USB OTG, I2C, McSPI, GPIO, MMC, JTAG, '''CAN'''
|$1150 plus shipping
| no
|-
|[http://www.origenboard.org Samsung Origen]
|Samsung Exynos 4210 Cortex A-9 1 GHz
|ARM Mali 400, [http://forums.arm.com/index.php?/topic/14236-mali-gpus-linux-device-drivers-r2p0-05rel0-source-code-released/ reuse Snowball drivers?]
|1 GB
|HMDI, SD, WiFi, Bluetooth, audio, LCD, JTAG, camera
|[http://www.insignal.co.kr "sub-$200", June 25]
|no
|-
|[http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=IMX53QSB i.MX53 Quick Start Board]
|Cortex A-8 1 GHz
|Freescale GPUv3, [http://imxcommunity.org/profiles/blogs/ubuntu-rebuilt-with-hardfp yes]
|1 GB
|LVDS, LCD, HDMI, SPDIF, I2C, SSI, SPI, SD/MMC, microSD, SATA, GigE, USB, USB OTG, JTAG, UART, accelerometer
|$149
|[http://www.youtube.com/watch?feature=player_embedded&v=osDlTdl5lAk yes, similar HW]
|-
|[http://pandaboard.org/ Pandaboard]
|Cortex A-9 Dual-Core OMAP 4430 1 GHz
|Imagination Technologies SGX540, [http://article.gmane.org/gmane.comp.embedded.pandaboard/1771/match=hardfp not yet]
|1 GB
|SD/MMC, UART, Camera connector, USB OTG, Audio, GiGE, LCD connector, HDMI, WiFi, Bluetooth, JTAG, SPI, GPIO, I2C, McBSP
|[http://pandaboard.org/content/buy $179]
|[[ARM/OMAP4_Panda|yes]]
|-
|[http://beagle.s3.amazonaws.com/design/xM-A/BB_xM_SRM_A2_01.pdf Beagleboard Xm]
|Cortex A-8 DM3730 1GHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|512 MB
|uSD, USB, USB OTG, UART, McBSP, JTAG, GiGE, Audio, DVI-D, Camera connector, McBSP, I2C, GPIO, MMC2/3, ADC, LCD connector
|[http://beagleboard.org/buy $149]
|[[ARM/Meego_on_Beagleboard_from_scratch|yes]]
|-
|[http://beagleboard.org/static/BBSRM_latest.pdf Beagleboard C4]
|Cortex A-8 OMAP3530 720 MHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|I2C, I2S, SPI, MMC, USB, UART, USB OTG, S-Video, Audio, LCD, JTAG, GiGE
|[http://beagleboard.org/buy $125]
|[[ARM/Meego_IVI_on_Beagle|yes]]
|}

== Releases ==
* [[MeeGo IVI 1.2 | MeeGo IVI 1.2]]
* [http://meego.com/downloads/releases/1.1/meego-v1.1-in-vehicle-infotainment-ivi MeeGo IVI 1.1]
* [http://meego.com/downloads/releases/1.0/meego-v1.0-in-vehicle-infotainment-ivi MeeGo IVI 1.0]

== Resources ==
* IRC irc.freenode.org #meego-ivi
* Mailing list sign-up: http://lists.meego.com/listinfo/meego-ivi
* Mailing list archive: http://lists.meego.com/pipermail/meego-ivi/
* [[Presentations_about_meego-ivi#Presentations_and_Articles_about_MeeGo_IVI|Presentations and articles about meego-ivi]]
* [[In-vehicle/IVI for users and developers|IVI for users and developers]]
* [[IVITopic|Topics]]

[[Category:IVI]]

In-vehicle

2011-06-29T05:18:59Z

Joel: /* Links */

= 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: '''[http://meego.com/users/RudolfStreif 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:
*** Intel: '''[http://meego.com/users/jahoffmann Joel Hoffmann]'''
*** LG Electronics: '''[https://meego.com/users/hyungjin Hyungjin Jeon]'''
*** Nokia: '''[http://meego.com/users/alistair Alistair Adams]'''
*** Pelagicore: '''[http://meego.com/users/mikael Mikael Soderberg]'''
*** Visteon: '''[http://meego.com/users/PavelKonopelko Pavel Konopelko]'''

* Product Manager (cross-function across Working Group and Project Team)
** Unifies and prioritizes overall requirements set.
** Owns the roadmap.
** co-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 with the Lead Architects and Lead Designers on effort estimates and schedules.
** co-leads the Project Team together with the Product 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: '''[http://meego.com/users/joel Joel Clark (Intel)]'''

==== Working Group Meetings and Minutes ====
The Working Group meets regularly. Information on current and past meetings can be found on [[in-vehicle/working-group|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: '''[http://meego.com/users/tomcounihan 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: '''[http://meego.com/users/jeremiah 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.

== Shipping MeeGo IVI Products ==

* [http://news.softpedia.com/news/MeeGo-Powered-In-Vehicle-Information-System-Makes-Appearance-at-MWC-2011-184651.shtml Hawtai B11]
* [http://www.allaboutmeego.com/news/item/12918_Red_Flag_Software_announces_Me.php Geely EC8]
* iKarPC [http://files.icp-deutschland.de/produkte2/124273/web/icp/IKARPC-W08A-datasheet-20110222.pdf datasheet] and [http://www.contradata.it/cataloghi/IEI_2011_In_Vehicle_PC.pdf catalog page]

== MeeGo IVI Demos ==

* MeeGo IVI UI from ICS: [http://www.youtube.com/watch?v=ZWbfGzyLoh8 video] and [http://www.ics.com/services/qtquick info], including source code

== 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.

The roadmap pages are the central collaboration point on laying out the future of MeeGo IVI. Here architecture details, system diagrams, use cases, etc. are shared.

[[In-vehicle/Roadmap|View the Roadmap]]

Before any new feature is committed to the Roadmap, a feature request is created in http://bugs.meego.com. Current MeeGo IVI feature requests can be found [https://bugs.meego.com/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=MeeGo+IVI+Features&content= here]

[https://bugs.meego.com/enter_bug.cgi?product=MeeGo%20IVI%20Features 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 in the [[In-vehicle/Roadmap|IVI roadmap]].

== 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. [[Release Engineering/Release Versioning|MeeGo Release Versioning]] explains the build version numbering scheme. For example '''1.2.80.xx''' is a 1.2 Alpha build, '''1.2.90.xx''' is a 1.2 Beta build, '''1.2.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]

Each weekly build directory is named with a version number and date. IVI live .iso images are found under the ''images'' link in each weekly build directory. 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 under ''repos'' in the weekly build directory.

==Upcoming Releases==
===Meego 1.2.0 Update ===

;Update release dates
{| border="1"
! Update name
! Code Freeze
! Release
|-
|Update 1
|June 30
|July 7
|-
|Update 2
|August 11
|August 18
|-
|Update 3
|Sept 22
|Sept 29
|}

====Links====
When the first MeeGo 1.2.0 update is released July 7, 2011, the updated packages will show up in the following repository:
* [http://repo.meego.com/MeeGo/updates/1.2.0/repos/ MeeGo 1.2.0 Update Repositories]

* [https://bugs.meego.com/buglist.cgi?emailtype2=substring&field0-0-0=flagtypes.name&classification=MeeGo%20Platform&emailcc2=1&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&email2=ivi-bugs&version=1.2.0&type0-0-0=anywordssubstr&value0-0-0=meego_update_release_blocker%2B&known_name=ivibugs_1.2.0Update%2B MeeGo IVI 1.2.0 Update approved bugs ]

* [https://bugs.meego.com/buglist.cgi?emailtype2=substring&field0-0-0=flagtypes.name&classification=MeeGo%20Platform&emailcc2=1&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&email2=ivi-bugs&version=1.2.0&type0-0-0=anywordssubstr&value0-0-0=meego_update_release_blocker%3F&known_name=ivibugs_1.2.0Update%3F MeeGo IVI 1.2.0 Update proposed bugs ]

===Meego 1.3===

;MeeGo 1.3 milestones
* New Package Planning complete: June 30
* Core Package integration / version freeze: July 15
* IVI Package integration / version freeze: August 5
* 1.3 branch and Release Candidate 1: September 16
* 1.3 final build: October 20
* 1.3 final release: October 28

==Platforms==
===MeeGo IVI Platforms Supported in Releases===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! Releases
! Plan
! status
! price/availability
|-
|meego-ivi-ia32
|Congatec IVI Kit (Russellville)
|Intel Atom Z5xx Series and Intel System Controller Hub US15Wx (eMenlow)
|Timberdale
|GPIO, DMA, SPI, I2C, UART, USB, IDE, Audio, KS8842 GigE, EMGD, Video-in, SDHC, TSC2007, I2S, SDHC, ADV7180, BT, Radio
|1.0.1, 1.1, 1.2
|EOL
|No known driver issues
|unavailable 5/11
|-
|meego-ivi-ia32
|Crown Bay
|Intel Atom 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
|1.2
|1.3
|No known driver issues
|
|-
|meego-ivi-ia32
|Stephenville/Crossville
|Intel Atom E6xx Series for Embedded (Tunnel Creek)
|Oki Semiconductors ML7213 IVI IOH
|GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, EMGD, SD/SDIO/MMC, USB-OTG, TDM, sDVO
|1.2
|1.3
|[https://bugs.meego.com/buglist.cgi?short_desc=oki&classification=MeeGo%20Platform&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&version=1.2&version=1.3&short_desc_type=allwordssubstr&component=Kernel%20and%20drivers%20%28generic%29&product=MeeGo%20IVI CV-ML7213 bugs ]
|
|}

===MeeGo IVI Trunk Prototype Platforms===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! status
|-
|meego-ivi-ia32-conx
|Stephenville/Northville/Crossville
|Intel Atom 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, several issues open, visit [[IVI Images for ConneXt IOH]] for more information
|}

;ARM
:Jeremiah Foster and Jan-Simon Moeller are working on updates to enable automated weekly builds of MeeGo IVI images for the Beagleboard-XM.
:The suggested reference platform is the Beagleboard xM. The [[ARM/OMAP4_Panda|PandaBoard]] and [[ARM/Snowball|Snowball]] most likely will be supported in the future.
{| border="1"
! Image name
! Platform name
! chipset
! status
|-
| meego-ivi-armv7l
| Beagleboard xM
| OMAP 3
| Not yet smoke tested. No QA
|-
| meego-ivi-armv7l
| Tegra2
| ARM v7 rev 0
| Not yet smoke tested. No QA
|-
|}

===[http://sf2011.meego.com/sites/all/files/slides/meegocon2011developmentboardbofslides.pdf MeeGo IVI Development Boards]===

;IA32
{| border="1"
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! price/availability as of 5/11
! tested with MeeGo?
|-
|Intel Embedded Development Board 1-N450/1-D510
|N450 or D510
|Intel 82801HM
|SSD, WiFi, SATA, USB, SPI, GPIO, PCIe, UART, GigE, Audio, IEGD, DMA, I2C
|[http://edc.intel.com/Platforms/Atom-N450-D410-D510/Development-Board/#bd1-content=bd1-toggle~~visible-content $149 for registered users]
|[http://wiki.meego.com/Devices/Ideapad yes]
|}

;ARM

Per Stskeeps on meego-arm IRC on 6/2/2011, Nokia-provided N900 SGX530 drivers with hardfp extensions are known to work with SGX530 revisions 121 and 125. Which OMAP3 SoCs have revision 121 and 125 is not always straightforward to determine. dm8tbr reports problems with N900 hardfp drivers on Beagleboard xM. Stskeeps reports success with these drivers on Beagleboard C4. Tripzero reports success with hardfp drivers on old build of IGEPv2 that had the Cortex A8 processor.

{| border="1"
! Platform name
! Processor
! GPU; [[http://wiki.meego.com/ARM/hardfp hardfp?]]
! Memory
! Features
! price/availability as of 5/11
! tested with MeeGo?
|-
|[http://www.igloocommunity.org/ Snowball] (usable in end products)
|Cortex A-9 Dual-Core Nova A9500 1 GHz
|ARM Mali 400, [[ARM/Snowball|yes]]
|1 GB
|HDMI, WiFi b/g/n, Bluetooth, GPS, USB OTG, FSMC, HSI, Audio, MiPi CSI / Camera, LCD, MiPi DSI, UART, SPI, I2C, GPIO, SD/MMC, accelerometer, magnetometer, gyrometer, pressure sensor [[ARM/Snowball|(complete specs)]]
| [[ARM/Snowball|June]]
| [[ARM/Snowball|yes]]
|-
|[http://www.igep.es/index.php?option=com_content&view=article&id=46&Itemid=55 IGEPv2]
|[http://www.igep.es/public_docs/IGEPv2/HW_User_Manuals/MAN-PR-IGEP.0020.HW_USER_MANUAL.pdf DM3730 1 GHz]
|Imagination Technologies SGX530, yes? (tested by IGES with both TI and Nokia drivers)
|512 MB
|GigE, WiFi b/g, Bluetooth, USB OTG, USB Host, DVI-D, audio, SPI, UART, LCD, serial; [http://shop.igep.es/index.php?main_page=product_info&cPath=1&products_id=49 expansion board] with GSM, VGA, video in, camera, '''CAN'''
| 116.0€ and up plus 152.0€ for expansion board
| yes, but with older Cortex A8 build
|-
|[http://www.variscite.com/products/item/35-var-am35customboard Variscite VAR-AM3517 CustomBoard]
|[http://www.variscite.com/images/stories/DataSheets/VAR-SOM-AM35_1_15.pdf Cortex A-8 Sitara 600 MHz]
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|DMA, QCIF, LCD, SDTV, S-Video, USB, USB OTG, I2C, McSPI, GPIO, MMC, JTAG, '''CAN'''
|$1150 plus shipping
| no
|-
|[http://www.origenboard.org Samsung Origen]
|Samsung Exynos 4210 Cortex A-9 1 GHz
|ARM Mali 400, [http://forums.arm.com/index.php?/topic/14236-mali-gpus-linux-device-drivers-r2p0-05rel0-source-code-released/ reuse Snowball drivers?]
|1 GB
|HMDI, SD, WiFi, Bluetooth, audio, LCD, JTAG, camera
|[http://www.insignal.co.kr "sub-$200", June 25]
|no
|-
|[http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=IMX53QSB i.MX53 Quick Start Board]
|Cortex A-8 1 GHz
|Freescale GPUv3, [http://imxcommunity.org/profiles/blogs/ubuntu-rebuilt-with-hardfp yes]
|1 GB
|LVDS, LCD, HDMI, SPDIF, I2C, SSI, SPI, SD/MMC, microSD, SATA, GigE, USB, USB OTG, JTAG, UART, accelerometer
|$149
|[http://www.youtube.com/watch?feature=player_embedded&v=osDlTdl5lAk yes, similar HW]
|-
|[http://pandaboard.org/ Pandaboard]
|Cortex A-9 Dual-Core OMAP 4430 1 GHz
|Imagination Technologies SGX540, [http://article.gmane.org/gmane.comp.embedded.pandaboard/1771/match=hardfp not yet]
|1 GB
|SD/MMC, UART, Camera connector, USB OTG, Audio, GiGE, LCD connector, HDMI, WiFi, Bluetooth, JTAG, SPI, GPIO, I2C, McBSP
|[http://pandaboard.org/content/buy $179]
|[[ARM/OMAP4_Panda|yes]]
|-
|[http://beagle.s3.amazonaws.com/design/xM-A/BB_xM_SRM_A2_01.pdf Beagleboard Xm]
|Cortex A-8 DM3730 1GHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|512 MB
|uSD, USB, USB OTG, UART, McBSP, JTAG, GiGE, Audio, DVI-D, Camera connector, McBSP, I2C, GPIO, MMC2/3, ADC, LCD connector
|[http://beagleboard.org/buy $149]
|[[ARM/Meego_on_Beagleboard_from_scratch|yes]]
|-
|[http://beagleboard.org/static/BBSRM_latest.pdf Beagleboard C4]
|Cortex A-8 OMAP3530 720 MHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|I2C, I2S, SPI, MMC, USB, UART, USB OTG, S-Video, Audio, LCD, JTAG, GiGE
|[http://beagleboard.org/buy $125]
|[[ARM/Meego_IVI_on_Beagle|yes]]
|}

== Releases ==
* [[MeeGo IVI 1.2 | MeeGo IVI 1.2]]
* [http://meego.com/downloads/releases/1.1/meego-v1.1-in-vehicle-infotainment-ivi MeeGo IVI 1.1]
* [http://meego.com/downloads/releases/1.0/meego-v1.0-in-vehicle-infotainment-ivi MeeGo IVI 1.0]

== Resources ==
* IRC irc.freenode.org #meego-ivi
* Mailing list sign-up: http://lists.meego.com/listinfo/meego-ivi
* Mailing list archive: http://lists.meego.com/pipermail/meego-ivi/
* [[Presentations_about_meego-ivi#Presentations_and_Articles_about_MeeGo_IVI|Presentations and articles about meego-ivi]]
* [[In-vehicle/IVI for users and developers|IVI for users and developers]]
* [[IVITopic|Topics]]

[[Category:IVI]]

In-vehicle

2011-06-29T05:16:43Z

Joel: /* Meego 1.2.0 Update */

= 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: '''[http://meego.com/users/RudolfStreif 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:
*** Intel: '''[http://meego.com/users/jahoffmann Joel Hoffmann]'''
*** LG Electronics: '''[https://meego.com/users/hyungjin Hyungjin Jeon]'''
*** Nokia: '''[http://meego.com/users/alistair Alistair Adams]'''
*** Pelagicore: '''[http://meego.com/users/mikael Mikael Soderberg]'''
*** Visteon: '''[http://meego.com/users/PavelKonopelko Pavel Konopelko]'''

* Product Manager (cross-function across Working Group and Project Team)
** Unifies and prioritizes overall requirements set.
** Owns the roadmap.
** co-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 with the Lead Architects and Lead Designers on effort estimates and schedules.
** co-leads the Project Team together with the Product 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: '''[http://meego.com/users/joel Joel Clark (Intel)]'''

==== Working Group Meetings and Minutes ====
The Working Group meets regularly. Information on current and past meetings can be found on [[in-vehicle/working-group|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: '''[http://meego.com/users/tomcounihan 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: '''[http://meego.com/users/jeremiah 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.

== Shipping MeeGo IVI Products ==

* [http://news.softpedia.com/news/MeeGo-Powered-In-Vehicle-Information-System-Makes-Appearance-at-MWC-2011-184651.shtml Hawtai B11]
* [http://www.allaboutmeego.com/news/item/12918_Red_Flag_Software_announces_Me.php Geely EC8]
* iKarPC [http://files.icp-deutschland.de/produkte2/124273/web/icp/IKARPC-W08A-datasheet-20110222.pdf datasheet] and [http://www.contradata.it/cataloghi/IEI_2011_In_Vehicle_PC.pdf catalog page]

== MeeGo IVI Demos ==

* MeeGo IVI UI from ICS: [http://www.youtube.com/watch?v=ZWbfGzyLoh8 video] and [http://www.ics.com/services/qtquick info], including source code

== 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.

The roadmap pages are the central collaboration point on laying out the future of MeeGo IVI. Here architecture details, system diagrams, use cases, etc. are shared.

[[In-vehicle/Roadmap|View the Roadmap]]

Before any new feature is committed to the Roadmap, a feature request is created in http://bugs.meego.com. Current MeeGo IVI feature requests can be found [https://bugs.meego.com/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=MeeGo+IVI+Features&content= here]

[https://bugs.meego.com/enter_bug.cgi?product=MeeGo%20IVI%20Features 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 in the [[In-vehicle/Roadmap|IVI roadmap]].

== 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. [[Release Engineering/Release Versioning|MeeGo Release Versioning]] explains the build version numbering scheme. For example '''1.2.80.xx''' is a 1.2 Alpha build, '''1.2.90.xx''' is a 1.2 Beta build, '''1.2.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]

Each weekly build directory is named with a version number and date. IVI live .iso images are found under the ''images'' link in each weekly build directory. 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 under ''repos'' in the weekly build directory.

==Upcoming Releases==
===Meego 1.2.0 Update ===

;Update release dates
{| border="1"
! Update name
! Code Freeze
! Release
|-
|Update 1
|June 30
|July 7
|-
|Update 2
|August 11
|August 18
|-
|Update 3
|Sept 22
|Sept 29
|}

====Links====

* [http://repo.meego.com/MeeGo/updates/1.2.0/repos/ MeeGo 1.2.0 Update Repositories]

* [https://bugs.meego.com/buglist.cgi?emailtype2=substring&field0-0-0=flagtypes.name&classification=MeeGo%20Platform&emailcc2=1&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&email2=ivi-bugs&version=1.2.0&type0-0-0=anywordssubstr&value0-0-0=meego_update_release_blocker%2B&known_name=ivibugs_1.2.0Update%2B MeeGo IVI 1.2.0 Update approved bugs ]

* [https://bugs.meego.com/buglist.cgi?emailtype2=substring&field0-0-0=flagtypes.name&classification=MeeGo%20Platform&emailcc2=1&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&email2=ivi-bugs&version=1.2.0&type0-0-0=anywordssubstr&value0-0-0=meego_update_release_blocker%3F&known_name=ivibugs_1.2.0Update%3F MeeGo IVI 1.2.0 Update proposed bugs ]

===Meego 1.3===

;MeeGo 1.3 milestones
* New Package Planning complete: June 30
* Core Package integration / version freeze: July 15
* IVI Package integration / version freeze: August 5
* 1.3 branch and Release Candidate 1: September 16
* 1.3 final build: October 20
* 1.3 final release: October 28

==Platforms==
===MeeGo IVI Platforms Supported in Releases===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! Releases
! Plan
! status
! price/availability
|-
|meego-ivi-ia32
|Congatec IVI Kit (Russellville)
|Intel Atom Z5xx Series and Intel System Controller Hub US15Wx (eMenlow)
|Timberdale
|GPIO, DMA, SPI, I2C, UART, USB, IDE, Audio, KS8842 GigE, EMGD, Video-in, SDHC, TSC2007, I2S, SDHC, ADV7180, BT, Radio
|1.0.1, 1.1, 1.2
|EOL
|No known driver issues
|unavailable 5/11
|-
|meego-ivi-ia32
|Crown Bay
|Intel Atom 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
|1.2
|1.3
|No known driver issues
|
|-
|meego-ivi-ia32
|Stephenville/Crossville
|Intel Atom E6xx Series for Embedded (Tunnel Creek)
|Oki Semiconductors ML7213 IVI IOH
|GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, EMGD, SD/SDIO/MMC, USB-OTG, TDM, sDVO
|1.2
|1.3
|[https://bugs.meego.com/buglist.cgi?short_desc=oki&classification=MeeGo%20Platform&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&version=1.2&version=1.3&short_desc_type=allwordssubstr&component=Kernel%20and%20drivers%20%28generic%29&product=MeeGo%20IVI CV-ML7213 bugs ]
|
|}

===MeeGo IVI Trunk Prototype Platforms===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! status
|-
|meego-ivi-ia32-conx
|Stephenville/Northville/Crossville
|Intel Atom 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, several issues open, visit [[IVI Images for ConneXt IOH]] for more information
|}

;ARM
:Jeremiah Foster and Jan-Simon Moeller are working on updates to enable automated weekly builds of MeeGo IVI images for the Beagleboard-XM.
:The suggested reference platform is the Beagleboard xM. The [[ARM/OMAP4_Panda|PandaBoard]] and [[ARM/Snowball|Snowball]] most likely will be supported in the future.
{| border="1"
! Image name
! Platform name
! chipset
! status
|-
| meego-ivi-armv7l
| Beagleboard xM
| OMAP 3
| Not yet smoke tested. No QA
|-
| meego-ivi-armv7l
| Tegra2
| ARM v7 rev 0
| Not yet smoke tested. No QA
|-
|}

===[http://sf2011.meego.com/sites/all/files/slides/meegocon2011developmentboardbofslides.pdf MeeGo IVI Development Boards]===

;IA32
{| border="1"
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! price/availability as of 5/11
! tested with MeeGo?
|-
|Intel Embedded Development Board 1-N450/1-D510
|N450 or D510
|Intel 82801HM
|SSD, WiFi, SATA, USB, SPI, GPIO, PCIe, UART, GigE, Audio, IEGD, DMA, I2C
|[http://edc.intel.com/Platforms/Atom-N450-D410-D510/Development-Board/#bd1-content=bd1-toggle~~visible-content $149 for registered users]
|[http://wiki.meego.com/Devices/Ideapad yes]
|}

;ARM

Per Stskeeps on meego-arm IRC on 6/2/2011, Nokia-provided N900 SGX530 drivers with hardfp extensions are known to work with SGX530 revisions 121 and 125. Which OMAP3 SoCs have revision 121 and 125 is not always straightforward to determine. dm8tbr reports problems with N900 hardfp drivers on Beagleboard xM. Stskeeps reports success with these drivers on Beagleboard C4. Tripzero reports success with hardfp drivers on old build of IGEPv2 that had the Cortex A8 processor.

{| border="1"
! Platform name
! Processor
! GPU; [[http://wiki.meego.com/ARM/hardfp hardfp?]]
! Memory
! Features
! price/availability as of 5/11
! tested with MeeGo?
|-
|[http://www.igloocommunity.org/ Snowball] (usable in end products)
|Cortex A-9 Dual-Core Nova A9500 1 GHz
|ARM Mali 400, [[ARM/Snowball|yes]]
|1 GB
|HDMI, WiFi b/g/n, Bluetooth, GPS, USB OTG, FSMC, HSI, Audio, MiPi CSI / Camera, LCD, MiPi DSI, UART, SPI, I2C, GPIO, SD/MMC, accelerometer, magnetometer, gyrometer, pressure sensor [[ARM/Snowball|(complete specs)]]
| [[ARM/Snowball|June]]
| [[ARM/Snowball|yes]]
|-
|[http://www.igep.es/index.php?option=com_content&view=article&id=46&Itemid=55 IGEPv2]
|[http://www.igep.es/public_docs/IGEPv2/HW_User_Manuals/MAN-PR-IGEP.0020.HW_USER_MANUAL.pdf DM3730 1 GHz]
|Imagination Technologies SGX530, yes? (tested by IGES with both TI and Nokia drivers)
|512 MB
|GigE, WiFi b/g, Bluetooth, USB OTG, USB Host, DVI-D, audio, SPI, UART, LCD, serial; [http://shop.igep.es/index.php?main_page=product_info&cPath=1&products_id=49 expansion board] with GSM, VGA, video in, camera, '''CAN'''
| 116.0€ and up plus 152.0€ for expansion board
| yes, but with older Cortex A8 build
|-
|[http://www.variscite.com/products/item/35-var-am35customboard Variscite VAR-AM3517 CustomBoard]
|[http://www.variscite.com/images/stories/DataSheets/VAR-SOM-AM35_1_15.pdf Cortex A-8 Sitara 600 MHz]
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|DMA, QCIF, LCD, SDTV, S-Video, USB, USB OTG, I2C, McSPI, GPIO, MMC, JTAG, '''CAN'''
|$1150 plus shipping
| no
|-
|[http://www.origenboard.org Samsung Origen]
|Samsung Exynos 4210 Cortex A-9 1 GHz
|ARM Mali 400, [http://forums.arm.com/index.php?/topic/14236-mali-gpus-linux-device-drivers-r2p0-05rel0-source-code-released/ reuse Snowball drivers?]
|1 GB
|HMDI, SD, WiFi, Bluetooth, audio, LCD, JTAG, camera
|[http://www.insignal.co.kr "sub-$200", June 25]
|no
|-
|[http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=IMX53QSB i.MX53 Quick Start Board]
|Cortex A-8 1 GHz
|Freescale GPUv3, [http://imxcommunity.org/profiles/blogs/ubuntu-rebuilt-with-hardfp yes]
|1 GB
|LVDS, LCD, HDMI, SPDIF, I2C, SSI, SPI, SD/MMC, microSD, SATA, GigE, USB, USB OTG, JTAG, UART, accelerometer
|$149
|[http://www.youtube.com/watch?feature=player_embedded&v=osDlTdl5lAk yes, similar HW]
|-
|[http://pandaboard.org/ Pandaboard]
|Cortex A-9 Dual-Core OMAP 4430 1 GHz
|Imagination Technologies SGX540, [http://article.gmane.org/gmane.comp.embedded.pandaboard/1771/match=hardfp not yet]
|1 GB
|SD/MMC, UART, Camera connector, USB OTG, Audio, GiGE, LCD connector, HDMI, WiFi, Bluetooth, JTAG, SPI, GPIO, I2C, McBSP
|[http://pandaboard.org/content/buy $179]
|[[ARM/OMAP4_Panda|yes]]
|-
|[http://beagle.s3.amazonaws.com/design/xM-A/BB_xM_SRM_A2_01.pdf Beagleboard Xm]
|Cortex A-8 DM3730 1GHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|512 MB
|uSD, USB, USB OTG, UART, McBSP, JTAG, GiGE, Audio, DVI-D, Camera connector, McBSP, I2C, GPIO, MMC2/3, ADC, LCD connector
|[http://beagleboard.org/buy $149]
|[[ARM/Meego_on_Beagleboard_from_scratch|yes]]
|-
|[http://beagleboard.org/static/BBSRM_latest.pdf Beagleboard C4]
|Cortex A-8 OMAP3530 720 MHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|I2C, I2S, SPI, MMC, USB, UART, USB OTG, S-Video, Audio, LCD, JTAG, GiGE
|[http://beagleboard.org/buy $125]
|[[ARM/Meego_IVI_on_Beagle|yes]]
|}

== Releases ==
* [[MeeGo IVI 1.2 | MeeGo IVI 1.2]]
* [http://meego.com/downloads/releases/1.1/meego-v1.1-in-vehicle-infotainment-ivi MeeGo IVI 1.1]
* [http://meego.com/downloads/releases/1.0/meego-v1.0-in-vehicle-infotainment-ivi MeeGo IVI 1.0]

== Resources ==
* IRC irc.freenode.org #meego-ivi
* Mailing list sign-up: http://lists.meego.com/listinfo/meego-ivi
* Mailing list archive: http://lists.meego.com/pipermail/meego-ivi/
* [[Presentations_about_meego-ivi#Presentations_and_Articles_about_MeeGo_IVI|Presentations and articles about meego-ivi]]
* [[In-vehicle/IVI for users and developers|IVI for users and developers]]
* [[IVITopic|Topics]]

[[Category:IVI]]

In-vehicle

2011-06-29T04:46:03Z

Joel: /* Platforms */

= 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: '''[http://meego.com/users/RudolfStreif 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:
*** Intel: '''[http://meego.com/users/jahoffmann Joel Hoffmann]'''
*** LG Electronics: '''[https://meego.com/users/hyungjin Hyungjin Jeon]'''
*** Nokia: '''[http://meego.com/users/alistair Alistair Adams]'''
*** Pelagicore: '''[http://meego.com/users/mikael Mikael Soderberg]'''
*** Visteon: '''[http://meego.com/users/PavelKonopelko Pavel Konopelko]'''

* Product Manager (cross-function across Working Group and Project Team)
** Unifies and prioritizes overall requirements set.
** Owns the roadmap.
** co-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 with the Lead Architects and Lead Designers on effort estimates and schedules.
** co-leads the Project Team together with the Product 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: '''[http://meego.com/users/joel Joel Clark (Intel)]'''

==== Working Group Meetings and Minutes ====
The Working Group meets regularly. Information on current and past meetings can be found on [[in-vehicle/working-group|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: '''[http://meego.com/users/tomcounihan 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: '''[http://meego.com/users/jeremiah 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.

== Shipping MeeGo IVI Products ==

* [http://news.softpedia.com/news/MeeGo-Powered-In-Vehicle-Information-System-Makes-Appearance-at-MWC-2011-184651.shtml Hawtai B11]
* [http://www.allaboutmeego.com/news/item/12918_Red_Flag_Software_announces_Me.php Geely EC8]
* iKarPC [http://files.icp-deutschland.de/produkte2/124273/web/icp/IKARPC-W08A-datasheet-20110222.pdf datasheet] and [http://www.contradata.it/cataloghi/IEI_2011_In_Vehicle_PC.pdf catalog page]

== MeeGo IVI Demos ==

* MeeGo IVI UI from ICS: [http://www.youtube.com/watch?v=ZWbfGzyLoh8 video] and [http://www.ics.com/services/qtquick info], including source code

== 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.

The roadmap pages are the central collaboration point on laying out the future of MeeGo IVI. Here architecture details, system diagrams, use cases, etc. are shared.

[[In-vehicle/Roadmap|View the Roadmap]]

Before any new feature is committed to the Roadmap, a feature request is created in http://bugs.meego.com. Current MeeGo IVI feature requests can be found [https://bugs.meego.com/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=MeeGo+IVI+Features&content= here]

[https://bugs.meego.com/enter_bug.cgi?product=MeeGo%20IVI%20Features 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 in the [[In-vehicle/Roadmap|IVI roadmap]].

== 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. [[Release Engineering/Release Versioning|MeeGo Release Versioning]] explains the build version numbering scheme. For example '''1.2.80.xx''' is a 1.2 Alpha build, '''1.2.90.xx''' is a 1.2 Beta build, '''1.2.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]

Each weekly build directory is named with a version number and date. IVI live .iso images are found under the ''images'' link in each weekly build directory. 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 under ''repos'' in the weekly build directory.

==Upcoming Releases==
===Meego 1.2.0 Update ===

MeeGo 1.2.0 Update is scheduled for release July 7

Code freeze for MeeGo 1.2.0 Update is scheduled for June 30.

Additional updates can be expected every 6 weeks.

====Links====

* [http://repo.meego.com/MeeGo/updates/1.2.0/repos/ MeeGo 1.2.0 Update Repositories]

* [https://bugs.meego.com/buglist.cgi?emailtype2=substring&field0-0-0=flagtypes.name&classification=MeeGo%20Platform&emailcc2=1&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&email2=ivi-bugs&version=1.2.0&type0-0-0=anywordssubstr&value0-0-0=meego_update_release_blocker%2B&known_name=ivibugs_1.2.0Update%2B MeeGo IVI 1.2.0 Update approved bugs ]

* [https://bugs.meego.com/buglist.cgi?emailtype2=substring&field0-0-0=flagtypes.name&classification=MeeGo%20Platform&emailcc2=1&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&email2=ivi-bugs&version=1.2.0&type0-0-0=anywordssubstr&value0-0-0=meego_update_release_blocker%3F&known_name=ivibugs_1.2.0Update%3F MeeGo IVI 1.2.0 Update proposed bugs ]

==Platforms==
===MeeGo IVI Platforms Supported in Releases===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! Releases
! Plan
! status
! price/availability
|-
|meego-ivi-ia32
|Congatec IVI Kit (Russellville)
|Intel Atom Z5xx Series and Intel System Controller Hub US15Wx (eMenlow)
|Timberdale
|GPIO, DMA, SPI, I2C, UART, USB, IDE, Audio, KS8842 GigE, EMGD, Video-in, SDHC, TSC2007, I2S, SDHC, ADV7180, BT, Radio
|1.0.1, 1.1, 1.2
|EOL
|No known driver issues
|unavailable 5/11
|-
|meego-ivi-ia32
|Crown Bay
|Intel Atom 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
|1.2
|1.3
|No known driver issues
|
|-
|meego-ivi-ia32
|Stephenville/Crossville
|Intel Atom E6xx Series for Embedded (Tunnel Creek)
|Oki Semiconductors ML7213 IVI IOH
|GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, EMGD, SD/SDIO/MMC, USB-OTG, TDM, sDVO
|1.2
|1.3
|[https://bugs.meego.com/buglist.cgi?short_desc=oki&classification=MeeGo%20Platform&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&version=1.2&version=1.3&short_desc_type=allwordssubstr&component=Kernel%20and%20drivers%20%28generic%29&product=MeeGo%20IVI CV-ML7213 bugs ]
|
|}

===MeeGo IVI Trunk Prototype Platforms===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! status
|-
|meego-ivi-ia32-conx
|Stephenville/Northville/Crossville
|Intel Atom 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, several issues open, visit [[IVI Images for ConneXt IOH]] for more information
|}

;ARM
:Jeremiah Foster and Jan-Simon Moeller are working on updates to enable automated weekly builds of MeeGo IVI images for the Beagleboard-XM.
:The suggested reference platform is the Beagleboard xM. The [[ARM/OMAP4_Panda|PandaBoard]] and [[ARM/Snowball|Snowball]] most likely will be supported in the future.
{| border="1"
! Image name
! Platform name
! chipset
! status
|-
| meego-ivi-armv7l
| Beagleboard xM
| OMAP 3
| Not yet smoke tested. No QA
|-
| meego-ivi-armv7l
| Tegra2
| ARM v7 rev 0
| Not yet smoke tested. No QA
|-
|}

===[http://sf2011.meego.com/sites/all/files/slides/meegocon2011developmentboardbofslides.pdf MeeGo IVI Development Boards]===

;IA32
{| border="1"
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! price/availability as of 5/11
! tested with MeeGo?
|-
|Intel Embedded Development Board 1-N450/1-D510
|N450 or D510
|Intel 82801HM
|SSD, WiFi, SATA, USB, SPI, GPIO, PCIe, UART, GigE, Audio, IEGD, DMA, I2C
|[http://edc.intel.com/Platforms/Atom-N450-D410-D510/Development-Board/#bd1-content=bd1-toggle~~visible-content $149 for registered users]
|[http://wiki.meego.com/Devices/Ideapad yes]
|}

;ARM

Per Stskeeps on meego-arm IRC on 6/2/2011, Nokia-provided N900 SGX530 drivers with hardfp extensions are known to work with SGX530 revisions 121 and 125. Which OMAP3 SoCs have revision 121 and 125 is not always straightforward to determine. dm8tbr reports problems with N900 hardfp drivers on Beagleboard xM. Stskeeps reports success with these drivers on Beagleboard C4. Tripzero reports success with hardfp drivers on old build of IGEPv2 that had the Cortex A8 processor.

{| border="1"
! Platform name
! Processor
! GPU; [[http://wiki.meego.com/ARM/hardfp hardfp?]]
! Memory
! Features
! price/availability as of 5/11
! tested with MeeGo?
|-
|[http://www.igloocommunity.org/ Snowball] (usable in end products)
|Cortex A-9 Dual-Core Nova A9500 1 GHz
|ARM Mali 400, [[ARM/Snowball|yes]]
|1 GB
|HDMI, WiFi b/g/n, Bluetooth, GPS, USB OTG, FSMC, HSI, Audio, MiPi CSI / Camera, LCD, MiPi DSI, UART, SPI, I2C, GPIO, SD/MMC, accelerometer, magnetometer, gyrometer, pressure sensor [[ARM/Snowball|(complete specs)]]
| [[ARM/Snowball|June]]
| [[ARM/Snowball|yes]]
|-
|[http://www.igep.es/index.php?option=com_content&view=article&id=46&Itemid=55 IGEPv2]
|[http://www.igep.es/public_docs/IGEPv2/HW_User_Manuals/MAN-PR-IGEP.0020.HW_USER_MANUAL.pdf DM3730 1 GHz]
|Imagination Technologies SGX530, yes? (tested by IGES with both TI and Nokia drivers)
|512 MB
|GigE, WiFi b/g, Bluetooth, USB OTG, USB Host, DVI-D, audio, SPI, UART, LCD, serial; [http://shop.igep.es/index.php?main_page=product_info&cPath=1&products_id=49 expansion board] with GSM, VGA, video in, camera, '''CAN'''
| 116.0€ and up plus 152.0€ for expansion board
| yes, but with older Cortex A8 build
|-
|[http://www.variscite.com/products/item/35-var-am35customboard Variscite VAR-AM3517 CustomBoard]
|[http://www.variscite.com/images/stories/DataSheets/VAR-SOM-AM35_1_15.pdf Cortex A-8 Sitara 600 MHz]
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|DMA, QCIF, LCD, SDTV, S-Video, USB, USB OTG, I2C, McSPI, GPIO, MMC, JTAG, '''CAN'''
|$1150 plus shipping
| no
|-
|[http://www.origenboard.org Samsung Origen]
|Samsung Exynos 4210 Cortex A-9 1 GHz
|ARM Mali 400, [http://forums.arm.com/index.php?/topic/14236-mali-gpus-linux-device-drivers-r2p0-05rel0-source-code-released/ reuse Snowball drivers?]
|1 GB
|HMDI, SD, WiFi, Bluetooth, audio, LCD, JTAG, camera
|[http://www.insignal.co.kr "sub-$200", June 25]
|no
|-
|[http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=IMX53QSB i.MX53 Quick Start Board]
|Cortex A-8 1 GHz
|Freescale GPUv3, [http://imxcommunity.org/profiles/blogs/ubuntu-rebuilt-with-hardfp yes]
|1 GB
|LVDS, LCD, HDMI, SPDIF, I2C, SSI, SPI, SD/MMC, microSD, SATA, GigE, USB, USB OTG, JTAG, UART, accelerometer
|$149
|[http://www.youtube.com/watch?feature=player_embedded&v=osDlTdl5lAk yes, similar HW]
|-
|[http://pandaboard.org/ Pandaboard]
|Cortex A-9 Dual-Core OMAP 4430 1 GHz
|Imagination Technologies SGX540, [http://article.gmane.org/gmane.comp.embedded.pandaboard/1771/match=hardfp not yet]
|1 GB
|SD/MMC, UART, Camera connector, USB OTG, Audio, GiGE, LCD connector, HDMI, WiFi, Bluetooth, JTAG, SPI, GPIO, I2C, McBSP
|[http://pandaboard.org/content/buy $179]
|[[ARM/OMAP4_Panda|yes]]
|-
|[http://beagle.s3.amazonaws.com/design/xM-A/BB_xM_SRM_A2_01.pdf Beagleboard Xm]
|Cortex A-8 DM3730 1GHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|512 MB
|uSD, USB, USB OTG, UART, McBSP, JTAG, GiGE, Audio, DVI-D, Camera connector, McBSP, I2C, GPIO, MMC2/3, ADC, LCD connector
|[http://beagleboard.org/buy $149]
|[[ARM/Meego_on_Beagleboard_from_scratch|yes]]
|-
|[http://beagleboard.org/static/BBSRM_latest.pdf Beagleboard C4]
|Cortex A-8 OMAP3530 720 MHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|I2C, I2S, SPI, MMC, USB, UART, USB OTG, S-Video, Audio, LCD, JTAG, GiGE
|[http://beagleboard.org/buy $125]
|[[ARM/Meego_IVI_on_Beagle|yes]]
|}

== Releases ==
* [[MeeGo IVI 1.2 | MeeGo IVI 1.2]]
* [http://meego.com/downloads/releases/1.1/meego-v1.1-in-vehicle-infotainment-ivi MeeGo IVI 1.1]
* [http://meego.com/downloads/releases/1.0/meego-v1.0-in-vehicle-infotainment-ivi MeeGo IVI 1.0]

== Resources ==
* IRC irc.freenode.org #meego-ivi
* Mailing list sign-up: http://lists.meego.com/listinfo/meego-ivi
* Mailing list archive: http://lists.meego.com/pipermail/meego-ivi/
* [[Presentations_about_meego-ivi#Presentations_and_Articles_about_MeeGo_IVI|Presentations and articles about meego-ivi]]
* [[In-vehicle/IVI for users and developers|IVI for users and developers]]
* [[IVITopic|Topics]]

[[Category:IVI]]

In-vehicle

2011-06-29T04:32:31Z

Joel: /* MeeGo IVI Weekly Builds */

= 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: '''[http://meego.com/users/RudolfStreif 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:
*** Intel: '''[http://meego.com/users/jahoffmann Joel Hoffmann]'''
*** LG Electronics: '''[https://meego.com/users/hyungjin Hyungjin Jeon]'''
*** Nokia: '''[http://meego.com/users/alistair Alistair Adams]'''
*** Pelagicore: '''[http://meego.com/users/mikael Mikael Soderberg]'''
*** Visteon: '''[http://meego.com/users/PavelKonopelko Pavel Konopelko]'''

* Product Manager (cross-function across Working Group and Project Team)
** Unifies and prioritizes overall requirements set.
** Owns the roadmap.
** co-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 with the Lead Architects and Lead Designers on effort estimates and schedules.
** co-leads the Project Team together with the Product 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: '''[http://meego.com/users/joel Joel Clark (Intel)]'''

==== Working Group Meetings and Minutes ====
The Working Group meets regularly. Information on current and past meetings can be found on [[in-vehicle/working-group|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: '''[http://meego.com/users/tomcounihan 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: '''[http://meego.com/users/jeremiah 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.

== Shipping MeeGo IVI Products ==

* [http://news.softpedia.com/news/MeeGo-Powered-In-Vehicle-Information-System-Makes-Appearance-at-MWC-2011-184651.shtml Hawtai B11]
* [http://www.allaboutmeego.com/news/item/12918_Red_Flag_Software_announces_Me.php Geely EC8]
* iKarPC [http://files.icp-deutschland.de/produkte2/124273/web/icp/IKARPC-W08A-datasheet-20110222.pdf datasheet] and [http://www.contradata.it/cataloghi/IEI_2011_In_Vehicle_PC.pdf catalog page]

== MeeGo IVI Demos ==

* MeeGo IVI UI from ICS: [http://www.youtube.com/watch?v=ZWbfGzyLoh8 video] and [http://www.ics.com/services/qtquick info], including source code

== 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.

The roadmap pages are the central collaboration point on laying out the future of MeeGo IVI. Here architecture details, system diagrams, use cases, etc. are shared.

[[In-vehicle/Roadmap|View the Roadmap]]

Before any new feature is committed to the Roadmap, a feature request is created in http://bugs.meego.com. Current MeeGo IVI feature requests can be found [https://bugs.meego.com/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=MeeGo+IVI+Features&content= here]

[https://bugs.meego.com/enter_bug.cgi?product=MeeGo%20IVI%20Features 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 in the [[In-vehicle/Roadmap|IVI roadmap]].

== 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. [[Release Engineering/Release Versioning|MeeGo Release Versioning]] explains the build version numbering scheme. For example '''1.2.80.xx''' is a 1.2 Alpha build, '''1.2.90.xx''' is a 1.2 Beta build, '''1.2.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]

Each weekly build directory is named with a version number and date. IVI live .iso images are found under the ''images'' link in each weekly build directory. 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 under ''repos'' in the weekly build directory.

==Platforms==
===MeeGo IVI Platforms Supported in Releases===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! Releases
! Plan
! status
! price/availability
|-
|meego-ivi-ia32
|Congatec IVI Kit (Russellville)
|Intel Atom Z5xx Series and Intel System Controller Hub US15Wx (eMenlow)
|Timberdale
|GPIO, DMA, SPI, I2C, UART, USB, IDE, Audio, KS8842 GigE, EMGD, Video-in, SDHC, TSC2007, I2S, SDHC, ADV7180, BT, Radio
|1.0.1, 1.1, 1.2
|EOL
|No known driver issues
|unavailable 5/11
|-
|meego-ivi-ia32
|Crown Bay
|Intel Atom 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
|1.2
|1.3
|No known driver issues
|
|-
|meego-ivi-ia32
|Stephenville/Crossville
|Intel Atom E6xx Series for Embedded (Tunnel Creek)
|Oki Semiconductors ML7213 IVI IOH
|GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, EMGD, SD/SDIO/MMC, USB-OTG, TDM, sDVO
|1.2
|1.3
|[https://bugs.meego.com/buglist.cgi?short_desc=oki&classification=MeeGo%20Platform&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&version=1.2&version=1.3&short_desc_type=allwordssubstr&component=Kernel%20and%20drivers%20%28generic%29&product=MeeGo%20IVI CV-ML7213 bugs ]
|
|}

===MeeGo IVI Trunk Prototype Platforms===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! status
|-
|meego-ivi-ia32-conx
|Stephenville/Northville/Crossville
|Intel Atom 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, several issues open, visit [[IVI Images for ConneXt IOH]] for more information
|}

;ARM
:Jeremiah Foster and Jan-Simon Moeller are working on updates to enable automated weekly builds of MeeGo IVI images for the Beagleboard-XM.
:The suggested reference platform is the Beagleboard xM. The [[ARM/OMAP4_Panda|PandaBoard]] and [[ARM/Snowball|Snowball]] most likely will be supported in the future.
{| border="1"
! Image name
! Platform name
! chipset
! status
|-
| meego-ivi-armv7l
| Beagleboard xM
| OMAP 3
| Not yet smoke tested. No QA
|-
| meego-ivi-armv7l
| Tegra2
| ARM v7 rev 0
| Not yet smoke tested. No QA
|-
|}

===[http://sf2011.meego.com/sites/all/files/slides/meegocon2011developmentboardbofslides.pdf MeeGo IVI Development Boards]===

;IA32
{| border="1"
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! price/availability as of 5/11
! tested with MeeGo?
|-
|Intel Embedded Development Board 1-N450/1-D510
|N450 or D510
|Intel 82801HM
|SSD, WiFi, SATA, USB, SPI, GPIO, PCIe, UART, GigE, Audio, IEGD, DMA, I2C
|[http://edc.intel.com/Platforms/Atom-N450-D410-D510/Development-Board/#bd1-content=bd1-toggle~~visible-content $149 for registered users]
|[http://wiki.meego.com/Devices/Ideapad yes]
|}

;ARM

Per Stskeeps on meego-arm IRC on 6/2/2011, Nokia-provided N900 SGX530 drivers with hardfp extensions are known to work with SGX530 revisions 121 and 125. Which OMAP3 SoCs have revision 121 and 125 is not always straightforward to determine. dm8tbr reports problems with N900 hardfp drivers on Beagleboard xM. Stskeeps reports success with these drivers on Beagleboard C4. Tripzero reports success with hardfp drivers on old build of IGEPv2 that had the Cortex A8 processor.

{| border="1"
! Platform name
! Processor
! GPU; [[http://wiki.meego.com/ARM/hardfp hardfp?]]
! Memory
! Features
! price/availability as of 5/11
! tested with MeeGo?
|-
|[http://www.igloocommunity.org/ Snowball] (usable in end products)
|Cortex A-9 Dual-Core Nova A9500 1 GHz
|ARM Mali 400, [[ARM/Snowball|yes]]
|1 GB
|HDMI, WiFi b/g/n, Bluetooth, GPS, USB OTG, FSMC, HSI, Audio, MiPi CSI / Camera, LCD, MiPi DSI, UART, SPI, I2C, GPIO, SD/MMC, accelerometer, magnetometer, gyrometer, pressure sensor [[ARM/Snowball|(complete specs)]]
| [[ARM/Snowball|June]]
| [[ARM/Snowball|yes]]
|-
|[http://www.igep.es/index.php?option=com_content&view=article&id=46&Itemid=55 IGEPv2]
|[http://www.igep.es/public_docs/IGEPv2/HW_User_Manuals/MAN-PR-IGEP.0020.HW_USER_MANUAL.pdf DM3730 1 GHz]
|Imagination Technologies SGX530, yes? (tested by IGES with both TI and Nokia drivers)
|512 MB
|GigE, WiFi b/g, Bluetooth, USB OTG, USB Host, DVI-D, audio, SPI, UART, LCD, serial; [http://shop.igep.es/index.php?main_page=product_info&cPath=1&products_id=49 expansion board] with GSM, VGA, video in, camera, '''CAN'''
| 116.0€ and up plus 152.0€ for expansion board
| yes, but with older Cortex A8 build
|-
|[http://www.variscite.com/products/item/35-var-am35customboard Variscite VAR-AM3517 CustomBoard]
|[http://www.variscite.com/images/stories/DataSheets/VAR-SOM-AM35_1_15.pdf Cortex A-8 Sitara 600 MHz]
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|DMA, QCIF, LCD, SDTV, S-Video, USB, USB OTG, I2C, McSPI, GPIO, MMC, JTAG, '''CAN'''
|$1150 plus shipping
| no
|-
|[http://www.origenboard.org Samsung Origen]
|Samsung Exynos 4210 Cortex A-9 1 GHz
|ARM Mali 400, [http://forums.arm.com/index.php?/topic/14236-mali-gpus-linux-device-drivers-r2p0-05rel0-source-code-released/ reuse Snowball drivers?]
|1 GB
|HMDI, SD, WiFi, Bluetooth, audio, LCD, JTAG, camera
|[http://www.insignal.co.kr "sub-$200", June 25]
|no
|-
|[http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=IMX53QSB i.MX53 Quick Start Board]
|Cortex A-8 1 GHz
|Freescale GPUv3, [http://imxcommunity.org/profiles/blogs/ubuntu-rebuilt-with-hardfp yes]
|1 GB
|LVDS, LCD, HDMI, SPDIF, I2C, SSI, SPI, SD/MMC, microSD, SATA, GigE, USB, USB OTG, JTAG, UART, accelerometer
|$149
|[http://www.youtube.com/watch?feature=player_embedded&v=osDlTdl5lAk yes, similar HW]
|-
|[http://pandaboard.org/ Pandaboard]
|Cortex A-9 Dual-Core OMAP 4430 1 GHz
|Imagination Technologies SGX540, [http://article.gmane.org/gmane.comp.embedded.pandaboard/1771/match=hardfp not yet]
|1 GB
|SD/MMC, UART, Camera connector, USB OTG, Audio, GiGE, LCD connector, HDMI, WiFi, Bluetooth, JTAG, SPI, GPIO, I2C, McBSP
|[http://pandaboard.org/content/buy $179]
|[[ARM/OMAP4_Panda|yes]]
|-
|[http://beagle.s3.amazonaws.com/design/xM-A/BB_xM_SRM_A2_01.pdf Beagleboard Xm]
|Cortex A-8 DM3730 1GHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|512 MB
|uSD, USB, USB OTG, UART, McBSP, JTAG, GiGE, Audio, DVI-D, Camera connector, McBSP, I2C, GPIO, MMC2/3, ADC, LCD connector
|[http://beagleboard.org/buy $149]
|[[ARM/Meego_on_Beagleboard_from_scratch|yes]]
|-
|[http://beagleboard.org/static/BBSRM_latest.pdf Beagleboard C4]
|Cortex A-8 OMAP3530 720 MHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|I2C, I2S, SPI, MMC, USB, UART, USB OTG, S-Video, Audio, LCD, JTAG, GiGE
|[http://beagleboard.org/buy $125]
|[[ARM/Meego_IVI_on_Beagle|yes]]
|}

== Releases ==
* [[MeeGo IVI 1.2 | MeeGo IVI 1.2]]
* [http://meego.com/downloads/releases/1.1/meego-v1.1-in-vehicle-infotainment-ivi MeeGo IVI 1.1]
* [http://meego.com/downloads/releases/1.0/meego-v1.0-in-vehicle-infotainment-ivi MeeGo IVI 1.0]

== Resources ==
* IRC irc.freenode.org #meego-ivi
* Mailing list sign-up: http://lists.meego.com/listinfo/meego-ivi
* Mailing list archive: http://lists.meego.com/pipermail/meego-ivi/
* [[Presentations_about_meego-ivi#Presentations_and_Articles_about_MeeGo_IVI|Presentations and articles about meego-ivi]]
* [[In-vehicle/IVI for users and developers|IVI for users and developers]]
* [[IVITopic|Topics]]

[[Category:IVI]]

In-vehicle

2011-06-29T04:32:11Z

Joel: /* MeeGo IVI Platforms Supported in Releases */

= 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: '''[http://meego.com/users/RudolfStreif 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:
*** Intel: '''[http://meego.com/users/jahoffmann Joel Hoffmann]'''
*** LG Electronics: '''[https://meego.com/users/hyungjin Hyungjin Jeon]'''
*** Nokia: '''[http://meego.com/users/alistair Alistair Adams]'''
*** Pelagicore: '''[http://meego.com/users/mikael Mikael Soderberg]'''
*** Visteon: '''[http://meego.com/users/PavelKonopelko Pavel Konopelko]'''

* Product Manager (cross-function across Working Group and Project Team)
** Unifies and prioritizes overall requirements set.
** Owns the roadmap.
** co-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 with the Lead Architects and Lead Designers on effort estimates and schedules.
** co-leads the Project Team together with the Product 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: '''[http://meego.com/users/joel Joel Clark (Intel)]'''

==== Working Group Meetings and Minutes ====
The Working Group meets regularly. Information on current and past meetings can be found on [[in-vehicle/working-group|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: '''[http://meego.com/users/tomcounihan 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: '''[http://meego.com/users/jeremiah 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.

== Shipping MeeGo IVI Products ==

* [http://news.softpedia.com/news/MeeGo-Powered-In-Vehicle-Information-System-Makes-Appearance-at-MWC-2011-184651.shtml Hawtai B11]
* [http://www.allaboutmeego.com/news/item/12918_Red_Flag_Software_announces_Me.php Geely EC8]
* iKarPC [http://files.icp-deutschland.de/produkte2/124273/web/icp/IKARPC-W08A-datasheet-20110222.pdf datasheet] and [http://www.contradata.it/cataloghi/IEI_2011_In_Vehicle_PC.pdf catalog page]

== MeeGo IVI Demos ==

* MeeGo IVI UI from ICS: [http://www.youtube.com/watch?v=ZWbfGzyLoh8 video] and [http://www.ics.com/services/qtquick info], including source code

== 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.

The roadmap pages are the central collaboration point on laying out the future of MeeGo IVI. Here architecture details, system diagrams, use cases, etc. are shared.

[[In-vehicle/Roadmap|View the Roadmap]]

Before any new feature is committed to the Roadmap, a feature request is created in http://bugs.meego.com. Current MeeGo IVI feature requests can be found [https://bugs.meego.com/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=MeeGo+IVI+Features&content= here]

[https://bugs.meego.com/enter_bug.cgi?product=MeeGo%20IVI%20Features 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 in the [[In-vehicle/Roadmap|IVI roadmap]].

=== 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. [[Release Engineering/Release Versioning|MeeGo Release Versioning]] explains the build version numbering scheme. For example '''1.2.80.xx''' is a 1.2 Alpha build, '''1.2.90.xx''' is a 1.2 Beta build, '''1.2.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]

Each weekly build directory is named with a version number and date. IVI live .iso images are found under the ''images'' link in each weekly build directory. 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 under ''repos'' in the weekly build directory.

==Platforms==
===MeeGo IVI Platforms Supported in Releases===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! Releases
! Plan
! status
! price/availability
|-
|meego-ivi-ia32
|Congatec IVI Kit (Russellville)
|Intel Atom Z5xx Series and Intel System Controller Hub US15Wx (eMenlow)
|Timberdale
|GPIO, DMA, SPI, I2C, UART, USB, IDE, Audio, KS8842 GigE, EMGD, Video-in, SDHC, TSC2007, I2S, SDHC, ADV7180, BT, Radio
|1.0.1, 1.1, 1.2
|EOL
|No known driver issues
|unavailable 5/11
|-
|meego-ivi-ia32
|Crown Bay
|Intel Atom 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
|1.2
|1.3
|No known driver issues
|
|-
|meego-ivi-ia32
|Stephenville/Crossville
|Intel Atom E6xx Series for Embedded (Tunnel Creek)
|Oki Semiconductors ML7213 IVI IOH
|GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, EMGD, SD/SDIO/MMC, USB-OTG, TDM, sDVO
|1.2
|1.3
|[https://bugs.meego.com/buglist.cgi?short_desc=oki&classification=MeeGo%20Platform&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&version=1.2&version=1.3&short_desc_type=allwordssubstr&component=Kernel%20and%20drivers%20%28generic%29&product=MeeGo%20IVI CV-ML7213 bugs ]
|
|}

===MeeGo IVI Trunk Prototype Platforms===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! status
|-
|meego-ivi-ia32-conx
|Stephenville/Northville/Crossville
|Intel Atom 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, several issues open, visit [[IVI Images for ConneXt IOH]] for more information
|}

;ARM
:Jeremiah Foster and Jan-Simon Moeller are working on updates to enable automated weekly builds of MeeGo IVI images for the Beagleboard-XM.
:The suggested reference platform is the Beagleboard xM. The [[ARM/OMAP4_Panda|PandaBoard]] and [[ARM/Snowball|Snowball]] most likely will be supported in the future.
{| border="1"
! Image name
! Platform name
! chipset
! status
|-
| meego-ivi-armv7l
| Beagleboard xM
| OMAP 3
| Not yet smoke tested. No QA
|-
| meego-ivi-armv7l
| Tegra2
| ARM v7 rev 0
| Not yet smoke tested. No QA
|-
|}

===[http://sf2011.meego.com/sites/all/files/slides/meegocon2011developmentboardbofslides.pdf MeeGo IVI Development Boards]===

;IA32
{| border="1"
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! price/availability as of 5/11
! tested with MeeGo?
|-
|Intel Embedded Development Board 1-N450/1-D510
|N450 or D510
|Intel 82801HM
|SSD, WiFi, SATA, USB, SPI, GPIO, PCIe, UART, GigE, Audio, IEGD, DMA, I2C
|[http://edc.intel.com/Platforms/Atom-N450-D410-D510/Development-Board/#bd1-content=bd1-toggle~~visible-content $149 for registered users]
|[http://wiki.meego.com/Devices/Ideapad yes]
|}

;ARM

Per Stskeeps on meego-arm IRC on 6/2/2011, Nokia-provided N900 SGX530 drivers with hardfp extensions are known to work with SGX530 revisions 121 and 125. Which OMAP3 SoCs have revision 121 and 125 is not always straightforward to determine. dm8tbr reports problems with N900 hardfp drivers on Beagleboard xM. Stskeeps reports success with these drivers on Beagleboard C4. Tripzero reports success with hardfp drivers on old build of IGEPv2 that had the Cortex A8 processor.

{| border="1"
! Platform name
! Processor
! GPU; [[http://wiki.meego.com/ARM/hardfp hardfp?]]
! Memory
! Features
! price/availability as of 5/11
! tested with MeeGo?
|-
|[http://www.igloocommunity.org/ Snowball] (usable in end products)
|Cortex A-9 Dual-Core Nova A9500 1 GHz
|ARM Mali 400, [[ARM/Snowball|yes]]
|1 GB
|HDMI, WiFi b/g/n, Bluetooth, GPS, USB OTG, FSMC, HSI, Audio, MiPi CSI / Camera, LCD, MiPi DSI, UART, SPI, I2C, GPIO, SD/MMC, accelerometer, magnetometer, gyrometer, pressure sensor [[ARM/Snowball|(complete specs)]]
| [[ARM/Snowball|June]]
| [[ARM/Snowball|yes]]
|-
|[http://www.igep.es/index.php?option=com_content&view=article&id=46&Itemid=55 IGEPv2]
|[http://www.igep.es/public_docs/IGEPv2/HW_User_Manuals/MAN-PR-IGEP.0020.HW_USER_MANUAL.pdf DM3730 1 GHz]
|Imagination Technologies SGX530, yes? (tested by IGES with both TI and Nokia drivers)
|512 MB
|GigE, WiFi b/g, Bluetooth, USB OTG, USB Host, DVI-D, audio, SPI, UART, LCD, serial; [http://shop.igep.es/index.php?main_page=product_info&cPath=1&products_id=49 expansion board] with GSM, VGA, video in, camera, '''CAN'''
| 116.0€ and up plus 152.0€ for expansion board
| yes, but with older Cortex A8 build
|-
|[http://www.variscite.com/products/item/35-var-am35customboard Variscite VAR-AM3517 CustomBoard]
|[http://www.variscite.com/images/stories/DataSheets/VAR-SOM-AM35_1_15.pdf Cortex A-8 Sitara 600 MHz]
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|DMA, QCIF, LCD, SDTV, S-Video, USB, USB OTG, I2C, McSPI, GPIO, MMC, JTAG, '''CAN'''
|$1150 plus shipping
| no
|-
|[http://www.origenboard.org Samsung Origen]
|Samsung Exynos 4210 Cortex A-9 1 GHz
|ARM Mali 400, [http://forums.arm.com/index.php?/topic/14236-mali-gpus-linux-device-drivers-r2p0-05rel0-source-code-released/ reuse Snowball drivers?]
|1 GB
|HMDI, SD, WiFi, Bluetooth, audio, LCD, JTAG, camera
|[http://www.insignal.co.kr "sub-$200", June 25]
|no
|-
|[http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=IMX53QSB i.MX53 Quick Start Board]
|Cortex A-8 1 GHz
|Freescale GPUv3, [http://imxcommunity.org/profiles/blogs/ubuntu-rebuilt-with-hardfp yes]
|1 GB
|LVDS, LCD, HDMI, SPDIF, I2C, SSI, SPI, SD/MMC, microSD, SATA, GigE, USB, USB OTG, JTAG, UART, accelerometer
|$149
|[http://www.youtube.com/watch?feature=player_embedded&v=osDlTdl5lAk yes, similar HW]
|-
|[http://pandaboard.org/ Pandaboard]
|Cortex A-9 Dual-Core OMAP 4430 1 GHz
|Imagination Technologies SGX540, [http://article.gmane.org/gmane.comp.embedded.pandaboard/1771/match=hardfp not yet]
|1 GB
|SD/MMC, UART, Camera connector, USB OTG, Audio, GiGE, LCD connector, HDMI, WiFi, Bluetooth, JTAG, SPI, GPIO, I2C, McBSP
|[http://pandaboard.org/content/buy $179]
|[[ARM/OMAP4_Panda|yes]]
|-
|[http://beagle.s3.amazonaws.com/design/xM-A/BB_xM_SRM_A2_01.pdf Beagleboard Xm]
|Cortex A-8 DM3730 1GHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|512 MB
|uSD, USB, USB OTG, UART, McBSP, JTAG, GiGE, Audio, DVI-D, Camera connector, McBSP, I2C, GPIO, MMC2/3, ADC, LCD connector
|[http://beagleboard.org/buy $149]
|[[ARM/Meego_on_Beagleboard_from_scratch|yes]]
|-
|[http://beagleboard.org/static/BBSRM_latest.pdf Beagleboard C4]
|Cortex A-8 OMAP3530 720 MHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|I2C, I2S, SPI, MMC, USB, UART, USB OTG, S-Video, Audio, LCD, JTAG, GiGE
|[http://beagleboard.org/buy $125]
|[[ARM/Meego_IVI_on_Beagle|yes]]
|}

== Releases ==
* [[MeeGo IVI 1.2 | MeeGo IVI 1.2]]
* [http://meego.com/downloads/releases/1.1/meego-v1.1-in-vehicle-infotainment-ivi MeeGo IVI 1.1]
* [http://meego.com/downloads/releases/1.0/meego-v1.0-in-vehicle-infotainment-ivi MeeGo IVI 1.0]

== Resources ==
* IRC irc.freenode.org #meego-ivi
* Mailing list sign-up: http://lists.meego.com/listinfo/meego-ivi
* Mailing list archive: http://lists.meego.com/pipermail/meego-ivi/
* [[Presentations_about_meego-ivi#Presentations_and_Articles_about_MeeGo_IVI|Presentations and articles about meego-ivi]]
* [[In-vehicle/IVI for users and developers|IVI for users and developers]]
* [[IVITopic|Topics]]

[[Category:IVI]]

In-vehicle

2011-06-29T04:29:58Z

Joel: /* MeeGo IVI Weekly Builds */

= 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: '''[http://meego.com/users/RudolfStreif 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:
*** Intel: '''[http://meego.com/users/jahoffmann Joel Hoffmann]'''
*** LG Electronics: '''[https://meego.com/users/hyungjin Hyungjin Jeon]'''
*** Nokia: '''[http://meego.com/users/alistair Alistair Adams]'''
*** Pelagicore: '''[http://meego.com/users/mikael Mikael Soderberg]'''
*** Visteon: '''[http://meego.com/users/PavelKonopelko Pavel Konopelko]'''

* Product Manager (cross-function across Working Group and Project Team)
** Unifies and prioritizes overall requirements set.
** Owns the roadmap.
** co-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 with the Lead Architects and Lead Designers on effort estimates and schedules.
** co-leads the Project Team together with the Product 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: '''[http://meego.com/users/joel Joel Clark (Intel)]'''

==== Working Group Meetings and Minutes ====
The Working Group meets regularly. Information on current and past meetings can be found on [[in-vehicle/working-group|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: '''[http://meego.com/users/tomcounihan 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: '''[http://meego.com/users/jeremiah 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.

== Shipping MeeGo IVI Products ==

* [http://news.softpedia.com/news/MeeGo-Powered-In-Vehicle-Information-System-Makes-Appearance-at-MWC-2011-184651.shtml Hawtai B11]
* [http://www.allaboutmeego.com/news/item/12918_Red_Flag_Software_announces_Me.php Geely EC8]
* iKarPC [http://files.icp-deutschland.de/produkte2/124273/web/icp/IKARPC-W08A-datasheet-20110222.pdf datasheet] and [http://www.contradata.it/cataloghi/IEI_2011_In_Vehicle_PC.pdf catalog page]

== MeeGo IVI Demos ==

* MeeGo IVI UI from ICS: [http://www.youtube.com/watch?v=ZWbfGzyLoh8 video] and [http://www.ics.com/services/qtquick info], including source code

== 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.

The roadmap pages are the central collaboration point on laying out the future of MeeGo IVI. Here architecture details, system diagrams, use cases, etc. are shared.

[[In-vehicle/Roadmap|View the Roadmap]]

Before any new feature is committed to the Roadmap, a feature request is created in http://bugs.meego.com. Current MeeGo IVI feature requests can be found [https://bugs.meego.com/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=MeeGo+IVI+Features&content= here]

[https://bugs.meego.com/enter_bug.cgi?product=MeeGo%20IVI%20Features 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 in the [[In-vehicle/Roadmap|IVI roadmap]].

=== 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. [[Release Engineering/Release Versioning|MeeGo Release Versioning]] explains the build version numbering scheme. For example '''1.2.80.xx''' is a 1.2 Alpha build, '''1.2.90.xx''' is a 1.2 Beta build, '''1.2.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]

Each weekly build directory is named with a version number and date. IVI live .iso images are found under the ''images'' link in each weekly build directory. 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 under ''repos'' in the weekly build directory.

===MeeGo IVI Platforms Supported in Releases===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! Releases
! Plan
! status
! price/availability
|-
|meego-ivi-ia32
|Congatec IVI Kit (Russellville)
|Intel Atom Z5xx Series and Intel System Controller Hub US15Wx (eMenlow)
|Timberdale
|GPIO, DMA, SPI, I2C, UART, USB, IDE, Audio, KS8842 GigE, EMGD, Video-in, SDHC, TSC2007, I2S, SDHC, ADV7180, BT, Radio
|1.0.1, 1.1, 1.2
|EOL
|No known driver issues
|unavailable 5/11
|-
|meego-ivi-ia32
|Crown Bay
|Intel Atom 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
|1.2
|1.3
|No known driver issues
|
|-
|meego-ivi-ia32
|Stephenville/Crossville
|Intel Atom E6xx Series for Embedded (Tunnel Creek)
|Oki Semiconductors ML7213 IVI IOH
|GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, EMGD, SD/SDIO/MMC, USB-OTG, TDM, sDVO
|1.2
|1.3
|[https://bugs.meego.com/buglist.cgi?short_desc=oki&classification=MeeGo%20Platform&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&version=1.2&version=1.3&short_desc_type=allwordssubstr&component=Kernel%20and%20drivers%20%28generic%29&product=MeeGo%20IVI CV-ML7213 bugs ]
|
|}

===MeeGo IVI Trunk Prototype Platforms===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! status
|-
|meego-ivi-ia32-conx
|Stephenville/Northville/Crossville
|Intel Atom 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, several issues open, visit [[IVI Images for ConneXt IOH]] for more information
|}

;ARM
:Jeremiah Foster and Jan-Simon Moeller are working on updates to enable automated weekly builds of MeeGo IVI images for the Beagleboard-XM.
:The suggested reference platform is the Beagleboard xM. The [[ARM/OMAP4_Panda|PandaBoard]] and [[ARM/Snowball|Snowball]] most likely will be supported in the future.
{| border="1"
! Image name
! Platform name
! chipset
! status
|-
| meego-ivi-armv7l
| Beagleboard xM
| OMAP 3
| Not yet smoke tested. No QA
|-
| meego-ivi-armv7l
| Tegra2
| ARM v7 rev 0
| Not yet smoke tested. No QA
|-
|}

===[http://sf2011.meego.com/sites/all/files/slides/meegocon2011developmentboardbofslides.pdf MeeGo IVI Development Boards]===

;IA32
{| border="1"
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! price/availability as of 5/11
! tested with MeeGo?
|-
|Intel Embedded Development Board 1-N450/1-D510
|N450 or D510
|Intel 82801HM
|SSD, WiFi, SATA, USB, SPI, GPIO, PCIe, UART, GigE, Audio, IEGD, DMA, I2C
|[http://edc.intel.com/Platforms/Atom-N450-D410-D510/Development-Board/#bd1-content=bd1-toggle~~visible-content $149 for registered users]
|[http://wiki.meego.com/Devices/Ideapad yes]
|}

;ARM

Per Stskeeps on meego-arm IRC on 6/2/2011, Nokia-provided N900 SGX530 drivers with hardfp extensions are known to work with SGX530 revisions 121 and 125. Which OMAP3 SoCs have revision 121 and 125 is not always straightforward to determine. dm8tbr reports problems with N900 hardfp drivers on Beagleboard xM. Stskeeps reports success with these drivers on Beagleboard C4. Tripzero reports success with hardfp drivers on old build of IGEPv2 that had the Cortex A8 processor.

{| border="1"
! Platform name
! Processor
! GPU; [[http://wiki.meego.com/ARM/hardfp hardfp?]]
! Memory
! Features
! price/availability as of 5/11
! tested with MeeGo?
|-
|[http://www.igloocommunity.org/ Snowball] (usable in end products)
|Cortex A-9 Dual-Core Nova A9500 1 GHz
|ARM Mali 400, [[ARM/Snowball|yes]]
|1 GB
|HDMI, WiFi b/g/n, Bluetooth, GPS, USB OTG, FSMC, HSI, Audio, MiPi CSI / Camera, LCD, MiPi DSI, UART, SPI, I2C, GPIO, SD/MMC, accelerometer, magnetometer, gyrometer, pressure sensor [[ARM/Snowball|(complete specs)]]
| [[ARM/Snowball|June]]
| [[ARM/Snowball|yes]]
|-
|[http://www.igep.es/index.php?option=com_content&view=article&id=46&Itemid=55 IGEPv2]
|[http://www.igep.es/public_docs/IGEPv2/HW_User_Manuals/MAN-PR-IGEP.0020.HW_USER_MANUAL.pdf DM3730 1 GHz]
|Imagination Technologies SGX530, yes? (tested by IGES with both TI and Nokia drivers)
|512 MB
|GigE, WiFi b/g, Bluetooth, USB OTG, USB Host, DVI-D, audio, SPI, UART, LCD, serial; [http://shop.igep.es/index.php?main_page=product_info&cPath=1&products_id=49 expansion board] with GSM, VGA, video in, camera, '''CAN'''
| 116.0€ and up plus 152.0€ for expansion board
| yes, but with older Cortex A8 build
|-
|[http://www.variscite.com/products/item/35-var-am35customboard Variscite VAR-AM3517 CustomBoard]
|[http://www.variscite.com/images/stories/DataSheets/VAR-SOM-AM35_1_15.pdf Cortex A-8 Sitara 600 MHz]
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|DMA, QCIF, LCD, SDTV, S-Video, USB, USB OTG, I2C, McSPI, GPIO, MMC, JTAG, '''CAN'''
|$1150 plus shipping
| no
|-
|[http://www.origenboard.org Samsung Origen]
|Samsung Exynos 4210 Cortex A-9 1 GHz
|ARM Mali 400, [http://forums.arm.com/index.php?/topic/14236-mali-gpus-linux-device-drivers-r2p0-05rel0-source-code-released/ reuse Snowball drivers?]
|1 GB
|HMDI, SD, WiFi, Bluetooth, audio, LCD, JTAG, camera
|[http://www.insignal.co.kr "sub-$200", June 25]
|no
|-
|[http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=IMX53QSB i.MX53 Quick Start Board]
|Cortex A-8 1 GHz
|Freescale GPUv3, [http://imxcommunity.org/profiles/blogs/ubuntu-rebuilt-with-hardfp yes]
|1 GB
|LVDS, LCD, HDMI, SPDIF, I2C, SSI, SPI, SD/MMC, microSD, SATA, GigE, USB, USB OTG, JTAG, UART, accelerometer
|$149
|[http://www.youtube.com/watch?feature=player_embedded&v=osDlTdl5lAk yes, similar HW]
|-
|[http://pandaboard.org/ Pandaboard]
|Cortex A-9 Dual-Core OMAP 4430 1 GHz
|Imagination Technologies SGX540, [http://article.gmane.org/gmane.comp.embedded.pandaboard/1771/match=hardfp not yet]
|1 GB
|SD/MMC, UART, Camera connector, USB OTG, Audio, GiGE, LCD connector, HDMI, WiFi, Bluetooth, JTAG, SPI, GPIO, I2C, McBSP
|[http://pandaboard.org/content/buy $179]
|[[ARM/OMAP4_Panda|yes]]
|-
|[http://beagle.s3.amazonaws.com/design/xM-A/BB_xM_SRM_A2_01.pdf Beagleboard Xm]
|Cortex A-8 DM3730 1GHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|512 MB
|uSD, USB, USB OTG, UART, McBSP, JTAG, GiGE, Audio, DVI-D, Camera connector, McBSP, I2C, GPIO, MMC2/3, ADC, LCD connector
|[http://beagleboard.org/buy $149]
|[[ARM/Meego_on_Beagleboard_from_scratch|yes]]
|-
|[http://beagleboard.org/static/BBSRM_latest.pdf Beagleboard C4]
|Cortex A-8 OMAP3530 720 MHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|I2C, I2S, SPI, MMC, USB, UART, USB OTG, S-Video, Audio, LCD, JTAG, GiGE
|[http://beagleboard.org/buy $125]
|[[ARM/Meego_IVI_on_Beagle|yes]]
|}

== Releases ==
* [[MeeGo IVI 1.2 | MeeGo IVI 1.2]]
* [http://meego.com/downloads/releases/1.1/meego-v1.1-in-vehicle-infotainment-ivi MeeGo IVI 1.1]
* [http://meego.com/downloads/releases/1.0/meego-v1.0-in-vehicle-infotainment-ivi MeeGo IVI 1.0]

== Resources ==
* IRC irc.freenode.org #meego-ivi
* Mailing list sign-up: http://lists.meego.com/listinfo/meego-ivi
* Mailing list archive: http://lists.meego.com/pipermail/meego-ivi/
* [[Presentations_about_meego-ivi#Presentations_and_Articles_about_MeeGo_IVI|Presentations and articles about meego-ivi]]
* [[In-vehicle/IVI for users and developers|IVI for users and developers]]
* [[IVITopic|Topics]]

[[Category:IVI]]

MeeGo IVI 1.2

2011-06-29T04:25:55Z

Joel: Created page with "MeeGo IVI 1.2 was released on May 19, 2011 ===Links=== [https://meego.com/downloads/releases/1.2/meego-v1.2-in-vehicle-infotainment-ivi MeeGo IVI 1.2 release page ] [[In-vehicl..."

MeeGo IVI 1.2 was released on May 19, 2011

===Links===
[https://meego.com/downloads/releases/1.2/meego-v1.2-in-vehicle-infotainment-ivi MeeGo IVI 1.2 release page ]

[[In-vehicle/IVIHome Guide|Guide for the IVI Home Screen]]

[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]

[https://bugs.meego.com/enter_bug.cgi?product=MeeGo%20IVI File bugs for MeeGo IVI 1.2 ]

===MeeGo IVI 1.2 New Features===

:IVI Home Screen Changes
::The IVI home screen has been ported to QML and it's now based on the MeeGo UX and launched through meego-ux-daemon. It implements an updated scroll menu and also supports quick access to commonly used apps through the desktop and a Top Application task bar. The scroll menu navigation 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. Both Text to Speech and Speech Recognition can now be toggled on the home screen for easier access. Since the UX is now based on QML, it makes customizing the UI much easier since they are script-based, and thus without the need of re-compiling for any changes.

::See [[In-vehicle/IVIHome Guide|Guide for the IVI Home Screen]] for more information.

:New Sample Applications
::The sample applications in MeeGo IVI 1.1 based on the MeeGo Touch Framework have been replaced in MeeGo 1.2 with a collection of commonly used applications based on QML. These can be accessed via the IVI home screen as discussed above.

:Nokia Terminal Mode
::Packages implementing the client side of Nokia Terminal Mode have been included in the build repositories. There are two packages(libqterminalmode and qterminalmodeclient) which must be installed from the ''oss'' repositories in order to try this code. These packages interact with phonesets that support the server side of Nokia Terminal Mode. Nokia has developer kit phone sets that implement the server side of terminal mode. [http://www.terminalmode.org/en/developer/developer-offering/ Terminal Mode Developer Offering] has more information about the software and how to get developer kits
: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. Also included in the repository (but not in the default boot image) is the <nowiki> "emgd-gui"</nowiki> utility for configuring and managing the graphics driver. Documentation and information on product support may be found on the [http://edc.intel.com/Software/Downloads/EMGD/ EMGD download page]

::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/Software/Downloads/EMGD/

In-vehicle

2011-06-29T03:40:39Z

Joel: /* Releases */

= 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: '''[http://meego.com/users/RudolfStreif 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:
*** Intel: '''[http://meego.com/users/jahoffmann Joel Hoffmann]'''
*** LG Electronics: '''[https://meego.com/users/hyungjin Hyungjin Jeon]'''
*** Nokia: '''[http://meego.com/users/alistair Alistair Adams]'''
*** Pelagicore: '''[http://meego.com/users/mikael Mikael Soderberg]'''
*** Visteon: '''[http://meego.com/users/PavelKonopelko Pavel Konopelko]'''

* Product Manager (cross-function across Working Group and Project Team)
** Unifies and prioritizes overall requirements set.
** Owns the roadmap.
** co-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 with the Lead Architects and Lead Designers on effort estimates and schedules.
** co-leads the Project Team together with the Product 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: '''[http://meego.com/users/joel Joel Clark (Intel)]'''

==== Working Group Meetings and Minutes ====
The Working Group meets regularly. Information on current and past meetings can be found on [[in-vehicle/working-group|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: '''[http://meego.com/users/tomcounihan 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: '''[http://meego.com/users/jeremiah 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.

== Shipping MeeGo IVI Products ==

* [http://news.softpedia.com/news/MeeGo-Powered-In-Vehicle-Information-System-Makes-Appearance-at-MWC-2011-184651.shtml Hawtai B11]
* [http://www.allaboutmeego.com/news/item/12918_Red_Flag_Software_announces_Me.php Geely EC8]
* iKarPC [http://files.icp-deutschland.de/produkte2/124273/web/icp/IKARPC-W08A-datasheet-20110222.pdf datasheet] and [http://www.contradata.it/cataloghi/IEI_2011_In_Vehicle_PC.pdf catalog page]

== MeeGo IVI Demos ==

* MeeGo IVI UI from ICS: [http://www.youtube.com/watch?v=ZWbfGzyLoh8 video] and [http://www.ics.com/services/qtquick info], including source code

== 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.

The roadmap pages are the central collaboration point on laying out the future of MeeGo IVI. Here architecture details, system diagrams, use cases, etc. are shared.

[[In-vehicle/Roadmap|View the Roadmap]]

Before any new feature is committed to the Roadmap, a feature request is created in http://bugs.meego.com. Current MeeGo IVI feature requests can be found [https://bugs.meego.com/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=MeeGo+IVI+Features&content= here]

[https://bugs.meego.com/enter_bug.cgi?product=MeeGo%20IVI%20Features 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 in the [[In-vehicle/Roadmap|IVI roadmap]].

=== 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. [[Release Engineering/Release Versioning|MeeGo Release Versioning]] explains the build version numbering scheme. For example '''1.2.80.xx''' is a 1.2 Alpha build, '''1.2.90.xx''' is a 1.2 Beta build, '''1.2.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.

'''MeeGo IVI 1.2 Feature Status'''

[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]

[[In-vehicle/IVIHome Guide|Guide for the IVI Home Screen]]

;May 15, 2011
The MeeGo 1.2 release is scheduled for May 19, 2011. The following changes have been made in IVI features for MeeGo 1.2 compared to MeeGo 1.1

:IVI Home Screen Changes
::The IVI home screen has been ported to QML and it's now based on the MeeGo UX and launched through meego-ux-daemon. It implements an updated scroll menu and also supports quick access to commonly used apps through the desktop and a Top Application task bar. The scroll menu navigation 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. Both Text to Speech and Speech Recognition can now be toggled on the home screen for easier access. Since the UX is now based on QML, it makes customizing the UI much easier since they are script-based, and thus without the need of re-compiling for any changes.

::See [[In-vehicle/IVIHome Guide|Guide for the IVI Home Screen]] for more information.

:New Sample Applications
::The sample applications in MeeGo IVI 1.1 based on the MeeGo Touch Framework have been replaced in MeeGo 1.2 with a collection of commonly used applications based on QML. These can be accessed via the IVI home screen as discussed above.

:Nokia Terminal Mode
::Packages implementing the client side of Nokia Terminal Mode have been included in the build repositories. There are two packages(libqterminalmode and qterminalmodeclient) which must be installed from the ''oss'' repositories in order to try this code. These packages interact with phonesets that support the server side of Nokia Terminal Mode. Nokia has developer kit phone sets that implement the server side of terminal mode. [http://www.terminalmode.org/en/developer/developer-offering/ Terminal Mode Developer Offering] has more information about the software and how to get developer kits
: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. Also included in the repository (but not in the default boot image) is the <nowiki> "emgd-gui"</nowiki> utility for configuring and managing the graphics driver. Documentation and information on product support may be found on the [http://edc.intel.com/Software/Downloads/EMGD/ EMGD download page]

::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/Software/Downloads/EMGD/

===MeeGo IVI Platforms Supported in Releases===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! Releases
! Plan
! status
! price/availability
|-
|meego-ivi-ia32
|Congatec IVI Kit (Russellville)
|Intel Atom Z5xx Series and Intel System Controller Hub US15Wx (eMenlow)
|Timberdale
|GPIO, DMA, SPI, I2C, UART, USB, IDE, Audio, KS8842 GigE, EMGD, Video-in, SDHC, TSC2007, I2S, SDHC, ADV7180, BT, Radio
|1.0.1, 1.1, 1.2
|EOL
|No known driver issues
|unavailable 5/11
|-
|meego-ivi-ia32
|Crown Bay
|Intel Atom 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
|1.2
|1.3
|No known driver issues
|
|-
|meego-ivi-ia32
|Stephenville/Crossville
|Intel Atom E6xx Series for Embedded (Tunnel Creek)
|Oki Semiconductors ML7213 IVI IOH
|GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, EMGD, SD/SDIO/MMC, USB-OTG, TDM, sDVO
|1.2
|1.3
|[https://bugs.meego.com/buglist.cgi?short_desc=oki&classification=MeeGo%20Platform&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&version=1.2&version=1.3&short_desc_type=allwordssubstr&component=Kernel%20and%20drivers%20%28generic%29&product=MeeGo%20IVI CV-ML7213 bugs ]
|
|}

===MeeGo IVI Trunk Prototype Platforms===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! status
|-
|meego-ivi-ia32-conx
|Stephenville/Northville/Crossville
|Intel Atom 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, several issues open, visit [[IVI Images for ConneXt IOH]] for more information
|}

;ARM
:Jeremiah Foster and Jan-Simon Moeller are working on updates to enable automated weekly builds of MeeGo IVI images for the Beagleboard-XM.
:The suggested reference platform is the Beagleboard xM. The [[ARM/OMAP4_Panda|PandaBoard]] and [[ARM/Snowball|Snowball]] most likely will be supported in the future.
{| border="1"
! Image name
! Platform name
! chipset
! status
|-
| meego-ivi-armv7l
| Beagleboard xM
| OMAP 3
| Not yet smoke tested. No QA
|-
| meego-ivi-armv7l
| Tegra2
| ARM v7 rev 0
| Not yet smoke tested. No QA
|-
|}

===[http://sf2011.meego.com/sites/all/files/slides/meegocon2011developmentboardbofslides.pdf MeeGo IVI Development Boards]===

;IA32
{| border="1"
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! price/availability as of 5/11
! tested with MeeGo?
|-
|Intel Embedded Development Board 1-N450/1-D510
|N450 or D510
|Intel 82801HM
|SSD, WiFi, SATA, USB, SPI, GPIO, PCIe, UART, GigE, Audio, IEGD, DMA, I2C
|[http://edc.intel.com/Platforms/Atom-N450-D410-D510/Development-Board/#bd1-content=bd1-toggle~~visible-content $149 for registered users]
|[http://wiki.meego.com/Devices/Ideapad yes]
|}

;ARM

Per Stskeeps on meego-arm IRC on 6/2/2011, Nokia-provided N900 SGX530 drivers with hardfp extensions are known to work with SGX530 revisions 121 and 125. Which OMAP3 SoCs have revision 121 and 125 is not always straightforward to determine. dm8tbr reports problems with N900 hardfp drivers on Beagleboard xM. Stskeeps reports success with these drivers on Beagleboard C4. Tripzero reports success with hardfp drivers on old build of IGEPv2 that had the Cortex A8 processor.

{| border="1"
! Platform name
! Processor
! GPU; [[http://wiki.meego.com/ARM/hardfp hardfp?]]
! Memory
! Features
! price/availability as of 5/11
! tested with MeeGo?
|-
|[http://www.igloocommunity.org/ Snowball] (usable in end products)
|Cortex A-9 Dual-Core Nova A9500 1 GHz
|ARM Mali 400, [[ARM/Snowball|yes]]
|1 GB
|HDMI, WiFi b/g/n, Bluetooth, GPS, USB OTG, FSMC, HSI, Audio, MiPi CSI / Camera, LCD, MiPi DSI, UART, SPI, I2C, GPIO, SD/MMC, accelerometer, magnetometer, gyrometer, pressure sensor [[ARM/Snowball|(complete specs)]]
| [[ARM/Snowball|June]]
| [[ARM/Snowball|yes]]
|-
|[http://www.igep.es/index.php?option=com_content&view=article&id=46&Itemid=55 IGEPv2]
|[http://www.igep.es/public_docs/IGEPv2/HW_User_Manuals/MAN-PR-IGEP.0020.HW_USER_MANUAL.pdf DM3730 1 GHz]
|Imagination Technologies SGX530, yes? (tested by IGES with both TI and Nokia drivers)
|512 MB
|GigE, WiFi b/g, Bluetooth, USB OTG, USB Host, DVI-D, audio, SPI, UART, LCD, serial; [http://shop.igep.es/index.php?main_page=product_info&cPath=1&products_id=49 expansion board] with GSM, VGA, video in, camera, '''CAN'''
| 116.0€ and up plus 152.0€ for expansion board
| yes, but with older Cortex A8 build
|-
|[http://www.variscite.com/products/item/35-var-am35customboard Variscite VAR-AM3517 CustomBoard]
|[http://www.variscite.com/images/stories/DataSheets/VAR-SOM-AM35_1_15.pdf Cortex A-8 Sitara 600 MHz]
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|DMA, QCIF, LCD, SDTV, S-Video, USB, USB OTG, I2C, McSPI, GPIO, MMC, JTAG, '''CAN'''
|$1150 plus shipping
| no
|-
|[http://www.origenboard.org Samsung Origen]
|Samsung Exynos 4210 Cortex A-9 1 GHz
|ARM Mali 400, [http://forums.arm.com/index.php?/topic/14236-mali-gpus-linux-device-drivers-r2p0-05rel0-source-code-released/ reuse Snowball drivers?]
|1 GB
|HMDI, SD, WiFi, Bluetooth, audio, LCD, JTAG, camera
|[http://www.insignal.co.kr "sub-$200", June 25]
|no
|-
|[http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=IMX53QSB i.MX53 Quick Start Board]
|Cortex A-8 1 GHz
|Freescale GPUv3, [http://imxcommunity.org/profiles/blogs/ubuntu-rebuilt-with-hardfp yes]
|1 GB
|LVDS, LCD, HDMI, SPDIF, I2C, SSI, SPI, SD/MMC, microSD, SATA, GigE, USB, USB OTG, JTAG, UART, accelerometer
|$149
|[http://www.youtube.com/watch?feature=player_embedded&v=osDlTdl5lAk yes, similar HW]
|-
|[http://pandaboard.org/ Pandaboard]
|Cortex A-9 Dual-Core OMAP 4430 1 GHz
|Imagination Technologies SGX540, [http://article.gmane.org/gmane.comp.embedded.pandaboard/1771/match=hardfp not yet]
|1 GB
|SD/MMC, UART, Camera connector, USB OTG, Audio, GiGE, LCD connector, HDMI, WiFi, Bluetooth, JTAG, SPI, GPIO, I2C, McBSP
|[http://pandaboard.org/content/buy $179]
|[[ARM/OMAP4_Panda|yes]]
|-
|[http://beagle.s3.amazonaws.com/design/xM-A/BB_xM_SRM_A2_01.pdf Beagleboard Xm]
|Cortex A-8 DM3730 1GHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|512 MB
|uSD, USB, USB OTG, UART, McBSP, JTAG, GiGE, Audio, DVI-D, Camera connector, McBSP, I2C, GPIO, MMC2/3, ADC, LCD connector
|[http://beagleboard.org/buy $149]
|[[ARM/Meego_on_Beagleboard_from_scratch|yes]]
|-
|[http://beagleboard.org/static/BBSRM_latest.pdf Beagleboard C4]
|Cortex A-8 OMAP3530 720 MHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|I2C, I2S, SPI, MMC, USB, UART, USB OTG, S-Video, Audio, LCD, JTAG, GiGE
|[http://beagleboard.org/buy $125]
|[[ARM/Meego_IVI_on_Beagle|yes]]
|}

== Releases ==
* [[MeeGo IVI 1.2 | MeeGo IVI 1.2]]
* [http://meego.com/downloads/releases/1.1/meego-v1.1-in-vehicle-infotainment-ivi MeeGo IVI 1.1]
* [http://meego.com/downloads/releases/1.0/meego-v1.0-in-vehicle-infotainment-ivi MeeGo IVI 1.0]

== Resources ==
* IRC irc.freenode.org #meego-ivi
* Mailing list sign-up: http://lists.meego.com/listinfo/meego-ivi
* Mailing list archive: http://lists.meego.com/pipermail/meego-ivi/
* [[Presentations_about_meego-ivi#Presentations_and_Articles_about_MeeGo_IVI|Presentations and articles about meego-ivi]]
* [[In-vehicle/IVI for users and developers|IVI for users and developers]]
* [[IVITopic|Topics]]

[[Category:IVI]]

In-vehicle

2011-06-29T03:36:56Z

Joel: /* MeeGo IVI 1.2 Release Supported Platforms */

= 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: '''[http://meego.com/users/RudolfStreif 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:
*** Intel: '''[http://meego.com/users/jahoffmann Joel Hoffmann]'''
*** LG Electronics: '''[https://meego.com/users/hyungjin Hyungjin Jeon]'''
*** Nokia: '''[http://meego.com/users/alistair Alistair Adams]'''
*** Pelagicore: '''[http://meego.com/users/mikael Mikael Soderberg]'''
*** Visteon: '''[http://meego.com/users/PavelKonopelko Pavel Konopelko]'''

* Product Manager (cross-function across Working Group and Project Team)
** Unifies and prioritizes overall requirements set.
** Owns the roadmap.
** co-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 with the Lead Architects and Lead Designers on effort estimates and schedules.
** co-leads the Project Team together with the Product 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: '''[http://meego.com/users/joel Joel Clark (Intel)]'''

==== Working Group Meetings and Minutes ====
The Working Group meets regularly. Information on current and past meetings can be found on [[in-vehicle/working-group|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: '''[http://meego.com/users/tomcounihan 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: '''[http://meego.com/users/jeremiah 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.

== Shipping MeeGo IVI Products ==

* [http://news.softpedia.com/news/MeeGo-Powered-In-Vehicle-Information-System-Makes-Appearance-at-MWC-2011-184651.shtml Hawtai B11]
* [http://www.allaboutmeego.com/news/item/12918_Red_Flag_Software_announces_Me.php Geely EC8]
* iKarPC [http://files.icp-deutschland.de/produkte2/124273/web/icp/IKARPC-W08A-datasheet-20110222.pdf datasheet] and [http://www.contradata.it/cataloghi/IEI_2011_In_Vehicle_PC.pdf catalog page]

== MeeGo IVI Demos ==

* MeeGo IVI UI from ICS: [http://www.youtube.com/watch?v=ZWbfGzyLoh8 video] and [http://www.ics.com/services/qtquick info], including source code

== 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.

The roadmap pages are the central collaboration point on laying out the future of MeeGo IVI. Here architecture details, system diagrams, use cases, etc. are shared.

[[In-vehicle/Roadmap|View the Roadmap]]

Before any new feature is committed to the Roadmap, a feature request is created in http://bugs.meego.com. Current MeeGo IVI feature requests can be found [https://bugs.meego.com/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=MeeGo+IVI+Features&content= here]

[https://bugs.meego.com/enter_bug.cgi?product=MeeGo%20IVI%20Features 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 in the [[In-vehicle/Roadmap|IVI roadmap]].

=== 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. [[Release Engineering/Release Versioning|MeeGo Release Versioning]] explains the build version numbering scheme. For example '''1.2.80.xx''' is a 1.2 Alpha build, '''1.2.90.xx''' is a 1.2 Beta build, '''1.2.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.

'''MeeGo IVI 1.2 Feature Status'''

[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]

[[In-vehicle/IVIHome Guide|Guide for the IVI Home Screen]]

;May 15, 2011
The MeeGo 1.2 release is scheduled for May 19, 2011. The following changes have been made in IVI features for MeeGo 1.2 compared to MeeGo 1.1

:IVI Home Screen Changes
::The IVI home screen has been ported to QML and it's now based on the MeeGo UX and launched through meego-ux-daemon. It implements an updated scroll menu and also supports quick access to commonly used apps through the desktop and a Top Application task bar. The scroll menu navigation 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. Both Text to Speech and Speech Recognition can now be toggled on the home screen for easier access. Since the UX is now based on QML, it makes customizing the UI much easier since they are script-based, and thus without the need of re-compiling for any changes.

::See [[In-vehicle/IVIHome Guide|Guide for the IVI Home Screen]] for more information.

:New Sample Applications
::The sample applications in MeeGo IVI 1.1 based on the MeeGo Touch Framework have been replaced in MeeGo 1.2 with a collection of commonly used applications based on QML. These can be accessed via the IVI home screen as discussed above.

:Nokia Terminal Mode
::Packages implementing the client side of Nokia Terminal Mode have been included in the build repositories. There are two packages(libqterminalmode and qterminalmodeclient) which must be installed from the ''oss'' repositories in order to try this code. These packages interact with phonesets that support the server side of Nokia Terminal Mode. Nokia has developer kit phone sets that implement the server side of terminal mode. [http://www.terminalmode.org/en/developer/developer-offering/ Terminal Mode Developer Offering] has more information about the software and how to get developer kits
: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. Also included in the repository (but not in the default boot image) is the <nowiki> "emgd-gui"</nowiki> utility for configuring and managing the graphics driver. Documentation and information on product support may be found on the [http://edc.intel.com/Software/Downloads/EMGD/ EMGD download page]

::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/Software/Downloads/EMGD/

===MeeGo IVI Platforms Supported in Releases===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! Releases
! Plan
! status
! price/availability
|-
|meego-ivi-ia32
|Congatec IVI Kit (Russellville)
|Intel Atom Z5xx Series and Intel System Controller Hub US15Wx (eMenlow)
|Timberdale
|GPIO, DMA, SPI, I2C, UART, USB, IDE, Audio, KS8842 GigE, EMGD, Video-in, SDHC, TSC2007, I2S, SDHC, ADV7180, BT, Radio
|1.0.1, 1.1, 1.2
|EOL
|No known driver issues
|unavailable 5/11
|-
|meego-ivi-ia32
|Crown Bay
|Intel Atom 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
|1.2
|1.3
|No known driver issues
|
|-
|meego-ivi-ia32
|Stephenville/Crossville
|Intel Atom E6xx Series for Embedded (Tunnel Creek)
|Oki Semiconductors ML7213 IVI IOH
|GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, EMGD, SD/SDIO/MMC, USB-OTG, TDM, sDVO
|1.2
|1.3
|[https://bugs.meego.com/buglist.cgi?short_desc=oki&classification=MeeGo%20Platform&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&version=1.2&version=1.3&short_desc_type=allwordssubstr&component=Kernel%20and%20drivers%20%28generic%29&product=MeeGo%20IVI CV-ML7213 bugs ]
|
|}

===MeeGo IVI Trunk Prototype Platforms===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! status
|-
|meego-ivi-ia32-conx
|Stephenville/Northville/Crossville
|Intel Atom 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, several issues open, visit [[IVI Images for ConneXt IOH]] for more information
|}

;ARM
:Jeremiah Foster and Jan-Simon Moeller are working on updates to enable automated weekly builds of MeeGo IVI images for the Beagleboard-XM.
:The suggested reference platform is the Beagleboard xM. The [[ARM/OMAP4_Panda|PandaBoard]] and [[ARM/Snowball|Snowball]] most likely will be supported in the future.
{| border="1"
! Image name
! Platform name
! chipset
! status
|-
| meego-ivi-armv7l
| Beagleboard xM
| OMAP 3
| Not yet smoke tested. No QA
|-
| meego-ivi-armv7l
| Tegra2
| ARM v7 rev 0
| Not yet smoke tested. No QA
|-
|}

===[http://sf2011.meego.com/sites/all/files/slides/meegocon2011developmentboardbofslides.pdf MeeGo IVI Development Boards]===

;IA32
{| border="1"
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! price/availability as of 5/11
! tested with MeeGo?
|-
|Intel Embedded Development Board 1-N450/1-D510
|N450 or D510
|Intel 82801HM
|SSD, WiFi, SATA, USB, SPI, GPIO, PCIe, UART, GigE, Audio, IEGD, DMA, I2C
|[http://edc.intel.com/Platforms/Atom-N450-D410-D510/Development-Board/#bd1-content=bd1-toggle~~visible-content $149 for registered users]
|[http://wiki.meego.com/Devices/Ideapad yes]
|}

;ARM

Per Stskeeps on meego-arm IRC on 6/2/2011, Nokia-provided N900 SGX530 drivers with hardfp extensions are known to work with SGX530 revisions 121 and 125. Which OMAP3 SoCs have revision 121 and 125 is not always straightforward to determine. dm8tbr reports problems with N900 hardfp drivers on Beagleboard xM. Stskeeps reports success with these drivers on Beagleboard C4. Tripzero reports success with hardfp drivers on old build of IGEPv2 that had the Cortex A8 processor.

{| border="1"
! Platform name
! Processor
! GPU; [[http://wiki.meego.com/ARM/hardfp hardfp?]]
! Memory
! Features
! price/availability as of 5/11
! tested with MeeGo?
|-
|[http://www.igloocommunity.org/ Snowball] (usable in end products)
|Cortex A-9 Dual-Core Nova A9500 1 GHz
|ARM Mali 400, [[ARM/Snowball|yes]]
|1 GB
|HDMI, WiFi b/g/n, Bluetooth, GPS, USB OTG, FSMC, HSI, Audio, MiPi CSI / Camera, LCD, MiPi DSI, UART, SPI, I2C, GPIO, SD/MMC, accelerometer, magnetometer, gyrometer, pressure sensor [[ARM/Snowball|(complete specs)]]
| [[ARM/Snowball|June]]
| [[ARM/Snowball|yes]]
|-
|[http://www.igep.es/index.php?option=com_content&view=article&id=46&Itemid=55 IGEPv2]
|[http://www.igep.es/public_docs/IGEPv2/HW_User_Manuals/MAN-PR-IGEP.0020.HW_USER_MANUAL.pdf DM3730 1 GHz]
|Imagination Technologies SGX530, yes? (tested by IGES with both TI and Nokia drivers)
|512 MB
|GigE, WiFi b/g, Bluetooth, USB OTG, USB Host, DVI-D, audio, SPI, UART, LCD, serial; [http://shop.igep.es/index.php?main_page=product_info&cPath=1&products_id=49 expansion board] with GSM, VGA, video in, camera, '''CAN'''
| 116.0€ and up plus 152.0€ for expansion board
| yes, but with older Cortex A8 build
|-
|[http://www.variscite.com/products/item/35-var-am35customboard Variscite VAR-AM3517 CustomBoard]
|[http://www.variscite.com/images/stories/DataSheets/VAR-SOM-AM35_1_15.pdf Cortex A-8 Sitara 600 MHz]
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|DMA, QCIF, LCD, SDTV, S-Video, USB, USB OTG, I2C, McSPI, GPIO, MMC, JTAG, '''CAN'''
|$1150 plus shipping
| no
|-
|[http://www.origenboard.org Samsung Origen]
|Samsung Exynos 4210 Cortex A-9 1 GHz
|ARM Mali 400, [http://forums.arm.com/index.php?/topic/14236-mali-gpus-linux-device-drivers-r2p0-05rel0-source-code-released/ reuse Snowball drivers?]
|1 GB
|HMDI, SD, WiFi, Bluetooth, audio, LCD, JTAG, camera
|[http://www.insignal.co.kr "sub-$200", June 25]
|no
|-
|[http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=IMX53QSB i.MX53 Quick Start Board]
|Cortex A-8 1 GHz
|Freescale GPUv3, [http://imxcommunity.org/profiles/blogs/ubuntu-rebuilt-with-hardfp yes]
|1 GB
|LVDS, LCD, HDMI, SPDIF, I2C, SSI, SPI, SD/MMC, microSD, SATA, GigE, USB, USB OTG, JTAG, UART, accelerometer
|$149
|[http://www.youtube.com/watch?feature=player_embedded&v=osDlTdl5lAk yes, similar HW]
|-
|[http://pandaboard.org/ Pandaboard]
|Cortex A-9 Dual-Core OMAP 4430 1 GHz
|Imagination Technologies SGX540, [http://article.gmane.org/gmane.comp.embedded.pandaboard/1771/match=hardfp not yet]
|1 GB
|SD/MMC, UART, Camera connector, USB OTG, Audio, GiGE, LCD connector, HDMI, WiFi, Bluetooth, JTAG, SPI, GPIO, I2C, McBSP
|[http://pandaboard.org/content/buy $179]
|[[ARM/OMAP4_Panda|yes]]
|-
|[http://beagle.s3.amazonaws.com/design/xM-A/BB_xM_SRM_A2_01.pdf Beagleboard Xm]
|Cortex A-8 DM3730 1GHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|512 MB
|uSD, USB, USB OTG, UART, McBSP, JTAG, GiGE, Audio, DVI-D, Camera connector, McBSP, I2C, GPIO, MMC2/3, ADC, LCD connector
|[http://beagleboard.org/buy $149]
|[[ARM/Meego_on_Beagleboard_from_scratch|yes]]
|-
|[http://beagleboard.org/static/BBSRM_latest.pdf Beagleboard C4]
|Cortex A-8 OMAP3530 720 MHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|I2C, I2S, SPI, MMC, USB, UART, USB OTG, S-Video, Audio, LCD, JTAG, GiGE
|[http://beagleboard.org/buy $125]
|[[ARM/Meego_IVI_on_Beagle|yes]]
|}

=== Releases ===
* [http://meego.com/downloads/releases/1.2/meego-v1.2-in-vehicle-infotainment-ivi MeeGo IVI 1.2]
* [http://meego.com/downloads/releases/1.1/meego-v1.1-in-vehicle-infotainment-ivi MeeGo IVI 1.1]
* [http://meego.com/downloads/releases/1.0/meego-v1.0-in-vehicle-infotainment-ivi MeeGo IVI 1.0]

== Resources ==
* IRC irc.freenode.org #meego-ivi
* Mailing list sign-up: http://lists.meego.com/listinfo/meego-ivi
* Mailing list archive: http://lists.meego.com/pipermail/meego-ivi/
* [[Presentations_about_meego-ivi#Presentations_and_Articles_about_MeeGo_IVI|Presentations and articles about meego-ivi]]
* [[In-vehicle/IVI for users and developers|IVI for users and developers]]
* [[IVITopic|Topics]]

[[Category:IVI]]

In-vehicle

2011-06-07T08:45:30Z

Joel: /* Working Group */

= 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: '''[http://meego.com/users/RudolfStreif 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:
*** Intel: '''[http://meego.com/users/jahoffmann Joel Hoffmann]'''
*** Nokia: '''[http://meego.com/users/alistair Alistair Adams]'''
*** Pelagicore: '''[http://meego.com/users/mikael Mikael Soderberg]'''
*** Visteon: '''[http://meego.com/users/PavelKonopelko Pavel Konopelko]'''

* Product Manager (cross-function across Working Group and Project Team)
** Unifies and prioritizes overall requirements set.
** Owns the roadmap.
** co-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 with the Lead Architects and Lead Designers on effort estimates and schedules.
** co-leads the Project Team together with the Product 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: '''[http://meego.com/users/joel Joel Clark (Intel)]'''

==== Working Group Meetings and Minutes ====
The Working Group meets regularly. Information on current and past meetings can be found on [[in-vehicle/working-group|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: '''[http://meego.com/users/tomcounihan 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: '''[http://meego.com/users/jeremiah 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.

== Shipping MeeGo IVI Products ==

* [http://news.softpedia.com/news/MeeGo-Powered-In-Vehicle-Information-System-Makes-Appearance-at-MWC-2011-184651.shtml Hawtai B11]
* [http://www.allaboutmeego.com/news/item/12918_Red_Flag_Software_announces_Me.php Geely EC8]
* [http://www.ieimobile.com/ikarpc08.html iKarPC]

== MeeGo IVI Demos ==

* MeeGo IVI UI from ICS: [http://www.youtube.com/watch?v=ZWbfGzyLoh8 video] and [http://www.ics.com/services/qtquick info], including source code

== 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.

The roadmap pages are the central collaboration point on laying out the future of MeeGo IVI. Here architecture details, system diagrams, use cases, etc. are shared.

[[In-vehicle/Roadmap|View the Roadmap]]

Before any new feature is committed to the Roadmap, a feature request is created in http://bugs.meego.com. Current MeeGo IVI feature requests can be found [https://bugs.meego.com/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=MeeGo+IVI+Features&content= here]

[https://bugs.meego.com/enter_bug.cgi?product=MeeGo%20IVI%20Features 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 in the [[In-vehicle/Roadmap|IVI roadmap]].

=== 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. [[Release Engineering/Release Versioning|MeeGo Release Versioning]] explains the build version numbering scheme. For example '''1.2.80.xx''' is a 1.2 Alpha build, '''1.2.90.xx''' is a 1.2 Beta build, '''1.2.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.

'''MeeGo IVI 1.2 Feature Status'''

[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]

[[In-vehicle/IVIHome Guide|Guide for the IVI Home Screen]]

;May 15, 2011
The MeeGo 1.2 release is scheduled for May 19, 2011. The following changes have been made in IVI features for MeeGo 1.2 compared to MeeGo 1.1

:IVI Home Screen Changes
::The IVI home screen has been ported to QML and it's now based on the MeeGo UX and launched through meego-ux-daemon. It implements an updated scroll menu and also supports quick access to commonly used apps through the desktop and a Top Application task bar. The scroll menu navigation 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. Both Text to Speech and Speech Recognition can now be toggled on the home screen for easier access. Since the UX is now based on QML, it makes customizing the UI much easier since they are script-based, and thus without the need of re-compiling for any changes.

::See [[In-vehicle/IVIHome Guide|Guide for the IVI Home Screen]] for more information.

:New Sample Applications
::The sample applications in MeeGo IVI 1.1 based on the MeeGo Touch Framework have been replaced in MeeGo 1.2 with a collection of commonly used applications based on QML. These can be accessed via the IVI home screen as discussed above.

:Nokia Terminal Mode
::Packages implementing the client side of Nokia Terminal Mode have been included in the build repositories. There are two packages(libqterminalmode and qterminalmodeclient) which must be installed from the ''oss'' repositories in order to try this code. These packages interact with phonesets that support the server side of Nokia Terminal Mode. Nokia has developer kit phone sets that implement the server side of terminal mode. [http://www.terminalmode.org/en/developer/developer-offering/ Terminal Mode Developer Offering] has more information about the software and how to get developer kits
: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. Also included in the repository (but not in the default boot image) is the <nowiki> "emgd-gui"</nowiki> utility for configuring and managing the graphics driver. Documentation and information on product support may be found on the [http://edc.intel.com/Software/Downloads/EMGD/ EMGD download page]

::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/Software/Downloads/EMGD/

===MeeGo IVI 1.2 Release Supported Platforms===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! status
! price/availability
|-
|meego-ivi-ia32
|Congatec IVI Kit (Russellville)
|Intel Atom Z5xx Series and Intel System Controller Hub US15Wx (eMenlow)
|Timberdale
|GPIO, DMA, SPI, I2C, UART, USB, IDE, Audio, KS8842 GigE, EMGD, Video-in, SDHC, TSC2007, I2S, SDHC, ADV7180, BT, Radio
|No known driver issues
|unavailable 5/11
|-
|meego-ivi-ia32
|Crown Bay
|Intel Atom 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
|Stephenville/Crossville
|Intel Atom E6xx Series for Embedded (Tunnel Creek)
|Oki Semiconductors ML7213 IVI IOH
|GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, EMGD, SD/SDIO/MMC, USB-OTG, TDM, sDVO
|No known driver issues
|
|}

===MeeGo IVI Trunk Prototype Platforms===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! status
|-
|meego-ivi-ia32-conx
|Stephenville/Northville/Crossville
|Intel Atom 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, several issues open
|}

;ARM
:Jeremiah Foster and Jan-Simon Moeller are working on updates to enable automated weekly builds of MeeGo IVI images for the Beagleboard-XM.
:The suggested reference platform is the Beagleboard xM. The [[ARM/OMAP4_Panda|PandaBoard]] and [[ARM/Snowball|Snowball]] most likely will be supported in the future.
{| border="1"
! Image name
! Platform name
! chipset
! status
|-
| meego-ivi-armv7l
| Beagleboard xM
| OMAP 3
| Not yet smoke tested. No QA
|-
| meego-ivi-armv7l
| Tegra2
| ARM v7 rev 0
| Not yet smoke tested. No QA
|-
|}

===[http://sf2011.meego.com/sites/all/files/slides/meegocon2011developmentboardbofslides.pdf MeeGo IVI Development Boards]===

;IA32
{| border="1"
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! price/availability as of 5/11
! tested with MeeGo?
|-
|Intel Embedded Development Board 1-N450/1-D510
|N450 or D510
|Intel 82801HM
|SSD, WiFi, SATA, USB, SPI, GPIO, PCIe, UART, GigE, Audio, IEGD, DMA, I2C
|[http://edc.intel.com/Platforms/Atom-N450-D410-D510/Development-Board/#bd1-content=bd1-toggle~~visible-content $149 for registered users]
|[http://wiki.meego.com/Devices/Ideapad yes]
|}

;ARM

Per Stskeeps on meego-arm IRC on 6/2/2011, Nokia-provided N900 SGX530 drivers with hardfp extensions are known to work with SGX530 revisions 121 and 125. Which OMAP3 SoCs have revision 121 and 125 is not always straightforward to determine. dm8tbr reports problems with N900 hardfp drivers on Beagleboard xM. Stskeeps reports success with these drivers on Beagleboard C4. Tripzero reports success with hardfp drivers on old build of IGEPv2 that had the Cortex A8 processor.

{| border="1"
! Platform name
! Processor
! GPU; [[http://wiki.meego.com/ARM/hardfp hardfp?]]
! Memory
! Features
! price/availability as of 5/11
! tested with MeeGo?
|-
|[http://www.igep.es/index.php?option=com_content&view=article&id=46&Itemid=55 IGEPv2]
|[http://www.igep.es/public_docs/IGEPv2/HW_User_Manuals/MAN-PR-IGEP.0020.HW_USER_MANUAL.pdf DM3730 1 GHz]
|Imagination Technologies SGX530, yes? (tested by IGES with both TI and Nokia drivers)
|512 MB
|GigE, WiFi b/g, Bluetooth, USB OTG, USB Host, DVI-D, audio, SPI, UART, LCD, serial; [http://shop.igep.es/index.php?main_page=product_info&cPath=1&products_id=49 expansion board] with GSM, VGA, video in, camera, '''CAN'''
| 116.0€ and up plus 152.0€ for expansion board
| yes, but with older Cortex A8 build
|-
|[http://www.variscite.com/products/item/35-var-am35customboard Variscite VAR-AM3517 CustomBoard]
|[http://www.variscite.com/images/stories/DataSheets/VAR-SOM-AM35_1_15.pdf Cortex A-8 Sitara 600 MHz]
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|DMA, QCIF, LCD, SDTV, S-Video, USB, USB OTG, I2C, McSPI, GPIO, MMC, JTAG, '''CAN'''
|$1150 plus shipping
| no
|-
|[http://www.engadget.com/2011/05/29/linaro-and-samsung-roll-out-exynos-4210-based-origen-development/ Samsung Origen]
|Samsung Exynos 4210 Cortex A-9 1 GHz
|ARM Mali 400, [http://forums.arm.com/index.php?/topic/14236-mali-gpus-linux-device-drivers-r2p0-05rel0-source-code-released/ ?]
|1 GB
|HMDI, SD, WiFi, Bluetooth, audio, LCD, JTAG, camera
|[http://www.insignal.co.kr "sub-$200"]
|no
|-
|[http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=IMX53QSB i.MX53 Quick Start Board]
|Cortex A-8 1 GHz
|Freescale GPUv3, [http://imxcommunity.org/profiles/blogs/ubuntu-rebuilt-with-hardfp yes]
|1 GB
|LVDS, LCD, HDMI, SPDIF, I2C, SSI, SPI, SD/MMC, microSD, SATA, GigE, USB, USB OTG, JTAG, UART, accelerometer
|$149
|[http://www.youtube.com/watch?feature=player_embedded&v=osDlTdl5lAk yes, similar HW]
|-
|[http://www.igloocommunity.org/ Snowball] (usable in end products)
|Cortex A-9 Dual-Core Nova A9500 1 GHz
|ARM Mali 400, [[ARM/Snowball|yes]]
|1 GB
|HDMI, WiFi b/g/n, Bluetooth, GPS, USB OTG, FSMC, HSI, Audio, MiPi CSI / Camera, LCD, MiPi DSI, UART, SPI, I2C, GPIO, SD/MMC, accelerometer, magnetometer, gyrometer, pressure sensor [[ARM/Snowball|(complete specs)]]
| [[ARM/Snowball|June]]
| [[ARM/Snowball|yes]]
|-
|[http://pandaboard.org/ Pandaboard]
|Cortex A-9 Dual-Core OMAP 4430 1 GHz
|Imagination Technologies SGX540, [http://article.gmane.org/gmane.comp.embedded.pandaboard/1771/match=hardfp not yet]
|1 GB
|SD/MMC, UART, Camera connector, USB OTG, Audio, GiGE, LCD connector, HDMI, WiFi, Bluetooth, JTAG, SPI, GPIO, I2C, McBSP
|[http://pandaboard.org/content/buy $179]
|[[ARM/OMAP4_Panda|yes]]
|-
|[http://beagle.s3.amazonaws.com/design/xM-A/BB_xM_SRM_A2_01.pdf Beagleboard Xm]
|Cortex A-8 DM3730 1GHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|512 MB
|uSD, USB, USB OTG, UART, McBSP, JTAG, GiGE, Audio, DVI-D, Camera connector, McBSP, I2C, GPIO, MMC2/3, ADC, LCD connector
|[http://beagleboard.org/buy $149]
|[[ARM/Meego_on_Beagleboard_from_scratch|yes]]
|-
|[http://beagleboard.org/static/BBSRM_latest.pdf Beagleboard C4]
|Cortex A-8 OMAP3530 720 MHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|I2C, I2S, SPI, MMC, USB, UART, USB OTG, S-Video, Audio, LCD, JTAG, GiGE
|[http://beagleboard.org/buy $125]
|[[ARM/Meego_IVI_on_Beagle|yes]]
|}

=== Releases ===
* [http://meego.com/downloads/releases/1.2/meego-v1.2-in-vehicle-infotainment-ivi MeeGo IVI 1.2]
* [http://meego.com/downloads/releases/1.1/meego-v1.1-in-vehicle-infotainment-ivi MeeGo IVI 1.1]
* [http://meego.com/downloads/releases/1.0/meego-v1.0-in-vehicle-infotainment-ivi MeeGo IVI 1.0]

== Resources ==
* IRC irc.freenode.org #meego-ivi
* Mailing list sign-up: http://lists.meego.com/listinfo/meego-ivi
* Mailing list archive: http://lists.meego.com/pipermail/meego-ivi/
* [[Presentations_about_meego-ivi#Presentations_and_Articles_about_MeeGo_IVI|Presentations and articles about meego-ivi]]
* [[In-vehicle/IVI for users and developers|IVI for users and developers]]
* [[IVITopic|Topics]]

[[Category:IVI]]

In-vehicle

2011-06-02T15:16:04Z

Joel: /* Shipping MeeGo IVI Products */

= 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: '''[http://meego.com/users/RudolfStreif 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:
*** Intel: '''[http://meego.com/users/jahoffmann Joel Hoffmann]'''
*** Nokia: '''[http://meego.com/users/alistair Alistair Adams]'''
*** Pelagicore: '''[http://meego.com/users/mikael Mikael Soderberg]'''
*** Visteon: '''[http://meego.com/users/PavelKonopelko Pavel Konopelko]'''

* 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: '''[http://meego.com/users/joel Joel Clark (Intel)]'''

==== Working Group Meetings and Minutes ====
The Working Group meets regularly. Information on current and past meetings can be found on [[in-vehicle/working-group|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: '''[http://meego.com/users/tomcounihan 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: '''[http://meego.com/users/jeremiah 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.

== Shipping MeeGo IVI Products ==

* [http://news.softpedia.com/news/MeeGo-Powered-In-Vehicle-Information-System-Makes-Appearance-at-MWC-2011-184651.shtml Hawtai B11]
* [http://www.allaboutmeego.com/news/item/12918_Red_Flag_Software_announces_Me.php Geely EC8]
* [http://www.ieimobile.com/ikarpc08.html iKarPC]

== MeeGo IVI Demos ==

* MeeGo IVI UI from ICS: [http://www.youtube.com/watch?v=ZWbfGzyLoh8 video] and [http://www.ics.com/services/qtquick info], including source code

== 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.

The roadmap pages are the central collaboration point on laying out the future of MeeGo IVI. Here architecture details, system diagrams, use cases, etc. are shared.

[[In-vehicle/Roadmap|View the Roadmap]]

Before any new feature is committed to the Roadmap, a feature request is created in http://bugs.meego.com. Current MeeGo IVI feature requests can be found [https://bugs.meego.com/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=MeeGo+IVI+Features&content= here]

[https://bugs.meego.com/enter_bug.cgi?product=MeeGo%20IVI%20Features 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 in the [[In-vehicle/Roadmap|IVI roadmap]].

=== 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. [[Release Engineering/Release Versioning|MeeGo Release Versioning]] explains the build version numbering scheme. For example '''1.2.80.xx''' is a 1.2 Alpha build, '''1.2.90.xx''' is a 1.2 Beta build, '''1.2.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.

'''MeeGo IVI 1.2 Feature Status'''

[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]

[[In-vehicle/IVIHome Guide|Guide for the IVI Home Screen]]

;May 15, 2011
The MeeGo 1.2 release is scheduled for May 19, 2011. The following changes have been made in IVI features for MeeGo 1.2 compared to MeeGo 1.1

:IVI Home Screen Changes
::The IVI home screen has been ported to QML and it's now based on the MeeGo UX and launched through meego-ux-daemon. It implements an updated scroll menu and also supports quick access to commonly used apps through the desktop and a Top Application task bar. The scroll menu navigation 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. Both Text to Speech and Speech Recognition can now be toggled on the home screen for easier access. Since the UX is now based on QML, it makes customizing the UI much easier since they are script-based, and thus without the need of re-compiling for any changes.

::See [[In-vehicle/IVIHome Guide|Guide for the IVI Home Screen]] for more information.

:New Sample Applications
::The sample applications in MeeGo IVI 1.1 based on the MeeGo Touch Framework have been replaced in MeeGo 1.2 with a collection of commonly used applications based on QML. These can be accessed via the IVI home screen as discussed above.

:Nokia Terminal Mode
::Packages implementing the client side of Nokia Terminal Mode have been included in the build repositories. There are two packages(libqterminalmode and qterminalmodeclient) which must be installed from the ''oss'' repositories in order to try this code. These packages interact with phonesets that support the server side of Nokia Terminal Mode. Nokia has developer kit phone sets that implement the server side of terminal mode. [http://www.terminalmode.org/en/developer/developer-offering/ Terminal Mode Developer Offering] has more information about the software and how to get developer kits
: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. Also included in the repository (but not in the default boot image) is the <nowiki> "emgd-gui"</nowiki> utility for configuring and managing the graphics driver. Documentation and information on product support may be found on the [http://edc.intel.com/Software/Downloads/EMGD/ EMGD download page]

::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/Software/Downloads/EMGD/

===MeeGo IVI 1.2 Release Supported Platforms===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! status
! price/availability
|-
|meego-ivi-ia32
|Congatec IVI Kit (Russellville)
|Intel Atom Z5xx Series and Intel System Controller Hub US15Wx (eMenlow)
|Timberdale
|GPIO, DMA, SPI, I2C, UART, USB, IDE, Audio, KS8842 GigE, EMGD, Video-in, SDHC, TSC2007, I2S, SDHC, ADV7180, BT, Radio
|No known driver issues
|unavailable 5/11
|-
|meego-ivi-ia32
|Crown Bay
|Intel Atom 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
|Stephenville/Crossville
|Intel Atom E6xx Series for Embedded (Tunnel Creek)
|Oki Semiconductors ML7213 IVI IOH
|GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, EMGD, SD/SDIO/MMC, USB-OTG, TDM, sDVO
|No known driver issues
|
|}

===MeeGo IVI Trunk Prototype Platforms===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! status
|-
|meego-ivi-ia32-conx
|Stephenville/Northville/Crossville
|Intel Atom 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, several issues open
|}

;ARM
:Jeremiah Foster and Jan-Simon Moeller are working on updates to enable automated weekly builds of MeeGo IVI images for the Beagleboard-XM.
:The suggested reference platform is the Beagleboard xM. The [[ARM/OMAP4_Panda|PandaBoard]] and [[ARM/Snowball|Snowball]] most likely will be supported in the future.
{| border="1"
! Image name
! Platform name
! chipset
! status
|-
| meego-ivi-armv7l
| Beagleboard xM
| OMAP 3
| Not yet smoke tested. No QA
|-
| meego-ivi-armv7l
| Tegra2
| ARM v7 rev 0
| Not yet smoke tested. No QA
|-
|}

===[http://sf2011.meego.com/sites/all/files/slides/meegocon2011developmentboardbofslides.pdf MeeGo IVI Development Boards]===

;IA32
{| border="1"
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! price/availability as of 5/11
! tested with MeeGo?
|-
|Intel Embedded Development Board 1-N450/1-D510
|N450 or D510
|Intel 82801HM
|SSD, WiFi, SATA, USB, SPI, GPIO, PCIe, UART, GigE, Audio, IEGD, DMA, I2C
|[http://edc.intel.com/Platforms/Atom-N450-D410-D510/Development-Board/#bd1-content=bd1-toggle~~visible-content $149 for registered users]
|[http://wiki.meego.com/Devices/Ideapad yes]
|}

;ARM
{| border="1"
! Platform name
! Processor
! GPU; [[http://wiki.meego.com/ARM/hardfp hardfp?]]
! Memory
! Features
! price/availability as of 5/11
! tested with MeeGo?
|-
|[http://www.variscite.com/products/item/35-var-am35customboard Variscite VAR-AM3517 CustomBoard]
|[http://www.variscite.com/images/stories/DataSheets/VAR-SOM-AM35_1_15.pdf Cortex A-8 Sitara 600 MHz]
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|DMA, QCIF, LCD, SDTV, S-Video, USB, USB OTG, I2C, McSPI, GPIO, MMC, JTAG, '''CAN'''
|$1150 plus shipping
| no
|-
|[http://www.engadget.com/2011/05/29/linaro-and-samsung-roll-out-exynos-4210-based-origen-development/ Samsung Origen]
|Samsung Exynos 4210 Cortex A-9 1 GHz
|ARM Mali 400, [http://forums.arm.com/index.php?/topic/14236-mali-gpus-linux-device-drivers-r2p0-05rel0-source-code-released/ ?]
|1 GB
|HMDI, SD, WiFi, Bluetooth, audio, LCD, JTAG, camera
|[http://www.insignal.co.kr "sub-$200"]
|no
|-
|[http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=IMX53QSB i.MX53 Quick Start Board]
|Cortex A-8 1 GHz
|Freescale GPUv3, [http://imxcommunity.org/profiles/blogs/ubuntu-rebuilt-with-hardfp yes]
|1 GB
|LVDS, LCD, HDMI, SPDIF, I2C, SSI, SPI, SD/MMC, microSD, SATA, GigE, USB, USB OTG, JTAG, UART, accelerometer
|$149
|[http://www.youtube.com/watch?feature=player_embedded&v=osDlTdl5lAk yes, similar HW]
|-
|[http://www.igloocommunity.org/ Snowball]
|Cortex A-9 Dual-Core Nova A9500 1 GHz
|ARM Mali 400, [http://forums.arm.com/index.php?/topic/14236-mali-gpus-linux-device-drivers-r2p0-05rel0-source-code-released/ ?]
|1 GB
|HDMI, WiFi b/g/n, Bluetooth, GPS, USB OTG, FSMC, HSI, Audio, MiPi CSI / Camera, LCD, MiPi DSI, UART, SPI, I2C, GPIO, SD/MMC, accelerometer, magnetometer, gyrometer, pressure sensor [[ARM/Snowball|(complete specs)]]
| [[ARM/Snowball|$225]]
| [[ARM/Snowball|yes]]
|-
|[http://pandaboard.org/ Pandaboard]
|Cortex A-9 Dual-Core OMAP 4430 1 GHz
|Imagination Technologies SGX540, [http://article.gmane.org/gmane.comp.embedded.pandaboard/1771/match=hardfp not yet]
|1 GB
|SD/MMC, UART, Camera connector, USB OTG, Audio, GiGE, LCD connector, HDMI, WiFi, Bluetooth, JTAG, SPI, GPIO, I2C, McBSP
|[http://pandaboard.org/content/buy $179]
|[[ARM/OMAP4_Panda|yes]]
|-
|[http://beagle.s3.amazonaws.com/design/xM-A/BB_xM_SRM_A2_01.pdf Beagleboard Xm]
|Cortex A-8 DM3730 1GHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|512 MB
|uSD, USB, USB OTG, UART, McBSP, JTAG, GiGE, Audio, DVI-D, Camera connector, McBSP, I2C, GPIO, MMC2/3, ADC, LCD connector
|[http://beagleboard.org/buy $149]
|[[ARM/Meego_on_Beagleboard_from_scratch|yes]]
|-
|[http://beagleboard.org/static/BBSRM_latest.pdf Beagleboard C4]
|Cortex A-8 OMAP3530 720 MHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|I2C, I2S, SPI, MMC, USB, UART, USB OTG, S-Video, Audio, LCD, JTAG, GiGE
|[http://beagleboard.org/buy $125]
|[[ARM/Meego_IVI_on_Beagle|yes]]
|}

=== Releases ===
* [http://meego.com/downloads/releases/1.2/meego-v1.2-in-vehicle-infotainment-ivi MeeGo IVI 1.2]
* [http://meego.com/downloads/releases/1.1/meego-v1.1-in-vehicle-infotainment-ivi MeeGo IVI 1.1]
* [http://meego.com/downloads/releases/1.0/meego-v1.0-in-vehicle-infotainment-ivi MeeGo IVI 1.0]

== Resources ==
* IRC irc.freenode.org #meego-ivi
* Mailing list sign-up: http://lists.meego.com/listinfo/meego-ivi
* Mailing list archive: http://lists.meego.com/pipermail/meego-ivi/
* [[Presentations_about_meego-ivi#Presentations_and_Articles_about_MeeGo_IVI|Presentations and articles about meego-ivi]]
* [[In-vehicle/IVI for users and developers|IVI for users and developers]]
* [[IVITopic|Topics]]

[[Category:IVI]]

In-vehicle

2011-05-21T19:34:47Z

Joel: /* MeeGo IVI Weekly Builds */

In-vehicle

2011-05-20T16:20:16Z

Joel: /* Working Group */

In-vehicle/Roadmap

2011-05-15T10:48:50Z

Joel: /* MeeGo 1.2 Target Features */

== High-level Roadmap ==

The big picture:
* [[In-vehicle/Roadmap/FeatureScope|Feature Scope]]
* [[In-vehicle/Roadmap/SystemArchitecture|System Architecture]]

Details on Roadmap items:
* [[In-vehicle/Roadmap/AutomotiveNetworking|Automotive Networking]]
* [[In-vehicle/Roadmap/AudioManagement|Audio management]]
* [[In-vehicle/Roadmap/UX|User Experience]]
* [[In-vehicle/Roadmap/API|API]]
* App Store Demonstration
* CE Device connectivity
* Navigation
* Auto UX
* BSP/ARM-support

To help the discussion of the road map content, there is a separate overview of the [[In-vehicle/Roadmap/FeatureScope|potential feature scope]] for In-Vehicle Infotainment.

== Feature list from Bugzilla ==
Feature suggestions and planning is tracked in the MeeGo bugzilla system.

[https://bugs.meego.com/enter_bug.cgi?product=MeeGo%20IVI%20Features Submit new MeeGo IVI feature suggestions]

New feature suggestions need design and development resources to be committed before they become "ACCEPTED".

[https://bugs.meego.com/report.cgi?x_axis_field=bug_status&y_axis_field=version&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=MeeGo+Features&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= Current status of features suggested or planned for MeeGo IVI]

== MeeGo 1.2 Target Features ==
The MeeGo 1.2 development milestones are:
* November 1, 2010 MeeGo 1.2 merge window open
* January 20, 2011 MeeGo 1.2 Feature freeze (Alpha finish, Beta start)
* March 20, 2011 MeeGo 1.2 Release Candidate start
* April 29, 2011 MeeGo 1.2 Release branch created
* May 19, 2011 MeeGo 1.2.0 Final Release

The new features planned for the MeeGo IVI 1.2 release are:
* Terminal Mode from Nokia [https://bugs.meego.com/show_bug.cgi?id=8704 Feature 8704]
* Integration of EMGD graphics [https://bugs.meego.com/show_bug.cgi?id=6863 Feature 6863] [http://bugs.meego.com/show_bug.cgi?id=8815 Feature 8815]
* Integration of TopCliff/Crown Bay drivers [https://bugs.meego.com/show_bug.cgi?id=6862 Feature 6862]
* Integration of Crossville ML7213/OKI IVI IOH drivers [https://bugs.meego.com/show_bug.cgi?id=12050 Feature 12050]
* Updating IVI Home screen with new layout for the task launch menus and porting from QT to QML.
* Updating sample apps (browser, contacts, video player, photo player, music player, settings) from MeeGo Touch Framework based (MTF) to QML based.

[[Category:IVI]]

In-vehicle

2011-05-15T10:47:06Z

Joel: /* MeeGo IVI Weekly Builds */

In-vehicle/Roadmap

2011-04-25T16:45:13Z

Joel: /* MeeGo 1.2 Target Features */

== High-level Roadmap ==

The big picture:
* [[In-vehicle/Roadmap/FeatureScope|Feature Scope]]
* [[In-vehicle/Roadmap/SystemArchitecture|System Architecture]]

Details on Roadmap items:
* [[In-vehicle/Roadmap/AutomotiveNetworking|Automotive Networking]]
* [[In-vehicle/Roadmap/AudioManagement|Audio management]]
* [[In-vehicle/Roadmap/UX|User Experience]]
* [[In-vehicle/Roadmap/API|API]]
* App Store Demonstration
* CE Device connectivity
* Navigation
* Auto UX
* BSP/ARM-support

To help the discussion of the road map content, there is a separate overview of the [[In-vehicle/Roadmap/FeatureScope|potential feature scope]] for In-Vehicle Infotainment.

== Feature list from Bugzilla ==
Feature suggestions and planning is tracked in the MeeGo bugzilla system.

[https://bugs.meego.com/enter_bug.cgi?product=MeeGo%20IVI%20Features Submit new MeeGo IVI feature suggestions]

New feature suggestions need design and development resources to be committed before they become "ACCEPTED".

[https://bugs.meego.com/report.cgi?x_axis_field=bug_status&y_axis_field=version&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=MeeGo+Features&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= Current status of features suggested or planned for MeeGo IVI]

== MeeGo 1.2 Target Features ==
The MeeGo 1.2 development milestones are:
* November 1, 2010 MeeGo 1.2 merge window open
* January 20, 2011 MeeGo 1.2 Feature freeze (Alpha finish, Beta start)
* March 20, 2011 MeeGo 1.2 Release Candidate start
* April 29, 2011 MeeGo 1.2 Release branch created
* May 19, 2011 MeeGo 1.2.0 Final Release

The new features planned for the MeeGo IVI 1.2 release are:
* Terminal Mode from Nokia [http://bugs.meego.com/show_bug.cgi?id=8704 Feature 8704]
* Integration of EMGD graphics [http://bugs.meego.com/show_bug.cgi?id=6863 Feature 6863] [http://bugs.meego.com/show_bug.cgi?id=8815 Feature 8815]
* Integration of TopCliff/Crown Bay drivers [http://bugs.meego.com/show_bug.cgi?id=6862 Feature 6862]
* Integration of Northville/ML7213/OKI IVI IOH drivers [http://bugs.meego.com/show_bug.cgi?id=12050 Feature 12050]
* Integration of Northville/ST ConneXt drivers [http://bugs.meego.com/show_bug.cgi?id=6865 Feature 6865]
* Updating IVI Home screen with new layout for the task launch menus and porting from QT to QML.
* Updating sample apps (browser, contacts, video player, photo player, music player, settings) from MeeGo Touch Framework based (MTF) to QML based.

In-vehicle

2011-04-25T14:30:01Z

Joel: /* MeeGo IVI 1.2 Supported Platforms */

In-vehicle

2011-04-10T23:27:47Z

Joel: /* Roadmap */

In-vehicle

2011-03-08T11:53:06Z

Joel: /* MeeGo IVI Weekly Builds */

In-vehicle/IVIHome Guide

2011-03-08T11:41:55Z

Joel: /* IVIHome Guide */

=== IVIHome Guide ===
MeeGo IVI provides a "IVIHome" application that is the default MeeGo IVI homescreen when the system boots. This section provides information about the design and use of the MeeGo "IVIHome" screen and taskbar.

''' IVIHome Design Objectives'''

The primary objectives in designing the IVI Home Screen were:
# Provide a sample taskbar that utilizes a scrollwheel, Text to Speech and Speech Recognition so that it can be operated without distracting driver by requiring them to look at the display or a keyboard. During system development the IVIHome and taskbar application may still be operated via touchscreen or mouse.
# Provide an "automotive" look and feel with a rounded taskbar to reflect the scrollwheel use and the ability to switch the taskbar from left side to right side of the display, presuming the display is in the automotive center console and the steering wheel could be on the left or right.

''' IVIHome Use'''

Navigating the IVIHome taskbar may be done via touchscreen, scrollwheel, and Speech Recognition of voice commands with the help of Text to Speech (TTS).

Touchscreen support
* IVIHome has full touchscreen support for platforms with working touchscreen hardware and drivers
* IVIHome can also be navigated using a mouse and the user can use the mouse wheel to scroll through the menu.
Scrollwheel Support
*Currently only the Contour ShuttleXpress is supported since the key mapping is hard-coded.
*Currently only the IVIHome screen and taskbar support the ShuttleXpress. The application support has not been implemented yet.
*The ShuttleXpress controller has 5 dedicated mouse buttons and knob that turns left/right, all of these buttons simulate key presses on a hardware button in a car and currently only works when you are at the IVIHome screen, they are not yet supported in any of the applications.
*Just plug in the ShuttleXpress and it will recognize the device automatically (may have to reboot the system or restart by “pkill ivihome”)
* The buttons are mapped to the following functions:
**Button1 – BACK, this takes you back to the previous menu or closes the menu completely.
**Button2 – HOME, this will always open up the navigation menu if the menu is closed, or return you back to the home menu if you are in a sub menu.
**Button3 – SELECT/OPEN, this will open the highlighted menu or application, it is the same as clicking on the application.
**Knob Left – UP, use this to navigate through the menu in UP direction.
**Knob Right – DOWN, use this to navigate through the menu in DOWN direction.
Text-to-Speech(TTS)
*Supported by IVIHome menu navigation
*When you navigate the scroll menu list, it will use Festival to say the current menu item, you should hear “Navigation, Communication”, etc as you browse through the menu.
*Text to speech is turned on by default, however, if you use TTS with speech recognition on a system with a mic too close to the speakers, they might interfere.
*You can turn TTS on/off by editing the configuration file in /usr/share/ivihome/settings.xml and change <texttospeech>on<texttospeech> to off, then restart ivihome by executing “pkill ivihome”
Speech recognition (IVIHome menu voice commands)
*Speech recognition is supported by IVIHome. Speech recognition in applications needs to be added.
*IVIHome speech recognition does not support continuous speech, it only recognizes voice commands for the IVIhome menu as shown below
*To turn on speech recognition, click on the microphone icon on the taskbar, to turn it off, click again.
*The following tables list the supported voice commands (you can also look in /usr/share/ivihome/data/ivihome.jsgf):
Menu Navigation Commands
{| border="1"
!Voice Command
!Resulting action
|-
|"Home"
|Opens the home menu if the menu is closed, or returns to the home menu, same as the clicking HOME button on ShuttleXpress
|-
|"Back"
|goes back to the last menu, same as clicking the BACK button on ShuttleXpress
|-
|"Cancel"
|closes the menu completely
|-
|"Next"
|moves to the next menu item in the list, same as turning the knob to the RIGHT on the ShuttleXpress
|-
|"Previous"
|moves to the last menu item in the list, same as turning the knob to the LEFT on the ShuttleXpress
|-
|"Next Window"
|switches to the next opened application window on the taskbar
|-
|"Previous Window"
|switches to the previous opened application window on the taskbar
|-
|"Close Window"
|closes the current application window, exiting the app
|}

Named Category and Application Commands

You can directly name any Catagory listed in the Root Menu or specific applications shown in each Catagory Menu.
{| border="1"
!Catagory Command
!Recognized Application Commands
|-
|"Navigation"
|
|-
|"Driver Assistance"
|
|-
|"Communication"
|"Web", "Phone", "Connect"
|-
|"Media"
|"Photos", "Video", "Music"
|-
|"Other"
|"Activities", "Tools", "More Apps"
|}

Application commands

Voice commands may be used to skip menu navigation and go directly to specific applications
{| border="1"
!Voice Command
!Resulting action
|-
|"Open Navigation"
|opens the Navit application
|-
|"Open Dialer"
|opens the handsfree dialer application
|-
|"Open Contacts"
|opens the MeeGo contacts application
|-
|"Open Web"
|opens the Fennec browser
|-
|"Open Browser"
|opens the Fennec browser
|-
|"Open Photo"
|opens the the MeeGo photo application
|-
|"Open Music"
|opens the MeeGo music application
|-
|"Open Video"
|opens the MeeGo video application
|-
|"Open Setting"
|opens the the MeeGo control panel application
|}

The list of applications for each of the above application commands are defined in the /usr/share/ivihome/settings.xml. You can edit this file to change the application that is launched by the voice commands. You cannot change the vocabulary list directly, it needs to be re-generated. If you want to add more voice commands, you’ll have to add the command in the dictionary and re-generate the language model (grammar) and dictionary and implement the logic in the application.

In-vehicle/IVIHome Guide

2011-03-08T04:01:48Z

Joel: /* IVIHome Guide */

In-vehicle/IVIHome Guide

2011-03-08T03:45:18Z

Joel: Created page with "=== IVIHome Guide === MeeGo IVI provides a "IVIHome" application that is the default MeeGo IVI homescreen when the system boots. This section provides information about the desig…"

In-vehicle

2011-03-08T03:30:17Z

Joel: /* MeeGo IVI 1.2 Supported Platforms */

In-vehicle

2011-03-08T03:29:22Z

Joel: /* MeeGo IVI Weekly Builds */

In-vehicle/Roadmap

2011-02-18T02:28:19Z

Joel: /* MeeGo 1.2 Target Features */

In-vehicle

2011-02-14T16:39:06Z

Joel: /* MeeGo IVI Weekly Builds */

In-vehicle

2011-02-14T09:31:48Z

Joel: /* MeeGo IVI Weekly Builds */

In-vehicle

2011-02-14T02:25:30Z

Joel:

IVIWeeklyBuildTestPage

2011-02-14T02:23:54Z

Joel: /* MeeGo IVI Weekly Builds */

=== 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.

'''MeeGo IVI 1.2 Feature Status'''

[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

'''MeeGo IVI 1.2 Supported Platforms'''

;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.

IVIWeeklyBuildTestPage

2011-02-14T01:58:43Z

Joel: /* MeeGo IVI Weekly Builds */

=== 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.

'''MeeGo IVI 1.2 Feature Status'''

[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

'''MeeGo IVI 1.2 Supported Platforms'''

;IA32
:There are now two IA32 images built every week. These images support the following platforms:

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

IVIWeeklyBuildTestPage

2011-02-14T01:47:05Z

Joel: Created page with "=== 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 v…"

In-vehicle

2011-02-13T22:14:52Z

Joel: /* Roadmap */

In-vehicle/Roadmap

2011-02-13T22:07:09Z

Joel: /* Feature list from Bugzilla */

Packaging/Maintainers

2011-02-07T16:19:00Z

Joel:

{|border="1"
! Package
! Maintainers (bugowner)
! Development Project
|-

|[http://build.meego.com/package/show?package=ConsoleKit&project=Trunk ConsoleKit]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=FUR&project=Trunk FUR]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=GConf-dbus&project=Trunk GConf-dbus]
|zhongxin
|
|-
|[http://build.meego.com/package/show?package=ImageMagick&project=Trunk ImageMagick]
|
|
|-
|[http://build.meego.com/package/show?package=MAKEDEV&project=Trunk MAKEDEV]
|
|
|-
|[http://build.meego.com/package/show?package=ORBit2&project=Trunk ORBit2]
|
|
|-
|[http://build.meego.com/package/show?package=OpenCV&project=Trunk OpenCV]
|
|
|-
|[http://build.meego.com/package/show?package=OpenEXR&project=Trunk OpenEXR]
|
|
|-
|[http://build.meego.com/package/show?package=PackageKit&project=Trunk PackageKit]
|xiaoqiang
|devel:packagemanagement
|-
|[http://build.meego.com/package/show?package=PyOpenGL&project=Trunk PyOpenGL]
|
|
|-
|[http://build.meego.com/package/show?package=PyXML&project=Trunk PyXML]
|
|
|-
|[http://build.meego.com/package/show?package=PyYAML&project=Trunk PyYAML]
|jfding
|
|-
|[http://build.meego.com/package/show?package=SDL&project=Trunk SDL]
|
|
|-
|[http://build.meego.com/package/show?package=SDL_Pango&project=Trunk SDL_Pango]
|
|
|-
|[http://build.meego.com/package/show?package=SDL_gfx&project=Trunk SDL_gfx]
|
|
|-
|[http://build.meego.com/package/show?package=SDL_image&project=Trunk SDL_image]
|
|
|-
|[http://build.meego.com/package/show?package=SDL_mixer&project=Trunk SDL_mixer]
|
|
|-
|[http://build.meego.com/package/show?package=SDL_net&project=Trunk SDL_net]
|
|
|-
|[http://build.meego.com/package/show?package=SDL_ttf&project=Trunk SDL_ttf]
|
|
|-
|[http://build.meego.com/package/show?package=SOAPpy&project=Trunk SOAPpy]
|
|
|-
|[http://build.meego.com/package/show?package=WebKit&project=Trunk WebKit]
|yanli
|
|-
|[http://build.meego.com/package/show?package=WiMAX-Network-Service&project=Trunk WiMAX-Network-Service]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=Xaw3d&project=Trunk Xaw3d]
|
|
|-
|[http://build.meego.com/package/show?package=abiword&project=Trunk abiword]
|
|
|-
|[http://build.meego.com/package/show?package=acct&project=Trunk acct]
|
|
|-
|[http://build.meego.com/package/show?package=acl&project=Trunk acl]
|qzhao9
|
|-
|[http://build.meego.com/package/show?package=acpid&project=Trunk acpid]
|
|
|-
|[http://build.meego.com/package/show?package=adns&project=Trunk adns]
|
|
|-
|[http://build.meego.com/package/show?package=aiksaurus&project=Trunk aiksaurus]
|
|
|-
|[http://build.meego.com/package/show?package=alsa-lib&project=Trunk alsa-lib]
|vivian
|devel:multimedia
|-
|[http://build.meego.com/package/show?package=alsa-plugins&project=Trunk alsa-plugins]
|vivian
|devel:multimedia
|-
|[http://build.meego.com/package/show?package=alsa-utils&project=Trunk alsa-utils]
|vivian
|devel:multimedia
|-
|[http://build.meego.com/package/show?package=anerley&project=Trunk anerley]
|
|devel:ux:netbook
|-
|[http://build.meego.com/package/show?package=anjuta&project=Trunk anjuta]
|
|
|-
|[http://build.meego.com/package/show?package=anthy&project=Trunk anthy]
|
|
|-
|[http://build.meego.com/package/show?package=apr&project=Trunk apr]
|
|
|-
|[http://build.meego.com/package/show?package=apr-util&project=Trunk apr-util]
|
|
|-
|[http://build.meego.com/package/show?package=aria2&project=Trunk aria2]
|xiaoqiang
|devel:packagemanagement
|-
|[http://build.meego.com/package/show?package=asciidoc&project=Trunk asciidoc]
|
|
|-
|[http://build.meego.com/package/show?package=asio&project=Trunk asio]
|
|
|-
|[http://build.meego.com/package/show?package=aspell&project=Trunk aspell]
|
|
|-
|[http://build.meego.com/package/show?package=aspell-en&project=Trunk aspell-en]
|
|
|-
|[http://build.meego.com/package/show?package=at&project=Trunk at]
|
|
|-
|[http://build.meego.com/package/show?package=at-spi&project=Trunk at-spi]
|
|
|-
|[http://build.meego.com/package/show?package=atk&project=Trunk atk]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=atproxy&project=Trunk atproxy]
|jpfreyen,ulf
|
|-
|[http://build.meego.com/package/show?package=attica&project=Trunk attica]
|boudra
|
|-
|[http://build.meego.com/package/show?package=attr&project=Trunk attr]
|
|
|-
|[http://build.meego.com/package/show?package=audio_management&project=Trunk audio_management]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=audiofile&project=Trunk audiofile]
|
|
|-
|[http://build.meego.com/package/show?package=augeas&project=Trunk augeas]
|
|
|-
|[http://build.meego.com/package/show?package=autoconf&project=Trunk autoconf]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=autoconf213&project=Trunk autoconf213]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=autogen&project=Trunk autogen]
|
|
|-
|[http://build.meego.com/package/show?package=automake&project=Trunk automake]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=automake14&project=Trunk automake14]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=automake17&project=Trunk automake17]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=automoc4&project=Trunk automoc4]
|boudra
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=autotrace&project=Trunk autotrace]
|
|
|-
|[http://build.meego.com/package/show?package=avahi&project=Trunk avahi]
|
|
|-
|[http://build.meego.com/package/show?package=babl&project=Trunk babl]
|
|
|-
|[http://build.meego.com/package/show?package=baekmuk-ttf-fonts&project=Trunk baekmuk-ttf-fonts]
|
|
|-
|[http://build.meego.com/package/show?package=banshee-1&project=Trunk banshee-1]
|abock
|
|-
|[http://build.meego.com/package/show?package=banshee-1-branding-meego&project=Trunk banshee-1-branding-meego]
|
|
|-
|[http://build.meego.com/package/show?package=basesystem&project=Trunk basesystem]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=bash&project=Trunk bash]
|yanli
|devel:base
|-
|[http://build.meego.com/package/show?package=bash-x86&project=Trunk bash-x86]
|jsmoeller
|devel:base
|-
|[http://build.meego.com/package/show?package=bc&project=Trunk bc]
|
|
|-
|[http://build.meego.com/package/show?package=bickley&project=Trunk bickley]
|
|
|-
|[http://build.meego.com/package/show?package=bind&project=Trunk bind]
|jfding
|
|-
|[http://build.meego.com/package/show?package=binutils&project=Trunk binutils]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=bisho&project=Trunk bisho]
|ross
|devel:ux:netbook
|-
|[http://build.meego.com/package/show?package=bison&project=Trunk bison]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=bitmap&project=Trunk bitmap]
|
|
|-
|[http://build.meego.com/package/show?package=bitstream-vera-fonts&project=Trunk bitstream-vera-fonts]
|
|
|-
|[http://build.meego.com/package/show?package=bluetooth-ivi&project=Trunk bluetooth-ivi]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=bluez&project=Trunk bluez]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=bognor-regis&project=Trunk bognor-regis]
|
|
|-
|[http://build.meego.com/package/show?package=boost&project=Trunk boost]
|
|devel:base
|-
|[http://build.meego.com/package/show?package=bootchart&project=Trunk bootchart]
|auke
|
|-
|[http://build.meego.com/package/show?package=bootstub&project=Trunk bootstub]
|praj
|
|-
|[http://build.meego.com/package/show?package=booty&project=Trunk booty]
|
|
|-
|[http://build.meego.com/package/show?package=brasero&project=Trunk brasero]
|
|
|-
|[http://build.meego.com/package/show?package=btrfs-progs&project=Trunk btrfs-progs]
|zhongxin
|
|-
|[http://build.meego.com/package/show?package=bugle&project=Trunk bugle]
|
|
|-
|[http://build.meego.com/package/show?package=build&project=Trunk build]
|nashif
|devel:tools:building
|-
|[http://build.meego.com/package/show?package=build-compare&project=Trunk build-compare]
|nashif
|
|-
|[http://build.meego.com/package/show?package=busybox&project=Trunk busybox]
|
|
|-
|[http://build.meego.com/package/show?package=buteo-mtp&project=Trunk buteo-mtp]
|bwachter
|
|-
|[http://build.meego.com/package/show?package=buteo-sync-plugins&project=Trunk buteo-sync-plugins]
|bwachter
|
|-
|[http://build.meego.com/package/show?package=buteo-syncfw&project=Trunk buteo-syncfw]
|bwachter
|
|-
|[http://build.meego.com/package/show?package=buteo-syncml&project=Trunk buteo-syncml]
|bwachter
|
|-
|[http://build.meego.com/package/show?package=byacc&project=Trunk byacc]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=bzip2&project=Trunk bzip2]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=bzip2-libs-x86&project=Trunk bzip2-libs-x86]
|austin
|
|-
|[http://build.meego.com/package/show?package=bzip2-x86&project=Trunk bzip2-x86]
|austin
|
|-
|[http://build.meego.com/package/show?package=c-ares&project=Trunk c-ares]
|
|
|-
|[http://build.meego.com/package/show?package=ca-certificates&project=Trunk ca-certificates]
|qzhao9
|
|-
|[http://build.meego.com/package/show?package=cabextract&project=Trunk cabextract]
|
|
|-
|[http://build.meego.com/package/show?package=cairo&project=Trunk cairo]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=cairomm&project=Trunk cairomm]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=calligra&project=Trunk calligra]
|bwachter
|
|-
|[http://build.meego.com/package/show?package=camera-adaption-layer&project=Trunk camera-adaption-layer]
|ulf
|
|-
|[http://build.meego.com/package/show?package=catdoc&project=Trunk catdoc]
|
|
|-
|[http://build.meego.com/package/show?package=ccache&project=Trunk ccache]
|nashif
|
|-
|[http://build.meego.com/package/show?package=cdrdao&project=Trunk cdrdao]
|
|
|-
|[http://build.meego.com/package/show?package=cdrkit&project=Trunk cdrkit]
|
|
|-
|[http://build.meego.com/package/show?package=cedevicemanager&project=Trunk cedevicemanager]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=cglaunch&project=Trunk cglaunch]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=check&project=Trunk check]
|
|
|-
|[http://build.meego.com/package/show?package=cheese&project=Trunk cheese]
|
|
|-
|[http://build.meego.com/package/show?package=chkconfig&project=Trunk chkconfig]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=chrome-meego-extension&project=Trunk chrome-meego-extension]
|nhu
|
|-
|[http://build.meego.com/package/show?package=chromium&project=Trunk chromium]
|
|devel:browser
|-
|[http://build.meego.com/package/show?package=chrpath&project=Trunk chrpath]
|
|devel:base
|-
|[http://build.meego.com/package/show?package=cjkuni-fonts&project=Trunk cjkuni-fonts]
|
|
|-
|[http://build.meego.com/package/show?package=clean-device&project=Trunk clean-device]
|kedz
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=cloog&project=Trunk cloog]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=clucene&project=Trunk clucene]
|
|
|-
|[http://build.meego.com/package/show?package=clutter&project=Trunk clutter]
|rbradford
|devel:tv
|-
|[http://build.meego.com/package/show?package=clutter-box2d&project=Trunk clutter-box2d]
|rbradford
|
|-
|[http://build.meego.com/package/show?package=clutter-gesture&project=Trunk clutter-gesture]
|rbradford
|
|-
|[http://build.meego.com/package/show?package=clutter-gst&project=Trunk clutter-gst]
|rbradford
|devel:ux:netbook
|-
|[http://build.meego.com/package/show?package=clutter-gtk&project=Trunk clutter-gtk]
|rbradford
|
|-
|[http://build.meego.com/package/show?package=clutter-imcontext&project=Trunk clutter-imcontext]
|rbradford
|
|-
|[http://build.meego.com/package/show?package=cmake&project=Trunk cmake]
|austin
|
|-
|[http://build.meego.com/package/show?package=cmake-gui&project=Trunk cmake-gui]
|boudra
|
|-
|[http://build.meego.com/package/show?package=commhistory-daemon&project=Trunk commhistory-daemon]
|pcapriotti
|
|-
|[http://build.meego.com/package/show?package=compat-libstdc++-33&project=Trunk compat-libstdc++-33]
|austin
|
|-
|[http://build.meego.com/package/show?package=compat-telepathy-qt4&project=Trunk compat-telepathy-qt4]
|pcapriotti
|
|-
|[http://build.meego.com/package/show?package=compface&project=Trunk compface]
|
|
|-
|[http://build.meego.com/package/show?package=comps-extras&project=Trunk comps-extras]
|xiaoqiang
|devel:packagemanagement
|-
|[http://build.meego.com/package/show?package=connman&project=Trunk connman]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=contacts&project=Trunk contacts]
|
|
|-
|[http://build.meego.com/package/show?package=contactsd&project=Trunk contactsd]
|
|devel:people
|-
|[http://build.meego.com/package/show?package=contextkit&project=Trunk contextkit]
|rusty
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=contextkit-maemo&project=Trunk contextkit-maemo]
|rusty
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=contextkit-meego&project=Trunk contextkit-meego]
|ceferron,ulf
|
|-
|[http://build.meego.com/package/show?package=coreutils&project=Trunk coreutils]
|yanli
|devel:base
|-
|[http://build.meego.com/package/show?package=coreutils-x86&project=Trunk coreutils-x86]
|austin
|
|-
|[http://build.meego.com/package/show?package=corewatcher&project=Trunk corewatcher]
|wdouglas
|
|-
|[http://build.meego.com/package/show?package=corkscrew&project=Trunk corkscrew]
|boudra
|
|-
|[http://build.meego.com/package/show?package=cpio&project=Trunk cpio]
|yanli
|
|-
|[http://build.meego.com/package/show?package=cppcheck&project=Trunk cppcheck]
|arjan
|
|-
|[http://build.meego.com/package/show?package=cppunit&project=Trunk cppunit]
|
|
|-
|[http://build.meego.com/package/show?package=crda&project=Trunk crda]
|
|
|-
|[http://build.meego.com/package/show?package=createrepo&project=Trunk createrepo]
|xiaoqiang
|
|-
|[http://build.meego.com/package/show?package=cronie&project=Trunk cronie]
|yyang
|
|-
|[http://build.meego.com/package/show?package=crontabs&project=Trunk crontabs]
|
|
|-
|[http://build.meego.com/package/show?package=cross-armv5tel-binutils&project=Trunk cross-armv5tel-binutils]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=cross-armv5tel-binutils-accel&project=Trunk cross-armv5tel-binutils-accel]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=cross-armv5tel-gcc&project=Trunk cross-armv5tel-gcc]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=cross-armv5tel-gcc-accel&project=Trunk cross-armv5tel-gcc-accel]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=cross-armv7l-binutils&project=Trunk cross-armv7l-binutils]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=cross-armv7l-binutils-accel&project=Trunk cross-armv7l-binutils-accel]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=cross-armv7l-gcc&project=Trunk cross-armv7l-gcc]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=cross-armv7l-gcc-accel&project=Trunk cross-armv7l-gcc-accel]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=cross-armv7l-platformfile&project=Trunk cross-armv7l-platformfile]
|cvm
|
|-
|[http://build.meego.com/package/show?package=cross-armv7tnhl-platformfile&project=Trunk cross-armv7tnhl-platformfile]
|cvm
|
|-
|[http://build.meego.com/package/show?package=cryptsetup-luks&project=Trunk cryptsetup-luks]
|qzhao9
|
|-
|[http://build.meego.com/package/show?package=cscope&project=Trunk cscope]
|
|
|-
|[http://build.meego.com/package/show?package=ctags&project=Trunk ctags]
|
|
|-
|[http://build.meego.com/package/show?package=ctdb&project=Trunk ctdb]
|
|
|-
|[http://build.meego.com/package/show?package=cups&project=Trunk cups]
|
|
|-
|[http://build.meego.com/package/show?package=curl&project=Trunk curl]
|
|
|-
|[http://build.meego.com/package/show?package=cvs&project=Trunk cvs]
|
|
|-
|[http://build.meego.com/package/show?package=cyrus-sasl&project=Trunk cyrus-sasl]
|
|
|-
|[http://build.meego.com/package/show?package=d-feet&project=Trunk d-feet]
|
|
|-
|[http://build.meego.com/package/show?package=dates&project=Trunk dates]
|
|
|-
|[http://build.meego.com/package/show?package=db4&project=Trunk db4]
|yyin2
|devel:base
|-
|[http://build.meego.com/package/show?package=db4-x86&project=Trunk db4-x86]
|austin
|
|-
|[http://build.meego.com/package/show?package=dblatex&project=Trunk dblatex]
|bwachter
|
|-
|[http://build.meego.com/package/show?package=dbus&project=Trunk dbus]
|huaxu
|devel:base
|-
|[http://build.meego.com/package/show?package=dbus-glib&project=Trunk dbus-glib]
|huaxu
|
|-
|[http://build.meego.com/package/show?package=dbus-python&project=Trunk dbus-python]
|quanxianwang
|
|-
|[http://build.meego.com/package/show?package=dejagnu&project=Trunk dejagnu]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=dejavu-fonts&project=Trunk dejavu-fonts]
|
|
|-
|[http://build.meego.com/package/show?package=deltarpm&project=Trunk deltarpm]
|xiaoqiang
|
|-
|[http://build.meego.com/package/show?package=deluge&project=Trunk deluge]
|
|
|-
|[http://build.meego.com/package/show?package=desktop-backgrounds&project=Trunk desktop-backgrounds]
|
|
|-
|[http://build.meego.com/package/show?package=desktop-file-utils&project=Trunk desktop-file-utils]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=dev86&project=Trunk dev86]
|
|
|-
|[http://build.meego.com/package/show?package=devhelp&project=Trunk devhelp]
|jfding
|
|-
|[http://build.meego.com/package/show?package=device-mapper&project=Trunk device-mapper]
|yyang
|
|-
|[http://build.meego.com/package/show?package=device-mapper-multipath&project=Trunk device-mapper-multipath]
|yyang
|
|-
|[http://build.meego.com/package/show?package=dia&project=Trunk dia]
|
|
|-
|[http://build.meego.com/package/show?package=dialog&project=Trunk dialog]
|
|
|-
|[http://build.meego.com/package/show?package=diffstat&project=Trunk diffstat]
|yyang
|
|-
|[http://build.meego.com/package/show?package=diffutils&project=Trunk diffutils]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=diffutils-x86&project=Trunk diffutils-x86]
|austin
|
|-
|[http://build.meego.com/package/show?package=distcc&project=Trunk distcc]
|
|
|-
|[http://build.meego.com/package/show?package=djvulibre&project=Trunk djvulibre]
|
|
|-
|[http://build.meego.com/package/show?package=dmidecode&project=Trunk dmidecode]
|
|
|-
|[http://build.meego.com/package/show?package=dnsmasq&project=Trunk dnsmasq]
|martin
|
|-
|[http://build.meego.com/package/show?package=docbook-dtds&project=Trunk docbook-dtds]
|
|
|-
|[http://build.meego.com/package/show?package=docbook-style-dsssl&project=Trunk docbook-style-dsssl]
|
|
|-
|[http://build.meego.com/package/show?package=docbook-style-xsl&project=Trunk docbook-style-xsl]
|
|
|-
|[http://build.meego.com/package/show?package=docbook-utils&project=Trunk docbook-utils]
|
|
|-
|[http://build.meego.com/package/show?package=dos2unix&project=Trunk dos2unix]
|
|
|-
|[http://build.meego.com/package/show?package=dosfstools&project=Trunk dosfstools]
|
|
|-
|[http://build.meego.com/package/show?package=dotconf&project=Trunk dotconf]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=doxygen&project=Trunk doxygen]
|
|
|-
|[http://build.meego.com/package/show?package=doxygen-x86&project=Trunk doxygen-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=doxymacs&project=Trunk doxymacs]
|
|
|-
|[http://build.meego.com/package/show?package=driconf&project=Trunk driconf]
|xyl
|
|-
|[http://build.meego.com/package/show?package=droid-fonts&project=Trunk droid-fonts]
|
|
|-
|[http://build.meego.com/package/show?package=dropbear&project=Trunk dropbear]
|austin
|
|-
|[http://build.meego.com/package/show?package=dsme&project=Trunk dsme]
|mlehtonen
|devel:systemsw
|-
|[http://build.meego.com/package/show?package=dsp-tools&project=Trunk dsp-tools]
|tosantak
|
|-
|[http://build.meego.com/package/show?package=dvd+rw-tools&project=Trunk dvd+rw-tools]
|
|
|-
|[http://build.meego.com/package/show?package=dvipdfm&project=Trunk dvipdfm]
|
|
|-
|[http://build.meego.com/package/show?package=dvipdfmx&project=Trunk dvipdfmx]
|yanli
|
|-
|[http://build.meego.com/package/show?package=dvipng&project=Trunk dvipng]
|
|
|-
|[http://build.meego.com/package/show?package=e2fsprogs&project=Trunk e2fsprogs]
|qzhao9
|
|-
|[http://build.meego.com/package/show?package=eat&project=Trunk eat]
|timoph,jokylanp
|
|-
|[http://build.meego.com/package/show?package=ecryptfs-utils&project=Trunk ecryptfs-utils]
|yanli
|
|-
|[http://build.meego.com/package/show?package=ed&project=Trunk ed]
|yyang
|
|-
|[http://build.meego.com/package/show?package=eggdbus&project=Trunk eggdbus]
|
|
|-
|[http://build.meego.com/package/show?package=eject&project=Trunk eject]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=elfutils&project=Trunk elfutils]
|qzhao9
|
|-
|[http://build.meego.com/package/show?package=elfutils-libelf-x86&project=Trunk elfutils-libelf-x86]
|austin
|
|-
|[http://build.meego.com/package/show?package=elfutils-libs-x86&project=Trunk elfutils-libs-x86]
|austin
|
|-
|[http://build.meego.com/package/show?package=elfutils-x86&project=Trunk elfutils-x86]
|austin
|
|-
|[http://build.meego.com/package/show?package=emacs&project=Trunk emacs]
|
|
|-
|[http://build.meego.com/package/show?package=empathy&project=Trunk empathy]
|
|
|-
|[http://build.meego.com/package/show?package=enchant&project=Trunk enchant]
|
|
|-
|[http://build.meego.com/package/show?package=enscript&project=Trunk enscript]
|
|
|-
|[http://build.meego.com/package/show?package=eog&project=Trunk eog]
|
|
|-
|[http://build.meego.com/package/show?package=eog-plugins&project=Trunk eog-plugins]
|
|
|-
|[http://build.meego.com/package/show?package=eom&project=Trunk eom]
|
|
|-
|[http://build.meego.com/package/show?package=epydoc&project=Trunk epydoc]
|
|
|-
|[http://build.meego.com/package/show?package=esound&project=Trunk esound]
|
|
|-
|[http://build.meego.com/package/show?package=etherboot&project=Trunk etherboot]
|
|
|-
|[http://build.meego.com/package/show?package=ethtool&project=Trunk ethtool]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=evince&project=Trunk evince]
|
|
|-
|[http://build.meego.com/package/show?package=evolution&project=Trunk evolution]
|ross
|
|-
|[http://build.meego.com/package/show?package=evolution-data-server&project=Trunk evolution-data-server]
|
|
|-
|[http://build.meego.com/package/show?package=exempi&project=Trunk exempi]
|
|
|-
|[http://build.meego.com/package/show?package=exiv2&project=Trunk exiv2]
|
|
|-
|[http://build.meego.com/package/show?package=expat&project=Trunk expat]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=expect&project=Trunk expect]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=fakechroot&project=Trunk fakechroot]
|yyang
|
|-
|[http://build.meego.com/package/show?package=fakeroot&project=Trunk fakeroot]
|
|
|-
|[http://build.meego.com/package/show?package=farsight2&project=Trunk farsight2]
|
|
|-
|[http://build.meego.com/package/show?package=fastinit&project=Trunk fastinit]
|
|
|-
|[http://build.meego.com/package/show?package=fastjar&project=Trunk fastjar]
|austin
|
|-
|[http://build.meego.com/package/show?package=fdupes&project=Trunk fdupes]
|nashif
|
|-
|[http://build.meego.com/package/show?package=fdupes-x86&project=Trunk fdupes-x86]
|zhongxin
|
|-
|[http://build.meego.com/package/show?package=fennec-qt&project=Trunk fennec-qt]
|
|
|-
|[http://build.meego.com/package/show?package=fennec-qt-branding-meego&project=Trunk fennec-qt-branding-meego]
|
|
|-
|[http://build.meego.com/package/show?package=fennec-taskswitcher-extension&project=Trunk fennec-taskswitcher-extension]
|logoel
|
|-
|[http://build.meego.com/package/show?package=festival&project=Trunk festival]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=festival-freebsoft-utils&project=Trunk festival-freebsoft-utils]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=file&project=Trunk file]
|
|
|-
|[http://build.meego.com/package/show?package=file-libs-x86&project=Trunk file-libs-x86]
|austin
|
|-
|[http://build.meego.com/package/show?package=file-roller&project=Trunk file-roller]
|
|
|-
|[http://build.meego.com/package/show?package=file-x86&project=Trunk file-x86]
|austin
|
|-
|[http://build.meego.com/package/show?package=filesystem&project=Trunk filesystem]
|
|
|-
|[http://build.meego.com/package/show?package=findutils&project=Trunk findutils]
|yanli
|
|-
|[http://build.meego.com/package/show?package=findutils-x86&project=Trunk findutils-x86]
|austin
|
|-
|[http://build.meego.com/package/show?package=firstboot&project=Trunk firstboot]
|vivian
|
|-
|[http://build.meego.com/package/show?package=flac&project=Trunk flac]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=flex&project=Trunk flex]
|
|devel:base
|-
|[http://build.meego.com/package/show?package=fontconfig&project=Trunk fontconfig]
|
|
|-
|[http://build.meego.com/package/show?package=fontforge&project=Trunk fontforge]
|
|
|-
|[http://build.meego.com/package/show?package=fontpackages&project=Trunk fontpackages]
|
|
|-
|[http://build.meego.com/package/show?package=foomatic&project=Trunk foomatic]
|
|
|-
|[http://build.meego.com/package/show?package=foomatic-db&project=Trunk foomatic-db]
|
|
|-
|[http://build.meego.com/package/show?package=fortune-mod&project=Trunk fortune-mod]
|ulf
|
|-
|[http://build.meego.com/package/show?package=fprintd&project=Trunk fprintd]
|
|
|-
|[http://build.meego.com/package/show?package=freeglut&project=Trunk freeglut]
|xyl
|
|-
|[http://build.meego.com/package/show?package=freepats&project=Trunk freepats]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=freetype&project=Trunk freetype]
|
|
|-
|[http://build.meego.com/package/show?package=fribidi&project=Trunk fribidi]
|
|
|-
|[http://build.meego.com/package/show?package=frozen-bubble&project=Trunk frozen-bubble]
|
|
|-
|[http://build.meego.com/package/show?package=fslint&project=Trunk fslint]
|jiachenghu
|
|-
|[http://build.meego.com/package/show?package=fuse&project=Trunk fuse]
|
|
|-
|[http://build.meego.com/package/show?package=fuse-sshfs&project=Trunk fuse-sshfs]
|
|
|-
|[http://build.meego.com/package/show?package=fvkbd&project=Trunk fvkbd]
|
|
|-
|[http://build.meego.com/package/show?package=fw-update&project=Trunk fw-update]
|praj
|
|-
|[http://build.meego.com/package/show?package=gamin&project=Trunk gamin]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=gammu&project=Trunk gammu]
|
|
|-
|[http://build.meego.com/package/show?package=garage-client-services&project=Trunk garage-client-services]
|jackiewu
|
|-
|[http://build.meego.com/package/show?package=garage-netbook-ui&project=Trunk garage-netbook-ui]
|jackiewu
|
|-
|[http://build.meego.com/package/show?package=gawk&project=Trunk gawk]
|yanli
|
|-
|[http://build.meego.com/package/show?package=gawk-x86&project=Trunk gawk-x86]
|austin
|
|-
|[http://build.meego.com/package/show?package=gc&project=Trunk gc]
|
|
|-
|[http://build.meego.com/package/show?package=gcalctool&project=Trunk gcalctool]
|
|
|-
|[http://build.meego.com/package/show?package=gcc&project=Trunk gcc]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=gcc-cross&project=Trunk gcc-cross]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=gconf-editor&project=Trunk gconf-editor]
|
|
|-
|[http://build.meego.com/package/show?package=gd&project=Trunk gd]
|
|
|-
|[http://build.meego.com/package/show?package=gdb&project=Trunk gdb]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=gdbm&project=Trunk gdbm]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=gdu-nautilus-extension&project=Trunk gdu-nautilus-extension]
|
|
|-
|[http://build.meego.com/package/show?package=gedit&project=Trunk gedit]
|
|
|-
|[http://build.meego.com/package/show?package=gegl&project=Trunk gegl]
|
|
|-
|[http://build.meego.com/package/show?package=generic-backgrounds&project=Trunk generic-backgrounds]
|
|
|-
|[http://build.meego.com/package/show?package=generic-logos&project=Trunk generic-logos]
|
|
|-
|[http://build.meego.com/package/show?package=geoclue&project=Trunk geoclue]
|
|
|-
|[http://build.meego.com/package/show?package=gettext&project=Trunk gettext]
|
|
|-
|[http://build.meego.com/package/show?package=ghostscript&project=Trunk ghostscript]
|
|
|-
|[http://build.meego.com/package/show?package=ghostscript-fonts&project=Trunk ghostscript-fonts]
|
|
|-
|[http://build.meego.com/package/show?package=giflib&project=Trunk giflib]
|
|
|-
|[http://build.meego.com/package/show?package=gimp&project=Trunk gimp]
|
|
|-
|[http://build.meego.com/package/show?package=git&project=Trunk git]
|
|
|-
|[http://build.meego.com/package/show?package=glade3&project=Trunk glade3]
|
|
|-
|[http://build.meego.com/package/show?package=gles-libs&project=Trunk gles-libs]
|boudra
|
|-
|[http://build.meego.com/package/show?package=glew&project=Trunk glew]
|
|
|-
|[http://build.meego.com/package/show?package=glib2&project=Trunk glib2]
|xiaoqiang,quanxianwang
|devel:base
|-
|[http://build.meego.com/package/show?package=glibc&project=Trunk glibc]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=glibc-arm&project=Trunk glibc-arm]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=glibc-devel-arm&project=Trunk glibc-devel-arm]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=glibc-headers-arm&project=Trunk glibc-headers-arm]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=glibc-x86&project=Trunk glibc-x86]
|jsmoeller
|devel:base
|-
|[http://build.meego.com/package/show?package=glibmm&project=Trunk glibmm]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=gmime&project=Trunk gmime]
|
|
|-
|[http://build.meego.com/package/show?package=gmp&project=Trunk gmp]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=gmp-x86&project=Trunk gmp-x86]
|jsmoeller
|devel:base
|-
|[http://build.meego.com/package/show?package=gnet2&project=Trunk gnet2]
|
|
|-
|[http://build.meego.com/package/show?package=gnome-bluetooth&project=Trunk gnome-bluetooth]
|
|
|-
|[http://build.meego.com/package/show?package=gnome-common&project=Trunk gnome-common]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=gnome-control-center-netbook&project=Trunk gnome-control-center-netbook]
|
|
|-
|[http://build.meego.com/package/show?package=gnome-desktop&project=Trunk gnome-desktop]
|
|
|-
|[http://build.meego.com/package/show?package=gnome-disk-utility&project=Trunk gnome-disk-utility]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=gnome-doc-utils&project=Trunk gnome-doc-utils]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=gnome-games&project=Trunk gnome-games]
|
|
|-
|[http://build.meego.com/package/show?package=gnome-icon-theme&project=Trunk gnome-icon-theme]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=gnome-keyring&project=Trunk gnome-keyring]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=gnome-media&project=Trunk gnome-media]
|
|
|-
|[http://build.meego.com/package/show?package=gnome-menus&project=Trunk gnome-menus]
|
|
|-
|[http://build.meego.com/package/show?package=gnome-mime-data&project=Trunk gnome-mime-data]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=gnome-packagekit&project=Trunk gnome-packagekit]
|
|devel:packagemanagement
|-
|[http://build.meego.com/package/show?package=gnome-panel&project=Trunk gnome-panel]
|
|
|-
|[http://build.meego.com/package/show?package=gnome-python2&project=Trunk gnome-python2]
|
|
|-
|[http://build.meego.com/package/show?package=gnome-python2-desktop&project=Trunk gnome-python2-desktop]
|
|
|-
|[http://build.meego.com/package/show?package=gnome-screensaver&project=Trunk gnome-screensaver]
|
|
|-
|[http://build.meego.com/package/show?package=gnome-session&project=Trunk gnome-session]
|
|
|-
|[http://build.meego.com/package/show?package=gnome-settings-daemon&project=Trunk gnome-settings-daemon]
|
|
|-
|[http://build.meego.com/package/show?package=gnome-sharp2&project=Trunk gnome-sharp2]
|mmeeks
|
|-
|[http://build.meego.com/package/show?package=gnome-terminal&project=Trunk gnome-terminal]
|
|
|-
|[http://build.meego.com/package/show?package=gnome-themes&project=Trunk gnome-themes]
|
|
|-
|[http://build.meego.com/package/show?package=gnome-user-docs&project=Trunk gnome-user-docs]
|
|
|-
|[http://build.meego.com/package/show?package=gnome-user-share&project=Trunk gnome-user-share]
|ross
|
|-
|[http://build.meego.com/package/show?package=gnome-utils&project=Trunk gnome-utils]
|
|
|-
|[http://build.meego.com/package/show?package=gnome-vfs2&project=Trunk gnome-vfs2]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=gnonlin&project=Trunk gnonlin]
|tosantak
|
|-
|[http://build.meego.com/package/show?package=gnu-efi&project=Trunk gnu-efi]
|
|
|-
|[http://build.meego.com/package/show?package=gnuchess&project=Trunk gnuchess]
|
|
|-
|[http://build.meego.com/package/show?package=gnumeric&project=Trunk gnumeric]
|
|
|-
|[http://build.meego.com/package/show?package=gnupg&project=Trunk gnupg]
|
|
|-
|[http://build.meego.com/package/show?package=gnupg2&project=Trunk gnupg2]
|yanli
|
|-
|[http://build.meego.com/package/show?package=gnutls&project=Trunk gnutls]
|qzhao9,yanli
|devel:security
|-
|[http://build.meego.com/package/show?package=goffice&project=Trunk goffice]
|
|
|-
|[http://build.meego.com/package/show?package=google-gadgets&project=Trunk google-gadgets]
|wwang29
|
|-
|[http://build.meego.com/package/show?package=gperf&project=Trunk gperf]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=gpgme&project=Trunk gpgme]
|
|
|-
|[http://build.meego.com/package/show?package=gphotofs&project=Trunk gphotofs]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=gpsbabel&project=Trunk gpsbabel]
|yanli
|
|-
|[http://build.meego.com/package/show?package=gpsd&project=Trunk gpsd]
|
|
|-
|[http://build.meego.com/package/show?package=gpsdrive&project=Trunk gpsdrive]
|
|
|-
|[http://build.meego.com/package/show?package=graphviz&project=Trunk graphviz]
|
|
|-
|[http://build.meego.com/package/show?package=grep&project=Trunk grep]
|yanli
|
|-
|[http://build.meego.com/package/show?package=grisbi&project=Trunk grisbi]
|
|
|-
|[http://build.meego.com/package/show?package=groff&project=Trunk groff]
|
|
|-
|[http://build.meego.com/package/show?package=grub&project=Trunk grub]
|
|
|-
|[http://build.meego.com/package/show?package=grubby&project=Trunk grubby]
|yyang
|
|-
|[http://build.meego.com/package/show?package=gsl&project=Trunk gsl]
|rolla
|
|-
|[http://build.meego.com/package/show?package=gsm&project=Trunk gsm]
|
|
|-
|[http://build.meego.com/package/show?package=gssdp&project=Trunk gssdp]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=gst-dsp&project=Trunk gst-dsp]
|
|
|-
|[http://build.meego.com/package/show?package=gst-plugins-bad-free&project=Trunk gst-plugins-bad-free]
|bgao1,lisayue
|devel:multimedia
|-
|[http://build.meego.com/package/show?package=gst-plugins-base&project=Trunk gst-plugins-base]
|lisayue
|devel:multimedia
|-
|[http://build.meego.com/package/show?package=gst-plugins-camera&project=Trunk gst-plugins-camera]
|vivian
|
|-
|[http://build.meego.com/package/show?package=gst-plugins-farsight&project=Trunk gst-plugins-farsight]
|
|
|-
|[http://build.meego.com/package/show?package=gst-plugins-good&project=Trunk gst-plugins-good]
|lisayue
|devel:multimedia
|-
|[http://build.meego.com/package/show?package=gst-plugins-va&project=Trunk gst-plugins-va]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=gst-v4l2-camsrc&project=Trunk gst-v4l2-camsrc]
|lisayue
|devel:multimedia
|-
|[http://build.meego.com/package/show?package=gst-vabuffer&project=Trunk gst-vabuffer]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=gstreamer&project=Trunk gstreamer]
|lisayue
|devel:multimedia
|-
|[http://build.meego.com/package/show?package=gstreamer-editing-services&project=Trunk gstreamer-editing-services]
|tosantak
|
|-
|[http://build.meego.com/package/show?package=gstreamer-python&project=Trunk gstreamer-python]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=gthumb&project=Trunk gthumb]
|
|
|-
|[http://build.meego.com/package/show?package=gtk-doc&project=Trunk gtk-doc]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=gtk-nodoka-engine&project=Trunk gtk-nodoka-engine]
|
|
|-
|[http://build.meego.com/package/show?package=gtk-sharp2&project=Trunk gtk-sharp2]
|mmeeks
|
|-
|[http://build.meego.com/package/show?package=gtk2&project=Trunk gtk2]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=gtk2-engines&project=Trunk gtk2-engines]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=gtkglext&project=Trunk gtkglext]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=gtkhtml3&project=Trunk gtkhtml3]
|
|
|-
|[http://build.meego.com/package/show?package=gtkmathview&project=Trunk gtkmathview]
|
|
|-
|[http://build.meego.com/package/show?package=gtkmm&project=Trunk gtkmm]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=gtksourceview2&project=Trunk gtksourceview2]
|
|
|-
|[http://build.meego.com/package/show?package=gtkspell&project=Trunk gtkspell]
|
|
|-
|[http://build.meego.com/package/show?package=guile&project=Trunk guile]
|
|
|-
|[http://build.meego.com/package/show?package=gupnp&project=Trunk gupnp]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=gupnp-av&project=Trunk gupnp-av]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=gupnp-dlna&project=Trunk gupnp-dlna]
|tosantak
|
|-
|[http://build.meego.com/package/show?package=gupnp-igd&project=Trunk gupnp-igd]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=gupnp-tools&project=Trunk gupnp-tools]
|
|
|-
|[http://build.meego.com/package/show?package=gupnp-ui&project=Trunk gupnp-ui]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=gupnp-vala&project=Trunk gupnp-vala]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=gvfs&project=Trunk gvfs]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=gwenhywfar&project=Trunk gwenhywfar]
|
|
|-
|[http://build.meego.com/package/show?package=gypsy&project=Trunk gypsy]
|
|
|-
|[http://build.meego.com/package/show?package=gzip&project=Trunk gzip]
|yanli
|
|-
|[http://build.meego.com/package/show?package=gzip-x86&project=Trunk gzip-x86]
|austin
|
|-
|[http://build.meego.com/package/show?package=hardlink&project=Trunk hardlink]
|yyang
|
|-
|[http://build.meego.com/package/show?package=help2man&project=Trunk help2man]
|
|
|-
|[http://build.meego.com/package/show?package=hfdialer&project=Trunk hfdialer]
|jimmyhuang,tracyg
|
|-
|[http://build.meego.com/package/show?package=hfdialer-branding-meego&project=Trunk hfdialer-branding-meego]
|jimmyhuang,tracyg
|
|-
|[http://build.meego.com/package/show?package=hfp&project=Trunk hfp]
|jimmyhuang,tracyg
|
|-
|[http://build.meego.com/package/show?package=hicolor-icon-theme&project=Trunk hicolor-icon-theme]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=html2ps&project=Trunk html2ps]
|
|
|-
|[http://build.meego.com/package/show?package=hunspell&project=Trunk hunspell]
|
|
|-
|[http://build.meego.com/package/show?package=hunspell-en&project=Trunk hunspell-en]
|
|
|-
|[http://build.meego.com/package/show?package=hwdata&project=Trunk hwdata]
|
|
|-
|[http://build.meego.com/package/show?package=i2c-tools&project=Trunk i2c-tools]
|cvm
|devel:devices:n900
|-
|[http://build.meego.com/package/show?package=icon-naming-utils&project=Trunk icon-naming-utils]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=icu&project=Trunk icu]
|quanxianwang
|
|-
|[http://build.meego.com/package/show?package=ilmbase&project=Trunk ilmbase]
|
|
|-
|[http://build.meego.com/package/show?package=image-configurations&project=Trunk image-configurations]
|nashif
|
|-
|[http://build.meego.com/package/show?package=image-manager&project=Trunk image-manager]
|yyang
|
|-
|[http://build.meego.com/package/show?package=imake&project=Trunk imake]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=indent&project=Trunk indent]
|
|devel:base
|-
|[http://build.meego.com/package/show?package=inkscape&project=Trunk inkscape]
|
|
|-
|[http://build.meego.com/package/show?package=inotify-tools&project=Trunk inotify-tools]
|
|
|-
|[http://build.meego.com/package/show?package=installer&project=Trunk installer]
|vivian
|
|-
|[http://build.meego.com/package/show?package=installer-shell&project=Trunk installer-shell]
|vivian
|
|-
|[http://build.meego.com/package/show?package=intel-gpu-tools&project=Trunk intel-gpu-tools]
|pli1,xyl
|devel:x11:Trunk
|-
|[http://build.meego.com/package/show?package=intltool&project=Trunk intltool]
|
|
|-
|[http://build.meego.com/package/show?package=iproute&project=Trunk iproute]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=iptables&project=Trunk iptables]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=iputils&project=Trunk iputils]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=iso-codes&project=Trunk iso-codes]
|
|
|-
|[http://build.meego.com/package/show?package=isomd5sum&project=Trunk isomd5sum]
|yyang
|
|-
|[http://build.meego.com/package/show?package=ividesktop&project=Trunk ividesktop]
|jimmyhuang,tracyg
|
|-
|[http://build.meego.com/package/show?package=ivihome&project=Trunk ivihome]
|jimmyhuang,tracyg
|
|-
|[http://build.meego.com/package/show?package=iw&project=Trunk iw]
|
|
|-
|[http://build.meego.com/package/show?package=jadetex&project=Trunk jadetex]
|
|
|-
|[http://build.meego.com/package/show?package=jana&project=Trunk jana]
|
|
|-
|[http://build.meego.com/package/show?package=jasper&project=Trunk jasper]
|
|
|-
|[http://build.meego.com/package/show?package=joe&project=Trunk joe]
|
|
|-
|[http://build.meego.com/package/show?package=joystick&project=Trunk joystick]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=json-c&project=Trunk json-c]
|jokylanp
|
|-
|[http://build.meego.com/package/show?package=json-glib&project=Trunk json-glib]
|
|
|-
|[http://build.meego.com/package/show?package=kasumi&project=Trunk kasumi]
|
|
|-
|[http://build.meego.com/package/show?package=kbd&project=Trunk kbd]
|
|
|-
|[http://build.meego.com/package/show?package=kcalcore&project=Trunk kcalcore]
|
|
|-
|[http://build.meego.com/package/show?package=kde-mobile&project=Trunk kde-mobile]
|bwachter
|
|-
|[http://build.meego.com/package/show?package=kernel&project=Trunk kernel]
|
|devel:kernel
|-
|[http://build.meego.com/package/show?package=kernel-adaptation-connext&project=Trunk kernel-adaptation-connext]
|qi
|devel:kernel
|-
|[http://build.meego.com/package/show?package=kernel-adaptation-intel-automotive&project=Trunk kernel-adaptation-intel-automotive]
|qi
|devel:kernel
|-
|[http://build.meego.com/package/show?package=kernel-adaptation-medfield&project=Trunk kernel-adaptation-medfield]
|ldmai
|
|-
|[http://build.meego.com/package/show?package=kernel-adaptation-mrst&project=Trunk kernel-adaptation-mrst]
|arjan
|devel:kernel
|-
|[http://build.meego.com/package/show?package=kernel-adaptation-n900&project=Trunk kernel-adaptation-n900]
|ikoskine
|devel:devices:n900
|-
|[http://build.meego.com/package/show?package=kernel-adaptation-oaktrail&project=Trunk kernel-adaptation-oaktrail]
|kai
|devel:kernel
|-
|[http://build.meego.com/package/show?package=kernel-headers&project=Trunk kernel-headers]
|arjan
|
|-
|[http://build.meego.com/package/show?package=kernel-headers-arm&project=Trunk kernel-headers-arm]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=kexec-tools&project=Trunk kexec-tools]
|apalande
|
|-
|[http://build.meego.com/package/show?package=keycodes-setup&project=Trunk keycodes-setup]
|ulf
|
|-
|[http://build.meego.com/package/show?package=keyutils&project=Trunk keyutils]
|
|
|-
|[http://build.meego.com/package/show?package=kickstarter&project=Trunk kickstarter]
|nashif
|devel:tools:building
|-
|[http://build.meego.com/package/show?package=kmod-virtiogl&project=Trunk kmod-virtiogl]
|boudra
|devel:tools:sdk:target
|-
|[http://build.meego.com/package/show?package=krb5&project=Trunk krb5]
|qzhao9
|
|-
|[http://build.meego.com/package/show?package=ladspa&project=Trunk ladspa]
|
|
|-
|[http://build.meego.com/package/show?package=lapack&project=Trunk lapack]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=latencytop&project=Trunk latencytop]
|arjan
|
|-
|[http://build.meego.com/package/show?package=latex2html&project=Trunk latex2html]
|
|
|-
|[http://build.meego.com/package/show?package=lcms&project=Trunk lcms]
|
|
|-
|[http://build.meego.com/package/show?package=less&project=Trunk less]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=lftp&project=Trunk lftp]
|boudra
|devel:tools:sdk:target
|-
|[http://build.meego.com/package/show?package=libCI&project=Trunk libCI]
|ulf
|
|-
|[http://build.meego.com/package/show?package=libICE&project=Trunk libICE]
|
|
|-
|[http://build.meego.com/package/show?package=libIDL&project=Trunk libIDL]
|
|
|-
|[http://build.meego.com/package/show?package=libSM&project=Trunk libSM]
|
|
|-
|[http://build.meego.com/package/show?package=libX11&project=Trunk libX11]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXScrnSaver&project=Trunk libXScrnSaver]
|
|
|-
|[http://build.meego.com/package/show?package=libXTrap&project=Trunk libXTrap]
|
|
|-
|[http://build.meego.com/package/show?package=libXau&project=Trunk libXau]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXaw&project=Trunk libXaw]
|
|
|-
|[http://build.meego.com/package/show?package=libXcomposite&project=Trunk libXcomposite]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXcursor&project=Trunk libXcursor]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXdamage&project=Trunk libXdamage]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXdmcp&project=Trunk libXdmcp]
|
|
|-
|[http://build.meego.com/package/show?package=libXevie&project=Trunk libXevie]
|
|
|-
|[http://build.meego.com/package/show?package=libXext&project=Trunk libXext]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXfixes&project=Trunk libXfixes]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXfont&project=Trunk libXfont]
|
|
|-
|[http://build.meego.com/package/show?package=libXfontcache&project=Trunk libXfontcache]
|
|
|-
|[http://build.meego.com/package/show?package=libXft&project=Trunk libXft]
|
|
|-
|[http://build.meego.com/package/show?package=libXi&project=Trunk libXi]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXinerama&project=Trunk libXinerama]
|
|
|-
|[http://build.meego.com/package/show?package=libXmu&project=Trunk libXmu]
|
|
|-
|[http://build.meego.com/package/show?package=libXpm&project=Trunk libXpm]
|
|
|-
|[http://build.meego.com/package/show?package=libXrandr&project=Trunk libXrandr]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXrender&project=Trunk libXrender]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXres&project=Trunk libXres]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXt&project=Trunk libXt]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXtst&project=Trunk libXtst]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXv&project=Trunk libXv]
|
|
|-
|[http://build.meego.com/package/show?package=libXvMC&project=Trunk libXvMC]
|
|
|-
|[http://build.meego.com/package/show?package=libXxf86dga&project=Trunk libXxf86dga]
|
|
|-
|[http://build.meego.com/package/show?package=libXxf86misc&project=Trunk libXxf86misc]
|
|
|-
|[http://build.meego.com/package/show?package=libXxf86vm&project=Trunk libXxf86vm]
|
|
|-
|[http://build.meego.com/package/show?package=libaccounts-glib&project=Trunk libaccounts-glib]
|bwachter
|devel:AccountsSSO
|-
|[http://build.meego.com/package/show?package=libaccounts-qt&project=Trunk libaccounts-qt]
|bwachter
|devel:AccountsSSO
|-
|[http://build.meego.com/package/show?package=libaccounts-ui&project=Trunk libaccounts-ui]
|pcapriotti
|
|-
|[http://build.meego.com/package/show?package=libacl-x86&project=Trunk libacl-x86]
|austin
|
|-
|[http://build.meego.com/package/show?package=libao&project=Trunk libao]
|
|
|-
|[http://build.meego.com/package/show?package=libarchive&project=Trunk libarchive]
|
|
|-
|[http://build.meego.com/package/show?package=libart_lgpl&project=Trunk libart_lgpl]
|
|
|-
|[http://build.meego.com/package/show?package=libassuan&project=Trunk libassuan]
|
|
|-
|[http://build.meego.com/package/show?package=libasyncns&project=Trunk libasyncns]
|jfding
|
|-
|[http://build.meego.com/package/show?package=libatasmart&project=Trunk libatasmart]
|
|
|-
|[http://build.meego.com/package/show?package=libatomic_ops&project=Trunk libatomic_ops]
|
|devel:base
|-
|[http://build.meego.com/package/show?package=libattr-x86&project=Trunk libattr-x86]
|austin
|
|-
|[http://build.meego.com/package/show?package=libbonobo&project=Trunk libbonobo]
|
|
|-
|[http://build.meego.com/package/show?package=libbonoboui&project=Trunk libbonoboui]
|
|
|-
|[http://build.meego.com/package/show?package=libburn&project=Trunk libburn]
|
|
|-
|[http://build.meego.com/package/show?package=libcanberra&project=Trunk libcanberra]
|vivian
|
|-
|[http://build.meego.com/package/show?package=libcap&project=Trunk libcap]
|
|
|-
|[http://build.meego.com/package/show?package=libcap-ng&project=Trunk libcap-ng]
|
|
|-
|[http://build.meego.com/package/show?package=libcap-x86&project=Trunk libcap-x86]
|austin
|
|-
|[http://build.meego.com/package/show?package=libchamplain&project=Trunk libchamplain]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=libchewing&project=Trunk libchewing]
|jfding
|
|-
|[http://build.meego.com/package/show?package=libcmtspeech-ifx&project=Trunk libcmtspeech-ifx]
|vivian
|
|-
|[http://build.meego.com/package/show?package=libcmtspeechdata&project=Trunk libcmtspeechdata]
|
|
|-
|[http://build.meego.com/package/show?package=libcommhistory&project=Trunk libcommhistory]
|pcapriotti
|
|-
|[http://build.meego.com/package/show?package=libcontentaction&project=Trunk libcontentaction]
|maimishr
|devel:contentfw
|-
|[http://build.meego.com/package/show?package=libcqpid&project=Trunk libcqpid]
|jokylanp
|
|-
|[http://build.meego.com/package/show?package=libcreds3&project=Trunk libcreds3]
|peter,rrware
|
|-
|[http://build.meego.com/package/show?package=libcroco&project=Trunk libcroco]
|jfding
|
|-
|[http://build.meego.com/package/show?package=libdaemon&project=Trunk libdaemon]
|jfding
|
|-
|[http://build.meego.com/package/show?package=libdbus-c++&project=Trunk libdbus-c++]
|huaxu
|
|-
|[http://build.meego.com/package/show?package=libdiscid&project=Trunk libdiscid]
|
|
|-
|[http://build.meego.com/package/show?package=libdmx&project=Trunk libdmx]
|
|
|-
|[http://build.meego.com/package/show?package=libdres&project=Trunk libdres]
|mlehtonen
|devel:resourcepolicy
|-
|[http://build.meego.com/package/show?package=libdrm&project=Trunk libdrm]
|pli1
|devel:x11:Trunk
|-
|[http://build.meego.com/package/show?package=libdsme&project=Trunk libdsme]
|mlehtonen
|devel:systemsw
|-
|[http://build.meego.com/package/show?package=libedit&project=Trunk libedit]
|
|
|-
|[http://build.meego.com/package/show?package=libeigen2&project=Trunk libeigen2]
|bwachter
|
|-
|[http://build.meego.com/package/show?package=libenca&project=Trunk libenca]
|maimishr
|
|-
|[http://build.meego.com/package/show?package=liberation-fonts&project=Trunk liberation-fonts]
|
|
|-
|[http://build.meego.com/package/show?package=libevent&project=Trunk libevent]
|
|
|-
|[http://build.meego.com/package/show?package=libexif&project=Trunk libexif]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libfakekey&project=Trunk libfakekey]
|
|
|-
|[http://build.meego.com/package/show?package=libffi&project=Trunk libffi]
|jfding
|
|-
|[http://build.meego.com/package/show?package=libfontenc&project=Trunk libfontenc]
|
|
|-
|[http://build.meego.com/package/show?package=libfprint&project=Trunk libfprint]
|
|
|-
|[http://build.meego.com/package/show?package=libgail-gnome&project=Trunk libgail-gnome]
|
|
|-
|[http://build.meego.com/package/show?package=libgcc-x86&project=Trunk libgcc-x86]
|jsmoeller
|devel:base
|-
|[http://build.meego.com/package/show?package=libgcrypt&project=Trunk libgcrypt]
|
|
|-
|[http://build.meego.com/package/show?package=libgda&project=Trunk libgda]
|
|
|-
|[http://build.meego.com/package/show?package=libgdata&project=Trunk libgdata]
|daihan
|
|-
|[http://build.meego.com/package/show?package=libgdbus&project=Trunk libgdbus]
|
|
|-
|[http://build.meego.com/package/show?package=libgdiplus0&project=Trunk libgdiplus0]
|mmeeks
|
|-
|[http://build.meego.com/package/show?package=libgdl&project=Trunk libgdl]
|
|
|-
|[http://build.meego.com/package/show?package=libgee&project=Trunk libgee]
|
|
|-
|[http://build.meego.com/package/show?package=libggz&project=Trunk libggz]
|
|
|-
|[http://build.meego.com/package/show?package=libglade2&project=Trunk libglade2]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=libglademm&project=Trunk libglademm]
|
|
|-
|[http://build.meego.com/package/show?package=libgnome&project=Trunk libgnome]
|
|
|-
|[http://build.meego.com/package/show?package=libgnome-keyring&project=Trunk libgnome-keyring]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=libgnomecanvas&project=Trunk libgnomecanvas]
|
|
|-
|[http://build.meego.com/package/show?package=libgnomecups&project=Trunk libgnomecups]
|
|
|-
|[http://build.meego.com/package/show?package=libgnomekbd&project=Trunk libgnomekbd]
|
|
|-
|[http://build.meego.com/package/show?package=libgnomeprint22&project=Trunk libgnomeprint22]
|
|
|-
|[http://build.meego.com/package/show?package=libgnomeprintui22&project=Trunk libgnomeprintui22]
|
|
|-
|[http://build.meego.com/package/show?package=libgnomeui&project=Trunk libgnomeui]
|
|
|-
|[http://build.meego.com/package/show?package=libgpg-error&project=Trunk libgpg-error]
|
|
|-
|[http://build.meego.com/package/show?package=libgphoto2&project=Trunk libgphoto2]
|
|
|-
|[http://build.meego.com/package/show?package=libgsf&project=Trunk libgsf]
|
|
|-
|[http://build.meego.com/package/show?package=libgtop2&project=Trunk libgtop2]
|
|
|-
|[http://build.meego.com/package/show?package=libgweather&project=Trunk libgweather]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=libhangul&project=Trunk libhangul]
|
|
|-
|[http://build.meego.com/package/show?package=libical&project=Trunk libical]
|
|
|-
|[http://build.meego.com/package/show?package=libid3tag&project=Trunk libid3tag]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libidn&project=Trunk libidn]
|jfding
|
|-
|[http://build.meego.com/package/show?package=libiodata&project=Trunk libiodata]
|tapioran
|devel:systemsw
|-
|[http://build.meego.com/package/show?package=libiphb&project=Trunk libiphb]
|
|devel:systemsw
|-
|[http://build.meego.com/package/show?package=libiptcdata&project=Trunk libiptcdata]
|zivchang
|
|-
|[http://build.meego.com/package/show?package=libisofs&project=Trunk libisofs]
|
|
|-
|[http://build.meego.com/package/show?package=libjingle&project=Trunk libjingle]
|
|
|-
|[http://build.meego.com/package/show?package=libjpeg&project=Trunk libjpeg]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libksba&project=Trunk libksba]
|yanli
|
|-
|[http://build.meego.com/package/show?package=liblua-x86&project=Trunk liblua-x86]
|austin
|
|-
|[http://build.meego.com/package/show?package=libmatchbox&project=Trunk libmatchbox]
|
|
|-
|[http://build.meego.com/package/show?package=libmeegochat&project=Trunk libmeegochat]
|
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=libmeegotouch&project=Trunk libmeegotouch]
|krupert,msafr
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=libmikmod&project=Trunk libmikmod]
|
|
|-
|[http://build.meego.com/package/show?package=libmlocknice&project=Trunk libmlocknice]
|cvm
|devel:devices:n900
|-
|[http://build.meego.com/package/show?package=libmng&project=Trunk libmng]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libmp4v2&project=Trunk libmp4v2]
|
|
|-
|[http://build.meego.com/package/show?package=libmtp&project=Trunk libmtp]
|
|
|-
|[http://build.meego.com/package/show?package=libngf&project=Trunk libngf]
|mantyharju
|
|-
|[http://build.meego.com/package/show?package=libnice&project=Trunk libnice]
|
|
|-
|[http://build.meego.com/package/show?package=libnl&project=Trunk libnl]
|
|
|-
|[http://build.meego.com/package/show?package=libnotify&project=Trunk libnotify]
|
|
|-
|[http://build.meego.com/package/show?package=libofono-qt&project=Trunk libofono-qt]
|sbryan,boudra
|
|-
|[http://build.meego.com/package/show?package=libofx&project=Trunk libofx]
|
|
|-
|[http://build.meego.com/package/show?package=libogg&project=Trunk libogg]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=liboil&project=Trunk liboil]
|
|
|-
|[http://build.meego.com/package/show?package=libopenraw&project=Trunk libopenraw]
|
|
|-
|[http://build.meego.com/package/show?package=libopensync&project=Trunk libopensync]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=libopensync-plugin-vformat&project=Trunk libopensync-plugin-vformat]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=libpaper&project=Trunk libpaper]
|
|
|-
|[http://build.meego.com/package/show?package=libpcap&project=Trunk libpcap]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=libpciaccess&project=Trunk libpciaccess]
|
|
|-
|[http://build.meego.com/package/show?package=libpng&project=Trunk libpng]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libprolog&project=Trunk libprolog]
|
|devel:resourcepolicy
|-
|[http://build.meego.com/package/show?package=libpthread-stubs&project=Trunk libpthread-stubs]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=libqmlog&project=Trunk libqmlog]
|tapioran
|devel:systemsw
|-
|[http://build.meego.com/package/show?package=libqterminalmode&project=Trunk libqterminalmode]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=libqtsparql&project=Trunk libqtsparql]
|
|
|-
|[http://build.meego.com/package/show?package=libqtsparql-tracker-extensions&project=Trunk libqtsparql-tracker-extensions]
|maimishr
|
|-
|[http://build.meego.com/package/show?package=libqttracker&project=Trunk libqttracker]
|rusty
|devel:contentfw
|-
|[http://build.meego.com/package/show?package=libquill&project=Trunk libquill]
|
|
|-
|[http://build.meego.com/package/show?package=libquillmetadata&project=Trunk libquillmetadata]
|
|
|-
|[http://build.meego.com/package/show?package=librapi2&project=Trunk librapi2]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=librds&project=Trunk librds]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=libresource&project=Trunk libresource]
|
|devel:resourcepolicy
|-
|[http://build.meego.com/package/show?package=libresourceqt&project=Trunk libresourceqt]
|mlehtonen
|devel:resourcepolicy
|-
|[http://build.meego.com/package/show?package=librsvg2&project=Trunk librsvg2]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libsamplerate&project=Trunk libsamplerate]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libsatsolver&project=Trunk libsatsolver]
|xiaoqiang
|devel:packagemanagement
|-
|[http://build.meego.com/package/show?package=libseaside&project=Trunk libseaside]
|ceferron,ulf
|
|-
|[http://build.meego.com/package/show?package=libsexy&project=Trunk libsexy]
|
|
|-
|[http://build.meego.com/package/show?package=libshare-ui&project=Trunk libshare-ui]
|teemu.hukkanen
|
|-
|[http://build.meego.com/package/show?package=libsigc++&project=Trunk libsigc++]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=libsignon&project=Trunk libsignon]
|bwachter
|devel:AccountsSSO
|-
|[http://build.meego.com/package/show?package=libsignon-glib&project=Trunk libsignon-glib]
|pcapriotti
|
|-
|[http://build.meego.com/package/show?package=libsignoncrypto-qt&project=Trunk libsignoncrypto-qt]
|mardy
|
|-
|[http://build.meego.com/package/show?package=libsilc&project=Trunk libsilc]
|jfding
|
|-
|[http://build.meego.com/package/show?package=libsmack&project=Trunk libsmack]
|rrware
|devel:security
|-
|[http://build.meego.com/package/show?package=libsmbios&project=Trunk libsmbios]
|
|
|-
|[http://build.meego.com/package/show?package=libsndfile&project=Trunk libsndfile]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libsocialweb&project=Trunk libsocialweb]
|
|
|-
|[http://build.meego.com/package/show?package=libsocialweb-keys&project=Trunk libsocialweb-keys]
|
|
|-
|[http://build.meego.com/package/show?package=libsocialweb-qml&project=Trunk libsocialweb-qml]
|krupert
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=libsocialweb-qt&project=Trunk libsocialweb-qt]
|
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=libsoup&project=Trunk libsoup]
|
|
|-
|[http://build.meego.com/package/show?package=libspectre&project=Trunk libspectre]
|jfding
|
|-
|[http://build.meego.com/package/show?package=libspiro&project=Trunk libspiro]
|
|
|-
|[http://build.meego.com/package/show?package=libstdc++-x86&project=Trunk libstdc++-x86]
|austin
|
|-
|[http://build.meego.com/package/show?package=libsynce&project=Trunk libsynce]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=libsyncml&project=Trunk libsyncml]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=libtalloc&project=Trunk libtalloc]
|
|
|-
|[http://build.meego.com/package/show?package=libtar&project=Trunk libtar]
|
|
|-
|[http://build.meego.com/package/show?package=libtasn1&project=Trunk libtasn1]
|
|
|-
|[http://build.meego.com/package/show?package=libtdb&project=Trunk libtdb]
|
|
|-
|[http://build.meego.com/package/show?package=libtdb-compat&project=Trunk libtdb-compat]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=libtee&project=Trunk libtee]
|rrware
|
|-
|[http://build.meego.com/package/show?package=libtelepathy&project=Trunk libtelepathy]
|huaxu
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=libthai&project=Trunk libthai]
|
|
|-
|[http://build.meego.com/package/show?package=libtheora&project=Trunk libtheora]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libthumbnailer&project=Trunk libthumbnailer]
|
|
|-
|[http://build.meego.com/package/show?package=libtiff&project=Trunk libtiff]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libtool&project=Trunk libtool]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=libtrace&project=Trunk libtrace]
|
|devel:resourcepolicy
|-
|[http://build.meego.com/package/show?package=libuninameslist&project=Trunk libuninameslist]
|
|
|-
|[http://build.meego.com/package/show?package=libusb&project=Trunk libusb]
|
|
|-
|[http://build.meego.com/package/show?package=libusb1&project=Trunk libusb1]
|
|
|-
|[http://build.meego.com/package/show?package=libuser&project=Trunk libuser]
|
|
|-
|[http://build.meego.com/package/show?package=libutempter&project=Trunk libutempter]
|jfding
|
|-
|[http://build.meego.com/package/show?package=libv4l&project=Trunk libv4l]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libva&project=Trunk libva]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libvisual&project=Trunk libvisual]
|
|
|-
|[http://build.meego.com/package/show?package=libvorbis&project=Trunk libvorbis]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libwbxml2&project=Trunk libwbxml2]
|bwachter
|
|-
|[http://build.meego.com/package/show?package=libwmf&project=Trunk libwmf]
|
|
|-
|[http://build.meego.com/package/show?package=libwnck&project=Trunk libwnck]
|
|
|-
|[http://build.meego.com/package/show?package=libwpd&project=Trunk libwpd]
|
|
|-
|[http://build.meego.com/package/show?package=libwpg&project=Trunk libwpg]
|
|
|-
|[http://build.meego.com/package/show?package=libwps&project=Trunk libwps]
|
|
|-
|[http://build.meego.com/package/show?package=libwsbm&project=Trunk libwsbm]
|
|
|-
|[http://build.meego.com/package/show?package=libxcb&project=Trunk libxcb]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libxkbfile&project=Trunk libxkbfile]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libxklavier&project=Trunk libxklavier]
|
|
|-
|[http://build.meego.com/package/show?package=libxml2&project=Trunk libxml2]
|
|
|-
|[http://build.meego.com/package/show?package=libxml2-python&project=Trunk libxml2-python]
|
|
|-
|[http://build.meego.com/package/show?package=libxslt&project=Trunk libxslt]
|jfding
|
|-
|[http://build.meego.com/package/show?package=libzip&project=Trunk libzip]
|yyang
|
|-
|[http://build.meego.com/package/show?package=libzypp&project=Trunk libzypp]
|xiaoqiang
|devel:packagemanagement
|-
|[http://build.meego.com/package/show?package=libzypp-bindings&project=Trunk libzypp-bindings]
|yyang
|
|-
|[http://build.meego.com/package/show?package=link-grammar&project=Trunk link-grammar]
|
|
|-
|[http://build.meego.com/package/show?package=linux-firmware&project=Trunk linux-firmware]
|
|
|-
|[http://build.meego.com/package/show?package=lirc&project=Trunk lirc]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=lklug-fonts&project=Trunk lklug-fonts]
|
|
|-
|[http://build.meego.com/package/show?package=lockdev&project=Trunk lockdev]
|
|
|-
|[http://build.meego.com/package/show?package=logrotate&project=Trunk logrotate]
|
|
|-
|[http://build.meego.com/package/show?package=lohit-assamese-fonts&project=Trunk lohit-assamese-fonts]
|vivian
|
|-
|[http://build.meego.com/package/show?package=lohit-bengali-fonts&project=Trunk lohit-bengali-fonts]
|
|
|-
|[http://build.meego.com/package/show?package=lohit-hindi-fonts&project=Trunk lohit-hindi-fonts]
|
|
|-
|[http://build.meego.com/package/show?package=lohit-kannada-fonts&project=Trunk lohit-kannada-fonts]
|
|
|-
|[http://build.meego.com/package/show?package=lohit-malayalam-fonts&project=Trunk lohit-malayalam-fonts]
|
|
|-
|[http://build.meego.com/package/show?package=lohit-oriya-fonts&project=Trunk lohit-oriya-fonts]
|
|
|-
|[http://build.meego.com/package/show?package=lohit-punjabi-fonts&project=Trunk lohit-punjabi-fonts]
|
|
|-
|[http://build.meego.com/package/show?package=lohit-tamil-fonts&project=Trunk lohit-tamil-fonts]
|
|
|-
|[http://build.meego.com/package/show?package=lohit-telugu-fonts&project=Trunk lohit-telugu-fonts]
|
|
|-
|[http://build.meego.com/package/show?package=loudmouth&project=Trunk loudmouth]
|
|
|-
|[http://build.meego.com/package/show?package=lpsolve&project=Trunk lpsolve]
|
|
|-
|[http://build.meego.com/package/show?package=lrzsz&project=Trunk lrzsz]
|
|
|-
|[http://build.meego.com/package/show?package=lsof&project=Trunk lsof]
|
|
|-
|[http://build.meego.com/package/show?package=ltrace&project=Trunk ltrace]
|
|
|-
|[http://build.meego.com/package/show?package=lua&project=Trunk lua]
|jfding
|
|-
|[http://build.meego.com/package/show?package=lzo&project=Trunk lzo]
|yyang
|
|-
|[http://build.meego.com/package/show?package=m17n-contrib&project=Trunk m17n-contrib]
|
|
|-
|[http://build.meego.com/package/show?package=m17n-db&project=Trunk m17n-db]
|
|
|-
|[http://build.meego.com/package/show?package=m17n-lib&project=Trunk m17n-lib]
|
|
|-
|[http://build.meego.com/package/show?package=m2crypto&project=Trunk m2crypto]
|
|devel:security
|-
|[http://build.meego.com/package/show?package=m4&project=Trunk m4]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=mad-developer&project=Trunk mad-developer]
|boudra
|devel:tools:sdk:target
|-
|[http://build.meego.com/package/show?package=maemo-video-thumbnailer&project=Trunk maemo-video-thumbnailer]
|dlespiau
|devel:contentfw
|-
|[http://build.meego.com/package/show?package=mailcap&project=Trunk mailcap]
|
|
|-
|[http://build.meego.com/package/show?package=mailx&project=Trunk mailx]
|
|
|-
|[http://build.meego.com/package/show?package=make&project=Trunk make]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=makebootfat&project=Trunk makebootfat]
|
|
|-
|[http://build.meego.com/package/show?package=man&project=Trunk man]
|
|
|-
|[http://build.meego.com/package/show?package=man-pages&project=Trunk man-pages]
|
|
|-
|[http://build.meego.com/package/show?package=marble&project=Trunk marble]
|
|
|-
|[http://build.meego.com/package/show?package=marmazon&project=Trunk marmazon]
|
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=matchbox-keyboard&project=Trunk matchbox-keyboard]
|
|
|-
|[http://build.meego.com/package/show?package=matchbox-panel&project=Trunk matchbox-panel]
|
|
|-
|[http://build.meego.com/package/show?package=matchbox-window-manager&project=Trunk matchbox-window-manager]
|tebrandt,tracyg
|
|-
|[http://build.meego.com/package/show?package=mathml-fonts&project=Trunk mathml-fonts]
|
|
|-
|[http://build.meego.com/package/show?package=mce&project=Trunk mce]
|tapioran
|devel:systemsw
|-
|[http://build.meego.com/package/show?package=mce-headers&project=Trunk mce-headers]
|tapioran
|devel:systemsw
|-
|[http://build.meego.com/package/show?package=meego-accelerator&project=Trunk meego-accelerator]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=meego-bookmarks&project=Trunk meego-bookmarks]
|
|
|-
|[http://build.meego.com/package/show?package=meego-cross-armv5tel-sysroot&project=Trunk meego-cross-armv5tel-sysroot]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=meego-cross-armv7hl-sysroot&project=Trunk meego-cross-armv7hl-sysroot]
|austin
|
|-
|[http://build.meego.com/package/show?package=meego-cross-armv7l-sysroot&project=Trunk meego-cross-armv7l-sysroot]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=meego-cursor-theme&project=Trunk meego-cursor-theme]
|
|
|-
|[http://build.meego.com/package/show?package=meego-handset-calendar&project=Trunk meego-handset-calendar]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-chat&project=Trunk meego-handset-chat]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-configs&project=Trunk meego-handset-configs]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-dialer&project=Trunk meego-handset-dialer]
|ceferron,ulf
|devel:ux:handset
|-
|[http://build.meego.com/package/show?package=meego-handset-dialer-branding-meego&project=Trunk meego-handset-dialer-branding-meego]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-dialer-translations&project=Trunk meego-handset-dialer-translations]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-email&project=Trunk meego-handset-email]
|ulf
|devel:ux:handset
|-
|[http://build.meego.com/package/show?package=meego-handset-email-translations&project=Trunk meego-handset-email-translations]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-icon-theme&project=Trunk meego-handset-icon-theme]
|ceferron,ulf
|devel:ux:handset
|-
|[http://build.meego.com/package/show?package=meego-handset-mannequin&project=Trunk meego-handset-mannequin]
|ceferron,ulf
|devel:ux:handset
|-
|[http://build.meego.com/package/show?package=meego-handset-music&project=Trunk meego-handset-music]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-music-branding-meego&project=Trunk meego-handset-music-branding-meego]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-people&project=Trunk meego-handset-people]
|ceferron,ulf
|devel:ux:handset
|-
|[http://build.meego.com/package/show?package=meego-handset-photos&project=Trunk meego-handset-photos]
|krupert,ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-photos-branding-meego&project=Trunk meego-handset-photos-branding-meego]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-sms&project=Trunk meego-handset-sms]
|ceferron,ulf
|devel:ux:handset
|-
|[http://build.meego.com/package/show?package=meego-handset-sms-translations&project=Trunk meego-handset-sms-translations]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-socialweb&project=Trunk meego-handset-socialweb]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-sound-theme&project=Trunk meego-handset-sound-theme]
|ulf,tracyg
|
|-
|[http://build.meego.com/package/show?package=meego-handset-video&project=Trunk meego-handset-video]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-video-branding-meego&project=Trunk meego-handset-video-branding-meego]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-help&project=Trunk meego-help]
|
|
|-
|[http://build.meego.com/package/show?package=meego-ivi-configs&project=Trunk meego-ivi-configs]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=meego-lsb&project=Trunk meego-lsb]
|
|
|-
|[http://build.meego.com/package/show?package=meego-menus&project=Trunk meego-menus]
|
|
|-
|[http://build.meego.com/package/show?package=meego-netbook-intro&project=Trunk meego-netbook-intro]
|
|
|-
|[http://build.meego.com/package/show?package=meego-netbook-settings&project=Trunk meego-netbook-settings]
|
|
|-
|[http://build.meego.com/package/show?package=meego-netbook-theme&project=Trunk meego-netbook-theme]
|
|
|-
|[http://build.meego.com/package/show?package=meego-netbook-user-skel&project=Trunk meego-netbook-user-skel]
|
|
|-
|[http://build.meego.com/package/show?package=meego-osc-plugins&project=Trunk meego-osc-plugins]
|jfding
|
|-
|[http://build.meego.com/package/show?package=meego-packaging-tools&project=Trunk meego-packaging-tools]
|jfding
|devel:tools:building
|-
|[http://build.meego.com/package/show?package=meego-panel-applications&project=Trunk meego-panel-applications]
|
|
|-
|[http://build.meego.com/package/show?package=meego-panel-datetime&project=Trunk meego-panel-datetime]
|
|
|-
|[http://build.meego.com/package/show?package=meego-panel-devices&project=Trunk meego-panel-devices]
|
|
|-
|[http://build.meego.com/package/show?package=meego-panel-myzone&project=Trunk meego-panel-myzone]
|
|
|-
|[http://build.meego.com/package/show?package=meego-panel-networks&project=Trunk meego-panel-networks]
|
|
|-
|[http://build.meego.com/package/show?package=meego-panel-pasteboard&project=Trunk meego-panel-pasteboard]
|
|
|-
|[http://build.meego.com/package/show?package=meego-panel-people&project=Trunk meego-panel-people]
|
|
|-
|[http://build.meego.com/package/show?package=meego-panel-status&project=Trunk meego-panel-status]
|
|
|-
|[http://build.meego.com/package/show?package=meego-panel-web&project=Trunk meego-panel-web]
|
|
|-
|[http://build.meego.com/package/show?package=meego-panel-zones&project=Trunk meego-panel-zones]
|
|
|-
|[http://build.meego.com/package/show?package=meego-release&project=Trunk meego-release]
|
|
|-
|[http://build.meego.com/package/show?package=meego-rpm-config&project=Trunk meego-rpm-config]
|
|devel:base
|-
|[http://build.meego.com/package/show?package=meego-sdk-qemugl-addon&project=Trunk meego-sdk-qemugl-addon]
|boudra
|devel:tools:sdk:target
|-
|[http://build.meego.com/package/show?package=meego-simulator-launcher&project=Trunk meego-simulator-launcher]
|boudra
|devel:tools:sdk:target
|-
|[http://build.meego.com/package/show?package=meego-sound-theme&project=Trunk meego-sound-theme]
|
|
|-
|[http://build.meego.com/package/show?package=meegotouch-applauncherd&project=Trunk meegotouch-applauncherd]
|
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-applifed&project=Trunk meegotouch-applifed]
|
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-compositor&project=Trunk meegotouch-compositor]
|krupert,msafr
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-controlpanel&project=Trunk meegotouch-controlpanel]
|krupert
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-controlpanelapplets&project=Trunk meegotouch-controlpanelapplets]
|
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-feedback&project=Trunk meegotouch-feedback]
|krupert,araujo
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-feedbackreactionmaps&project=Trunk meegotouch-feedbackreactionmaps]
|krupert,araujo
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-home&project=Trunk meegotouch-home]
|krupert,msafr
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-inputmethodbridges&project=Trunk meegotouch-inputmethodbridges]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meegotouch-inputmethodengine&project=Trunk meegotouch-inputmethodengine]
|krupert,araujo
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-inputmethodframework&project=Trunk meegotouch-inputmethodframework]
|krupert,araujo
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-inputmethodkeyboard&project=Trunk meegotouch-inputmethodkeyboard]
|krupert,araujo
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-qt-style&project=Trunk meegotouch-qt-style]
|boudra
|
|-
|[http://build.meego.com/package/show?package=meegotouch-systemtui&project=Trunk meegotouch-systemtui]
|
|
|-
|[http://build.meego.com/package/show?package=meegotouch-systemui&project=Trunk meegotouch-systemui]
|krupert
|
|-
|[http://build.meego.com/package/show?package=meegotouch-theme&project=Trunk meegotouch-theme]
|krupert,msafr
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-theme-meego&project=Trunk meegotouch-theme-meego]
|ceferron,ulf
|
|-
|[http://build.meego.com/package/show?package=meegotouchcp-bluetooth&project=Trunk meegotouchcp-bluetooth]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meegotouchcp-chat&project=Trunk meegotouchcp-chat]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meegotouchcp-connman&project=Trunk meegotouchcp-connman]
|ceferron,ulf
|
|-
|[http://build.meego.com/package/show?package=meegotouchcp-connman-ivi&project=Trunk meegotouchcp-connman-ivi]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=meegotouchcp-datetime&project=Trunk meegotouchcp-datetime]
|
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouchcp-language&project=Trunk meegotouchcp-language]
|
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouchcp-regionformat&project=Trunk meegotouchcp-regionformat]
|krupert
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouchcp-socialweb&project=Trunk meegotouchcp-socialweb]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meegotouchcp-telephony&project=Trunk meegotouchcp-telephony]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meld&project=Trunk meld]
|
|
|-
|[http://build.meego.com/package/show?package=memuse&project=Trunk memuse]
|
|
|-
|[http://build.meego.com/package/show?package=mesa&project=Trunk mesa]
|pli1
|devel:x11:Trunk
|-
|[http://build.meego.com/package/show?package=mesa-demos&project=Trunk mesa-demos]
|
|devel:x11:Trunk
|-
|[http://build.meego.com/package/show?package=mic2&project=Trunk mic2]
|yyang
|devel:tools:building
|-
|[http://build.meego.com/package/show?package=min&project=Trunk min]
|timoph,jokylanp
|
|-
|[http://build.meego.com/package/show?package=mingetty&project=Trunk mingetty]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=minicom&project=Trunk minicom]
|
|
|-
|[http://build.meego.com/package/show?package=mkcal&project=Trunk mkcal]
|
|
|-
|[http://build.meego.com/package/show?package=mkdevnodes&project=Trunk mkdevnodes]
|
|
|-
|[http://build.meego.com/package/show?package=mkinitrd&project=Trunk mkinitrd]
|yyang
|
|-
|[http://build.meego.com/package/show?package=mlocate&project=Trunk mlocate]
|
|
|-
|[http://build.meego.com/package/show?package=mm-common&project=Trunk mm-common]
|
|
|-
|[http://build.meego.com/package/show?package=mobile-broadband-provider-info&project=Trunk mobile-broadband-provider-info]
|
|
|-
|[http://build.meego.com/package/show?package=moblin-generic-backgrounds&project=Trunk moblin-generic-backgrounds]
|
|
|-
|[http://build.meego.com/package/show?package=moblin-icon-theme&project=Trunk moblin-icon-theme]
|
|
|-
|[http://build.meego.com/package/show?package=moblin-live&project=Trunk moblin-live]
|
|
|-
|[http://build.meego.com/package/show?package=moblin-user-guide&project=Trunk moblin-user-guide]
|
|
|-
|[http://build.meego.com/package/show?package=module-init-tools&project=Trunk module-init-tools]
|
|
|-
|[http://build.meego.com/package/show?package=monit&project=Trunk monit]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=monitor-call-audio-setting-mid&project=Trunk monitor-call-audio-setting-mid]
|vivian
|
|-
|[http://build.meego.com/package/show?package=mono-addins&project=Trunk mono-addins]
|mmeeks
|
|-
|[http://build.meego.com/package/show?package=mono-core&project=Trunk mono-core]
|priya
|
|-
|[http://build.meego.com/package/show?package=mono-zeroconf&project=Trunk mono-zeroconf]
|mmeeks
|
|-
|[http://build.meego.com/package/show?package=mozilla-filesystem&project=Trunk mozilla-filesystem]
|jfding
|
|-
|[http://build.meego.com/package/show?package=mpage&project=Trunk mpage]
|
|
|-
|[http://build.meego.com/package/show?package=mpc&project=Trunk mpc]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=mpc-x86&project=Trunk mpc-x86]
|jsmoeller
|devel:base
|-
|[http://build.meego.com/package/show?package=mpfr&project=Trunk mpfr]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=mpfr-x86&project=Trunk mpfr-x86]
|jsmoeller
|devel:base
|-
|[http://build.meego.com/package/show?package=mssf-certman&project=Trunk mssf-certman]
|rrware
|
|-
|[http://build.meego.com/package/show?package=mssf-crypto&project=Trunk mssf-crypto]
|rrware
|
|-
|[http://build.meego.com/package/show?package=mtd-utils&project=Trunk mtd-utils]
|
|
|-
|[http://build.meego.com/package/show?package=mtdev&project=Trunk mtdev]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=mtools&project=Trunk mtools]
|yyang
|
|-
|[http://build.meego.com/package/show?package=mutter&project=Trunk mutter]
|
|devel:ux:netbook
|-
|[http://build.meego.com/package/show?package=mutter-meego&project=Trunk mutter-meego]
|
|
|-
|[http://build.meego.com/package/show?package=mx&project=Trunk mx]
|
|
|-
|[http://build.meego.com/package/show?package=n900-camera-firmware&project=Trunk n900-camera-firmware]
|cvm
|devel:devices:n900
|-
|[http://build.meego.com/package/show?package=nano&project=Trunk nano]
|
|
|-
|[http://build.meego.com/package/show?package=nasm&project=Trunk nasm]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=nautilus&project=Trunk nautilus]
|
|
|-
|[http://build.meego.com/package/show?package=nautilus-python&project=Trunk nautilus-python]
|
|
|-
|[http://build.meego.com/package/show?package=navit&project=Trunk navit]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=navit-maps&project=Trunk navit-maps]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=nc&project=Trunk nc]
|
|
|-
|[http://build.meego.com/package/show?package=ncurses&project=Trunk ncurses]
|jfding
|
|-
|[http://build.meego.com/package/show?package=ncurses-libs-x86&project=Trunk ncurses-libs-x86]
|jsmoeller
|devel:base
|-
|[http://build.meego.com/package/show?package=ndesk-dbus&project=Trunk ndesk-dbus]
|mmeeks
|
|-
|[http://build.meego.com/package/show?package=ndesk-dbus-glib&project=Trunk ndesk-dbus-glib]
|mmeeks
|
|-
|[http://build.meego.com/package/show?package=neon&project=Trunk neon]
|jfding
|
|-
|[http://build.meego.com/package/show?package=net-tools&project=Trunk net-tools]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=netbook-backgrounds&project=Trunk netbook-backgrounds]
|
|
|-
|[http://build.meego.com/package/show?package=netbook-icon-theme&project=Trunk netbook-icon-theme]
|
|
|-
|[http://build.meego.com/package/show?package=netpbm&project=Trunk netpbm]
|
|
|-
|[http://build.meego.com/package/show?package=neverball&project=Trunk neverball]
|
|
|-
|[http://build.meego.com/package/show?package=newt&project=Trunk newt]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=newt-python&project=Trunk newt-python]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=ngfd&project=Trunk ngfd]
|mantyharju
|
|-
|[http://build.meego.com/package/show?package=nodoka-theme-gnome&project=Trunk nodoka-theme-gnome]
|
|
|-
|[http://build.meego.com/package/show?package=nokia-n900-configs&project=Trunk nokia-n900-configs]
|cvm
|devel:devices:n900
|-
|[http://build.meego.com/package/show?package=nokia-n900-rescue-initrd&project=Trunk nokia-n900-rescue-initrd]
|cvm
|devel:devices:n900
|-
|[http://build.meego.com/package/show?package=nokia-usb-networking&project=Trunk nokia-usb-networking]
|cvm
|devel:devices:n900
|-
|[http://build.meego.com/package/show?package=notification-daemon&project=Trunk notification-daemon]
|
|
|-
|[http://build.meego.com/package/show?package=notification-daemon-engine-nodoka&project=Trunk notification-daemon-engine-nodoka]
|
|
|-
|[http://build.meego.com/package/show?package=notify-python&project=Trunk notify-python]
|
|
|-
|[http://build.meego.com/package/show?package=notify-sharp&project=Trunk notify-sharp]
|mmeeks
|
|-
|[http://build.meego.com/package/show?package=nspr&project=Trunk nspr]
|jfding
|
|-
|[http://build.meego.com/package/show?package=nspr-x86&project=Trunk nspr-x86]
|austin
|
|-
|[http://build.meego.com/package/show?package=nss&project=Trunk nss]
|qzhao9
|devel:security
|-
|[http://build.meego.com/package/show?package=nss-mdns&project=Trunk nss-mdns]
|
|
|-
|[http://build.meego.com/package/show?package=nss-softokn-freebl-x86&project=Trunk nss-softokn-freebl-x86]
|austin
|
|-
|[http://build.meego.com/package/show?package=nss-x86&project=Trunk nss-x86]
|austin
|
|-
|[http://build.meego.com/package/show?package=ntp&project=Trunk ntp]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=o3read&project=Trunk o3read]
|
|
|-
|[http://build.meego.com/package/show?package=obex-data-server&project=Trunk obex-data-server]
|
|
|-
|[http://build.meego.com/package/show?package=obexd&project=Trunk obexd]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=ofono&project=Trunk ofono]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=ohm&project=Trunk ohm]
|mlehtonen
|devel:resourcepolicy
|-
|[http://build.meego.com/package/show?package=ohm-plugins-misc&project=Trunk ohm-plugins-misc]
|mlehtonen
|devel:resourcepolicy
|-
|[http://build.meego.com/package/show?package=opal&project=Trunk opal]
|
|
|-
|[http://build.meego.com/package/show?package=openconnect&project=Trunk openconnect]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=opengl-games-utils&project=Trunk opengl-games-utils]
|
|
|-
|[http://build.meego.com/package/show?package=openjade&project=Trunk openjade]
|
|
|-
|[http://build.meego.com/package/show?package=openjpeg&project=Trunk openjpeg]
|
|
|-
|[http://build.meego.com/package/show?package=openldap&project=Trunk openldap]
|
|
|-
|[http://build.meego.com/package/show?package=openobex&project=Trunk openobex]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=opensp&project=Trunk opensp]
|
|
|-
|[http://build.meego.com/package/show?package=openssh&project=Trunk openssh]
|qzhao9
|
|-
|[http://build.meego.com/package/show?package=openssl&project=Trunk openssl]
|qzhao9
|devel:security
|-
|[http://build.meego.com/package/show?package=openssl-certs&project=Trunk openssl-certs]
|
|
|-
|[http://build.meego.com/package/show?package=orc&project=Trunk orc]
|lisayue
|devel:multimedia
|-
|[http://build.meego.com/package/show?package=org-mode&project=Trunk org-mode]
|
|
|-
|[http://build.meego.com/package/show?package=osc&project=Trunk osc]
|jfding
|devel:tools:building
|-
|[http://build.meego.com/package/show?package=ots&project=Trunk ots]
|
|
|-
|[http://build.meego.com/package/show?package=package-groups&project=Trunk package-groups]
|nashif
|
|-
|[http://build.meego.com/package/show?package=pacrunner&project=Trunk pacrunner]
|martin
|
|-
|[http://build.meego.com/package/show?package=pakchois&project=Trunk pakchois]
|
|
|-
|[http://build.meego.com/package/show?package=pam&project=Trunk pam]
|qzhao9
|
|-
|[http://build.meego.com/package/show?package=pam_pkcs11&project=Trunk pam_pkcs11]
|
|
|-
|[http://build.meego.com/package/show?package=pango&project=Trunk pango]
|
|
|-
|[http://build.meego.com/package/show?package=pangomm&project=Trunk pangomm]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=paps&project=Trunk paps]
|
|
|-
|[http://build.meego.com/package/show?package=papyon&project=Trunk papyon]
|lixu
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=parted&project=Trunk parted]
|vivian
|
|-
|[http://build.meego.com/package/show?package=passivetex&project=Trunk passivetex]
|
|
|-
|[http://build.meego.com/package/show?package=passwd&project=Trunk passwd]
|qzhao9
|
|-
|[http://build.meego.com/package/show?package=patch&project=Trunk patch]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=patch-x86&project=Trunk patch-x86]
|austin
|
|-
|[http://build.meego.com/package/show?package=patchelf&project=Trunk patchelf]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=patchutils&project=Trunk patchutils]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=pavucontrol&project=Trunk pavucontrol]
|vivian
|
|-
|[http://build.meego.com/package/show?package=pax&project=Trunk pax]
|
|
|-
|[http://build.meego.com/package/show?package=pciutils&project=Trunk pciutils]
|
|
|-
|[http://build.meego.com/package/show?package=pcre&project=Trunk pcre]
|
|
|-
|[http://build.meego.com/package/show?package=perl&project=Trunk perl]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Archive-Zip&project=Trunk perl-Archive-Zip]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Array-Compare&project=Trunk perl-Array-Compare]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Config-IniFiles&project=Trunk perl-Config-IniFiles]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Convert-ASN1&project=Trunk perl-Convert-ASN1]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Convert-BinHex&project=Trunk perl-Convert-BinHex]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Crypt-SSLeay&project=Trunk perl-Crypt-SSLeay]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Date-Manip&project=Trunk perl-Date-Manip]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Devel-StackTrace&project=Trunk perl-Devel-StackTrace]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Devel-Symdump&project=Trunk perl-Devel-Symdump]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Error&project=Trunk perl-Error]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-ExtUtils-Depends&project=Trunk perl-ExtUtils-Depends]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-ExtUtils-MakeMaker-Coverage&project=Trunk perl-ExtUtils-MakeMaker-Coverage]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-ExtUtils-PkgConfig&project=Trunk perl-ExtUtils-PkgConfig]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-File-BaseDir&project=Trunk perl-File-BaseDir]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-File-DesktopEntry&project=Trunk perl-File-DesktopEntry]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-File-MimeInfo&project=Trunk perl-File-MimeInfo]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-File-Which&project=Trunk perl-File-Which]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Finance-Quote&project=Trunk perl-Finance-Quote]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Font-TTF&project=Trunk perl-Font-TTF]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Glib&project=Trunk perl-Glib]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-HTML-Parser&project=Trunk perl-HTML-Parser]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-HTML-TableExtract&project=Trunk perl-HTML-TableExtract]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-HTML-Tagset&project=Trunk perl-HTML-Tagset]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-HTML-Tree&project=Trunk perl-HTML-Tree]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-IO-Socket-INET6&project=Trunk perl-IO-Socket-INET6]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-IO-Socket-SSL&project=Trunk perl-IO-Socket-SSL]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-IO-stringy&project=Trunk perl-IO-stringy]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-JSON&project=Trunk perl-JSON]
|qzhao9,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=perl-MIME-Lite&project=Trunk perl-MIME-Lite]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-MIME-tools&project=Trunk perl-MIME-tools]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-MailTools&project=Trunk perl-MailTools]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Net-LibIDN&project=Trunk perl-Net-LibIDN]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Net-SMTP-SSL&project=Trunk perl-Net-SMTP-SSL]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Net-SSLeay&project=Trunk perl-Net-SSLeay]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Parse-Yapp&project=Trunk perl-Parse-Yapp]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Pod-Coverage&project=Trunk perl-Pod-Coverage]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-SDL&project=Trunk perl-SDL]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-SGMLSpm&project=Trunk perl-SGMLSpm]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-SOAP-Lite&project=Trunk perl-SOAP-Lite]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-SVG&project=Trunk perl-SVG]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-SVG-Parser&project=Trunk perl-SVG-Parser]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Socket6&project=Trunk perl-Socket6]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Sub-Uplevel&project=Trunk perl-Sub-Uplevel]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Test-Exception&project=Trunk perl-Test-Exception]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Test-MockObject&project=Trunk perl-Test-MockObject]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Test-NoWarnings&project=Trunk perl-Test-NoWarnings]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Test-Number-Delta&project=Trunk perl-Test-Number-Delta]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Test-Pod&project=Trunk perl-Test-Pod]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Test-Pod-Coverage&project=Trunk perl-Test-Pod-Coverage]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Test-Tester&project=Trunk perl-Test-Tester]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Test-Warn&project=Trunk perl-Test-Warn]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Text-Unidecode&project=Trunk perl-Text-Unidecode]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Tie-IxHash&project=Trunk perl-Tie-IxHash]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-TimeDate&project=Trunk perl-TimeDate]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Tk&project=Trunk perl-Tk]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Tree-DAG_Node&project=Trunk perl-Tree-DAG_Node]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-UNIVERSAL-can&project=Trunk perl-UNIVERSAL-can]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-UNIVERSAL-isa&project=Trunk perl-UNIVERSAL-isa]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-URI&project=Trunk perl-URI]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-XML-DOM&project=Trunk perl-XML-DOM]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-XML-LibXML&project=Trunk perl-XML-LibXML]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-XML-NamespaceSupport&project=Trunk perl-XML-NamespaceSupport]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-XML-Parser&project=Trunk perl-XML-Parser]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-XML-RegExp&project=Trunk perl-XML-RegExp]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-XML-SAX&project=Trunk perl-XML-SAX]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-XML-Simple&project=Trunk perl-XML-Simple]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-XML-TreeBuilder&project=Trunk perl-XML-TreeBuilder]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-XML-XQL&project=Trunk perl-XML-XQL]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-YAML&project=Trunk perl-YAML]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-gettext&project=Trunk perl-gettext]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-libwww-perl&project=Trunk perl-libwww-perl]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-libxml-perl&project=Trunk perl-libxml-perl]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=persistman&project=Trunk persistman]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=phidgetlinux&project=Trunk phidgetlinux]
|xing
|
|-
|[http://build.meego.com/package/show?package=phonesim&project=Trunk phonesim]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=phonon&project=Trunk phonon]
|xiaoqiang,quanxianwang,boudra
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=pidgin&project=Trunk pidgin]
|
|
|-
|[http://build.meego.com/package/show?package=pidgin-sipe&project=Trunk pidgin-sipe]
|
|
|-
|[http://build.meego.com/package/show?package=pixman&project=Trunk pixman]
|xyl
|
|-
|[http://build.meego.com/package/show?package=pkgconfig&project=Trunk pkgconfig]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=plib&project=Trunk plib]
|
|
|-
|[http://build.meego.com/package/show?package=plymouth-lite&project=Trunk plymouth-lite]
|
|
|-
|[http://build.meego.com/package/show?package=pm-utils&project=Trunk pm-utils]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=pmtools&project=Trunk pmtools]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=pocketsphinx&project=Trunk pocketsphinx]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=poedit&project=Trunk poedit]
|
|
|-
|[http://build.meego.com/package/show?package=policy-settings-basic-mfld&project=Trunk policy-settings-basic-mfld]
|mlehtonen
|
|-
|[http://build.meego.com/package/show?package=policy-settings-basic-n900&project=Trunk policy-settings-basic-n900]
|mlehtonen
|
|-
|[http://build.meego.com/package/show?package=polkit&project=Trunk polkit]
|qzhao9
|
|-
|[http://build.meego.com/package/show?package=polkit-gnome&project=Trunk polkit-gnome]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=poppler&project=Trunk poppler]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=poppler-data&project=Trunk poppler-data]
|boudra
|
|-
|[http://build.meego.com/package/show?package=poppler-qt&project=Trunk poppler-qt]
|boudra
|
|-
|[http://build.meego.com/package/show?package=popt&project=Trunk popt]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=popt-x86&project=Trunk popt-x86]
|austin
|
|-
|[http://build.meego.com/package/show?package=post-build-checks&project=Trunk post-build-checks]
|nashif
|
|-
|[http://build.meego.com/package/show?package=poster&project=Trunk poster]
|
|
|-
|[http://build.meego.com/package/show?package=powerstatemgr&project=Trunk powerstatemgr]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=powertop&project=Trunk powertop]
|arjan
|
|-
|[http://build.meego.com/package/show?package=ppl&project=Trunk ppl]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=ppp&project=Trunk ppp]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=prelink&project=Trunk prelink]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=procps&project=Trunk procps]
|
|
|-
|[http://build.meego.com/package/show?package=psb-headers&project=Trunk psb-headers]
|
|
|-
|[http://build.meego.com/package/show?package=psmisc&project=Trunk psmisc]
|yyang
|
|-
|[http://build.meego.com/package/show?package=psutils&project=Trunk psutils]
|
|
|-
|[http://build.meego.com/package/show?package=pth&project=Trunk pth]
|
|
|-
|[http://build.meego.com/package/show?package=ptlib&project=Trunk ptlib]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=pulseaudio&project=Trunk pulseaudio]
|vivian
|devel:resourcepolicy
|-
|[http://build.meego.com/package/show?package=pulseaudio-modules-meego&project=Trunk pulseaudio-modules-meego]
|
|devel:multimedia
|-
|[http://build.meego.com/package/show?package=pulseaudio-modules-mfld&project=Trunk pulseaudio-modules-mfld]
|ulf
|
|-
|[http://build.meego.com/package/show?package=pulseaudio-policy-enforcement&project=Trunk pulseaudio-policy-enforcement]
|mlehtonen
|
|-
|[http://build.meego.com/package/show?package=pulseaudio-settings-n900&project=Trunk pulseaudio-settings-n900]
|cvm
|devel:devices:n900
|-
|[http://build.meego.com/package/show?package=pyOpenSSL&project=Trunk pyOpenSSL]
|
|
|-
|[http://build.meego.com/package/show?package=pycairo&project=Trunk pycairo]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=pyclutter&project=Trunk pyclutter]
|rbradford,ebassi
|
|-
|[http://build.meego.com/package/show?package=pyclutter-gtk&project=Trunk pyclutter-gtk]
|rbradford,ebassi
|
|-
|[http://build.meego.com/package/show?package=pygobject2&project=Trunk pygobject2]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=pygpgme&project=Trunk pygpgme]
|
|
|-
|[http://build.meego.com/package/show?package=pygtk2&project=Trunk pygtk2]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=pygtkglext&project=Trunk pygtkglext]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=pygtksourceview&project=Trunk pygtksourceview]
|
|
|-
|[http://build.meego.com/package/show?package=pykickstart&project=Trunk pykickstart]
|vivian
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=pyorbit&project=Trunk pyorbit]
|
|
|-
|[http://build.meego.com/package/show?package=pyparted&project=Trunk pyparted]
|vivian
|
|-
|[http://build.meego.com/package/show?package=python&project=Trunk python]
|quanxianwang
|
|-
|[http://build.meego.com/package/show?package=python-Coherence&project=Trunk python-Coherence]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-ZSI&project=Trunk python-ZSI]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-adns&project=Trunk python-adns]
|quanxianwang
|
|-
|[http://build.meego.com/package/show?package=python-chardet&project=Trunk python-chardet]
|jiachenghu
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-cheetah&project=Trunk python-cheetah]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-configobj&project=Trunk python-configobj]
|quanxianwang
|
|-
|[http://build.meego.com/package/show?package=python-crypto&project=Trunk python-crypto]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-dateutil&project=Trunk python-dateutil]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-decorator&project=Trunk python-decorator]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-docutils&project=Trunk python-docutils]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-dtopt&project=Trunk python-dtopt]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-enchant&project=Trunk python-enchant]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-formencode&project=Trunk python-formencode]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-fpconst&project=Trunk python-fpconst]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-gdata&project=Trunk python-gdata]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-imaging&project=Trunk python-imaging]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-iniparse&project=Trunk python-iniparse]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-louie&project=Trunk python-louie]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-lxml&project=Trunk python-lxml]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-magic&project=Trunk python-magic]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-markdown&project=Trunk python-markdown]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-mutagen&project=Trunk python-mutagen]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-nose&project=Trunk python-nose]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-numeric&project=Trunk python-numeric]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-paste&project=Trunk python-paste]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-paste-deploy&project=Trunk python-paste-deploy]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-pycurl&project=Trunk python-pycurl]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-pygments&project=Trunk python-pygments]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-reportlab&project=Trunk python-reportlab]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-setuptools&project=Trunk python-setuptools]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-sexy&project=Trunk python-sexy]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-simplejson&project=Trunk python-simplejson]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-sqlite2&project=Trunk python-sqlite2]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-telepathy&project=Trunk python-telepathy]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-tempita&project=Trunk python-tempita]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-toscawidgets&project=Trunk python-toscawidgets]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-tw-forms&project=Trunk python-tw-forms]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-twisted&project=Trunk python-twisted]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-twisted-conch&project=Trunk python-twisted-conch]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-twisted-core&project=Trunk python-twisted-core]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-twisted-lore&project=Trunk python-twisted-lore]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-twisted-mail&project=Trunk python-twisted-mail]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-twisted-names&project=Trunk python-twisted-names]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-twisted-news&project=Trunk python-twisted-news]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-twisted-runner&project=Trunk python-twisted-runner]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-twisted-web&project=Trunk python-twisted-web]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-twisted-web2&project=Trunk python-twisted-web2]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-twisted-words&project=Trunk python-twisted-words]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-urlgrabber&project=Trunk python-urlgrabber]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-webob&project=Trunk python-webob]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-which&project=Trunk python-which]
|
|
|-
|[http://build.meego.com/package/show?package=python-wsgiproxy&project=Trunk python-wsgiproxy]
|quanxianwang
|
|-
|[http://build.meego.com/package/show?package=python-xklavier&project=Trunk python-xklavier]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-zope-filesystem&project=Trunk python-zope-filesystem]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-zope-interface&project=Trunk python-zope-interface]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=pytz&project=Trunk pytz]
|
|
|-
|[http://build.meego.com/package/show?package=pyxdg&project=Trunk pyxdg]
|jiachenghu
|
|-
|[http://build.meego.com/package/show?package=qca2&project=Trunk qca2]
|boudra
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=qca2-ossl&project=Trunk qca2-ossl]
|boudra
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=qjson&project=Trunk qjson]
|rusty
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=qmf&project=Trunk qmf]
|boudra
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=qmsystem&project=Trunk qmsystem]
|tapioran
|devel:systemsw
|-
|[http://build.meego.com/package/show?package=qpid-cpp&project=Trunk qpid-cpp]
|jokylanp
|
|-
|[http://build.meego.com/package/show?package=qt&project=Trunk qt]
|boudra
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=qt-creator&project=Trunk qt-creator]
|priya,boudra
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=qt-mobility&project=Trunk qt-mobility]
|boudra
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=qt-mobility-geoservices-cloudmade&project=Trunk qt-mobility-geoservices-cloudmade]
|mikeleib
|
|-
|[http://build.meego.com/package/show?package=qt-obex-ftp-library&project=Trunk qt-obex-ftp-library]
|
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=qtcontacts-tracker&project=Trunk qtcontacts-tracker]
|
|devel:people
|-
|[http://build.meego.com/package/show?package=qterminalmodeclient&project=Trunk qterminalmodeclient]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=qtgstreamer&project=Trunk qtgstreamer]
|tosantak
|
|-
|[http://build.meego.com/package/show?package=qttas-server&project=Trunk qttas-server]
|talahtel
|
|-
|[http://build.meego.com/package/show?package=qtwebkit&project=Trunk qtwebkit]
|boudra
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=quicksynergy&project=Trunk quicksynergy]
|
|
|-
|[http://build.meego.com/package/show?package=quillimagefilter&project=Trunk quillimagefilter]
|
|
|-
|[http://build.meego.com/package/show?package=quilt&project=Trunk quilt]
|
|
|-
|[http://build.meego.com/package/show?package=rar-kernel-headers&project=Trunk rar-kernel-headers]
|ulf
|
|-
|[http://build.meego.com/package/show?package=rarian&project=Trunk rarian]
|
|
|-
|[http://build.meego.com/package/show?package=rdsd&project=Trunk rdsd]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=rdsquery&project=Trunk rdsquery]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=readline&project=Trunk readline]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=recode&project=Trunk recode]
|
|
|-
|[http://build.meego.com/package/show?package=rest&project=Trunk rest]
|
|
|-
|[http://build.meego.com/package/show?package=rfkill&project=Trunk rfkill]
|erwanmahe
|
|-
|[http://build.meego.com/package/show?package=rhpl&project=Trunk rhpl]
|vivian
|
|-
|[http://build.meego.com/package/show?package=rhythmbox&project=Trunk rhythmbox]
|
|
|-
|[http://build.meego.com/package/show?package=rootfiles&project=Trunk rootfiles]
|
|
|-
|[http://build.meego.com/package/show?package=rpm&project=Trunk rpm]
|nashif,xiaoqiang
|devel:packagemanagement
|-
|[http://build.meego.com/package/show?package=rpm-build-x86&project=Trunk rpm-build-x86]
|austin
|
|-
|[http://build.meego.com/package/show?package=rpm-libs-x86&project=Trunk rpm-libs-x86]
|austin
|
|-
|[http://build.meego.com/package/show?package=rpm-python&project=Trunk rpm-python]
|nashif
|
|-
|[http://build.meego.com/package/show?package=rpm-x86&project=Trunk rpm-x86]
|austin
|
|-
|[http://build.meego.com/package/show?package=rpmcheck&project=Trunk rpmcheck]
|xiaoqiang
|
|-
|[http://build.meego.com/package/show?package=rpmdevtools&project=Trunk rpmdevtools]
|xiaoqiang
|
|-
|[http://build.meego.com/package/show?package=rpmlint&project=Trunk rpmlint]
|nashif
|
|-
|[http://build.meego.com/package/show?package=rpmlint-Moblin&project=Trunk rpmlint-Moblin]
|nashif
|
|-
|[http://build.meego.com/package/show?package=rpmlint-mini&project=Trunk rpmlint-mini]
|nashif
|
|-
|[http://build.meego.com/package/show?package=rpmlint-mini-x86&project=Trunk rpmlint-mini-x86]
|austin
|
|-
|[http://build.meego.com/package/show?package=rpmorphan&project=Trunk rpmorphan]
|xiaoqiang
|
|-
|[http://build.meego.com/package/show?package=rpmreaper&project=Trunk rpmreaper]
|xiaoqiang
|
|-
|[http://build.meego.com/package/show?package=rsync&project=Trunk rsync]
|
|
|-
|[http://build.meego.com/package/show?package=rsyslog&project=Trunk rsyslog]
|
|
|-
|[http://build.meego.com/package/show?package=rtkit&project=Trunk rtkit]
|yyang
|
|-
|[http://build.meego.com/package/show?package=ruby&project=Trunk ruby]
|jfding
|
|-
|[http://build.meego.com/package/show?package=rygel&project=Trunk rygel]
|tosantak
|
|-
|[http://build.meego.com/package/show?package=samba&project=Trunk samba]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=sample-media&project=Trunk sample-media]
|auke
|
|-
|[http://build.meego.com/package/show?package=sane-backends&project=Trunk sane-backends]
|
|
|-
|[http://build.meego.com/package/show?package=scim&project=Trunk scim]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=scim-anthy&project=Trunk scim-anthy]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=scim-bridge&project=Trunk scim-bridge]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=scim-chewing&project=Trunk scim-chewing]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=scim-hangul&project=Trunk scim-hangul]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=scim-m17n&project=Trunk scim-m17n]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=scim-panel-vkb-gtk&project=Trunk scim-panel-vkb-gtk]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=scim-pinyin&project=Trunk scim-pinyin]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=scim-skk&project=Trunk scim-skk]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=scons&project=Trunk scons]
|
|
|-
|[http://build.meego.com/package/show?package=screen&project=Trunk screen]
|
|
|-
|[http://build.meego.com/package/show?package=sed&project=Trunk sed]
|yanli
|
|-
|[http://build.meego.com/package/show?package=sed-x86&project=Trunk sed-x86]
|austin
|
|-
|[http://build.meego.com/package/show?package=sensorfw&project=Trunk sensorfw]
|mlehtonen
|devel:systemsw
|-
|[http://build.meego.com/package/show?package=setup&project=Trunk setup]
|
|
|-
|[http://build.meego.com/package/show?package=setuptool&project=Trunk setuptool]
|
|
|-
|[http://build.meego.com/package/show?package=sg3_utils&project=Trunk sg3_utils]
|
|
|-
|[http://build.meego.com/package/show?package=sgml-common&project=Trunk sgml-common]
|
|
|-
|[http://build.meego.com/package/show?package=shadow-utils&project=Trunk shadow-utils]
|qzhao9
|
|-
|[http://build.meego.com/package/show?package=shared-mime-info&project=Trunk shared-mime-info]
|vivian
|
|-
|[http://build.meego.com/package/show?package=sharutils&project=Trunk sharutils]
|yyang
|
|-
|[http://build.meego.com/package/show?package=signon-digest&project=Trunk signon-digest]
|pcapriotti
|
|-
|[http://build.meego.com/package/show?package=signon-oauth2&project=Trunk signon-oauth2]
|senko
|
|-
|[http://build.meego.com/package/show?package=simple-scan&project=Trunk simple-scan]
|
|
|-
|[http://build.meego.com/package/show?package=skkdic&project=Trunk skkdic]
|
|
|-
|[http://build.meego.com/package/show?package=slang&project=Trunk slang]
|
|
|-
|[http://build.meego.com/package/show?package=slib&project=Trunk slib]
|
|
|-
|[http://build.meego.com/package/show?package=smartmontools&project=Trunk smartmontools]
|
|
|-
|[http://build.meego.com/package/show?package=smem&project=Trunk smem]
|
|
|-
|[http://build.meego.com/package/show?package=smshistory&project=Trunk smshistory]
|krupert,ulf
|devel:ux:handset
|-
|[http://build.meego.com/package/show?package=sofia-sip&project=Trunk sofia-sip]
|
|
|-
|[http://build.meego.com/package/show?package=sound-theme-freedesktop&project=Trunk sound-theme-freedesktop]
|
|
|-
|[http://build.meego.com/package/show?package=soundtouch&project=Trunk soundtouch]
|
|
|-
|[http://build.meego.com/package/show?package=spectacle&project=Trunk spectacle]
|jfding
|devel:tools:building
|-
|[http://build.meego.com/package/show?package=speech-dispatcher&project=Trunk speech-dispatcher]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=speex&project=Trunk speex]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=sphinxbase&project=Trunk sphinxbase]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=sqlite&project=Trunk sqlite]
|yyang
|
|-
|[http://build.meego.com/package/show?package=sqlite-x86&project=Trunk sqlite-x86]
|austin
|
|-
|[http://build.meego.com/package/show?package=squashfs-tools&project=Trunk squashfs-tools]
|yyang
|
|-
|[http://build.meego.com/package/show?package=sreadahead&project=Trunk sreadahead]
|auke
|
|-
|[http://build.meego.com/package/show?package=ssmtp&project=Trunk ssmtp]
|
|
|-
|[http://build.meego.com/package/show?package=startup-notification&project=Trunk startup-notification]
|jfding
|
|-
|[http://build.meego.com/package/show?package=strace&project=Trunk strace]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=subversion&project=Trunk subversion]
|
|
|-
|[http://build.meego.com/package/show?package=sudo&project=Trunk sudo]
|yanli
|devel:base
|-
|[http://build.meego.com/package/show?package=swi-prolog&project=Trunk swi-prolog]
|mlehtonen
|devel:resourcepolicy
|-
|[http://build.meego.com/package/show?package=swig&project=Trunk swig]
|
|devel:base
|-
|[http://build.meego.com/package/show?package=syncevolution&project=Trunk syncevolution]
|pohly
|
|-
|[http://build.meego.com/package/show?package=syncevolution-gtk&project=Trunk syncevolution-gtk]
|pohly
|
|-
|[http://build.meego.com/package/show?package=synergy&project=Trunk synergy]
|
|
|-
|[http://build.meego.com/package/show?package=sysfsutils&project=Trunk sysfsutils]
|
|
|-
|[http://build.meego.com/package/show?package=sysklogd&project=Trunk sysklogd]
|
|
|-
|[http://build.meego.com/package/show?package=syslinux&project=Trunk syslinux]
|yyang
|
|-
|[http://build.meego.com/package/show?package=sysprof&project=Trunk sysprof]
|
|
|-
|[http://build.meego.com/package/show?package=system-config-boot&project=Trunk system-config-boot]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=system-config-date&project=Trunk system-config-date]
|vivian
|
|-
|[http://build.meego.com/package/show?package=system-config-date-docs&project=Trunk system-config-date-docs]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=system-config-language&project=Trunk system-config-language]
|
|
|-
|[http://build.meego.com/package/show?package=system-config-printer&project=Trunk system-config-printer]
|
|
|-
|[http://build.meego.com/package/show?package=system-config-users&project=Trunk system-config-users]
|
|
|-
|[http://build.meego.com/package/show?package=sysvinit&project=Trunk sysvinit]
|
|
|-
|[http://build.meego.com/package/show?package=t1lib&project=Trunk t1lib]
|
|
|-
|[http://build.meego.com/package/show?package=taglib&project=Trunk taglib]
|
|
|-
|[http://build.meego.com/package/show?package=taglib-sharp&project=Trunk taglib-sharp]
|abock
|
|-
|[http://build.meego.com/package/show?package=tar&project=Trunk tar]
|yanli
|
|-
|[http://build.meego.com/package/show?package=tar-x86&project=Trunk tar-x86]
|austin
|
|-
|[http://build.meego.com/package/show?package=tasks&project=Trunk tasks]
|
|
|-
|[http://build.meego.com/package/show?package=tcl&project=Trunk tcl]
|jfding
|
|-
|[http://build.meego.com/package/show?package=tcp_wrappers&project=Trunk tcp_wrappers]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=tcpdump&project=Trunk tcpdump]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=tcsh&project=Trunk tcsh]
|
|
|-
|[http://build.meego.com/package/show?package=teckit&project=Trunk teckit]
|
|
|-
|[http://build.meego.com/package/show?package=telepathy-butterfly&project=Trunk telepathy-butterfly]
|huaxu
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-farsight&project=Trunk telepathy-farsight]
|huaxu
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-filesystem&project=Trunk telepathy-filesystem]
|huaxu
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-gabble&project=Trunk telepathy-gabble]
|huaxu
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-glib&project=Trunk telepathy-glib]
|huaxu
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-haze&project=Trunk telepathy-haze]
|huaxu
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-idle&project=Trunk telepathy-idle]
|huaxu
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-logger&project=Trunk telepathy-logger]
|rbradford
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-mission-control&project=Trunk telepathy-mission-control]
|huaxu
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-qt4&project=Trunk telepathy-qt4]
|
|
|-
|[http://build.meego.com/package/show?package=telepathy-ring&project=Trunk telepathy-ring]
|bwachter
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-salut&project=Trunk telepathy-salut]
|huaxu
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-sofiasip&project=Trunk telepathy-sofiasip]
|bwachter
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-stream-engine&project=Trunk telepathy-stream-engine]
|senko
|
|-
|[http://build.meego.com/package/show?package=test-definition&project=Trunk test-definition]
|timoph,jokylanp
|
|-
|[http://build.meego.com/package/show?package=testrunner-lite&project=Trunk testrunner-lite]
|timoph,jokylanp
|
|-
|[http://build.meego.com/package/show?package=texi2html&project=Trunk texi2html]
|
|
|-
|[http://build.meego.com/package/show?package=texinfo&project=Trunk texinfo]
|
|
|-
|[http://build.meego.com/package/show?package=texlive&project=Trunk texlive]
|yanli
|
|-
|[http://build.meego.com/package/show?package=texlive-texmf&project=Trunk texlive-texmf]
|yanli
|
|-
|[http://build.meego.com/package/show?package=texlive-texmf-errata&project=Trunk texlive-texmf-errata]
|yanli
|
|-
|[http://build.meego.com/package/show?package=ti-uim&project=Trunk ti-uim]
|erwanmahe
|
|-
|[http://build.meego.com/package/show?package=tig&project=Trunk tig]
|
|
|-
|[http://build.meego.com/package/show?package=time&project=Trunk time]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=timed&project=Trunk timed]
|tapioran
|devel:systemsw
|-
|[http://build.meego.com/package/show?package=tinycdb&project=Trunk tinycdb]
|rusty
|
|-
|[http://build.meego.com/package/show?package=tix&project=Trunk tix]
|jfding
|
|-
|[http://build.meego.com/package/show?package=tk&project=Trunk tk]
|jfding
|
|-
|[http://build.meego.com/package/show?package=tmpwatch&project=Trunk tmpwatch]
|
|
|-
|[http://build.meego.com/package/show?package=tone-generator&project=Trunk tone-generator]
|
|
|-
|[http://build.meego.com/package/show?package=totem&project=Trunk totem]
|
|
|-
|[http://build.meego.com/package/show?package=totem-pl-parser&project=Trunk totem-pl-parser]
|
|devel:contentfw
|-
|[http://build.meego.com/package/show?package=tpm-tools&project=Trunk tpm-tools]
|
|
|-
|[http://build.meego.com/package/show?package=traceroute&project=Trunk traceroute]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=tracker&project=Trunk tracker]
|
|devel:contentfw
|-
|[http://build.meego.com/package/show?package=transfer-ui&project=Trunk transfer-ui]
|teemu.hukkanen
|
|-
|[http://build.meego.com/package/show?package=transifex-client&project=Trunk transifex-client]
|
|
|-
|[http://build.meego.com/package/show?package=transmission&project=Trunk transmission]
|
|
|-
|[http://build.meego.com/package/show?package=trousers&project=Trunk trousers]
|
|
|-
|[http://build.meego.com/package/show?package=tsc2007-config&project=Trunk tsc2007-config]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=ttmkfdir&project=Trunk ttmkfdir]
|
|
|-
|[http://build.meego.com/package/show?package=tumbler&project=Trunk tumbler]
|
|
|-
|[http://build.meego.com/package/show?package=twitter-glib&project=Trunk twitter-glib]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=tzdata&project=Trunk tzdata]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=u-boot&project=Trunk u-boot]
|nm
|
|-
|[http://build.meego.com/package/show?package=udev&project=Trunk udev]
|kai,zhongxin
|
|-
|[http://build.meego.com/package/show?package=udev-rules-handset-mid&project=Trunk udev-rules-handset-mid]
|
|
|-
|[http://build.meego.com/package/show?package=udev-rules-netbook&project=Trunk udev-rules-netbook]
|
|
|-
|[http://build.meego.com/package/show?package=udev-rules-nokia-n900&project=Trunk udev-rules-nokia-n900]
|cvm
|devel:devices:n900
|-
|[http://build.meego.com/package/show?package=udiskie&project=Trunk udiskie]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=udisks&project=Trunk udisks]
|vivian,yyin2,zhongxin
|
|-
|[http://build.meego.com/package/show?package=udisks-helper-extras&project=Trunk udisks-helper-extras]
|zhongxin
|
|-
|[http://build.meego.com/package/show?package=un-core-fonts&project=Trunk un-core-fonts]
|
|
|-
|[http://build.meego.com/package/show?package=unique&project=Trunk unique]
|
|
|-
|[http://build.meego.com/package/show?package=unzip&project=Trunk unzip]
|yyang
|
|-
|[http://build.meego.com/package/show?package=upower&project=Trunk upower]
|yyin2,zhongxin
|
|-
|[http://build.meego.com/package/show?package=urw-fonts&project=Trunk urw-fonts]
|
|
|-
|[http://build.meego.com/package/show?package=usb-modeswitch&project=Trunk usb-modeswitch]
|
|
|-
|[http://build.meego.com/package/show?package=usb-modeswitch-data&project=Trunk usb-modeswitch-data]
|
|
|-
|[http://build.meego.com/package/show?package=usbutils&project=Trunk usbutils]
|
|
|-
|[http://build.meego.com/package/show?package=usermode&project=Trunk usermode]
|
|
|-
|[http://build.meego.com/package/show?package=usleep&project=Trunk usleep]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=utfs&project=Trunk utfs]
|boudra
|devel:tools:sdk:target
|-
|[http://build.meego.com/package/show?package=uthash&project=Trunk uthash]
|rrware
|
|-
|[http://build.meego.com/package/show?package=util-linux-ng&project=Trunk util-linux-ng]
|yanli
|
|-
|[http://build.meego.com/package/show?package=uuid&project=Trunk uuid]
|
|
|-
|[http://build.meego.com/package/show?package=uxlaunch&project=Trunk uxlaunch]
|auke
|
|-
|[http://build.meego.com/package/show?package=v8&project=Trunk v8]
|
|devel:browser
|-
|[http://build.meego.com/package/show?package=vala&project=Trunk vala]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=valgrind&project=Trunk valgrind]
|qzhao9
|
|-
|[http://build.meego.com/package/show?package=vamp-plugin-sdk&project=Trunk vamp-plugin-sdk]
|
|
|-
|[http://build.meego.com/package/show?package=vibrant-icon-theme&project=Trunk vibrant-icon-theme]
|
|
|-
|[http://build.meego.com/package/show?package=vim&project=Trunk vim]
|
|
|-
|[http://build.meego.com/package/show?package=vlgothic-fonts&project=Trunk vlgothic-fonts]
|
|
|-
|[http://build.meego.com/package/show?package=voicecallhistory&project=Trunk voicecallhistory]
|krupert,ulf
|
|-
|[http://build.meego.com/package/show?package=vorbis-tools&project=Trunk vorbis-tools]
|
|
|-
|[http://build.meego.com/package/show?package=vpnc&project=Trunk vpnc]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=vte&project=Trunk vte]
|xiaoqiang
|
|-
|[http://build.meego.com/package/show?package=w3m&project=Trunk w3m]
|
|
|-
|[http://build.meego.com/package/show?package=webupload-engine&project=Trunk webupload-engine]
|teemu.hukkanen
|
|-
|[http://build.meego.com/package/show?package=wget&project=Trunk wget]
|jfding
|
|-
|[http://build.meego.com/package/show?package=wildmidi&project=Trunk wildmidi]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=wimax-tools&project=Trunk wimax-tools]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=wireless-regdb&project=Trunk wireless-regdb]
|cleech
|
|-
|[http://build.meego.com/package/show?package=wireless-tools&project=Trunk wireless-tools]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=wlanconfig&project=Trunk wlanconfig]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=wpa_supplicant&project=Trunk wpa_supplicant]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=wv&project=Trunk wv]
|
|
|-
|[http://build.meego.com/package/show?package=wxGTK&project=Trunk wxGTK]
|
|
|-
|[http://build.meego.com/package/show?package=wxPython&project=Trunk wxPython]
|quanxianwang
|
|-
|[http://build.meego.com/package/show?package=xbacklight&project=Trunk xbacklight]
|
|
|-
|[http://build.meego.com/package/show?package=xbindkeys&project=Trunk xbindkeys]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xcb-proto&project=Trunk xcb-proto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xcb-util&project=Trunk xcb-util]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xdg-user-dirs&project=Trunk xdg-user-dirs]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=xdg-user-dirs-gtk&project=Trunk xdg-user-dirs-gtk]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=xdg-utils&project=Trunk xdg-utils]
|xiaoqiang,quanxianwang,boudra
|
|-
|[http://build.meego.com/package/show?package=xdvipdfmx&project=Trunk xdvipdfmx]
|
|
|-
|[http://build.meego.com/package/show?package=xerces-c&project=Trunk xerces-c]
|
|
|-
|[http://build.meego.com/package/show?package=xhtml1-dtds&project=Trunk xhtml1-dtds]
|
|
|-
|[http://build.meego.com/package/show?package=xhtml2fo-style-xsl&project=Trunk xhtml2fo-style-xsl]
|
|
|-
|[http://build.meego.com/package/show?package=xinetd&project=Trunk xinetd]
|
|
|-
|[http://build.meego.com/package/show?package=xinput_calibrator&project=Trunk xinput_calibrator]
|
|
|-
|[http://build.meego.com/package/show?package=xkeyboard-config&project=Trunk xkeyboard-config]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xmlrpc-c&project=Trunk xmlrpc-c]
|
|
|-
|[http://build.meego.com/package/show?package=xmltex&project=Trunk xmltex]
|
|
|-
|[http://build.meego.com/package/show?package=xmlto&project=Trunk xmlto]
|jfding
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-apps&project=Trunk xorg-x11-apps]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-evdev&project=Trunk xorg-x11-drv-evdev]
|pli1
|devel:x11:Trunk
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-evtouch&project=Trunk xorg-x11-drv-evtouch]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-fbdev&project=Trunk xorg-x11-drv-fbdev]
|kad
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-intel&project=Trunk xorg-x11-drv-intel]
|pli1
|devel:x11:Trunk
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-joystick&project=Trunk xorg-x11-drv-joystick]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-keyboard&project=Trunk xorg-x11-drv-keyboard]
|
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-kvm&project=Trunk xorg-x11-drv-kvm]
|
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-mga&project=Trunk xorg-x11-drv-mga]
|
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-mouse&project=Trunk xorg-x11-drv-mouse]
|
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-mtev&project=Trunk xorg-x11-drv-mtev]
|
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-omapfb&project=Trunk xorg-x11-drv-omapfb]
|
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-synaptics&project=Trunk xorg-x11-drv-synaptics]
|yanli
|devel:x11:Trunk
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-vesa&project=Trunk xorg-x11-drv-vesa]
|
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-vmmouse&project=Trunk xorg-x11-drv-vmmouse]
|
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-vmware&project=Trunk xorg-x11-drv-vmware]
|
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-void&project=Trunk xorg-x11-drv-void]
|
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-wacom&project=Trunk xorg-x11-drv-wacom]
|
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-filesystem&project=Trunk xorg-x11-filesystem]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-font-utils&project=Trunk xorg-x11-font-utils]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-fonts&project=Trunk xorg-x11-fonts]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-meego-configs&project=Trunk xorg-x11-meego-configs]
|ulf
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-bigreqsproto&project=Trunk xorg-x11-proto-bigreqsproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-compositeproto&project=Trunk xorg-x11-proto-compositeproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-damageproto&project=Trunk xorg-x11-proto-damageproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-dmxproto&project=Trunk xorg-x11-proto-dmxproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-dri2proto&project=Trunk xorg-x11-proto-dri2proto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-evieext&project=Trunk xorg-x11-proto-evieext]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-fixesproto&project=Trunk xorg-x11-proto-fixesproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-fontcacheproto&project=Trunk xorg-x11-proto-fontcacheproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-fontsproto&project=Trunk xorg-x11-proto-fontsproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-glproto&project=Trunk xorg-x11-proto-glproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-inputproto&project=Trunk xorg-x11-proto-inputproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-kbproto&project=Trunk xorg-x11-proto-kbproto]
|
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-randrproto&project=Trunk xorg-x11-proto-randrproto]
|
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-recordproto&project=Trunk xorg-x11-proto-recordproto]
|
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-renderproto&project=Trunk xorg-x11-proto-renderproto]
|
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-resourceproto&project=Trunk xorg-x11-proto-resourceproto]
|
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-scrnsaverproto&project=Trunk xorg-x11-proto-scrnsaverproto]
|
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-trapproto&project=Trunk xorg-x11-proto-trapproto]
|
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-videoproto&project=Trunk xorg-x11-proto-videoproto]
|
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-xcmiscproto&project=Trunk xorg-x11-proto-xcmiscproto]
|
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-xextproto&project=Trunk xorg-x11-proto-xextproto]
|
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-xf86bigfontproto&project=Trunk xorg-x11-proto-xf86bigfontproto]
|
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-xf86dgaproto&project=Trunk xorg-x11-proto-xf86dgaproto]
|
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-xf86driproto&project=Trunk xorg-x11-proto-xf86driproto]
|
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-xf86miscproto&project=Trunk xorg-x11-proto-xf86miscproto]
|
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-xf86rushproto&project=Trunk xorg-x11-proto-xf86rushproto]
|
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-xf86vidmodeproto&project=Trunk xorg-x11-proto-xf86vidmodeproto]
|
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-xineramaproto&project=Trunk xorg-x11-proto-xineramaproto]
|
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-xproto&project=Trunk xorg-x11-proto-xproto]
|
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-xproxymanagementprotocol&project=Trunk xorg-x11-proto-xproxymanagementprotocol]
|
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-server&project=Trunk xorg-x11-server]
|pli1
|devel:x11:Trunk
|-
|[http://build.meego.com/package/show?package=xorg-x11-server-utils&project=Trunk xorg-x11-server-utils]
|
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-twm&project=Trunk xorg-x11-twm]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-util-macros&project=Trunk xorg-x11-util-macros]
|pli1,xyl
|devel:x11:Trunk
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils&project=Trunk xorg-x11-utils]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-iceauth&project=Trunk xorg-x11-utils-iceauth]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-rgb&project=Trunk xorg-x11-utils-rgb]
|
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-sessreg&project=Trunk xorg-x11-utils-sessreg]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xcmsdb&project=Trunk xorg-x11-utils-xcmsdb]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xdpyinfo&project=Trunk xorg-x11-utils-xdpyinfo]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xdriinfo&project=Trunk xorg-x11-utils-xdriinfo]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xev&project=Trunk xorg-x11-utils-xev]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xfd&project=Trunk xorg-x11-utils-xfd]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xfontsel&project=Trunk xorg-x11-utils-xfontsel]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xgamma&project=Trunk xorg-x11-utils-xgamma]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xhost&project=Trunk xorg-x11-utils-xhost]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xinput&project=Trunk xorg-x11-utils-xinput]
|
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xlsatoms&project=Trunk xorg-x11-utils-xlsatoms]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xlsclients&project=Trunk xorg-x11-utils-xlsclients]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xlsfonts&project=Trunk xorg-x11-utils-xlsfonts]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xmodmap&project=Trunk xorg-x11-utils-xmodmap]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xprop&project=Trunk xorg-x11-utils-xprop]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xrandr&project=Trunk xorg-x11-utils-xrandr]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xrdb&project=Trunk xorg-x11-utils-xrdb]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xrefresh&project=Trunk xorg-x11-utils-xrefresh]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xset&project=Trunk xorg-x11-utils-xset]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xsetroot&project=Trunk xorg-x11-utils-xsetroot]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xvinfo&project=Trunk xorg-x11-utils-xvinfo]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xwininfo&project=Trunk xorg-x11-utils-xwininfo]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-xauth&project=Trunk xorg-x11-xauth]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-xbitmaps&project=Trunk xorg-x11-xbitmaps]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-xinit&project=Trunk xorg-x11-xinit]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-xkb-utils&project=Trunk xorg-x11-xkb-utils]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-xtrans-devel&project=Trunk xorg-x11-xtrans-devel]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xterm&project=Trunk xterm]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xz&project=Trunk xz]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=xz-libs-x86&project=Trunk xz-libs-x86]
|austin
|
|-
|[http://build.meego.com/package/show?package=yasm&project=Trunk yasm]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=yelp&project=Trunk yelp]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=yum&project=Trunk yum]
|xiaoqiang
|devel:packagemanagement
|-
|[http://build.meego.com/package/show?package=yum-metadata-parser&project=Trunk yum-metadata-parser]
|
|
|-
|[http://build.meego.com/package/show?package=yum-utils&project=Trunk yum-utils]
|xiaoqiang
|devel:packagemanagement
|-
|[http://build.meego.com/package/show?package=zenity&project=Trunk zenity]
|
|
|-
|[http://build.meego.com/package/show?package=zile&project=Trunk zile]
|
|
|-
|[http://build.meego.com/package/show?package=zip&project=Trunk zip]
|yyang,xiaoqiang
|
|-
|[http://build.meego.com/package/show?package=zlib&project=Trunk zlib]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=zlib-x86&project=Trunk zlib-x86]
|jsmoeller
|devel:base
|-
|[http://build.meego.com/package/show?package=zsh&project=Trunk zsh]
|nashif
|
|-
|[http://build.meego.com/package/show?package=zypper&project=Trunk zypper]
|xiaoqiang
|devel:packagemanagement
|-
|}

In-vehicle/Roadmap

2011-01-21T22:33:20Z

Joel:

= Roadmap for MeeGo In-Vehicle Infotainment =
== High-level Roadmap ==
Items on the near-term roadmap:
* App Store Demonstration
* Automotive Networking
* Audio management
* Device connectivity
* Navigation
* Auto UX
* BSP/ARM-support

== Feature list from Bugzilla ==

{| border="1"
|-
! Bugzilla ID
! Title
! URL
|-
| 7668
| [FEA] Multi Screen Support
| http://bugs.meego.com/show_bug.cgi?id=7668
|-
| 7669
| [FEA] Tethered Device Indexing
| http://bugs.meego.com/show_bug.cgi?id=7669
|-
| 7670
| [FEA] Multi Zone Audio
| http://bugs.meego.com/show_bug.cgi?id=7670
|-
| 7671
| [FEA] Distributed Audio Management
| http://bugs.meego.com/show_bug.cgi?id=7671
|-
| 7672
| [FEA] Network Gateway
| http://bugs.meego.com/show_bug.cgi?id=7672
|-
| 7674
| [FEA] Phonebook Sync with CE Device
| http://bugs.meego.com/show_bug.cgi?id=7674
|-
| 7675
| [FEA] Media Sync with home PC
| http://bugs.meego.com/show_bug.cgi?id=7675
|-
| 7677
| [FEA] Multi-User Support
| http://bugs.meego.com/show_bug.cgi?id=7677
|-
| 7678
| [FEA] IVI Fastboot
| | http://bugs.meego.com/show_bug.cgi?id=7678
|-
| 7679
| [FEA] Persistency Management
| | http://bugs.meego.com/show_bug.cgi?id=7679
|-
| 7680
| [FEA] Power Management
| | http://bugs.meego.com/show_bug.cgi?id=7680
|-
| 7681
| [FEA] System Health Monitor
| http://bugs.meego.com/show_bug.cgi?id=7681
|-
| 7682
| [FEA] Inertia based Application control
| http://bugs.meego.com/show_bug.cgi?id=7682
|-
| 8704
| [FEA] Smartphone Connectivity using Terminal Mode for MeeGo IVI
| http://bugs.meego.com/show_bug.cgi?id=8704
|-
| 8813
| [FEA] Terminal Mode VNC Client
| http://bugs.meego.com/show_bug.cgi?id=8813
|-
| 8814
| [FEA] Remote Framebuffer Protocol
| http://bugs.meego.com/show_bug.cgi?id=8814
|-
| 8815
| [FEA] Integrate EMGD 1.0 Update user mode driver components
| http://bugs.meego.com/show_bug.cgi?id=8815
|-
| 8816
| [FEA] RFB Encodings
| http://bugs.meego.com/show_bug.cgi?id=8816
|-
| 8817
| [FEA] Terminal Mode 1.0 RFB extension messages
| http://bugs.meego.com/show_bug.cgi?id=8817
|-
| 8818
| [FEA] Terminal Mode UpnP Control Point
| http://bugs.meego.com/show_bug.cgi?id=8818
|-
| 8819
| [FEA] IVI document viewer
| http://bugs.meego.com/show_bug.cgi?id=8819
|-
| 8821
| [FEA] TmServerDevice:1 Device
| http://bugs.meego.com/show_bug.cgi?id=8821
|-
| 8822
| [FEA] IVI Nobody
| http://bugs.meego.com/show_bug.cgi?id=8822
|-
| 8823
| [FEA] Terminal Mode Audio
| http://bugs.meego.com/show_bug.cgi?id=8823
|-
| 8824
| [FEA] IVI Proximity
| http://bugs.meego.com/show_bug.cgi?id=8824
|-
| 8827
| [FEA] IVI Persistancy Control Manager
| http://bugs.meego.com/show_bug.cgi?id=8827
|-
| 8828
| [FEA] RTP Client supporting Terminal Mode payload
| http://bugs.meego.com/show_bug.cgi?id=8828
|-
| 8829
| [FEA] Terminal Mode Client Controller
| http://bugs.meego.com/show_bug.cgi?id=8829
|-
| 9169
| [FEA] Contacts should have routing integration
| http://bugs.meego.com/show_bug.cgi?id=9169
|-
| 9171
| [FEA] Weather app
| http://bugs.meego.com/show_bug.cgi?id=9171
|-
| 9174
| [FEA] Media player: FM/AM radio
| http://bugs.meego.com/show_bug.cgi?id=9174
|-
| 9175
| [FEA] MCP pluggable mass storage controls
| http://bugs.meego.com/show_bug.cgi?id=9175
|-
| 9209
| [FEA] btrfs compression during installation
| http://bugs.meego.com/show_bug.cgi?id=9209
|-
| 9210
| [FEA] Remove physical keyboard requirement
| http://bugs.meego.com/show_bug.cgi?id=9210
|-
| 9211
| [FEA] Enhance meego-handset-songs to a classed audio sources
| http://bugs.meego.com/show_bug.cgi?id=9211
|-
| 9212
| [FEA] Sample Sirius radio integration
| http://bugs.meego.com/show_bug.cgi?id=9212
|-
| 9213
| [FEA] Rebase Russellville tsc2007 touchscreen to evdev
| http://bugs.meego.com/show_bug.cgi?id=9213
|-
| 10295
| [FEA] Request for Bluetooth DUN support for both server and client role
| http://bugs.meego.com/show_bug.cgi?id=10295
|-
| 10355
| [FEA] UI should include a day/night mode
| http://bugs.meego.com/show_bug.cgi?id=10355
|-
| 11256
| [FEA] Over-the-Air (OTA) Updates
| http://bugs.meego.com/show_bug.cgi?id=11256
|-
| pending
| [FEA-IVI-UX] Align IVI Home Screen with MeeGo Touch direction
| pending
|-
| pending
| [FEA-IVI-UX] Unified Media Player
| pending
|-
| pending
| [FEA-IVI-UX] Unified Dialler
| pending
|-
| pending
| [FEA-IVI-UX] Navigation
| pending
|-
| pending
| [FEA-IVI-UX] Document Viewer
| pending
|-
| pending
| [FEA-IVI-UX] Picture Viewer
| pending
|-
| pending
|[FEA-IVI-UX] Speech recognition
| pending
|}

== MeeGo 1.2 Target Features ==
The MeeGo 1.2 development milestones are:
* November 1, 2010 MeeGo 1.2 merge window open
* January 20, 2011 MeeGo 1.2 Feature freeze (Alpha finish, Beta start)
* March 20, 2011 MeeGo 1.2 Code Freeze (Beta finish, Release Candidate start)
* April 27, 2011 MeeGo 1.2 Release

The new features planned for the MeeGo IVI 1.2 release are:
* Terminal Mode from Nokia [http://bugs.meego.com/show_bug.cgi?id=8704 Feature 8704]
* Integration of EMGD graphics [http://bugs.meego.com/show_bug.cgi?id=6863 Feature 6863] [http://bugs.meego.com/show_bug.cgi?id=8815 Feature 8815]
* Integration of TopCliff/Crown Bay drivers [http://bugs.meego.com/show_bug.cgi?id=6862 Feature 6862]
* Integration of Northville/ML7213/OKI IVI IOH drivers [http://bugs.meego.com/show_bug.cgi?id=12050 Feature 12050]
* Integration of Northville/ST ConneXt drivers [http://bugs.meego.com/show_bug.cgi?id=6865 Feature 6865]
* Updating IVI Home screen with new layout of taskbar and porting from QT to QML.
* Updating sample apps (browser, contacts, video player, photo player, music player, settings) from MeeGo Touch Framework based (MTF) to QML based.

In-vehicle

2011-01-21T22:12:48Z

Joel:

Main Page

2011-01-07T21:26:15Z

Joel: /* MeeGo Project Functions */

= Structure and Governance =

MeeGo is an open source project led by the MeeGo Technical Steering Group (TSG). The governance model is based on meritocracy and the best practices and values of the Open Source culture. The MeeGo project lives under the auspices of the Linux Foundation.

* [http://meego.com/about/governance MeeGo Project Structure and Governance Overview]

Anyone can attend the bi-weekly [[Technical Steering Group meetings]] to learn more about the decisions being made in the MeeGo project.

== MeeGo Project Functions ==
* [[Community Office]]
* [[Localization team|Localization]]
* [http://meego.com/about/governance/program-office Program Office]
* [[Architecture | Architecture]]
* [[Core_OS_Program | Core OS Program]]
* [[Handset_Program | Handset UX Program]]
* [[In-vehicle | In Vehicle Infotainment - IVI]]
* [[Quality]]
* [[Release_Engineering|Release Engineering]]
* [http://meego.com/about/governance/ui-design User Interface Design]
* [[SDK]]
* [[Architecture]]

= User =

* [[MeeGo Netbook FAQ]]
* [http://meego.com/devices/netbook/installing-meego-your-netbook Install MeeGo on your netbook]
* [[Devices|Supported devices]]

= Developer =
== Developer Guide ==

* [[SDK/Docs/1.1|Developer Guide for MeeGo 1.1]]
* [[SDK/Docs/1.0|Developer Guide for MeeGo 1.0]]
* [[Build_Infrastructure | Build Infrastructure]]
* [[MeeGo Porting Guide]]
* [[QML tutorials]] - Some tutorials to help get started with QML, the Qt Modelling Language.

Other documents:
{| border="1"
! Document
! Variety (Version)
! Architectures
|-
|Instructions for [[ARM|ARM based devices (N900, N8x0, Beagleboard, MSM/QSD, QEMU, Tegra 2)]]
|All
|ARM
|-
|Instructions for [[MeeGo_1.0_Netbook_VirtualBox|VirtualBox]]
|Netbook (1.0)
|Intel
|-
|Instructions for [[MeeGo SDK on Windows with VirtualBox]]
|All
|All
|-
|Tips for [[Developing With The Aava]]
|Handset/Aava
|Intel
|}

== Release Process ==
The MeeGo Release Process includes:
* [[Release_Engineering/Process|Release process and work flow]]
* [[Release_Engineering/Release_Timeline|MeeGo releases every 6 months]]
* [[Release_Engineering/Process|Nightly builds for developers and weekly releases will be available]]

= Community =

== Contributing to MeeGo ==
* Read our [[Community guidelines]]: [[Wiki contribution guidelines|Wiki]], [[Mailing list guidelines|mailing list]], [[Forum/Guidelines|forum]], and [[Community guidelines|more]].
* [[Community communication|Participate in our forums, mailing lists, and more]].
* [http://meego.com/about/contribution-guidelines Contribute to MeeGo].
* [[Build_Infrastructure/Community_Builder|Building applications]] for MeeGo

See also [[Who's who]].

== Meetings ==

[[MeeGo-Meeting IRC Schedule]]

The following groups have regular meetings, see their respective pages for details.

* [[Technical Steering Group meetings]]
* [[http://wiki.meego.com/Community_Office/Meetings|Community Office meetings]]
* [[Localization team]]

Regional Activities.
* [[Local MeeGo Networks]]

== Bi-Annual MeeGo Conference ==

=== Fall 2010 ===
The [http://conference2010.meego.com/ MeeGo Conference 2010] was held at Aviva Stadium in Dublin, Ireland, November 15-17th, 2010.
* Videos, presentation materials and other information can be found on the [http://conference2010.meego.com/ MeeGo Conference 2010 page].
* Links to blog posts, pictures and other event information are on the [[MeeGo_Conference_2010]] wiki page.

=== Spring 2011 ===
Planning has started for the [[MeeGo Conference Spring 2011|Spring 2011]]

The Conference will be held May 23-25 at the Hyatt Regency, San Francisco. This is the Hyatt on the Embarcadero, call for proposals, registration and planning details will be posted early January.

=== Fall 2011 ===
Venue selection for the November Conference will begin soon, venue requirements will be posted and suggestions on venues after requirements posted is encouraged!

== Resources ==
* [[MeeGo FAQ]]
* [[Glossary|Glossary and Acronyms]]
* [[Community guidelines]]
* [[Special:PopularPages|Popular Wiki Pages]]
* [[Special:MostLinkedPages|Most Linked-to Pages]]

[[Category:Top level]]

In-vehicle/IVI topic areas

2010-12-18T20:35:19Z

Joel: /* References */

= IVI Topic Areas =

== Automotive Audio Management ==

At a course grain level, we will have up to 7.2 speakers. In conjunction with this, we have to cater for dedicated audio jacks on for instance front and rear arm rests. We add to this complexity with the need to integrate BT head sets.
In terms of input, we can have a number of Mics for the obvious need, but also to support advanced echo cancelation - take the scenario of a cabrio from rest to 180mk/hr and the wind break noise, we need to get to a scenario where one could take a hands free call with minimum interference.

If we can picture the deployment scenario of the multitude of channels from above, then we extend this with the concept of zones. Zones are roughly equivalent to passengers. As such we need a policy control framework for controlling dynamic management of these zones. For instance, ramping down radio for incoming HFP call and the inverse when the call terminates.

In general, this area can be broken up into two coarse grained areas; audio processing itself and audio policy management.

In terms of processing, we need to cater for a DSP view of the world and an optimized opcode view of the world. In today's deployment, a multitude of filters will be applied to the channels to improve sound quality and reduce cost, for example where one wants to use cheaper speakers. We have to cater for a variety of audio re-sampling scenarios. Build in echo cancelation etc...

From a policy management perspective, we need a flexible framework to handle needs for ramping, corking, and mixing. So, along with the HFP mentioned above, we need to cater for all those gongs and bells you experience today when you fail to belt-up, lights on with door open etc...

From a MeeGo Architecture perspective, we have today PulseAudio as our server, Alsa underneath, Gstreamer from a framework perspective, and from a policy perspective we have a very interesting addition with the Policy Framework: http://conference2010.meego.com/session/policy-framework-flexible-way-orchestrate-multiple-functionalities-meego-devices
So, pulseAudio, Gstreamer and Policy framework experts would be greatly appreciated.

=== Use Cases ===

Use Cases will be broken out into this section to give a clear overview of what Automotive Audio Management requires.

[[File:AudioControl.gif]]

Add Brief Description of Audio Control - Very simply usescases, just sat in front of my car radio and identified these.

[[File:AudioProcessing.gif]]

Add description for Automotive Audio processing.
One of the key areas to cover here is Audio Policy control - i.e. mixing, ramping down radio when inbound hands free

== Design ==

Highlight the key components here - for example, PA, GST, Policy Framework, ALSA - and show the interations for the architecturally signification use cases
Sequence diagrams and component diagrams to go in this section - focus on IVI, highlight the deficiencies and potential required patches etc..

== Open Question ==

Where is IIR and/or FIR filtering best handled - GStreamer or Pulse?
GStreamer has some implementations, is that the most appropriate place?

== References ==
[http://wiki.meego.com/images/Meego-policy-framework-developer-guide.pdf MeeGo Policy Framework Developer Guide ]