MeeGo wiki - User contributions [en]

How to integrate osc (OBS API communication) in a python code

2011-08-08T18:57:33Z

Jeremiah: Minor spelling changes

When complexity creeps up, a ''simple'' Bash script can quickly become a very complex, unmaintainable piece of code.

Integrating the osc command into a Python script is an easy alternative to Bash when automating fairly complex tasks.
It's very easy to integrate osc in your own python code.

You need to import 2 Packages.</code>

*'''from osc import conf'''
*'''from osc import core'''

conf: Allow the access to the osc's configuration.[[http://wiki.meego.com/Osc.conf]]

core: Provide Functions to communicate with the OBS API.[[http://wiki.meego.com/Osc.core]]

Here, a simple example.

#!/usr/bin/python
# Authors Ronan Le Martret (Intel OTC)
# ronan@fridu.net
# Date 8 Aug 2011
# License GLPv2

# This Python script
# list of the packages of a project,
# get the status, and so, if the status is "failed", rebuild the package.</code>

from osc import conf
from osc import core
from xml.etree import ElementTree

if __name__ == '__main__':
apiurl="http://obsserver:81"
prj="MeeGo:1.2.0:oss"
repos="standard"
arch="i586"

#init the osc's configuration.
aConf=conf.get_config()

# Use directly the core fonction.
list_package=core.meta_get_packagelist(apiurl, prj)

for package in list_package:
url=apiurl+"/build/"+prj+"/"+repos+"/"+arch+"/"+package+"/_status"

# You can also use directly the obs API directly.
aElement=ElementTree.fromstring(core.http_request("GET", url).read())
code=aElement.attrib["code"]
print "code",code,
if code=="failed":
print "rebuild"
core.rebuild(apiurl, prj, package, repos, arch)
else:
print
--Ronan Le Martret Intel OpenSource Technology Centre 12:46, 8 August 2011 (UTC)

Quality/Compliance/IVIProfile

2011-05-12T09:52:12Z

Jeremiah: /* Handset Profile Packages */

Quality/Compliance/IVIProfile

2011-05-12T09:51:50Z

Jeremiah: /* ABI and API */

This page holds the compliance profile for MeeGo IVI. The IV compliance profile builds upon and extends the MeeGo Core compliance.

= MeeGo IVI Profile Specification =
== Hardware Requirements ==
'''ATOM Russelville or later (with SSSE3)'''

The Low Power Intel® In-Vehicle Infotainment Reference Design is a 1-DIN form factor board featuring the Intel® AtomTM processor and the Intel® System Controller Hub US15W chipset. The reference design contains various interfaces required to build an in-vehicle head unit including MOST, Video Input, SDHC Mass Storage support, Radio Tuner, and Ethernet.

The reference design consists of three distinct board modules:

A carrier board containing the FPGA codenamed Timberdale
An Automotive System Controller Board (ASCB)
A congatec* processor module, which is attached via a Type II COM Express connection
The congatec* module contains an Intel® AtomTM-based system (comprised of Intel® AtomTM CPU + Intel® SCH + 1GB DDR2 memory). The Automotive System Controller Board (ASCB) was developed to address basic power management of the Low Power Intel® IVI Reference Design system. Users of the system can add software to this micro-controller that is specific to their use cases/applications.

'''OMAP 3530 ARM Cortex A8'''

The ARM reference platform is the Beagle Board, specifically Revision xM. You can get more information on the Beagle Board web site.

== Package Management ==
None listed at this time

== ABI and API ==

More information coming shortly.

== Other Requirements ==
None listed at this time

== Handset Profile Packages ==
The MeeGo Handset Profile adds these additional packages beyond those required for MeeGo Core compliance:

{| class="prettytable"
| '''Source Package'''
| '''Version'''
| Type
| '''Binary Packages'''

|-
| '''libmeegotouch'''
|
| core
| '''libmeegotouch'''

|-
| '''meegotouch-applauncherd'''
|
| core
| '''meegotouch-applauncherd'''

|-
| '''meegotouch-applifed'''
|
| core
| '''meegotouch-applifed'''

|-
| '''meegotouch-controlpanel'''
|
| core
| '''meegotouch-controlpanel'''

|-
| '''meegotouch-feedback'''
|
| core
| '''meegotouch-feedback'''

|-
| '''meegotouch-feedbackreactionmaps'''
|
| core
| '''meegotouch-feedbackreactionmaps'''

|-
| '''meegotouch-inputmethodengine'''
|
| core
| '''meegotouch-inputmethodengine'''

|-
| '''meegotouch-inputmethodframework'''
|
| core
| '''meegotouch-inputmethodframework'''

|-
| '''meegotouch-theme'''
|
| dep
| '''meegotouch-theme'''

|}

Quality/Compliance/IVIProfile

2011-05-12T09:51:21Z

Jeremiah: /* Hardware Requirements */

This page holds the compliance profile for MeeGo IVI. The IV compliance profile builds upon and extends the MeeGo Core compliance.

= MeeGo IVI Profile Specification =
== Hardware Requirements ==
'''ATOM Russelville or later (with SSSE3)'''

The Low Power Intel® In-Vehicle Infotainment Reference Design is a 1-DIN form factor board featuring the Intel® AtomTM processor and the Intel® System Controller Hub US15W chipset. The reference design contains various interfaces required to build an in-vehicle head unit including MOST, Video Input, SDHC Mass Storage support, Radio Tuner, and Ethernet.

The reference design consists of three distinct board modules:

A carrier board containing the FPGA codenamed Timberdale
An Automotive System Controller Board (ASCB)
A congatec* processor module, which is attached via a Type II COM Express connection
The congatec* module contains an Intel® AtomTM-based system (comprised of Intel® AtomTM CPU + Intel® SCH + 1GB DDR2 memory). The Automotive System Controller Board (ASCB) was developed to address basic power management of the Low Power Intel® IVI Reference Design system. Users of the system can add software to this micro-controller that is specific to their use cases/applications.

'''OMAP 3530 ARM Cortex A8'''

The ARM reference platform is the Beagle Board, specifically Revision xM. You can get more information on the Beagle Board web site.

== Package Management ==
None listed at this time

== ABI and API ==
The MeeGo Handset Profile extends the Platform API with the following components:

* MeeGo Touch Framework (TBD: version)

== Other Requirements ==
None listed at this time

== Handset Profile Packages ==
The MeeGo Handset Profile adds these additional packages beyond those required for MeeGo Core compliance:

{| class="prettytable"
| '''Source Package'''
| '''Version'''
| Type
| '''Binary Packages'''

|-
| '''libmeegotouch'''
|
| core
| '''libmeegotouch'''

|-
| '''meegotouch-applauncherd'''
|
| core
| '''meegotouch-applauncherd'''

|-
| '''meegotouch-applifed'''
|
| core
| '''meegotouch-applifed'''

|-
| '''meegotouch-controlpanel'''
|
| core
| '''meegotouch-controlpanel'''

|-
| '''meegotouch-feedback'''
|
| core
| '''meegotouch-feedback'''

|-
| '''meegotouch-feedbackreactionmaps'''
|
| core
| '''meegotouch-feedbackreactionmaps'''

|-
| '''meegotouch-inputmethodengine'''
|
| core
| '''meegotouch-inputmethodengine'''

|-
| '''meegotouch-inputmethodframework'''
|
| core
| '''meegotouch-inputmethodframework'''

|-
| '''meegotouch-theme'''
|
| dep
| '''meegotouch-theme'''

|}

Quality/Compliance/IVIProfile

2011-05-12T09:49:26Z

Jeremiah:

This page holds the compliance profile for MeeGo IVI. The IV compliance profile builds upon and extends the MeeGo Core compliance.

= MeeGo IVI Profile Specification =
== Hardware Requirements ==
'''ATOM Russelville or later (with SSSE3)'''

The Low Power Intel® In-Vehicle Infotainment Reference Design is a 1-DIN form factor board featuring the Intel® AtomTM processor and the Intel® System Controller Hub US15W chipset. The reference design contains various interfaces required to build an in-vehicle head unit including MOST, Video Input, SDHC Mass Storage support, Radio Tuner, and Ethernet.

The reference design consists of three distinct board modules:

A carrier board containing the FPGA codenamed Timberdale
An Automotive System Controller Board (ASCB)
A congatec* processor module, which is attached via a Type II COM Express connection
The congatec* module contains an Intel® AtomTM-based system (comprised of Intel® AtomTM CPU + Intel® SCH + 1GB DDR2 memory). The Automotive System Controller Board (ASCB) was developed to address basic power management of the Low Power Intel® IVI Reference Design system. Users of the system can add software to this micro-controller that is specific to their use cases/applications.

== Package Management ==
None listed at this time

== ABI and API ==
The MeeGo Handset Profile extends the Platform API with the following components:

* MeeGo Touch Framework (TBD: version)

== Other Requirements ==
None listed at this time

== Handset Profile Packages ==
The MeeGo Handset Profile adds these additional packages beyond those required for MeeGo Core compliance:

{| class="prettytable"
| '''Source Package'''
| '''Version'''
| Type
| '''Binary Packages'''

|-
| '''libmeegotouch'''
|
| core
| '''libmeegotouch'''

|-
| '''meegotouch-applauncherd'''
|
| core
| '''meegotouch-applauncherd'''

|-
| '''meegotouch-applifed'''
|
| core
| '''meegotouch-applifed'''

|-
| '''meegotouch-controlpanel'''
|
| core
| '''meegotouch-controlpanel'''

|-
| '''meegotouch-feedback'''
|
| core
| '''meegotouch-feedback'''

|-
| '''meegotouch-feedbackreactionmaps'''
|
| core
| '''meegotouch-feedbackreactionmaps'''

|-
| '''meegotouch-inputmethodengine'''
|
| core
| '''meegotouch-inputmethodengine'''

|-
| '''meegotouch-inputmethodframework'''
|
| core
| '''meegotouch-inputmethodframework'''

|-
| '''meegotouch-theme'''
|
| dep
| '''meegotouch-theme'''

|}

Quality/Compliance/IVIProfile

2011-05-12T09:41:18Z

Jeremiah: Created page with "This page holds the compliance profile for MeeGo IVI."

This page holds the compliance profile for MeeGo IVI.

Quality/Compliance

2011-05-12T09:40:53Z

Jeremiah: /* Specification */

= MeeGo Compliance =

The MeeGo compliance program is designed to make sure things stay compatible, such that the devices supporting a particular MeeGo version can run the same software, and so that app developers know how to build software which will run across the family. Simply put, we want to make it possible for an application developer to write a MeeGo compliant application once and run it on any MeeGo compliant device.

MeeGo compliance addresses two categories of compliance: MeeGo compliant applications and MeeGo compliant devices / software products (which will be referred to simply as "devices"). In both cases, the use of the MeeGo brand will be granted based on being compliant. Following is an overview of the approach for each of these categories.

==MeeGo Compliant Device Overview==

For MeeGo compliant devices, we're taking a stack-based compliance approach, meaning that all MeeGo devices must use the same core software stack. Referring to the MeeGo architecture diagram, this core software stack is the MeeGo OS base layer plus the MeeGo OS Middleware layer.

In addition to a sharing the same core software stack, MeeGo compliance will have profiles for each device category (Netbook, Handset, and so on). A profile specifies additional required components for the profile (e.g. providing device category APIs), minimum hardware requirements and minimum hardware component requirements (such as cellular modem in the handset profile).

It's important to note that the device profiles won't require the inclusion of a complete user experience - but rather the UI framework providing core user interaction and APIs.

A MeeGo compliant device would be compliant to the MeeGo core software stack definition and one (or more) device category profiles.

==MeeGo Compliant Application Overview==

Given that definition of compliance for devices / software products, MeeGo compliance for applications will verify that an application's external dependencies are satisfied by a MeeGo compliant device (in other words, that any libraries or other dependencies of the application are provided within the core software stack and target device profile)

An application can be written to be dependent only on the MeeGo core software stack - in which case it would run on any MeeGo compliant device. However, applications with UI would typically target a specific device profile - so for example an application could be MeeGo Handset Compliant - meaning that it would run on any device compliant with the MeeGo Handset profile.

==More Detail on Stack Based Compliance==

Stack-based compliance means that a compliant device / software product must use the MeeGo package set without re-packaging - including the MeeGo version of RPM and the MeeGo package names.

Compliance requires the use of the MeeGo source packages for required components, and that any applied patches (e.g. to fix bugs found in the field) must not effect API, ABI, or defined functionality of interfaces.

Additional packages (beyond those required by compliance) may be added as long as they don't override MeeGo packages or provide functions with the same namespace of MeeGo APIs. Of course there will also be additional packages and components required to adapt MeeGo to run on a specific hardware platform (we call this "Hardware Adaptation Software" in MeeGo) - the compliance specification will call out any specific packages or components that may vary based on hardware capabilities.

Some details on how this is implemented can be seen at [[Quality/Compliance_Implementation|Compliance_Implementaion]].

A core part of the program is the Compliance Specification, which describes the rules and requirements for complying. There's more to the program (trademark licensing, application process, etc.) which will be added later.

== Specification ==

The specification is intended to match up with MeeGo releases, so it uses a similar numbering scheme. Completed specifications are approved by the TSG. The current approved version is [http://wiki.meego.com/images/MeeGo-Compliance-Spec-1.1.0.0.pdf Spec 1.1]

Some pre-release review versions are archived: [http://dev.linuxfoundation.org/~mats/MeeGo-Compliance-Spec-1.0.99.9.pdf Spec 1.0.99.9] | [[Media:MeeGo-Compliance-Spec-1.0.99.5.pdf|Spec 1.0.99.5]] | [[Media:MeeGo-Compliance-Spec-1.0.99.4.pdf|Spec 1.0.99.4]] | [[Media:MeeGo-Compliance-Spec-1.0.99.3.pdf|Spec 1.0.99.3]] | [[Media:MeeGo-Compliance-Spec-1.0.99.2.pdf|Spec 1.0.99.2]] | [[Media:MeeGo-Compliance-Spec-1.0.99.1.pdf|Spec 1.0.99.1]] | [[Media:MeeGo-Compliance-Spec-1.0.99.7x.pdf|Spec 1.0.99.7]] | [[Media:MeeGo-Compliance-Spec-1.0.80.8.pdf|Spec 1.0.80.8]]

Comments on the specification can go to the meego-dev mailing list (until we get kicked off!). For concrete bugs, feature requests, etc. please file bugs in the MeeGo bugzilla, there is a Compliance category.

Work in progress:

* [[Quality/Compliance/HandsetProfile|Handset Profile]]
* [[Quality/Compliance/TabletProfile|Tablet Profile]]
* [[Quality/Compliance/IVIProfile|IVI Profile]]

== Compliance Tools ==

The Compliance Tools are used to check compliance for MeeGo Distributions or MeeGo Applications. The reference input is the MeeGo core package/file list and a minimal MeeGo reference image created by MIC2, which will contain all the required core packages, as well as source rpms.

For MeeGo distribution compliance checking, the input needs to include the OS image and the source rpms for all the packages.

For MeeGo Application compliance checking, the input is the application rpm file.

See [[Quality/ComplianceTools|ComplianceTools]] for details.

== MeeGo 1.2 Compliance Program Schedule ==

Tasks:

* Preliminary compliance package list (i.e. the minimum set of required on-device packages) - now covered by package patterns
* Next Rev of compliance spec including profiles
* 1.2 version of compliance tools for distribution / device
* 1.2 version of compliance tools for applications

== Talks about Compliance ==

At the Meego Conference 2010, Mark Skarpness gave a talk on [http://conference2010.meego.com/session/app-compatibility-and-meego-compliance-program Compliance]

Quality/Compliance/IVIProfil

2011-05-12T09:40:03Z

Jeremiah: Created page with "This is an evolving draft, please propose changes in Talk:Quality/Compliance/HandsetProfile and have larger discussions on meego-dev@meego.com mailing list. Changes not discu..."

This is an evolving draft, please propose changes in [[Talk:Quality/Compliance/HandsetProfile]] and have larger discussions on meego-dev@meego.com mailing list. Changes not discussed in the discussion page will be reverted.

= MeeGo Handset Profile Specification =
== Hardware Requirements ==
None listed at this time

== Package Management ==
None listed at this time

== ABI and API ==
The MeeGo Handset Profile extends the Platform API with the following components:

* MeeGo Touch Framework (TBD: version)

== Other Requirements ==
None listed at this time

== Handset Profile Packages ==
The MeeGo Handset Profile adds these additional packages beyond those required for MeeGo Core compliance:

{| class="prettytable"
| '''Source Package'''
| '''Version'''
| Type
| '''Binary Packages'''

|-
| '''libmeegotouch'''
|
| core
| '''libmeegotouch'''

|-
| '''meegotouch-applauncherd'''
|
| core
| '''meegotouch-applauncherd'''

|-
| '''meegotouch-applifed'''
|
| core
| '''meegotouch-applifed'''

|-
| '''meegotouch-controlpanel'''
|
| core
| '''meegotouch-controlpanel'''

|-
| '''meegotouch-feedback'''
|
| core
| '''meegotouch-feedback'''

|-
| '''meegotouch-feedbackreactionmaps'''
|
| core
| '''meegotouch-feedbackreactionmaps'''

|-
| '''meegotouch-inputmethodengine'''
|
| core
| '''meegotouch-inputmethodengine'''

|-
| '''meegotouch-inputmethodframework'''
|
| core
| '''meegotouch-inputmethodframework'''

|-
| '''meegotouch-theme'''
|
| dep
| '''meegotouch-theme'''

|}

Quality/Compliance

2011-05-12T09:39:49Z

Jeremiah: /* Specification */

= MeeGo Compliance =

The MeeGo compliance program is designed to make sure things stay compatible, such that the devices supporting a particular MeeGo version can run the same software, and so that app developers know how to build software which will run across the family. Simply put, we want to make it possible for an application developer to write a MeeGo compliant application once and run it on any MeeGo compliant device.

MeeGo compliance addresses two categories of compliance: MeeGo compliant applications and MeeGo compliant devices / software products (which will be referred to simply as "devices"). In both cases, the use of the MeeGo brand will be granted based on being compliant. Following is an overview of the approach for each of these categories.

==MeeGo Compliant Device Overview==

For MeeGo compliant devices, we're taking a stack-based compliance approach, meaning that all MeeGo devices must use the same core software stack. Referring to the MeeGo architecture diagram, this core software stack is the MeeGo OS base layer plus the MeeGo OS Middleware layer.

In addition to a sharing the same core software stack, MeeGo compliance will have profiles for each device category (Netbook, Handset, and so on). A profile specifies additional required components for the profile (e.g. providing device category APIs), minimum hardware requirements and minimum hardware component requirements (such as cellular modem in the handset profile).

It's important to note that the device profiles won't require the inclusion of a complete user experience - but rather the UI framework providing core user interaction and APIs.

A MeeGo compliant device would be compliant to the MeeGo core software stack definition and one (or more) device category profiles.

==MeeGo Compliant Application Overview==

Given that definition of compliance for devices / software products, MeeGo compliance for applications will verify that an application's external dependencies are satisfied by a MeeGo compliant device (in other words, that any libraries or other dependencies of the application are provided within the core software stack and target device profile)

An application can be written to be dependent only on the MeeGo core software stack - in which case it would run on any MeeGo compliant device. However, applications with UI would typically target a specific device profile - so for example an application could be MeeGo Handset Compliant - meaning that it would run on any device compliant with the MeeGo Handset profile.

==More Detail on Stack Based Compliance==

Stack-based compliance means that a compliant device / software product must use the MeeGo package set without re-packaging - including the MeeGo version of RPM and the MeeGo package names.

Compliance requires the use of the MeeGo source packages for required components, and that any applied patches (e.g. to fix bugs found in the field) must not effect API, ABI, or defined functionality of interfaces.

Additional packages (beyond those required by compliance) may be added as long as they don't override MeeGo packages or provide functions with the same namespace of MeeGo APIs. Of course there will also be additional packages and components required to adapt MeeGo to run on a specific hardware platform (we call this "Hardware Adaptation Software" in MeeGo) - the compliance specification will call out any specific packages or components that may vary based on hardware capabilities.

Some details on how this is implemented can be seen at [[Quality/Compliance_Implementation|Compliance_Implementaion]].

A core part of the program is the Compliance Specification, which describes the rules and requirements for complying. There's more to the program (trademark licensing, application process, etc.) which will be added later.

== Specification ==

The specification is intended to match up with MeeGo releases, so it uses a similar numbering scheme. Completed specifications are approved by the TSG. The current approved version is [http://wiki.meego.com/images/MeeGo-Compliance-Spec-1.1.0.0.pdf Spec 1.1]

Some pre-release review versions are archived: [http://dev.linuxfoundation.org/~mats/MeeGo-Compliance-Spec-1.0.99.9.pdf Spec 1.0.99.9] | [[Media:MeeGo-Compliance-Spec-1.0.99.5.pdf|Spec 1.0.99.5]] | [[Media:MeeGo-Compliance-Spec-1.0.99.4.pdf|Spec 1.0.99.4]] | [[Media:MeeGo-Compliance-Spec-1.0.99.3.pdf|Spec 1.0.99.3]] | [[Media:MeeGo-Compliance-Spec-1.0.99.2.pdf|Spec 1.0.99.2]] | [[Media:MeeGo-Compliance-Spec-1.0.99.1.pdf|Spec 1.0.99.1]] | [[Media:MeeGo-Compliance-Spec-1.0.99.7x.pdf|Spec 1.0.99.7]] | [[Media:MeeGo-Compliance-Spec-1.0.80.8.pdf|Spec 1.0.80.8]]

Comments on the specification can go to the meego-dev mailing list (until we get kicked off!). For concrete bugs, feature requests, etc. please file bugs in the MeeGo bugzilla, there is a Compliance category.

Work in progress:

* [[Quality/Compliance/HandsetProfile|Handset Profile]]
* [[Quality/Compliance/TabletProfile|Tablet Profile]]
* [[Quality/Compliance/IVIProfil|IVI Profile]]

== Compliance Tools ==

The Compliance Tools are used to check compliance for MeeGo Distributions or MeeGo Applications. The reference input is the MeeGo core package/file list and a minimal MeeGo reference image created by MIC2, which will contain all the required core packages, as well as source rpms.

For MeeGo distribution compliance checking, the input needs to include the OS image and the source rpms for all the packages.

For MeeGo Application compliance checking, the input is the application rpm file.

See [[Quality/ComplianceTools|ComplianceTools]] for details.

== MeeGo 1.2 Compliance Program Schedule ==

Tasks:

* Preliminary compliance package list (i.e. the minimum set of required on-device packages) - now covered by package patterns
* Next Rev of compliance spec including profiles
* 1.2 version of compliance tools for distribution / device
* 1.2 version of compliance tools for applications

== Talks about Compliance ==

At the Meego Conference 2010, Mark Skarpness gave a talk on [http://conference2010.meego.com/session/app-compatibility-and-meego-compliance-program Compliance]

Quality/Compliance Implementation

2011-05-09T12:15:59Z

Jeremiah: /* Implementation of Compliance */ minor syntax correction.

= Compliance Implementation =

== Definition ==
The objective of '''Compliance''' is to provide a base set of functionality that application writers can depend on being there - effectively, an ABI plus other supporting details.

There are two aspects to compliance:
* For application writers, the key aspect is the set of services (libraries, services such as dbus, etc.) that are always present, so that apps know they can use them safely. It also includes a picture of which of those will be consistently provided in future releases so developers can detemine whether their apps will be "future-proof" or not.
* For device implementors, what is needed is a complete picture of what must be delivered, not just the external ABI view, so dependencies are also part of the picture.

In effect, the MeeGo Architecture makes up the starting point for compliance, while the the dependencies of the architecture packages can be seen as providing functionality "on behalf of" the architecture packages so to be practical, they end up in compliance as well. Dependencies could change over time - a dependency in 1.2 might not be a dependency in 1.3 any longer, so this part should not be counted on by applications; but for a given MeeGo release, dependencies are mandatory for devices.

== MeeGo Core vs. Compliance ==

The Compliance set does not need to describe a bootable system, indeed does not need to be a "real OS", it's just the minimum set an OSV needs to provide so that ISVs get a "compatible" OS.

Meego-core on the other hand actually needs to boot, so there's a bunch of things in there that are needed to boot, but that an application couldn't care less about. Bootloaders are a quick example of things that must be in core, but are not important for compliance.

So for all intents and purposes, compliance ends up being a subset of core.

As an example, compliance could include a requirement to handle sysv initscripts, but not describe how that requirement is to be met, so an OSV could replace the exsiting init processing with upstart. As long as the sysv initscripts are handled correctly, that's compliant.

== Implementation of Compliance ==

Since package groups are used to drive image creation anyway, proper grouping can make keeping track of compliance straightforward.

Conceptually, these patterns could be used:

* Base: bootable system, not compliant
* Compliance: Application Compliance packages
* Core = Base + Compliance
* Derived Compliance (need a better name for that) : Compliance and its dependencies
* Hardware Adaption Groups
* UX Groups

The MeeGo package-groups git tree (git://gitorious.org/meego-os-base/package-groups.git) now has these patterns to describe the compliance picture (additional patterns for adaptation, UX, etc):

* meego-base.xml - Basic system
* meego-compliance.xml - Packages needed for Compliance
* meego-full-compliance.xml - MeeGo full compliance including core compliance and its dependencies
* meego-core.xml - MeeGo Core OS

As a note, there is some compliance stuff that isn't expressed as a specific pattern, and has to be handled separately:

* Kernel 2.6.35 or later -We have separate kernel for separate platforms
* /usr/lib/libEGL.so.1 - we have separate gfx package to provide this
* /usr/lib/libGLES2.so.1 - we have separate gfx package to provide this

In-vehicle

2011-04-11T12:40:13Z

Jeremiah: /* MeeGo IVI 1.2 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]'''
*** 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)]'''

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.

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

[http://wiki.meego.com/In-vehicle/Roadmap/SystemArchitecture System Architecture]

[http://wiki.meego.com/In-vehicle/Roadmap/FeatureScope Feature Scope]

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

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

[http://wiki.meego.com/IVIHome_Guide Guide for the IVI Home Screen]

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

;March 8, 2011
:EMGD
::The Intel EMGD graphics driver has had continued updates including the addition of support for hardware accelerated video decode.
:ML7213 platform
::kernel driver support for the Oki Semiconductor ML7213 IVI IOH chipset has been added. This chipset is used on the Intel Stephenville/Crossville IVI platform. This platform is in very early sampling now to select customers of the Intel Embedded Computing Group.

===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, IDE, 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
|Stephenville/Crossville
|Intel® Atom™ Processor 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-ia32-conx
|Stephenville/Northville/Crossville
|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, 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
|-
|}

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

== 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/
* [[IVI|IVI for users and developers]]
* [[IVITopic|Topics]]

In-vehicle

2011-04-11T12:39:05Z

Jeremiah: /* MeeGo IVI 1.2 Supported Platforms */

Community communication

2011-04-03T16:58:22Z

Jeremiah: /* MeeGo IRC Channels */

'''This is a work in progress - we are still in the process of creating some of these new mailing lists, but most of this document is accurate.'''

Visit [[Community communication/Status]] for updates.

==Read Before Posting - Helping Yourself==

===Search for existing answers===
'''IMPORTANT: Before you post to any of our mailing lists or forums, be sure that you have done a thorough search and read our FAQs to see if your question has already been answered.''' We've already answered many questions, and you will get a better response from people if you have already done your due diligence to find obvious or partial answers.
* '''[[MeeGo FAQ]]''': Main frequently asked questions document with links to specialized FAQs.
* '''[http://forum.meego.com/search.php Forum Search]''': Use the [http://forum.meego.com/search.php forum search page] to find answers to user questions.
* '''[http://wiki.meego.com/index.php?title=Special%3ASearch&search=&fulltext=Search Wiki Search]: Find existing documentation and helpful tips.
* '''Mailing list search''': In Google type: ''my search terms site:lists.meego.com''
* '''Search Everything''' (meego.com, mailing lists, forums, wiki, etc.): In Google type: ''my search terms site:meego.com''

===Etiquette: What to know before you post===
* '''Post in the right place''': Read the section below carefully to find the right place to post your question or comment. For example, posting user questions to developer lists annoys developers and you are less likely to get a good response if you don't take the time to find the right place for your post.
* '''Adhere to our [[Community guidelines]]''': [[Mailing list guidelines]], [[Forum/Guidelines|forum guidelines]], [[Gitorious guidelines]] and [[Wiki contribution guidelines]].
* '''File bugs in the right place''': If you found a bug, just go ahead and file it in [http://bugs.meego.com/ bugs.meego.com] ([[Quality/How To Report Bugs|instructions for how to report bugs]])

==Mailing Lists and Forums==
Discussions about MeeGo, asynchronous project collaboration and answers to questions across a variety of mailing lists and forums. Please note that you must subscribe before you can post to a mailing list, and you need to have a meego.com account to post in our forums. You can learn more by reading our [[Forum/Guidelines|Forum guidelines]] and [[Mailing list guidelines]].

===Announcements===
Subscribe to these lists to receive announcements.

* '''[http://lists.meego.com/listinfo/meego-announce MeeGo-announce Mailing List]''': General announcements related to the MeeGo project (announcement list - general interest)
* '''[http://lists.meego.com/listinfo/meego-security MeeGo-security Mailing List]''': MeeGo Security Announcements (announcement list for security professionals and developers)

===Users===
Issues with installation, user level bugs, or general questions about MeeGo. This is where users of MeeGo can ask questions and discuss MeeGo with other users in our forums.

* '''[http://forum.meego.com/forumdisplay.php?f=2 General]''': MeeGo related topics not classified in a specific subforum.
* '''[http://forum.meego.com/forumdisplay.php?f=7 Handset]''': MeeGo Handset related topics.
* '''[http://forum.meego.com/forumdisplay.php?f=9 In-Vehicle]''': MeeGo In-Vehicle Infotainment (IVI) related topics.
* '''[http://forum.meego.com/forumdisplay.php?f=6 Netbook]''': MeeGo Netbook related topics.
* '''[http://forum.meego.com/forumdisplay.php?f=8 Tablet]''': MeeGo Tablet related topics.
* '''[http://forum.meego.com/forumdisplay.php?f=5 Community Matters]''': Discussion about infrastructure, processes, marketing, events, and other community matters for the MeeGo project.
* '''[http://forum.meego.com/forumdisplay.php?f=4 Off-Topic]''': Totally unrelated but still worth discussing between ameegos.

===Application Developers===
Ask questions and discuss techniques for developing applications to run on top of MeeGo.

* '''[http://forum.meego.com/forumdisplay.php?f=3 Application Developer Support Forum]''': Offer/get help dealing with application developer tools and APIs.
* '''[http://lists.meego.com/listinfo/meego-sdk MeeGo-sdk Mailing List]''': MeeGo application development - using the SDK / APIs and developing applications for MeeGo.
* '''[http://lists.meego.com/listinfo/meego-python MeeGo-python Mailing List]''': Discuss Python in the MeeGo project and using Python as a prominent choice for third party development (using PySide and QML).
* '''MeeGo-media-dev Mailing List''': Proposed: Discussions about creating media experience applications on MeeGo.

===Contributors===
People who are contributing to the MeeGo project collaborate on these lists.

* '''[http://lists.meego.com/listinfo/meego-community MeeGo-Community Mailing List]''': Community, general operations, openness, events and other general interest questions.
* '''[http://lists.meego.com/listinfo/meego-dev MeeGo-dev Mailing List]''': Development on the MeeGo distribution - '''not''' for application development or user level questions (high volume).
* '''[http://lists.meego.com/listinfo/meego-il10n MeeGo-il10n Mailing List]''': Localization list for MeeGo community.
* '''[http://lists.meego.com/listinfo/meego-packaging MeeGo-Packaging Mailing List]''': Communication about packaging and the build system.
* '''[http://lists.meego.com/listinfo/meego-pm MeeGo-pm Mailing List]''': Program management, product management and general coordination for people working in key roles in the project.
* '''[http://lists.meego.com/listinfo/meego-touch-dev MeeGo-touch-dev Mailing List]''': MeeGo Touch Framework Development.
* '''[http://lists.meego.com/listinfo/meego-releases MeeGo-releases Mailing List]''': Collaboration list on daily activities for Release Engineering and Quality Assurance teams.
* '''[http://lists.meego.com/listinfo/meego-qa MeeGo-qa Mailing List]''': Collaboration list on daily activities for the Quality Assurance team.
* '''[http://lists.meego.com/listinfo/meego-commits MeeGo-commits Mailing List]''': Broadcast list with auto-generated posts by people committing code into MeeGo.
* '''[http://lists.meego.com/listinfo/meego-kernel MeeGo-kernel Mailing List]''': MeeGo kernel discussions and patches.
* '''[http://lists.meego.com/listinfo/meego-architecture MeeGo-architecture Mailing List]''': MeeGo architecture discussions.
* '''[http://lists.meego.com/listinfo/meego-handset MeeGo-handset Mailing List]''': MeeGo handset program management, product management and development.
* '''MeeGo-netbook Mailing List''' (proposed): MeeGo netbook program management, product management and development.
* '''[http://lists.meego.com/listinfo/meego-ivi MeeGo-ivi Mailing List]''': MeeGo In-Vehicle Infotainment program management, product management and development.
* '''MeeGo-mirrors Mailing List''' (proposed): Communication with people who are mirroring our downloads.
* '''[http://lists.meego.com/listinfo/meego-security-discussion MeeGo-security-discussion Mailing List]''': Discussion about the MeeGo Security Framework and other security topics.
* '''[http://lists.meego.com/listinfo/meego-it MeeGo-it Mailing List]''': Discussion about IT and infrastructure for MeeGo.
* '''[http://lists.meego.com/listinfo/meego-porting MeeGo-porting Mailing List]''': Discussions about porting MeeGo to various platforms / devices.
* '''[http://lists.meego.com/listinfo/meego-events MeeGo-events Mailing List]''': Discussions about MeeGo Conferences and other MeeGo events.
* '''[http://lists.meego.com/listinfo/meego-distribution-tools MeeGo-distribution-tools Mailing List]''': Discussion list for the [http://meego.gitorious.org/meego-developer-tools distribution development] and [http://meego.gitorious.org/meego-infrastructure-tools distribution infrastructure] tools used in MeeGo release and packaging.
* '''[http://lists.meego.com/listinfo/meego-adaptation-intel-automotive MeeGo-adaptation-intel-automotive Mailing List]''': MeeGo Intel Automotive Adaptation kernel discussion and patches.
* '''[http://lists.meego.com/listinfo/meego-tv MeeGo-tv Mailing List]''': Discussions about Connected TV, Set-Top Boxes (STB) and Media Center devices.
* '''MeeGo-Media''' (proposed): Discussions about multimedia and media-specific middleware, codecs, reference media applications, sharing frameworks and other media topics.
* '''[http://lists.meego.com/listinfo/meego-inputmethods MeeGo-Inputmethods]''': Communication channel for the [[Meego Input Methods]] project used by core developers, contributors and external input method plug-in developers.

Note: Lists without links may still be tentative and have not been created or configured yet.

==IRC==

Internet Relay Chat (IRC) for real-time discussions about MeeGo and online meetings. All of our IRC channels are hosted at [http://freenode.net/ irc.freenode.net].

===MeeGo IRC Channels===

* '''#meego''': 24/7 open discussion.
* '''#meego-meeting''': scheduled IRC meetings ([[MeeGo-Meeting IRC Schedule]]).
* '''#meego-meeting-questions''': used for questions during moderated IRC meetings (rarely used).
* '''#meego-arm''': MeeGo ARM team channel as well as home to the MeeGo N900 hardware adaptation team.
* '''#meego-sdk''': Discussion about the MeeGo SDK.
* '''#meego-handset''': Collaboration for the MeeGo Handset team.
* '''#meego-art''': Graphics and theming.
* '''#meego-qa''': MeeGo QA channel
* '''#meego-python''': The MeeGo Python project - Developing and packaging Python for MeeGo + application development using Python
* '''#meego-l10n''': Used for questions and discussion on localizing MeeGo
* '''#meego-bar''': Used for drinking Guinness and general off topic chat with colleagues and friends around the world
* '''#meego-fi''': Regional channel for MeeGo Network Finland. Includes discussions about MeeGo Summit FI
* '''#meego-rus''': Regional channel for MeeGo Network Russia.
* '''#meego-inputmethods''': IRC channel for [[Meego Input Methods]] (text input, virtual-keyboard et.c.)
* '''#meego-ivi''': IRC channel for MeeGo In-Vehicle

===IRC How-to===

* '''MeeGo [[IRC guidelines]]'''
* '''[http://irchelp.org/irchelp/ircprimer.html IRC Primer]''': Read this if you are new to IRC.
* '''[http://freenode.net/channel_guidelines.shtml Freenode Guidelines]'''.
* '''[http://webchat.freenode.net/ IRC Webchat]''': If you are new to IRC and don't already use an IRC client, you can get into IRC using any browser.
* '''[http://en.wikipedia.org/wiki/Internet_Relay_Chat_client#Clients IRC Clients]'''.

==Bugs==

Quite a bit of discussion happens in Bugzilla to discuss bugs and possible solutions.

* '''[[Quality/How To Report Bugs|How to Report Bugs]]''': Instructions, process and guidelines
* '''[http://bugs.meego.com/ bugs.meego.com]''': MeeGo Bugzilla

==Documentation==

Some of our documentation can be found on [http://meego.com MeeGo.com], but most of the documentation can be found in the [[Main Page|MeeGo Wiki]] where you can contribute by:
* Adding new documentation to help other people in the MeeGo community
* Correcting technical errors or adding additional information in the documentation
* Cleaning up the language and correcting typos

==Contributing to MeeGo==

There are also many ways that you can contribute to MeeGo beyond just discussions. See our [http://meego.com/about/contribution-guidelines Contribution Guidelines] page for more details.

Community communication

2011-04-03T16:55:24Z

Jeremiah: /* MeeGo IRC Channels */

'''This is a work in progress - we are still in the process of creating some of these new mailing lists, but most of this document is accurate.'''

Visit [[Community communication/Status]] for updates.

==Read Before Posting - Helping Yourself==

===Search for existing answers===
'''IMPORTANT: Before you post to any of our mailing lists or forums, be sure that you have done a thorough search and read our FAQs to see if your question has already been answered.''' We've already answered many questions, and you will get a better response from people if you have already done your due diligence to find obvious or partial answers.
* '''[[MeeGo FAQ]]''': Main frequently asked questions document with links to specialized FAQs.
* '''[http://forum.meego.com/search.php Forum Search]''': Use the [http://forum.meego.com/search.php forum search page] to find answers to user questions.
* '''[http://wiki.meego.com/index.php?title=Special%3ASearch&search=&fulltext=Search Wiki Search]: Find existing documentation and helpful tips.
* '''Mailing list search''': In Google type: ''my search terms site:lists.meego.com''
* '''Search Everything''' (meego.com, mailing lists, forums, wiki, etc.): In Google type: ''my search terms site:meego.com''

===Etiquette: What to know before you post===
* '''Post in the right place''': Read the section below carefully to find the right place to post your question or comment. For example, posting user questions to developer lists annoys developers and you are less likely to get a good response if you don't take the time to find the right place for your post.
* '''Adhere to our [[Community guidelines]]''': [[Mailing list guidelines]], [[Forum/Guidelines|forum guidelines]], [[Gitorious guidelines]] and [[Wiki contribution guidelines]].
* '''File bugs in the right place''': If you found a bug, just go ahead and file it in [http://bugs.meego.com/ bugs.meego.com] ([[Quality/How To Report Bugs|instructions for how to report bugs]])

==Mailing Lists and Forums==
Discussions about MeeGo, asynchronous project collaboration and answers to questions across a variety of mailing lists and forums. Please note that you must subscribe before you can post to a mailing list, and you need to have a meego.com account to post in our forums. You can learn more by reading our [[Forum/Guidelines|Forum guidelines]] and [[Mailing list guidelines]].

===Announcements===
Subscribe to these lists to receive announcements.

* '''[http://lists.meego.com/listinfo/meego-announce MeeGo-announce Mailing List]''': General announcements related to the MeeGo project (announcement list - general interest)
* '''[http://lists.meego.com/listinfo/meego-security MeeGo-security Mailing List]''': MeeGo Security Announcements (announcement list for security professionals and developers)

===Users===
Issues with installation, user level bugs, or general questions about MeeGo. This is where users of MeeGo can ask questions and discuss MeeGo with other users in our forums.

* '''[http://forum.meego.com/forumdisplay.php?f=2 General]''': MeeGo related topics not classified in a specific subforum.
* '''[http://forum.meego.com/forumdisplay.php?f=7 Handset]''': MeeGo Handset related topics.
* '''[http://forum.meego.com/forumdisplay.php?f=9 In-Vehicle]''': MeeGo In-Vehicle Infotainment (IVI) related topics.
* '''[http://forum.meego.com/forumdisplay.php?f=6 Netbook]''': MeeGo Netbook related topics.
* '''[http://forum.meego.com/forumdisplay.php?f=8 Tablet]''': MeeGo Tablet related topics.
* '''[http://forum.meego.com/forumdisplay.php?f=5 Community Matters]''': Discussion about infrastructure, processes, marketing, events, and other community matters for the MeeGo project.
* '''[http://forum.meego.com/forumdisplay.php?f=4 Off-Topic]''': Totally unrelated but still worth discussing between ameegos.

===Application Developers===
Ask questions and discuss techniques for developing applications to run on top of MeeGo.

* '''[http://forum.meego.com/forumdisplay.php?f=3 Application Developer Support Forum]''': Offer/get help dealing with application developer tools and APIs.
* '''[http://lists.meego.com/listinfo/meego-sdk MeeGo-sdk Mailing List]''': MeeGo application development - using the SDK / APIs and developing applications for MeeGo.
* '''[http://lists.meego.com/listinfo/meego-python MeeGo-python Mailing List]''': Discuss Python in the MeeGo project and using Python as a prominent choice for third party development (using PySide and QML).
* '''MeeGo-media-dev Mailing List''': Proposed: Discussions about creating media experience applications on MeeGo.

===Contributors===
People who are contributing to the MeeGo project collaborate on these lists.

* '''[http://lists.meego.com/listinfo/meego-community MeeGo-Community Mailing List]''': Community, general operations, openness, events and other general interest questions.
* '''[http://lists.meego.com/listinfo/meego-dev MeeGo-dev Mailing List]''': Development on the MeeGo distribution - '''not''' for application development or user level questions (high volume).
* '''[http://lists.meego.com/listinfo/meego-il10n MeeGo-il10n Mailing List]''': Localization list for MeeGo community.
* '''[http://lists.meego.com/listinfo/meego-packaging MeeGo-Packaging Mailing List]''': Communication about packaging and the build system.
* '''[http://lists.meego.com/listinfo/meego-pm MeeGo-pm Mailing List]''': Program management, product management and general coordination for people working in key roles in the project.
* '''[http://lists.meego.com/listinfo/meego-touch-dev MeeGo-touch-dev Mailing List]''': MeeGo Touch Framework Development.
* '''[http://lists.meego.com/listinfo/meego-releases MeeGo-releases Mailing List]''': Collaboration list on daily activities for Release Engineering and Quality Assurance teams.
* '''[http://lists.meego.com/listinfo/meego-qa MeeGo-qa Mailing List]''': Collaboration list on daily activities for the Quality Assurance team.
* '''[http://lists.meego.com/listinfo/meego-commits MeeGo-commits Mailing List]''': Broadcast list with auto-generated posts by people committing code into MeeGo.
* '''[http://lists.meego.com/listinfo/meego-kernel MeeGo-kernel Mailing List]''': MeeGo kernel discussions and patches.
* '''[http://lists.meego.com/listinfo/meego-architecture MeeGo-architecture Mailing List]''': MeeGo architecture discussions.
* '''[http://lists.meego.com/listinfo/meego-handset MeeGo-handset Mailing List]''': MeeGo handset program management, product management and development.
* '''MeeGo-netbook Mailing List''' (proposed): MeeGo netbook program management, product management and development.
* '''[http://lists.meego.com/listinfo/meego-ivi MeeGo-ivi Mailing List]''': MeeGo In-Vehicle Infotainment program management, product management and development.
* '''MeeGo-mirrors Mailing List''' (proposed): Communication with people who are mirroring our downloads.
* '''[http://lists.meego.com/listinfo/meego-security-discussion MeeGo-security-discussion Mailing List]''': Discussion about the MeeGo Security Framework and other security topics.
* '''[http://lists.meego.com/listinfo/meego-it MeeGo-it Mailing List]''': Discussion about IT and infrastructure for MeeGo.
* '''[http://lists.meego.com/listinfo/meego-porting MeeGo-porting Mailing List]''': Discussions about porting MeeGo to various platforms / devices.
* '''[http://lists.meego.com/listinfo/meego-events MeeGo-events Mailing List]''': Discussions about MeeGo Conferences and other MeeGo events.
* '''[http://lists.meego.com/listinfo/meego-distribution-tools MeeGo-distribution-tools Mailing List]''': Discussion list for the [http://meego.gitorious.org/meego-developer-tools distribution development] and [http://meego.gitorious.org/meego-infrastructure-tools distribution infrastructure] tools used in MeeGo release and packaging.
* '''[http://lists.meego.com/listinfo/meego-adaptation-intel-automotive MeeGo-adaptation-intel-automotive Mailing List]''': MeeGo Intel Automotive Adaptation kernel discussion and patches.
* '''[http://lists.meego.com/listinfo/meego-tv MeeGo-tv Mailing List]''': Discussions about Connected TV, Set-Top Boxes (STB) and Media Center devices.
* '''MeeGo-Media''' (proposed): Discussions about multimedia and media-specific middleware, codecs, reference media applications, sharing frameworks and other media topics.
* '''[http://lists.meego.com/listinfo/meego-inputmethods MeeGo-Inputmethods]''': Communication channel for the [[Meego Input Methods]] project used by core developers, contributors and external input method plug-in developers.

Note: Lists without links may still be tentative and have not been created or configured yet.

==IRC==

Internet Relay Chat (IRC) for real-time discussions about MeeGo and online meetings. All of our IRC channels are hosted at [http://freenode.net/ irc.freenode.net].

===MeeGo IRC Channels===

* '''#meego''': 24/7 open discussion.
* '''#meego-meeting''': scheduled IRC meetings ([[MeeGo-Meeting IRC Schedule]]).
* '''#meego-meeting-questions''': used for questions during moderated IRC meetings (rarely used).
* '''#meego-arm''': MeeGo ARM team channel as well as home to the MeeGo N900 hardware adaptation team.
* '''#meego-sdk''': Discussion about the MeeGo SDK.
* '''#meego-handset''': Collaboration for the MeeGo Handset team.
* '''#meego-art''': Graphics and theming.
* '''#meego-qa''': MeeGo QA channel
* '''#meego-python''': The MeeGo Python project - Developing and packaging Python for MeeGo + application development using Python
* '''#meego-l10n''': Used for questions and discussion on localizing MeeGo
* '''#meego-bar''': Used for drinking Guinness and general off topic chat with colleagues and friends around the world
* '''#meego-fi''': Regional channel for MeeGo Network Finland. Includes discussions about MeeGo Summit FI
* '''#meego-rus''': Regional channel for MeeGo Network Russia.
* '''#meego-inputmethods''': IRC channel for [[Meego Input Methods]] (text input, virtual-keyboard et.c.)
* '''#meego-ivi''': IRC channel for [[http://meego.com/devices/in-vehicle]]

===IRC How-to===

* '''MeeGo [[IRC guidelines]]'''
* '''[http://irchelp.org/irchelp/ircprimer.html IRC Primer]''': Read this if you are new to IRC.
* '''[http://freenode.net/channel_guidelines.shtml Freenode Guidelines]'''.
* '''[http://webchat.freenode.net/ IRC Webchat]''': If you are new to IRC and don't already use an IRC client, you can get into IRC using any browser.
* '''[http://en.wikipedia.org/wiki/Internet_Relay_Chat_client#Clients IRC Clients]'''.

==Bugs==

Quite a bit of discussion happens in Bugzilla to discuss bugs and possible solutions.

* '''[[Quality/How To Report Bugs|How to Report Bugs]]''': Instructions, process and guidelines
* '''[http://bugs.meego.com/ bugs.meego.com]''': MeeGo Bugzilla

==Documentation==

Some of our documentation can be found on [http://meego.com MeeGo.com], but most of the documentation can be found in the [[Main Page|MeeGo Wiki]] where you can contribute by:
* Adding new documentation to help other people in the MeeGo community
* Correcting technical errors or adding additional information in the documentation
* Cleaning up the language and correcting typos

==Contributing to MeeGo==

There are also many ways that you can contribute to MeeGo beyond just discussions. See our [http://meego.com/about/contribution-guidelines Contribution Guidelines] page for more details.

Community communication

2011-04-03T16:54:30Z

Jeremiah: /* MeeGo IRC Channels */

'''This is a work in progress - we are still in the process of creating some of these new mailing lists, but most of this document is accurate.'''

Visit [[Community communication/Status]] for updates.

==Read Before Posting - Helping Yourself==

===Search for existing answers===
'''IMPORTANT: Before you post to any of our mailing lists or forums, be sure that you have done a thorough search and read our FAQs to see if your question has already been answered.''' We've already answered many questions, and you will get a better response from people if you have already done your due diligence to find obvious or partial answers.
* '''[[MeeGo FAQ]]''': Main frequently asked questions document with links to specialized FAQs.
* '''[http://forum.meego.com/search.php Forum Search]''': Use the [http://forum.meego.com/search.php forum search page] to find answers to user questions.
* '''[http://wiki.meego.com/index.php?title=Special%3ASearch&search=&fulltext=Search Wiki Search]: Find existing documentation and helpful tips.
* '''Mailing list search''': In Google type: ''my search terms site:lists.meego.com''
* '''Search Everything''' (meego.com, mailing lists, forums, wiki, etc.): In Google type: ''my search terms site:meego.com''

===Etiquette: What to know before you post===
* '''Post in the right place''': Read the section below carefully to find the right place to post your question or comment. For example, posting user questions to developer lists annoys developers and you are less likely to get a good response if you don't take the time to find the right place for your post.
* '''Adhere to our [[Community guidelines]]''': [[Mailing list guidelines]], [[Forum/Guidelines|forum guidelines]], [[Gitorious guidelines]] and [[Wiki contribution guidelines]].
* '''File bugs in the right place''': If you found a bug, just go ahead and file it in [http://bugs.meego.com/ bugs.meego.com] ([[Quality/How To Report Bugs|instructions for how to report bugs]])

==Mailing Lists and Forums==
Discussions about MeeGo, asynchronous project collaboration and answers to questions across a variety of mailing lists and forums. Please note that you must subscribe before you can post to a mailing list, and you need to have a meego.com account to post in our forums. You can learn more by reading our [[Forum/Guidelines|Forum guidelines]] and [[Mailing list guidelines]].

===Announcements===
Subscribe to these lists to receive announcements.

* '''[http://lists.meego.com/listinfo/meego-announce MeeGo-announce Mailing List]''': General announcements related to the MeeGo project (announcement list - general interest)
* '''[http://lists.meego.com/listinfo/meego-security MeeGo-security Mailing List]''': MeeGo Security Announcements (announcement list for security professionals and developers)

===Users===
Issues with installation, user level bugs, or general questions about MeeGo. This is where users of MeeGo can ask questions and discuss MeeGo with other users in our forums.

* '''[http://forum.meego.com/forumdisplay.php?f=2 General]''': MeeGo related topics not classified in a specific subforum.
* '''[http://forum.meego.com/forumdisplay.php?f=7 Handset]''': MeeGo Handset related topics.
* '''[http://forum.meego.com/forumdisplay.php?f=9 In-Vehicle]''': MeeGo In-Vehicle Infotainment (IVI) related topics.
* '''[http://forum.meego.com/forumdisplay.php?f=6 Netbook]''': MeeGo Netbook related topics.
* '''[http://forum.meego.com/forumdisplay.php?f=8 Tablet]''': MeeGo Tablet related topics.
* '''[http://forum.meego.com/forumdisplay.php?f=5 Community Matters]''': Discussion about infrastructure, processes, marketing, events, and other community matters for the MeeGo project.
* '''[http://forum.meego.com/forumdisplay.php?f=4 Off-Topic]''': Totally unrelated but still worth discussing between ameegos.

===Application Developers===
Ask questions and discuss techniques for developing applications to run on top of MeeGo.

* '''[http://forum.meego.com/forumdisplay.php?f=3 Application Developer Support Forum]''': Offer/get help dealing with application developer tools and APIs.
* '''[http://lists.meego.com/listinfo/meego-sdk MeeGo-sdk Mailing List]''': MeeGo application development - using the SDK / APIs and developing applications for MeeGo.
* '''[http://lists.meego.com/listinfo/meego-python MeeGo-python Mailing List]''': Discuss Python in the MeeGo project and using Python as a prominent choice for third party development (using PySide and QML).
* '''MeeGo-media-dev Mailing List''': Proposed: Discussions about creating media experience applications on MeeGo.

===Contributors===
People who are contributing to the MeeGo project collaborate on these lists.

* '''[http://lists.meego.com/listinfo/meego-community MeeGo-Community Mailing List]''': Community, general operations, openness, events and other general interest questions.
* '''[http://lists.meego.com/listinfo/meego-dev MeeGo-dev Mailing List]''': Development on the MeeGo distribution - '''not''' for application development or user level questions (high volume).
* '''[http://lists.meego.com/listinfo/meego-il10n MeeGo-il10n Mailing List]''': Localization list for MeeGo community.
* '''[http://lists.meego.com/listinfo/meego-packaging MeeGo-Packaging Mailing List]''': Communication about packaging and the build system.
* '''[http://lists.meego.com/listinfo/meego-pm MeeGo-pm Mailing List]''': Program management, product management and general coordination for people working in key roles in the project.
* '''[http://lists.meego.com/listinfo/meego-touch-dev MeeGo-touch-dev Mailing List]''': MeeGo Touch Framework Development.
* '''[http://lists.meego.com/listinfo/meego-releases MeeGo-releases Mailing List]''': Collaboration list on daily activities for Release Engineering and Quality Assurance teams.
* '''[http://lists.meego.com/listinfo/meego-qa MeeGo-qa Mailing List]''': Collaboration list on daily activities for the Quality Assurance team.
* '''[http://lists.meego.com/listinfo/meego-commits MeeGo-commits Mailing List]''': Broadcast list with auto-generated posts by people committing code into MeeGo.
* '''[http://lists.meego.com/listinfo/meego-kernel MeeGo-kernel Mailing List]''': MeeGo kernel discussions and patches.
* '''[http://lists.meego.com/listinfo/meego-architecture MeeGo-architecture Mailing List]''': MeeGo architecture discussions.
* '''[http://lists.meego.com/listinfo/meego-handset MeeGo-handset Mailing List]''': MeeGo handset program management, product management and development.
* '''MeeGo-netbook Mailing List''' (proposed): MeeGo netbook program management, product management and development.
* '''[http://lists.meego.com/listinfo/meego-ivi MeeGo-ivi Mailing List]''': MeeGo In-Vehicle Infotainment program management, product management and development.
* '''MeeGo-mirrors Mailing List''' (proposed): Communication with people who are mirroring our downloads.
* '''[http://lists.meego.com/listinfo/meego-security-discussion MeeGo-security-discussion Mailing List]''': Discussion about the MeeGo Security Framework and other security topics.
* '''[http://lists.meego.com/listinfo/meego-it MeeGo-it Mailing List]''': Discussion about IT and infrastructure for MeeGo.
* '''[http://lists.meego.com/listinfo/meego-porting MeeGo-porting Mailing List]''': Discussions about porting MeeGo to various platforms / devices.
* '''[http://lists.meego.com/listinfo/meego-events MeeGo-events Mailing List]''': Discussions about MeeGo Conferences and other MeeGo events.
* '''[http://lists.meego.com/listinfo/meego-distribution-tools MeeGo-distribution-tools Mailing List]''': Discussion list for the [http://meego.gitorious.org/meego-developer-tools distribution development] and [http://meego.gitorious.org/meego-infrastructure-tools distribution infrastructure] tools used in MeeGo release and packaging.
* '''[http://lists.meego.com/listinfo/meego-adaptation-intel-automotive MeeGo-adaptation-intel-automotive Mailing List]''': MeeGo Intel Automotive Adaptation kernel discussion and patches.
* '''[http://lists.meego.com/listinfo/meego-tv MeeGo-tv Mailing List]''': Discussions about Connected TV, Set-Top Boxes (STB) and Media Center devices.
* '''MeeGo-Media''' (proposed): Discussions about multimedia and media-specific middleware, codecs, reference media applications, sharing frameworks and other media topics.
* '''[http://lists.meego.com/listinfo/meego-inputmethods MeeGo-Inputmethods]''': Communication channel for the [[Meego Input Methods]] project used by core developers, contributors and external input method plug-in developers.

Note: Lists without links may still be tentative and have not been created or configured yet.

==IRC==

Internet Relay Chat (IRC) for real-time discussions about MeeGo and online meetings. All of our IRC channels are hosted at [http://freenode.net/ irc.freenode.net].

===MeeGo IRC Channels===

* '''#meego''': 24/7 open discussion.
* '''#meego-meeting''': scheduled IRC meetings ([[MeeGo-Meeting IRC Schedule]]).
* '''#meego-meeting-questions''': used for questions during moderated IRC meetings (rarely used).
* '''#meego-arm''': MeeGo ARM team channel as well as home to the MeeGo N900 hardware adaptation team.
* '''#meego-sdk''': Discussion about the MeeGo SDK.
* '''#meego-handset''': Collaboration for the MeeGo Handset team.
* '''#meego-art''': Graphics and theming.
* '''#meego-qa''': MeeGo QA channel
* '''#meego-python''': The MeeGo Python project - Developing and packaging Python for MeeGo + application development using Python
* '''#meego-l10n''': Used for questions and discussion on localizing MeeGo
* '''#meego-bar''': Used for drinking Guinness and general off topic chat with colleagues and friends around the world
* '''#meego-fi''': Regional channel for MeeGo Network Finland. Includes discussions about MeeGo Summit FI
* '''#meego-rus''': Regional channel for MeeGo Network Russia.
* '''#meego-inputmethods''': IRC channel for [[Meego Input Methods]] (text input, virtual-keyboard et.c.)
* '''#meego-ivi''': IRC channel for [[Meego IVI]]

===IRC How-to===

* '''MeeGo [[IRC guidelines]]'''
* '''[http://irchelp.org/irchelp/ircprimer.html IRC Primer]''': Read this if you are new to IRC.
* '''[http://freenode.net/channel_guidelines.shtml Freenode Guidelines]'''.
* '''[http://webchat.freenode.net/ IRC Webchat]''': If you are new to IRC and don't already use an IRC client, you can get into IRC using any browser.
* '''[http://en.wikipedia.org/wiki/Internet_Relay_Chat_client#Clients IRC Clients]'''.

==Bugs==

Quite a bit of discussion happens in Bugzilla to discuss bugs and possible solutions.

* '''[[Quality/How To Report Bugs|How to Report Bugs]]''': Instructions, process and guidelines
* '''[http://bugs.meego.com/ bugs.meego.com]''': MeeGo Bugzilla

==Documentation==

Some of our documentation can be found on [http://meego.com MeeGo.com], but most of the documentation can be found in the [[Main Page|MeeGo Wiki]] where you can contribute by:
* Adding new documentation to help other people in the MeeGo community
* Correcting technical errors or adding additional information in the documentation
* Cleaning up the language and correcting typos

==Contributing to MeeGo==

There are also many ways that you can contribute to MeeGo beyond just discussions. See our [http://meego.com/about/contribution-guidelines Contribution Guidelines] page for more details.

Recompile kernel

2011-03-31T14:26:07Z

Jeremiah: /* Recompiling the MeeGo Kernel */

=Recompiling the MeeGo Kernel for the Beagleboard=

This page explains the kernel recompilation process. If you'd like information on how to configure the MeeGo kernel, see this page: http://wiki.meego.com/MeeGo_kernel_documentation_for_contributors 
There already is a guide on how to compile the kernel for MeeGo, including links to packaging: http://wiki.meego.com/Tips_on_compiling_and_packaging_kernels_in_MeeGo 
This document is going to focus on the process I used to create a kernel, specifically for the Beagleboard for MeeGo IVI.

== Fetch the kernel source ==

The first thing you'll need to do to recompile the MeeGo kernel is to download and unpack the MeeGo kernel package. To get that package you can download it with wget like this;

<pre>
wget http://repo.meego.com/MeeGo/releases/1.1/core/repos/source/kernel-2.6.35.3-10.3.src.rpm
</pre>

You can of course get your kernel directly from upstream at kernel.org for example or clone it from MeeGo's git repos;

<pre>
git clone git://gitorious.org/meego-os-base/kernel-source.git
</pre>

I've chosen to build upon the work of others and am going to checkout a kernel build by Jan-Simon Möller.

== Unpack rpm ==

If you take the packaged MeeGo kernel, then you'll need to unpack this rpm. You can do that this way;
<pre>
rpm2cpio kernel-2.6.35.3-10.3.src.rpm | cpio -id
</pre>
and spot the linux-2.6.35.tar.bz2 file and patch-2.6.35.3.bz2

Recompile kernel

2011-03-31T14:25:33Z

Jeremiah: /* Recompiling the MeeGo Kernel */

=Recompiling the MeeGo Kernel=

This page explains the kernel recompilation process. If you'd like information on how to configure the MeeGo kernel, see this page: http://wiki.meego.com/MeeGo_kernel_documentation_for_contributors 
There already is a guide on how to compile the kernel for MeeGo, including links to packaging: http://wiki.meego.com/Tips_on_compiling_and_packaging_kernels_in_MeeGo 
This document is going to focus on the process I used to create a kernel, specifically for the Beagleboard for MeeGo IVI.

== Fetch the kernel source ==

The first thing you'll need to do to recompile the MeeGo kernel is to download and unpack the MeeGo kernel package. To get that package you can download it with wget like this;

<pre>
wget http://repo.meego.com/MeeGo/releases/1.1/core/repos/source/kernel-2.6.35.3-10.3.src.rpm
</pre>

You can of course get your kernel directly from upstream at kernel.org for example or clone it from MeeGo's git repos;

<pre>
git clone git://gitorious.org/meego-os-base/kernel-source.git
</pre>

I've chosen to build upon the work of others and am going to checkout a kernel build by Jan-Simon Möller.

== Unpack rpm ==

If you take the packaged MeeGo kernel, then you'll need to unpack this rpm. You can do that this way;
<pre>
rpm2cpio kernel-2.6.35.3-10.3.src.rpm | cpio -id
</pre>
and spot the linux-2.6.35.tar.bz2 file and patch-2.6.35.3.bz2

Recompile kernel

2011-03-31T14:17:42Z

Jeremiah: /* Recompiling the MeeGo Kernel */

=Recompiling the MeeGo Kernel=

This page explains the kernel recompilation process. If you'd like information on how to configure the MeeGo kernel, see this page: http://wiki.meego.com/MeeGo_kernel_documentation_for_contributors 
Note at the bottom of the page there is a link to more information on configuring the Linux kernel.

== Fetch the kernel source ==

The first thing you'll need to do to recompile the MeeGo kernel is to download and unpack the MeeGo kernel package. To get that package you can download it with wget like this;

<pre>
wget http://repo.meego.com/MeeGo/releases/1.1/core/repos/source/kernel-2.6.35.3-10.3.src.rpm
</pre>

You can of course get your kernel directly from upstream at kernel.org for example or clone it from MeeGo's git repos;

<pre>
git clone git://gitorious.org/meego-os-base/kernel-source.git
</pre>

== Unpack rpm ==

If you take the packaged MeeGo kernel, then you'll need to unpack this rpm. You can do that this way;
<pre>
rpm2cpio kernel-2.6.35.3-10.3.src.rpm | cpio -id
</pre>
and spot the linux-2.6.35.tar.bz2 file and patch-2.6.35.3.bz2

Recompile kernel

2011-03-31T14:15:46Z

Jeremiah:

=Recompiling the MeeGo Kernel=

This page explains the kernel recompilation process. 
More info here: http://wiki.meego.com/MeeGo_kernel_documentation_for_contributors

== Fetch the kernel source ==

The first thing you'll need to do to recompile the MeeGo kernel is to download and unpack the MeeGo kernel package. To get that package you can download it with wget like this;

<pre>
wget http://repo.meego.com/MeeGo/releases/1.1/core/repos/source/kernel-2.6.35.3-10.3.src.rpm
</pre>

You can of course get your kernel directly from upstream at kernel.org for example or clone it from MeeGo's git repos;

<pre>
git clone git://gitorious.org/meego-os-base/kernel-source.git
</pre>

== Unpack rpm ==

If you take the packaged MeeGo kernel, then you'll need to unpack this rpm. You can do that this way;
<pre>
rpm2cpio kernel-2.6.35.3-10.3.src.rpm | cpio -id
</pre>
and spot the linux-2.6.35.tar.bz2 file and patch-2.6.35.3.bz2

Recompile kernel

2011-03-31T14:14:01Z

Jeremiah:

=Recompiling the MeeGo Kernel=

This page explains the kernel recompilation process.

== Fetch the kernel source ==

The first thing you'll need to do to recompile the MeeGo kernel is to download and unpack the MeeGo kernel package. To get that package you can download it with wget like this;

<pre>
wget http://repo.meego.com/MeeGo/releases/1.1/core/repos/source/kernel-2.6.35.3-10.3.src.rpm
</pre>

You can of course get your kernel directly from upstream at kernel.org for example or clone it from MeeGo's git repos;

<pre>
git clone git://gitorious.org/meego-os-base/kernel-source.git
</pre>

== Unpack rpm ==

If you take the packaged MeeGo kernel, then you'll need to unpack this rpm. You can do that this way;
<pre>
rpm2cpio kernel-2.6.35.3-10.3.src.rpm | cpio -id
</pre>
and spot the linux-2.6.35.tar.bz2 file and patch-2.6.35.3.bz2

User:Jeremiah

2011-03-31T14:11:43Z

Jeremiah: /* 1.2 Release */

OHAI

This is the MeeGo wiki page for Jeremiah C. Foster. I am the MeeGo IVI Release Manger. I am a Free Software developer working for Pelagicore AB in Gothenburg, Sweden.

This wiki page serves as a "stack" of todo items. This stack lists things I have to do as MeeGo IVI Release Manager. Since this is a wiki, feel free to place things on this stack if you think that there are something I should focus on. Feel free to place general MeeGo issues in the MeeGo bug and feature trackers, but certainly if you feel that your concern is not appropriate for those resources, place a note here.

=== *Stack* ===

==== 1.2 Release ====
# Test the state of the most recent releases on the ARM platform (Ongoing)
#* A working kickstart file for the Beagleboard is available. Currently there is no internet.
#* I've contacted Anas and Tracy about maintainership of the kickstart file in gitorious
#** Should have access to the Gitorious repo which stores "official" kickstart files
# Document how a release is created
#* see if there is a general MeeGo release document to start from

==== 1.3 Release ====
# Get a content map onto the wiki

=== Documentation in progress ===

[[recompile_kernel|Recompiling the MeeGo kernel]] 
[[changing_desktops|Changing the UX on IVI]] 
[[ivi_release|IVI release creation]]

ARM

2011-03-29T13:06:40Z

Jeremiah: There is no necessarily fierce competition but rather cooperation between projects.

The situation between MeeGo and the ARM community is quite peculiar currently. The role of Intel awakes a predictable suspicion but at the same time many ARM stakeholders are increasingly involved in MeeGo related activities. The mobile focus combined with the multiple form factors targeted and the open setup make MeeGo a very interesting proposition for chipset vendors in the ARM community and device vendors shipping ARM based products.

== Technical specifications ==

MeeGo 1.2 ARM port comes with the following features:

* Baseline of ARMv7-A, float=vfpv3-d16, float-abi=hard and no thumb usage (means MeeGo.com releases are usable on all known ARMv7-A processors)
* Defined RPM sub-architectures for NEON and Thumb2 capability, optimize individual packages for NEON or Thumb2
* Built with and including Linaro toolchain 4.5 2010.09
* Cross-compilers and accelerated binaries built-in to the build system, making build time of packages comparable to that of X86 builds, with no difference in development usage between X86 and ARM
* ARM support in MeeGo release tools such as MeeGo Image Creator and in MeeGo SDK

== Highlights ==
* The MeeGo project is committed to support Intel/Atom and ARM architectures. Decisions on roadmapping, architecture and development take this requirement into account.
* The [http://meego.com/about/governance/release-engineering Release Engineering team] has specific roles for ARM related activities. Risto Lankinen is responsible for maintaining the ARM architecture-specific toolchain and libraries in MeeGo. [http://meego.com/users/stskeeps Carsten Munk] is responsible for maintaining MeeGo releases on the Nokia N900 hardware platform.
* #meego-arm is the MeeGo ARM team IRC channel as well as home to the MeeGo N900 hardware adaptation team.
* The Nokia N900 (TI OMAP3) is an official reference device for MeeGo Core and Handset. See [[ARM/N900]].
* 2010-10-27 [http://blogs.forbes.com/elizabethwoyke/2010/10/27/ti-views-tablets-meego-windows-phone-7-as-big-opportunity/ TI Views Tablets, MeeGo, Windows Phone 7 As ‘Big Opportunity’] (Forbes)
* 2010-10-27 TI's OMAP4 Panda board project officially launched including a MeeGo support project: http://pandaboard.org/
* ST-Ericsson presented at the MeeGo Conference a session about [http://conference2010.meego.com/session/st-ericsson-u8500-linaro-and-meego ST-Ericsson U8500 Linaro and MeeGo].
** 2011-02-15 ST-Ericsson launches the Snowball board with support for MeeGo: http://www.igloocommunity.org/
* Proof points of MeeGo running on ARM based platforms are popping up. Some of them are R&D initiatives of the vendors, some other are personal initiatives: [[ARM/MSMQSD|MSM/QSD]], [[ARM/Meego_on_Beagleboard_from_scratch|Beagleboard]].

== Linaro ==

* [http://www.linaro.org/ Linaro] aims to make ARM open source development easier and faster. Linaro creates a common software foundation for software stacks and distributions to land on and provide the best open source tools for developers to develop on. The focus is on low level software around the Linux kernel that touches the silicon, key pieces of middleware that enable new markets and tools that help the developer write and debug code. Linaro aims to maximize the potential of the latest features of ARM-based processors, helping provide optimized performance in a lower power envelope. Linaro is both a community and a supported project with engineering teams spread globally.
* '''ST-Ericsson''' and '''Texas Instruments''' are MeeGo supporters and Linaro members: [https://wiki.linaro.org/Platform/UserPlatforms/Heads/Meego MeeGo Platform]
* We must focus on these vendors' offerings (see below) to keep the ARM momentum going.
* There is development in other areas too: [http://www.linaro.org/software-leaders-to-advise-linaro/ Canonical (= Ubuntu), GENIVI, HP, LiMo and MontaVista become Advisors to Linaro]

See the article on [[ARM/LinaroInclusion|Linaro inclusion in MeeGo]].

== Running MeeGo on ARM ==
Information on how to use MeeGo on ARM-based devices and contacts to the teams working on it.

=== Nokia ===
* [[ARM/N900|The Nokia N900 hardware adaptation team]], team lead: Harri Hakulinen (IRC: harha)
* [[ARM/N900/DeveloperEdition|MeeGo 1.2 Developer Edition for N900 project]]

=== QEMU ===
* [[:wikipedia:QEMU|QEMU]] allows you to try out MeeGo safely on your Desktop PC.
* [[ARM/Meego on Qemu|QEMU instructions]]

=== Beagleboard ===
*[[ARM/Meego_on_Beagleboard_from_scratch|Meego on Beagleboard from scratch]]
*[[ARM/Meego_IVI_on_Beagle| MeeGo IVI on the Beagleboard]]
*[[ARM/Meego_on_the_Beagle|Demo image from Linux Foundation]]

=== Texas Instruments ===
* [[ARM/OMAP4_Panda|MeeGo on OMAP4 PandaBoard]] ([http://www.slideshare.net/menonnishanth/meego presentation])
* [[ARM/OMAP4_Blaze|MeeGo on OMAP4 Blaze]] ([http://www.youtube.com/watch?v=S20k1mvL8d0 video])

=== ST-Ericsson ===
* [http://www.calao-systems.com/articles.php?lng=en&pg=6186 Snowball] is a powerful board with ST-Ericsson’s Nova A9500 processor (ARM dual-core Cortex A9 @ 1GHz), combined with the [http://www.arm.com/products/multimedia/mali-graphics-hardware/mali-400-mp.php Mali 400 GPU.]
* [http://www.igloocommunity.org/ The Igloo community] will offer MeeGo, Android and Ubuntu releases for Snowball, and provide support for both hobbyist and professional users of the Snowball board.
* [http://www.stericsson.com/press_releases/Igloo_Snowball.jsp Press Release], [http://www.linaro.org/snowball-announcement/ Linaro blog]
* [[ARM/Snowball|MeeGo on Snowball]]

=== Qualcomm (Unofficial) ===
[[ARM/MSMQSD|MSM/QSD hardware adaptation]]

=== Samsung (Unofficial) ===
[[ARM/Hummingbird| Hummingbird hardware adaptation]]

=== Archos (Unofficial) ===
[http://codex.xiaoka.com/wiki/meego:archos Archos Gen7] port

=== Renesas ===
[http://www.youtube.com/watch?feature=player_embedded&v=xuNOweDXh3Q Video] from [http://nomovok.com/ Nomovok] demonstrating MeeGo Core OS and an own tablet-like UX running on top of [http://www.renesas.com/prod/assp/mobile/ap4.html Renesas SH-Mobile AP4]

=== Freescale ===
[http://www.youtube.com/watch?feature=player_embedded&v=osDlTdl5lAk Video] from [http://nomovok.com/ Nomovok] demonstrating MeeGo Core OS and an own tablet-like UX running on top of [http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=MCIMX51EVKJ Freescale i.MX51]

=== Nvidia (Unofficial) ===
[[ARM/TEGRA2|Tegra 2 hardware adaptation]]

== Engaging the ARM community ==
According to the [[Community_Office/Marketing|marketing strategy]], it is crucial for MeeGo to be a neutral platform. This implies the engagement of chipset vendors other than Intel and device manufacturers other than Nokia. The link between this goal and the ARM community is obvious.

How to improve the current situation? List your ideas below and get involved to make them happen. Proposals and discussions about this topic are welcome at the [http://lists.meego.com/listinfo/meego-community meego-community] mailing list.

# Highlight the MeeGo/ARM related projects and news in one place (this page?). Currently it's hard to follow.--[[User:Qgil|Qgil]] 17:05, 1 October 2010 (UTC)
# Get ARM stakeholders directly involved in the MeeGo project to start accruing merits.--[[User:Qgil|Qgil]] 17:05, 1 October 2010 (UTC)
# Invite and highlight the participation of ARM related topics and speakers in MeeGo events (happening already, more needed).--[[User:Qgil|Qgil]] 17:05, 1 October 2010 (UTC)
# Get MeeGo speakers in ARM related events, from the ARM community and its stakeholders (proposals?).--[[User:Qgil|Qgil]] 17:05, 1 October 2010 (UTC)
# Offer the participation in MeeGo working groups to companies involved in MeeGo products.--[[User:Qgil|Qgil]] 17:05, 1 October 2010 (UTC)
# Get ARM development products into the hands of MeeGo developers free or at discount! See http://forum.meego.com/showthread.php?p=14202 --[[User:Texrat|Texrat]] 19:44, 1 December 2010 (UTC)

[[Category:Hardware]]

OBS

2011-03-29T10:06:32Z

Jeremiah:

'''Open Build Service (OBS)'''

The OBS (Open Build Service) is a build management system written for the community by openSuse/Novell.

MeeGo has two main OBS setups:
* The [[Core OBS]] : https://build.meego.com/ - used by core developers to build the main MeeGo distribution; accounts provided to anyone who earns commit rights to a MeeGo package.
* The [[OBS/Community OBS|Community OBS]] : https://build.pub.meego.com/ - used by MeeGo community members to build opensource applications and libraries

Additionally vendors may have private OBS installations

OBS installations may be linked to each other so that software build on a vendor OBS or the community OBS may refer to and track software packages being developed on the core OBS.

Whilst the OBS does the bulk of the compiling and building there is additional QA, automation and test infrastructure used by the MeeGo Project : The [[Build Infrastructure]] article has more details.

'''Get a Community OBS account'''

https://build.pub.meego.com/user/register_user

'''Setup a local test instance'''

There is a wiki article on how to [[OBS setup|setup a Build Service of your own]] - note that you don't need to do this to build locally; it's only usually needed by vendors.

User talk:Tgraydon/Kickstart BOSS

2011-03-23T15:11:20Z

Jeremiah:

Is there more info on BOSS?
(Found some, there is some on the wiki)

User talk:Tgraydon/Kickstart BOSS

2011-03-23T15:04:48Z

Jeremiah: Created page with "Is there more info on BOSS?"

Is there more info on BOSS?

Core OBS

2011-03-22T10:52:34Z

Jeremiah: Created page

This page describes the core OBS.

It outlines the nature of the tool, describes the composition of the core OBS team, and delineates the points of contact and governance.

Technical Steering Group meetings

2011-03-22T09:05:09Z

Jeremiah: /* Next TSG meeting */

== Meeting Logistics ==

Until further notice, the Technical Steering Group meets every other Wednesday at 20:00 UTC for one hour.

All TSG meetings take place in the MeeGo [http://meego.com/community/irc-channel IRC channels]:
* Main meeting: #meego-meeting
* Back channel & other discussions (optional): #meego

== Next TSG meeting ==

Meetings are currently scheduled on an ad hoc basis.

'''Agenda'''
* IVI WG Nominations - Presented by Rudolf Streif
** Pelagicore - Representative: Mikael Söderberg
** Visteon - Representative: Pavel Konopelko
** Note: [http://wiki.meego.com/In-vehicle Intel, Linux Foundation and Nokia representatives] already nominated in prior TSG.
* Handset WG Nominations - Presented by Ibrahim Haddad
** China Mobile - Representative Yonghui Wang (Robert)
** Intel - Representative: Lilian Zia
** LGE - Representatives Hotaek Jung and Wol-Chul Choi
** Nokia - Representative: Sami Pienimäki
* Smart TV WG Nominations - Presented by Rudolf Streif
** WG lead: Narm Gadiraju (Intel)
** Amino - Representative: Kevin Lingley
** Intel - Representative: Dominique Le Foll
** JetHead Development - Representative: John Stebbins
** Linux Foundation - Representative: Rudolf Streif
** Locatel - Representative: Thomas Wentzel
** MIPS Technologies - Representative: Paolo Masini
** Nokia - Representative: Dilip Kenchammana
** Nokia Siemens Networks - Representative: Wade Goudie
** Telecom Italia - Representative: Nico Tiberi
** Videon Central - Representative: Jim Condon
** Ysten - Representative: Peter Zhang
* All other business (Open Items and General Questions)

Note: Learn more about the [[Working Group Process]]

== TSG Meeting Process ==

TSG presenters should read the [[Technical_Steering_Group_meetings/Instructions_for_presenters|Instructions for presenters]] document several days in advance of the meeting to make sure that you meet the advance preparation deadlines.

TSG meetings are unmoderated. Please stay on topic, hold your questions until we ask for them, keep it constructive and give the TSG time to respond before posting new questions (one question at a time, please). All questions should also be prefaced with 'QUESTION:'

We may turn moderation on during the meeting if needed to keep it on track.

== Backlog of Proposed Topics ==

* Final compliance spec for approval (Mark Skarpness)
* Community OBS and Apps Nominations (David Greaves and Niels Breet)
* Compliance process approval (Ibrahim Haddad)

== Propose a topic ==
Follow these instructions and your topic will be addressed in a TSG meeting sooner or later.

* Make sure your topic is on-topic. The TSG meetings handle project-level decisions, nominations, escalated disputes and, in general, anything the dependent teams are not able to solve themselves. Check the [http://meego.com/about/governance MeeGo governance] for more information.
* Your topic proposal contains a title linking to a relevant page, and the names of the team or individuals proposing that topic, linking to their meego.com pages/profiles.
* If the topic involves pre-agreements with teams or disputes the TSG needs to resolve, they must be detailed in the page linked.
* The people behind the proposal need to take part in the TSG meeting. If you can't make it on a certain scheduled meeting, please specify.

=== Resolution ===
* The TSG members pick the topics to be discussed in the next TSG meeting.
* The agenda is frozen approximately 24h before the meeting.
* Topics proposed might be addressed through other channels as well, being answered by TSG members through other channels or being forwarded to the right team.

== Meeting Logs ==
TSG discussion logs are archived.
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-18-14.58.html March 18, 2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-26-20.00.html January 26, 2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-12-15-19.58.html December 15, 2010]

* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-12-01-20.02.html December 1, 2010]

* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-10-20.00.html November 10, 2010]

* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-10-27-19.00.html October 27, 2010]

* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-10-13-18.56.html October 13, 2010]

* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-15-19.01.html September 15, 2010]

* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-01-18.57.html September 1, 2010]

* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-08-18-18.58.html August 18, 2010]

* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-30-18.59.html June 30, 2010]

* June 23, 2010 - [http://wiki.meego.com/index.php?title=MeeGo-Meeting_IRC_Schedule&oldid=4306 Rescheduled for June 30]

* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-09-19.03.html June 9, 2010]

* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-05-26-19.02.html May 26, 2010] - [http://wiki.meego.com/index.php?title=Technical_Steering_Group_meetings&diff=prev&oldid=2464 Announcement]

* May 19, 2010 - [http://wiki.meego.com/index.php?title=Technical_Steering_Group_meetings&diff=prev&oldid=2464 Canceled]

* May 12, 2010 - [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-05-05-18.58.html Announcement] - Canceled

* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-05-05-18.58.html May 5, 2010]

* April 28, 2010 - [http://lists.meego.com/pipermail/meego-dev/2010-April/001914.html Canceled]

* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-21-18.58.html April 21, 2010]

* April 14, 2010 - [http://lists.meego.com/pipermail/meego-dev/2010-April/001576.html Canceled]

* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-07-18.58.html April 7, 2010]

* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-03-31-19.58.html March 31, 2010]

* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-03-24-19.58.html March 24, 2010] - First meeting

* February 28, 2010 - [http://lists.meego.com/pipermail/meego-dev/2010-February/000625.html Weekly meetings "in the next week or two"]

Technical Steering Group meetings

2011-03-18T13:20:03Z

Jeremiah: /* Next TSG meeting */

== Meeting Logistics ==

Until further notice, the Technical Steering Group meets every other Wednesday at 20:00 UTC for one hour.

All TSG meetings take place in the MeeGo [http://meego.com/community/irc-channel IRC channels]:
* Main meeting: #meego-meeting
* Back channel & other discussions (optional): #meego

== Next TSG meeting ==
Next meeting March 18 at [http://www.timeanddate.com/worldclock/fixedtime.html?month=3&day=18&year=2011&hour=15&min=0&sec=0&p1=0 15:00 UTC]

'''Agenda'''
* IVI WG Nominations - Presented by Rudolf Streif
** Pelagicore - Representative: Mikael Söderberg
** Visteon - Representative: Pavel Konopelko
** Note: [http://wiki.meego.com/In-vehicle Intel, Linux Foundation and Nokia representatives] already nominated in prior TSG.
* Handset WG Nominations - Presented by Ibrahim Haddad
** China Mobile - Representative Yonghui Wang (Robert)
** Intel - Representative: Lilian Zia
** LGE - Representatives Hotaek Jung and Wol-Chul Choi
** Nokia - Representative: Sami Pienimäki
* Smart TV WG Nominations - Presented by Rudolf Streif
** WG lead: Narm Gadiraju (Intel)
** Amino - Representative: Kevin Lingley
** Intel - Representative: Dominique Le Foll
** JetHead Development - Representative: John Stebbins
** Linux Foundation - Representative: Rudolf Streif
** Locatel - Representative: Thomas Wentzel
** MIPS Technologies - Representative: Paolo Masini
** Nokia - Representative: Dilip Kenchammana
** Nokia Siemens Networks - Representative: Wade Goudie
** Telecom Italia - Representative: Nico Tiberi
** Videon Central - Representative: Jim Condon
** Ysten - Representative: Peter Zhang
* All other business (Open Items and General Questions)

Note: Learn more about the [[Working Group Process]]

== TSG Meeting Process ==

TSG presenters should read the [[Technical_Steering_Group_meetings/Instructions_for_presenters|Instructions for presenters]] document several days in advance of the meeting to make sure that you meet the advance preparation deadlines.

TSG meetings are unmoderated. Please stay on topic, hold your questions until we ask for them, keep it constructive and give the TSG time to respond before posting new questions (one question at a time, please). All questions should also be prefaced with 'QUESTION:'

We may turn moderation on during the meeting if needed to keep it on track.

== Backlog of Proposed Topics ==

* Final compliance spec for approval (Mark Skarpness): Tentatively scheduled for Feb 9.
* Community OBS and Apps Nominations (David Greaves and Niels Breet): Tentatively scheduled for Feb 23.
* Compliance process approval (Ibrahim Haddad): Tentatively scheduled for Feb 23.

== Propose a topic ==
Follow these instructions and your topic will be addressed in a TSG meeting sooner or later.

* Make sure your topic is on-topic. The TSG meetings handle project-level decisions, nominations, escalated disputes and, in general, anything the dependent teams are not able to solve themselves. Check the [http://meego.com/about/governance MeeGo governance] for more information.
* Your topic proposal contains a title linking to a relevant page, and the names of the team or individuals proposing that topic, linking to their meego.com pages/profiles.
* If the topic involves pre-agreements with teams or disputes the TSG needs to resolve, they must be detailed in the page linked.
* The people behind the proposal need to take part in the TSG meeting. If you can't make it on a certain scheduled meeting, please specify.

=== Resolution ===
* The TSG members pick the topics to be discussed in the next TSG meeting.
* The agenda is frozen approximately 24h before the meeting.
* Topics proposed might be addressed through other channels as well, being answered by TSG members through other channels or being forwarded to the right team.

== Meeting Logs ==
TSG discussion logs are archived.
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-26-20.00.html January 26, 2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-12-15-19.58.html December 15, 2010]

* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-12-01-20.02.html December 1, 2010]

* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-10-20.00.html November 10, 2010]

* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-10-27-19.00.html October 27, 2010]

* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-10-13-18.56.html October 13, 2010]

* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-15-19.01.html September 15, 2010]

* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-01-18.57.html September 1, 2010]

* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-08-18-18.58.html August 18, 2010]

* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-30-18.59.html June 30, 2010]

* June 23, 2010 - [http://wiki.meego.com/index.php?title=MeeGo-Meeting_IRC_Schedule&oldid=4306 Rescheduled for June 30]

* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-09-19.03.html June 9, 2010]

* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-05-26-19.02.html May 26, 2010] - [http://wiki.meego.com/index.php?title=Technical_Steering_Group_meetings&diff=prev&oldid=2464 Announcement]

* May 19, 2010 - [http://wiki.meego.com/index.php?title=Technical_Steering_Group_meetings&diff=prev&oldid=2464 Canceled]

* May 12, 2010 - [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-05-05-18.58.html Announcement] - Canceled

* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-05-05-18.58.html May 5, 2010]

* April 28, 2010 - [http://lists.meego.com/pipermail/meego-dev/2010-April/001914.html Canceled]

* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-21-18.58.html April 21, 2010]

* April 14, 2010 - [http://lists.meego.com/pipermail/meego-dev/2010-April/001576.html Canceled]

* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-07-18.58.html April 7, 2010]

* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-03-31-19.58.html March 31, 2010]

* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-03-24-19.58.html March 24, 2010] - First meeting

* February 28, 2010 - [http://lists.meego.com/pipermail/meego-dev/2010-February/000625.html Weekly meetings "in the next week or two"]

User:Jeremiah

2011-03-11T13:42:01Z

Jeremiah: /* Documentation in progress */

OHAI

This is the MeeGo wiki page for Jeremiah C. Foster. I am the MeeGo IVI Release Manger. I am a Free Software developer working for Pelagicore AB in Gothenburg, Sweden.

This wiki page serves as a "stack" of todo items. This stack lists things I have to do as MeeGo IVI Release Manager. Since this is a wiki, feel free to place things on this stack if you think that there are something I should focus on. Feel free to place general MeeGo issues in the MeeGo bug and feature trackers, but certainly if you feel that your concern is not appropriate for those resources, place a note here.

=== *Stack* ===

==== 1.2 Release ====
# Test the state of the most recent releases on the ARM platform (Beagle)
#* Jan-Simon is helping with a kickstart file for the Beagleboard
#* I've contacted Anas and Tracy about maintainership of the kickstart file in gitorious
#** Should have access to the Gitorious repo which stores "official" kickstart files
# Document how a release is created
#* see if there is a general MeeGo release document to start from

==== 1.3 Release ====
# Get a content map onto the wiki

=== Documentation in progress ===

[[recompile_kernel|Recompiling the MeeGo kernel]] 
[[changing_desktops|Changing the UX on IVI]] 
[[ivi_release|IVI release creation]]

User:Jeremiah

2011-03-11T13:41:14Z

Jeremiah: /* Documentation in progress */

OHAI

This is the MeeGo wiki page for Jeremiah C. Foster. I am the MeeGo IVI Release Manger. I am a Free Software developer working for Pelagicore AB in Gothenburg, Sweden.

This wiki page serves as a "stack" of todo items. This stack lists things I have to do as MeeGo IVI Release Manager. Since this is a wiki, feel free to place things on this stack if you think that there are something I should focus on. Feel free to place general MeeGo issues in the MeeGo bug and feature trackers, but certainly if you feel that your concern is not appropriate for those resources, place a note here.

=== *Stack* ===

==== 1.2 Release ====
# Test the state of the most recent releases on the ARM platform (Beagle)
#* Jan-Simon is helping with a kickstart file for the Beagleboard
#* I've contacted Anas and Tracy about maintainership of the kickstart file in gitorious
#** Should have access to the Gitorious repo which stores "official" kickstart files
# Document how a release is created
#* see if there is a general MeeGo release document to start from

==== 1.3 Release ====
# Get a content map onto the wiki

=== Documentation in progress ===

[[recompile_kernel|Recompiling the MeeGo kernel]] 
[[changing_desktops|Changing the UX on IVI]]
[[ivi_release|IVI release creation]]

User:Jeremiah

2011-03-11T13:40:12Z

Jeremiah: /* 1.2 Release */

OHAI

This is the MeeGo wiki page for Jeremiah C. Foster. I am the MeeGo IVI Release Manger. I am a Free Software developer working for Pelagicore AB in Gothenburg, Sweden.

This wiki page serves as a "stack" of todo items. This stack lists things I have to do as MeeGo IVI Release Manager. Since this is a wiki, feel free to place things on this stack if you think that there are something I should focus on. Feel free to place general MeeGo issues in the MeeGo bug and feature trackers, but certainly if you feel that your concern is not appropriate for those resources, place a note here.

=== *Stack* ===

==== 1.2 Release ====
# Test the state of the most recent releases on the ARM platform (Beagle)
#* Jan-Simon is helping with a kickstart file for the Beagleboard
#* I've contacted Anas and Tracy about maintainership of the kickstart file in gitorious
#** Should have access to the Gitorious repo which stores "official" kickstart files
# Document how a release is created
#* see if there is a general MeeGo release document to start from

==== 1.3 Release ====
# Get a content map onto the wiki

=== Documentation in progress ===

[[recompile_kernel|Recompiling the MeeGo kernel]] 
[[changing_desktops|Changing the UX on IVI]]

User:Jeremiah

2011-03-09T17:39:33Z

Jeremiah: /* *Stack* */

OHAI

This is the MeeGo wiki page for Jeremiah C. Foster. I am the MeeGo IVI Release Manger. I am a Free Software developer working for Pelagicore AB in Gothenburg, Sweden.

This wiki page serves as a "stack" of todo items. This stack lists things I have to do as MeeGo IVI Release Manager. Since this is a wiki, feel free to place things on this stack if you think that there are something I should focus on. Feel free to place general MeeGo issues in the MeeGo bug and feature trackers, but certainly if you feel that your concern is not appropriate for those resources, place a note here.

=== *Stack* ===

==== 1.2 Release ====
# Test the state of the most recent releases on the ARM platform (Beagle)
#* Jan-Simon is helping with a kickstart file for the Beagleboard
#* I've contacted Anas and Tracy about maintainership of the kickstart file in gitorious
# Document how a release is created
#* see if there is a general MeeGo release document to start from

==== 1.3 Release ====
# Get a content map onto the wiki

=== Documentation in progress ===

[[recompile_kernel|Recompiling the MeeGo kernel]] 
[[changing_desktops|Changing the UX on IVI]]

User:Jeremiah

2011-03-09T14:42:25Z

Jeremiah: /* 1.3 Release */

OHAI

This is the MeeGo wiki page for Jeremiah C. Foster. I am the MeeGo IVI Release Manger. I am a Free Software developer working for Pelagicore AB in Gothenburg, Sweden.

This wiki page serves as a "stack" of todo items. This stack lists things I have to do as MeeGo IVI Release Manager. Since this is a wiki, feel free to place things on this stack if you think that there are something I should focus on. Feel free to place general MeeGo issues in the MeeGo bug and feature trackers, but certainly if you feel that your concern is not appropriate for those resources, place a note here.

=== *Stack* ===

==== 1.2 Release ====
# Test the state of the most recent releases on the ARM platform (Beagle)
# Document how a release is created
#* see if there is a general MeeGo release document to start from

==== 1.3 Release ====
# Get a content map onto the wiki

=== Documentation in progress ===

[[recompile_kernel|Recompiling the MeeGo kernel]] 
[[changing_desktops|Changing the UX on IVI]]

User:Jeremiah

2011-03-09T14:42:11Z

Jeremiah: /* 1.2 Release */

OHAI

This is the MeeGo wiki page for Jeremiah C. Foster. I am the MeeGo IVI Release Manger. I am a Free Software developer working for Pelagicore AB in Gothenburg, Sweden.

This wiki page serves as a "stack" of todo items. This stack lists things I have to do as MeeGo IVI Release Manager. Since this is a wiki, feel free to place things on this stack if you think that there are something I should focus on. Feel free to place general MeeGo issues in the MeeGo bug and feature trackers, but certainly if you feel that your concern is not appropriate for those resources, place a note here.

=== *Stack* ===

==== 1.2 Release ====
# Test the state of the most recent releases on the ARM platform (Beagle)
# Document how a release is created
#* see if there is a general MeeGo release document to start from

==== 1.3 Release ====
#* Get a content map onto the wiki

=== Documentation in progress ===

[[recompile_kernel|Recompiling the MeeGo kernel]] 
[[changing_desktops|Changing the UX on IVI]]

User:Jeremiah

2011-03-09T14:41:32Z

Jeremiah: /* *Stack* */

OHAI

This is the MeeGo wiki page for Jeremiah C. Foster. I am the MeeGo IVI Release Manger. I am a Free Software developer working for Pelagicore AB in Gothenburg, Sweden.

This wiki page serves as a "stack" of todo items. This stack lists things I have to do as MeeGo IVI Release Manager. Since this is a wiki, feel free to place things on this stack if you think that there are something I should focus on. Feel free to place general MeeGo issues in the MeeGo bug and feature trackers, but certainly if you feel that your concern is not appropriate for those resources, place a note here.

=== *Stack* ===

==== 1.2 Release ====
#* Test the state of the most recent releases on the ARM platform (Beagle)
#* Document how a release is created

==== 1.3 Release ====
#* Get a content map onto the wiki

=== Documentation in progress ===

[[recompile_kernel|Recompiling the MeeGo kernel]] 
[[changing_desktops|Changing the UX on IVI]]

User:Jeremiah

2011-03-09T14:40:07Z

Jeremiah: /* *Stack* */

User:Jeremiah

2011-03-09T11:12:06Z

Jeremiah: /* *Stack* */

User:Jeremiah

2011-03-09T11:09:58Z

Jeremiah:

User:Jeremiah

2011-03-09T11:08:47Z

Jeremiah:

In-vehicle

2011-02-14T12:31:28Z

Jeremiah: /* 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]'''
*** Nokia: '''[http://meego.com/users/alistair Alistair Adams]'''

* 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)]'''

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.

=== Roadmap ===

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

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

[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 at [http://wiki.meego.com/In-vehicle/Roadmap Roadmap Details]

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

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

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

'''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, IDE, 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.
:The suggested reference platform is the Beagleboard xM. The Pandaboard 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
|-
|}

=== Releases ===
* [http://meego.com/downloads/releases/1.0/meego-v1.0-in-vehicle-infotainment-ivi MeeGo IVI 1.0]
* [http://meego.com/downloads/releases/1.1/meego-v1.1-in-vehicle-infotainment-ivi MeeGo IVI 1.1]
== 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/
* [http://wiki.meego.com/IVI IVI for users and developers]
* [http://wiki.meego.com/IVITopic Topics]

In-vehicle

2011-02-14T12:30:47Z

Jeremiah: /* 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]'''
*** Nokia: '''[http://meego.com/users/alistair Alistair Adams]'''

* 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)]'''

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.

=== Roadmap ===

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

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

[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 at [http://wiki.meego.com/In-vehicle/Roadmap Roadmap Details]

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

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

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

'''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, IDE, 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.

ARM
:The suggested reference platform is the Beagleboard xM. The Pandaboard 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
|-
|}

=== Releases ===
* [http://meego.com/downloads/releases/1.0/meego-v1.0-in-vehicle-infotainment-ivi MeeGo IVI 1.0]
* [http://meego.com/downloads/releases/1.1/meego-v1.1-in-vehicle-infotainment-ivi MeeGo IVI 1.1]
== 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/
* [http://wiki.meego.com/IVI IVI for users and developers]
* [http://wiki.meego.com/IVITopic Topics]

In-vehicle

2011-01-27T09:42:37Z

Jeremiah: /* Resources */ (Added mailing lists and IRC channel.)

ARM/Meego on Qemu

2011-01-26T16:24:13Z

Jeremiah: /* Prerequisites */

'''Under construction, experimental and unsupported'''

QEMU offers one an easy way to try out MeeGo on ARM

== Building QEMU ==

=== Prerequisites ===
* git (to get the source code)
* build-essential
* zlib (called zlib-bin and zlib1g-dev under Debian Squeeze)
* SDL-devel libraries.

git clone git://gitorious.org/qemu-maemo/qemu.git
cd qemu
./configure --target-list=arm-softmmu --enable-sdl
make

The qemu binary will appear as arm-softmmu/qemu-system-arm
(Note: if you experience this message "cc1: warnings being treated as errors" during compilation, you can get around it with passing "--disable-werror" to "configure" as an argument)

== Downloading MeeGo image ==

The MeeGo QEMU needs a NAND image prepared for QEMU ( meego_qemu_nand.img.gz ), which is available for N900 owners from:

http://tablets-dev.nokia.com/meego-codedrop.php

Uncompress the image with "gunzip" command.

== Starting QEMU ==

qemu-system-arm -M n900 -mtdblock meego_qemu_nand.img -serial stdio -clock unix

You can then log in with root/meego.

ARM/Meego on Qemu

2011-01-26T16:22:17Z

Jeremiah: /* Building QEMU */

'''Under construction, experimental and unsupported'''

QEMU offers one an easy way to try out MeeGo on ARM

== Building QEMU ==

=== Prerequisites ===
* git (to get the source code)
* build-essential
* zlib (called zlib-bin and zlib1g-dev under Debian Squeeze)
* SDL-devel libraries.

git clone git://gitorious.org/qemu-maemo/qemu.git
cd qemu
./configure --target-list=arm-softmmu --enable-sdl
make

The qemu binary will appear as arm-softmmu/qemu-system-arm
(Kind note: if you shall experience this note "cc1: warnings being treated as errors" during compilation, you could get around it with feeding "--disable-werror" to "configure")

== Downloading MeeGo image ==

The MeeGo QEMU needs a NAND image prepared for QEMU ( meego_qemu_nand.img.gz ), which is available for N900 owners from:

http://tablets-dev.nokia.com/meego-codedrop.php

Uncompress the image with "gunzip" command.

== Starting QEMU ==

qemu-system-arm -M n900 -mtdblock meego_qemu_nand.img -serial stdio -clock unix

You can then log in with root/meego.

ARM/Meego on Beagleboard from scratch

2010-12-23T16:20:41Z

Jeremiah: /* Related links */

This document describes how to create a MeeGo image for the beagleboard. 
More information regarding MeeGo on the Beagleboard can be found at [[ARM/Meego_on_the_Beagle]].

[[http://www.youtube.com/watch?v=LdKcNOrC5e4 Youtube video of BeagleBoard running MeeGo handset UX]]

= Introduction =

== Tested distros ==

Creating this image has been tested on Ubuntu 10.10, other distros may require some things to be done
differently. Several people have tried and failed to make this work on Ubuntu 9.04 and Ubuntu 9.10. Ubuntu 10.04 requires some tweaks when installing the cross compilers. It is recommended to use Ubuntu 10.10, if you want the best chance of success. Conversely, if you have made this work for other versions of Ubuntu or other distros,
please add to this page any information that will help others achieve the same success.

* Debian Lenny (you'll need to install some packages from Sid and you'll need to build some software.)

This is a work in progress. However, if you think these instructions are incomplete
or lack some important aspect, feel free to edit this page or ask for help on
IRC in <nowiki>#meego-arm</nowiki> on <nowiki>irc.freenode.net</nowiki>.

== What works, what remains to be done ==

Please keep in mind that MeeGo is a work in progress. Things which already worked may be broken again and you might not end up with a working setup even though you followed the instructions precisely. Everything up to the running TI demos will likely be stable, but the MeeGo UI itself is still broken every now and then.

Working:
* Same features as MeeGo on n900
* MeeGo handset UX with touchscreen
* 2D/3D video acceleration
* Audio
* Various USB add-ons incl. ethernet, mass-storage and bluetooth
* Setup toolchain known working on Ubuntu 10.04/10.10

Todo:
* Make mouse cursor visible under MeeGo HX for users without touchscreen
* Definitive works / does not work on other distros and other versions

Known issues:
* No beagleboard specific problems known, all known n900 problems still apply

== Supported BeagleBoard versions ==

The '''RevA''' and '''RevB''' boards have only 128MB RAM. This is not enough for the handset distribution of MeeGo. With swap enabled the UX boots, but is barely usable. Tested board revisions: B7

The '''RevC''' boards are the best choice at this moment as their hardware is fully supported by the Linux kernel and since their 256MB RAM allow for a more fluid UX experience. Tested board revisions: C4

The '''XM RevA''' boots into handset UX and is very fast and responsive. The stock kernel doesn't yet fully support this board (CPU only runs at 800Mhz) and most important, the USB hub doesn't work under the MeeGo kernel. Tested board revisions: XM-A2

'''The only board currently fully supported is the BeagleBoard RevC!'''

== Prerequisites ==

This document assumes that you have worked with the beagleboard
before and it may be helpful if you e.g. know how to format a memory card to boot from.

If you are new to BeagleBoard you might want to learn the basics using the following resources:
* [http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat Step by Step SD card formatting from scratch].
* [http://elinux.org/BeagleBoardBeginners eLinux.org BeagleBoard beginners guide]
* [http://elinux.org/BeagleBoard eLinux BeagleBoard main page]
* [http://beagleboard.org/ BeagleBoard.org home page]

The following instructions assume that your beagleboard boots from sd card. Xloader and uboot versions stored in beagleboard internal nand memory might prevent the following setup from working properly. If a bootloader is installed, you'll usually get its command prompt on the serial console when booting without sd card inserted. Entering

<pre>
nand erase
</pre>

there will erase the entire nand memory and reset the beagleboard into the state expected in the following instructions. Warning: Other beagleboard sd cards you might be using may rely on certain parts being store in nand and might not work anymore afterwards.

Please use a memory card of at least 2GB size for the following experiments. Otherwise the generated image may not fit onto the card.

= Building MeeGo for the BeagleBoard =

The beagleboard sd card image generation consists of three major steps:
* Build of kernel and kernel modules
* Assembly of root file system
* Installation of bootloader, kernel and root file system on sd card

Shell scripts have been created to automate all of these steps as much as possible. You can download an archive containing those scripts [http://wiki.meego.com/images/Meego_beagle.tgz here]. Unpack the contents of this somewhere into your hard disk. The following steps will require about 4GB of additional free disk space.

This archive contains three shell scripts, each of them performing one of the three steps outlined before:
* build_kernel.sh build the kernel and the modules,
* build_image.sh assembles the root file system, and
* setup_sdcard.sh creates an sd card from these

== Build of kernel and kernel modules ==

To build the kernel and its modules, you'll need to [http://en.wikipedia.org/wiki/Cross_compiler cross compile] for the ARM platform. The most convenient option under Ubuntu is to install the arm cross compiler that comes with ubuntu:

<pre>
sudo apt-get install gcc-4.5-arm-linux-gnueabi
</pre>

The MeeGo kernel source code is downloaded and compiled using the build_kernel.sh shell script:

<pre>
./build_kernel.sh
</pre>

All downloaded files go into the ./downloads directory, temporary build files are created in ./build and the resulting kernel will be placed in the ./deploy directory. If you are low on disk space, you can delete the ./downloads and ./build directories after the kernel has successfully been built.

=== Setup for Ubuntu 10.04 LTS Lucid Lynx ===
The gnueabi cross compiler is not available by default on the Lucid Lynx distribution. But you can get access to it using either the natty or maverick universe repositories (just be careful to disable them when you are done getting what you need).

Add the following line to your /etc/apt/sources.list. Or use the Synaptic package manager (sudo synaptic, Settings->Repositories, Other Software->Add). You may choose your own mirror if xmission is slow or doesn't work for you.
<pre>
deb http://mirrors.xmission.com/ubuntu/ maverick main universe >> /etc/apt/sources.list
</pre>
Do an update (hit Reload in synaptic or sudo apt-get update) and then install the gnueabi cross compiler + a few other programs that might be missing:
<pre>
sudo apt-get install gcc-4.5-arm-linux-gnueabi rpm2cpio uboot-mkimage
</pre>

== Assembly of the root file system ==

The root file system (rootfs) is assembled from binary packages available in the MeeGo ARM repositories. The tool used to assemble the rootfs is called mic (MeeGo image creator).
Follow the instructions at [[Image_Creation#From_Development_Git_Tree]] to install the latest version from git. Older versions will probably not work.

When using ubuntu 10.04/10.10 you'll need to install qemu using the
qemu-kvm-extras-static package. If you have an existing scratchbox setup,
this will collide with qemu-kvm-extras-static. After installing that
package scratchbox arm will not work anymore. Removing that package and
restarting the scratchbox services makes scratchbox work again.

The rootfs will also include the kernel modules. Thus the kernel has already to be built before starting the rootfs image assembly.

The rootfs image creation itself is started by the following command:

<pre>
sudo ./build_image.sh
</pre>

This will download all packages required to build the root file system from the internet into the ./mycachedir directory and assemble the root file system image in the ./daily directory.

If you need to save hard disk space you can remove the ./mycachedir directory once the image has successfully been built.

== Installation on sd card ==

The last step is to put the kernel and the rootfs onto an sd card together with an xloader and uboot boot loader as required to boot the beagleboard. This is accomplished by invoking the third shell script. This script has to be given the device name of the sd card you are intending to use. On my system the sd card is /dev/sdd, so i have to invoke the script as follows:

<pre>
./setup_sdcard.sh --mmc /dev/sdd
</pre>

The script will as you to acknowledge this. Please watch the output carefully. Specifying e.g. your systems hard drive will wipe your entire hard disk instead of the sd card.

This will take some time as the sd card is reformatted, all bootloaders are installed, file systems are created and the kernel and the contents of the root file system are copied onto the sd card.

== Boot ==

Plug the resulting SD card into your beagleboard and power on. After a few seconds the video will switch to 800x480 pixels and the MeeGo handset UX should appear on the screen. The first boot will always take several minutes as some media files are copied forth and back on the card.

[[File:Meego_beagle.jpg]]

= Peripheral hardware =

I have tested various peripheral devices on this setup and most of them
are working out of the box.

== USB hubs, mice and keyboards ==

These just work, nothing to configure.

On the BB-XM the built-in USB hub is not detected and not working. This is currently being investigated as this worked well with previous non-MeeGo kernel versions and is broken since we switched to the MeeGo kernel line. The OTG port works and can be equipped with an external hub as a temporary work-around.

== Bluetooth keyboard ==

My CSR bluetooth dongle works out of the box. Hcitool is present to scan for devices as well
as hidd to connect to bluetooth HID devices. This has been tested with a bluetooth
keyboard.

== Touchscreen ==

My 7 inch egalax based touchscreen worked nearly perfectly out of the box. It was just a little bit mis-calibrated.

The latest hal driven xorg can be given a input configuration file to deal with this.An example setup is already included at /etc/X11/xorg.conf.d/50-input-touch.conf. If you don't have a touchscreen this file is ignored.

This configuration is automatically applied to all touchscreen devices that map to /dev/input/event*. You may have to adjust the calibration values in that file to match your device.

== Ethernet ==

A D-Link DUB-E100 ethernet dongle works out of the box and gets an IP address via DHCP. With this network connection i was able to verify that zypper and the package management also work. A "zypper up" successfully updated a few packages.

The beagleboard XM's onboard Ethernet (a SMSC95xx based USB device) cannot be tested with the MeeGo kernel since the USB hub it is connected to currently isn't supported.

== WLAN ==

A Ralink RT2501 based USB dongle works, is detected and can scan for networks. But it isn't provided an address via dhcp.

== Audio ==

Audio works out of the box. Appropriate configuration files for the beagleboard have been included.

= Troubleshooting/hints =

== Starting X programs from the serial console ==

If you have a keyboard and mouse you can skip this section. If you don't have a keyboard connected and want to run X programs from the console, you need to set the DISPLAY environment variable. Also it's required to change to the meego user before doing so:

<pre>
[root@localhost ~]# su meego
[meego@localhost root]$ export DISPLAY=:0
[meego@localhost root]$ widgetsgallery
</pre>

== Making screenshots ==

Do you like what you see? Want to share it? Make a screenshot! This doesn't need any
special software. Just copy the framebuffer contents into some file:

<pre>
cp /dev/fb0 screenshot.raw
</pre>

The resulting file should have a size of exactly 770048 bytes (800x480x2) if you are using a 800x480
display size at 16 bits per pixel.

On your host use ffmpeg to convert this into some standard format like png:

<pre>
ffmpeg -vcodec rawvideo -f rawvideo -pix_fmt rgb565 -s 800x480 -i screenshot.raw -f image2 -vcodec png screenshot.png
</pre>

[[File:Beagle-Main.jpg]]

Screenshot of an early handset UX on beagle (jul 2010)

[[File:Beagle-Ivi.png]]

Screenshot of IVI UX on beagle (nov 2010)

= Related links =

* [http://www.alwaysinnovating.com/wiki/index.php/MeeGo Meego in the touchbook]
* [http://processors.wiki.ti.com/index.php/GSG:_Rebuilding_the_Software#Building_the_OMAP35x_Graphics_Demo_Software SGX SDK rebuild instructions]
* [http://elinux.org/BeagleBoard Beagleboard on elinux]
* [http://elinux.org/BeagleBoardUbuntu Beagleboard Ubuntu inkl. bzr kernel howto]

Image Creation

2010-12-22T17:57:19Z

Jeremiah: /* Installing requirements for Ubuntu 10.04 */

= Overview =

This is the main Image Creator developer's guide. For a more simplistic, step-by-step document, go to: [[Image Creation For Beginners]].

The tool used to create MeeGo images is something called "MIC2" (for distinguishing from obsolete MIC - Moblin Image Creator). MIC is composed of a series of tools to create images, convert images and do some development work on MeeGo. MIC2 is based primarily on Fedora livecd-tools and appliance-tools.

With MIC2 tools, users can create different types of images for different purposes, including live CD images, live USB images, raw images for KVM, VMDK images for Vmware, vdi images for VirtualBox, loop images for IVI platforms, NAND images for Moorestown platforms, ubi images for N900, fs image for MeeGo developers. Also, users can use MIC2 tools to manipulate images like transforming an image from a virtual machine to a live image, and providing a chroot environment based on an existing live image. With these features, developers can do development work on a host virtual machine running MeeGo or a Meego chroot environment, and transfer the resulting new live image to a target device for final debug/verification.

This document discusses only features, usage guide, and known issues.

= Features =

MIC2 offers these major tools:
* mic-image-creator: create images.
* mic-image-convertor: convert a raw/vmdk/vdi/live image into a live image.
* mic-chroot: provide a MeeGo environment from a live/loop image for development, it also can translate that chroot file system into a live image.
* mic-image-writer: write a MeeGo image to a USB disk. This is a safe alternative to dd.

The following support is provided:

* Supports mainstream Linux distros. MIC2 has been thoroughly tested on these distributions:
** Meego
** Fedora (Fedora 10 and above)
** Opensuse (> OpenSUSE 11.1)
** and Ubuntu > 9.04
* Supports various types of images: livecd, liveusb, loop, raw, vmdk, nandmrst, vdi, fs, ubi
* Supports image coversion from virtual machine/live images to live images.
* Uses kickstart (.ks) files for image creation. Through this, users can specify which software repositories to use, which packages to install and basic system configuration directives. Please refer to http://fedoraproject.org/wiki/Anaconda/Kickstart for more information about kickstart configuration files.

= Usage =

== Requirements ==

To be able to use MIC2, your host machine to run mic2 must have Intel(r) Atom(tm) or Intel(r) Core(tm) 2 CPU (support for SSSE3), this is a hard requirement (ARM image is exceptional), the following packages must be available on your system. (Most of the packages are installed by default, depending on the distribution.):

* yum
* rpm
* kpartx
* parted
* syslinux
* isomd5sum
* kvm
* zlib-devel(for compiling)
* python-devel(for installation)

You should load these modules as well, if not loaded automatically by the kernel:
 (Use <code>lsmod</code> to list modules.)

* squashfs
* squashfs-tools
* dm_snapshot
* loop

Specific packages for Fedora:

* pykickstart
* device-mapper

Specific packages for Ubuntu 8.10:

* python-celementtree
* python-elementtree
* dmsetup

=== Installing requirements for Ubuntu 10.04 ===

sudo apt-get install yum rpm kpartx parted syslinux isomd5sum kvm zlib1g-dev squashfs-tools python2.6-dev qemu-arm-static

== Installation ==

We currently build MIC2 binary rpms/debs for many popular Linux distributions, including Fedora 11, Fedora 12, Ubuntu 9.10, Ubuntu 10.04, OpenSUSE 11.1, OpenSUSE 11.2, and Debian 5.0. Please go to http://repo.meego.com/tools/repos/ to get a repository URL corresponding to your Linux distribution, then add it into your repo or package source for installation and update later. If your distribution isn't in the support list, please install MIC2 from git source.

=== Binary Package installation ===

* '''Installation Steps For Fedora 11, Fedora 12 and Fedora 13'''

1. Add MIC2 repo as user root:

<pre>
# cat <<REPO > /etc/yum.repos.d/meego-tools.repo
[meego-tools]
name=MeeGo Tools for Fedora
baseurl=http://repo.meego.com/MeeGo/tools/repos/fedora/\$releasever
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-meego
REPO
</pre>

2. Add gpg key as user root:

<pre>
# gpg2 --keyserver subkeys.pgp.net --recv 0BC7BEC479FC1F8A
# gpg2 --export --armor 0BC7BEC479FC1F8A > /etc/pki/rpm-gpg/RPM-GPG-KEY-meego
</pre>

3. Install mic2 as user root:
<pre>
# yum install mic2
</pre>

if you get asked to import the key do so:
<pre>
warning: rpmts_HdrFromFdno: Header V3 DSA/SHA1 Signature, key ID 79fc1f8a: NOKEY
meego-fedora/gpgkey | 3.3 kB 00:00 ...
Importing GPG key 0x79FC1F8A:
Userid: "Moblin Build (Moblin Build User) <build@moblin.org>"
From : /etc/pki/rpm-gpg/RPM-GPG-KEY-meego
Is this ok [y/N]: y
</pre>

* '''Update Steps For Fedora 11, Fedora 12 and Fedora 13'''

You can use the below command to get the latest mic2 package.

<pre>
# yum update mic2
</pre>

* '''Installation Steps For Ubuntu 9.10, Ubuntu 10.04 and Debian 5.0'''

1. Add package source

For Ubuntu 9.10, add the below line to /etc/apt/sources.list

<pre>
deb http://repo.meego.com/MeeGo/tools/repos/ubuntu/9.10/ /
</pre>

For Ubuntu 10.04, add the below line to /etc/apt/sources.list

<pre>
deb http://repo.meego.com/MeeGo/tools/repos/ubuntu/10.04/ /
</pre>

For Ubuntu 10.10, add the below line to /etc/apt/sources.list

<pre>
deb http://repo.meego.com/MeeGo/tools/repos/ubuntu/10.10/ /
</pre>

For Debian 5.0, add the below line to /etc/apt/sources.list

<pre>
deb http://repo.meego.com/MeeGo/tools/repos/debian/5.0/ /
</pre>

mic2 is also available in Debian Testing which will become Debian 6.0.

2. sudo apt-get update

You should see the following error:
W: GPG error: http://repo.meego.com Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0BC7BEC479FC1F8A

To add the repository public key use the following command:
:gpg --keyserver subkeys.pgp.net --recv 0BC7BEC479FC1F8A
:gpg --export --armor 0BC7BEC479FC1F8A | sudo apt-key add -

Now redo sudo apt-get update

3. sudo apt-get install mic2

* '''Installation Steps For OpenSUSE 11.1, OpenSUSE 11.2 and OpenSUSE 11.3'''

1. Add repos

For OpenSUSE 11.1:

<pre>sudo zypper addrepo http://repo.meego.com/MeeGo/tools/repos/opensuse/11.1/ meego-tools</pre>

For OpenSUSE 11.2:

<pre>sudo zypper addrepo http://repo.meego.com/MeeGo/tools/repos/opensuse/11.2/ meego-tools</pre>

For OpenSUSE 11.3:

<pre>sudo zypper addrepo http://repo.meego.com/MeeGo/tools/repos/opensuse/11.3/ meego-tools</pre>

2. sudo zypper install mic2

* '''Update Steps For OpenSUSE 11.1, OpenSUSE 11.2 and OpenSUSE 11.3'''

<pre>
sudo zypper update mic2
</pre>

=== From Stable Git Source Releases ===

You can get the latest stable release of MIC2 from the tag section in http://meego.gitorious.org/meego-developer-tools/image-creator. Click on the "Source tree" link on the top of the screen. There will be a list of tags on the right hand side.

You should follow the below steps to install it:

<pre>
git clone git://gitorious.org/meego-developer-tools/image-creator.git
cd image-creator
git checkout 0.17 #check Gitorious for the most recent tag
make
sudo make install
</pre>

=== From Development Git Tree ===

Note: MIC2 GIT tree has latest-and-greatest source, so stability is not guaranteed. If you run into errors, please use a 'Stable Release' instead before filing a bug.

You need to follow the below steps to git clone MIC2:

<pre>
git clone git://gitorious.org/meego-developer-tools/image-creator.git
</pre>

Build and install:

<pre>
cd image-creator
make clean
make
sudo make install
</pre>

You should add the repo for mic2 then run

<pre>
sudo ./tools/mic-check-alldeps
</pre>

to check/install all the depended packages, otherwise mic2 can't work normally.

== Running mic-image-creator ==

Configuration of images is based on kickstart, the format used for unattended installation in Fedora and Redhat.

Super user privileges are needed. The tool is more or less self-documented, use the --help option to see options.
<pre>
sudo mic-image-creator --help
</pre>

=== Creating Supported Image Types ===

KickStart (.ks) configuration files are passed to MIC2 to create tailored images. KickStart files specify what repos to pull from, what packages to include, what post-scripts to run and what type of images to create.

To obtain the official Meego .ks files, go here: TO-DO-LINK

'''Create ARMv7 Images'''

When creating images for ARMv7 hardware, pass ''--arch=armv7l'' to ''mic-image-creator'' commands.

'''Create Livecd Image'''

<pre>
sudo mic-image-creator --config=default.ks --format=livecd --cache=mycache
</pre>

This tells image-creator to use the kickstart file default.ks to obtain info about which packages to download and include in the image, and --cache is the directory on your local machine which will host a cache of these packages. The cache is very useful if you are remote to the server and reduces the amount of downloaded packages next time you create an image. Next time the command is run, this cache will simply be 'updated' if there are changes, rather than re-downloading from the repositories again.

The output of this command will be a file named meego-1.0-default-XX.iso created. This ISO image is a hybrid image and can be either written to a disk device or burned onto a cd.

To burn it onto a USB stick, just run the following command, assuming the USB stick is /dev/sdb in your system:

<pre>
sudo mic-image-writer meego-1.0-default-XX.iso
</pre>

'''Create Moorestown NAND Image'''

<pre>
sudo mic-image-creator --config=default.ks --format=mrstnand

remove the first 512 bytes from the image to remove the partition information.
sudo dd bs=512 skip=1 if=meego-1.0-default-XX-sda.bin of= meego-1.0-default-XX-nand.img
</pre>

'''Create Liveusb Image'''

<pre>
sudo mic-image-creator --config=default.ks --format=liveusb --cache=mycache
</pre>

A file named meego-1.0-default-XX.usbimg will be created. To burn it onto a USB stick, run the following command, assuming the USB stick is /dev/sdb in your system:

<pre>
sudo mic-image-writer meego-1.0-default-XX.usbimg
</pre>

This image has a FAT file system and can be mounted easily on Windows and other OSes.

'''Create Liveusb Image Interactively'''

<pre>
sudo mic-image-creator --config=default.ks --format=liveusb --interactive --cache=mycache
</pre>

It directly creates a MeeGo live usb stick.

Liveusb image can be created in two different ways, interactive and non-interactive (default). When running MIC2 in a non-interactive mode, MIC2 creates a USB images file that can be copied directly into a USB stick. The non-interactive mode can be used for daily build or automated testing. The interactive mode will write the images onto a USB disk, it will detect if a USB stick is available and detects and verifies a partition is available. If two or more USB devices are present, you will be asked to select the target device. This way the contents of the existing USB stick won't be destroyed unless no appropriate partition is found, end user should use it to create the live USB.

'''Create Loop Image'''

This is the simplest image format available. Such images can be loop mounted and chrooted into, for example, to build applications or for debugging purposes.

<pre>
sudo mic-image-creator --config=default.ks --format=loop --cache=mycache
</pre>

A file named meego-1.0-default-XX.img is created. You can use below to mount it and chroot into it.

<pre>
sudo mount -o loop meego-1.0-default-XX.img /mnt
sudo chroot /mnt su -
</pre>

'''Create KVM Image'''

Can be used with QEMU or other VMM applications to launch MeeGo as a virtualized instance.

<pre>
sudo mic-image-creator --config=default.ks --format=raw --cache=mycache
</pre>

A file named meego-1.0-default-XX folder with a meego-1.0-default-XX-sda.raw image is created. For optimal results, use this feature in a machine with VT support and enable it in the BIOS.

If you use Fedora or openSUSE, run the following command to launch the image into MeeGo KVM virtual machine:

<pre>
sudo qemu-kvm -m 512 -boot c -hda meego-1.0-default-XX-sda.raw -std-vga
</pre>

If you use Ubuntu, run the following command launch image:

<pre>
sudo kvm -m 512 -boot c -hda meego-1.0-default-XX-sda.raw
</pre>

'''Create VMDK Image'''

VMDK images can be loaded into Vmware or Vmware player. MIC2 also generates a VMX file that has image configuration and can be used to launch the image in Vmware by just clicking the file. If you have vmplayer, it should open automatically.

<pre>
sudo mic-image-creator --config=default.ks --format=vmdk --cache=mycache
</pre>

A file named meego-1.0-default-XX folder with both meego-1.0-default-XX-sda.vmdk image and meego-1.0-default-XX-sda.vmx is created. Just run vmware or vmware player, and select the generated vmx file.

=== KickStart Files (configuration files used for image creation) ===

KickStart (.ks) configuration files are passed to MIC2 to create tailored images. KickStart files specify what repos to pull from, what packages to include, what post-scripts to run and what type of images to create.

For more details about the kickstart format, see http://fedoraproject.org/wiki/Anaconda/Kickstart.

Note that not all KickStart directives and options are supported for creating Meego images. MIC2 also adds some specific directives and options. More explained below.

====Official Meego .ks files====

The official Meego .ks files are here:

*For ARM based Nokia N900: http://repo.meego.com/MeeGo/builds/trunk/ <version>/handset/images/meego-handset-armv7l-n900/
*For Intel Atom based netbook and handset (Moorestown): http://repo.meego.com/MeeGo/builds/trunk/ <version>/{netbook,handset,ivi}/images/<respective directory>/

You can download and use them as a base for the Meego images you create. Modify these .ks files as you wish to create tailored images.

====Modifying your .ks====

Developers may want to modify the .ks files to create their own custom images. Here are the main options and sections within the .ks file.

You can also find in-depth .ks option information here: http://fedoraproject.org/wiki/Anaconda/Kickstart#Chapter_2._Kickstart_Options

'''''Partition, Setup and Bootloader options'''''

''Example''

<pre>
lang en_US.UTF-8
keyboard us
timezone --utc America/New_York
auth --useshadow --enablemd5
part / --size 1500 --ondisk sda --fstype=ext3
rootpw meego
xconfig --startxonboot
bootloader --timeout=0 --append="quiet"
desktop --autologinuser=meego --defaultdesktop=xfce
user --name meego --groups audio,video --password meego
</pre>

These are mostly self-explanatory and set up important things such as partition size, filesystem type, kernel paramters, etc. You can change these depending on what your needs are.

'''''Repos'''''

This is where you can specify the yum repositories that you want MIC2 to search and pull your packages from which to make up your image. You can add official Meego repos, other remote repos, or your own local repos on your dev machine.

''Example''

<pre>
# This is a comment

# My first repo
repo --name=trunk --baseurl=http://mytrunk.myrepo.com

# My second repo
#repo --name=<repo-name-2> --baseurl=< url | local-repo-dir >
</pre>

'''NOTE:''' --name of the repo can be any unique alphanumeric name you give your repo, it can be anything. Just make sure you don't use the same name twice for any of the listed repos, remember they have to be unique.

To create a repo you can point to on your local developer machine, you can run the following command:

<pre>
createrepo -d <local-dir>
</pre>

Where 'local-dir' is a local directory on your machine that contains the rpms you want include in your local directory.

'''''Adding Packages and Package Groups'''''

''Example''

<pre>
%packages

# Example adding pkg groups

@Core
@X for Netbooks
@Base
@Development Tools
@<my-PkgGroup1>
@<my-PkgGroup2>

# Example adding individual pkgs

kernel-netbook
xorg-x11-server-Xorg-setuid
carrick
xorg-x11-drv-evtouch
<my-pkg-1>
<my-pkg-2>
%end

</pre>

This specifies exactly what packages will be included in your image. Package groups can be specified with a "@" preceding it, as you can see from the examples above. Package groups are defined in the 'repodata' section of a repo, under a 'comps*.xml' file. Defined therein are package group names, and what packages are included in each package group. The Meego package groups are standard, and cannot be changed. You can, however, define your own package groups in your own non-Meego repos if you are using those.

Please see here for more info on defining package groups in repositories: TO-DO-LINK

You can also add individual package names to be included in the image as you can see from the second part in the above example.

'''''Important Note about how MIC2 picks a package when different versions are available'''''

A common problem is that, let's say, a packageA has more than one version residing in a repo(s) that your .ks is pointing to.

How will the MIC2 know which one to pick?

''Example''

There exists in the repo(s) these different versions of PackageA:

PackageA-1.0

PackageA-2.0

PackageA-3.0

MIC2 will pick the PackageA with the highest version number (PackageA-3.0 in this case).

There is one way to get around that, and that is to set the 'Epoch' version within a package .spec file.

<pre>
Example (works in both .spec and .yaml file)

Name: <name>
Summary: <summary>
Epoch: 1
Version: <version>

</pre>

MIC2 will first look to compare the 'Epoch' version of the packages. All Meego official packages do not include an 'Epoch' version, so if you set the 'Epoch' number within your .spec file to any positive integer, no matter if your package version is smaller, MIC2 will choose your package.

So back to our example.

''Example''

PackageA-1.0 (Epoch not set)

PackageA-2.0 (Epoch = 1)

PackageA-3.0 (Epoch not set)

MIC2 will choose PackageA-2.0 in this case. And it follow that:

''Example''

PackageA-1.0 (Epoch=100)

PackageA-2.0 (Epoch = 1)

PackageA-3.0 (Epoch not set)

MIC2 will choose PackageA-1.0.

Remember that Meego packages will not have 'Epoch' set, so chances are that if you set 'Epoch' in your own package to any positive integer, it will be the one MIC2 chooses to pull down and include in an image.

'''''Removing Packages'''''

If you would like to make sure that a pkg is _not_ included, you can specify that with a '-' preceding the package name.

''Example''
<pre>
%packages

# Example pkg groups

@Core

# Example adding individual pkgs

kernel-netbook

# Example removing individual pkgs

-carrick
-package-xyz

%end
</pre>

with the above example, packages 'carrick' and 'package-xyz' will _not_ be included in the image.

'''Note:''' all packages that depend on the package you want to remove should also be removed, or else MIC2 will ignore your request to remove that package from an image. For example, if 'carrick' depends on 'package-xyz', and you specified only to remove 'package-xyz', and keep carrick, MIC2 will ignore the request to remove package-xyz (since carrick depends on it), and it includes both of these pgks in the image.

'''''Post scripts'''''

You can also specify post-scripts to be run after the image is installed.

''Example''
<pre>
%post

# Example - saving some space
rm -f /boot/initrd*
rm -f /core*

# Example - Install working xorg.conf
if [ -f /usr/share/my.conf ]; then
cp /usr/share/my.conf /etc/X11/xorg.conf
fi

# Example - Tell alsa the correct audio card to use for your platform
echo -e "options snd-hda-intel index=0\noptions snd-timbi2s index=1" > /etc/modp
robe.d/alsa.conf

%end
</pre>

====Proxy settings for the repos in .ks====

An option you might find useful if you're behind a firewall is the --proxy flag for the "repo" definition. You can specify it in the .ks as follows:

repo --name=meego --baseurl=http://repo.meego.com/trunk/repo/ia32/os/ --proxy=http://proxyhost:proxyport/ --proxyuser=proxyusername
--proxypaswd=proxyuserpassword

If you are behind a firewall, you don't need to set proxyuser and proxypasswd, like:

repo --name=meego --baseurl=http://repo.meego.com/trunk/repo/ia32/os/ --proxy=http://proxyhost:proxyport

'''Note:''' You can also insert this in your sudoers config:

<pre>
$ sudo visudo

Add: Defaults env_keep += " no_proxy http_proxy ........."
</pre>
so sudo will adhere to the no_proxy and proxy settings.

=== MIC2 Configuration file ===

MIC2 options can be specified in a global configuration file ('''/etc/mic2/mic2.conf''') and local configuration file ('''$HOME/.mic2.conf''') where you can specify
* Repository configuration
* proxy settings
* cache directories and
* other variables
that you normally would have to re-type in your command-line.

The two configuration files have the same format, /etc/mic2/mic2.conf is global, no matter whoever is running MIC2, this configuration file will be read first, $HOME/.mic2.conf is just valid for current user, every user can have their own settings.
The final configuration is a combination of two configuration files, options in '''$HOME/.mic2.conf''' will override those from '''/etc/mic2/mic2.conf'''. Options from command line have the highest priority.
If an option is specified on the command line, the same option in both configuration files, global and local will be ignored.

Below is an example you can cut-and-paste, and reuse for your needs:

<pre>
[main]
cachedir=/home/user1/mycache
tmpdir=/home/user1/mystorage/tmp
outdir=/home/user1/mystorage
proxy=http://my.proxy.com:911/
no_proxy=localhost,127.0.0.0/8,.mysite.com,172.16.0.0/16
</pre>

''cachedir'' = directory where the cached repo(s) will reside. With this variable set, you do not need to pass the --cache flag in the command-line.

''tmpdir'' = temporary directory used by MIC2 when creating images. With this variable set, you do not need to pass the --tmpdir flag in the command-line.

''outdir'' = where your images will reside once they are created. With this variable set, you do not need to pass the --outdir flag in the command-line.

''proxy'' = specify your proxy if you're behind a behind a firewall.

''no_proxy'' = specify what domains should not sure the proxy setting.

''image_format'' = specify image format.

''default_ks'' = specify a default kickstart file, there are several kickstart files provided in repository http://repo.meego.com/MeeGo/devel/trunk/repo/ia32/os/

'''Note:''' When specifying proxy and no_proxy, you do not need to use the --proxy flag in your .ks files when referring to repos.

In configuration files, you also can specify one or multiple repositories, for example:

<pre>
[trunk]
name=trunk
baseurl=http://repo.meego.com/MeeGo/devel/trunk/repo/ia32/os/
enabled=1
</pre>

Once there is this repository info in your configuration files, and both image_format and default_ks are set, you can just run "sudo mic-image-creator" to create a image, there isn't any extra argument needed.

=== Use Bootstrap ===

MIC2 highly depends on yum and librpm, but different Linux distributions used diffrent yum and librpm versions, so MIC2 has some compatibility issues on OpenSUSE, Ubuntu and Debian, bootstrap is just for fixing these compatibility issues.

bootstrap is a minimal MeeGo file system, MIC2 can run very smoothly on it using chroot mode. You can use the below command to create a bootstrap:

<pre>
sudo mic-create-bootstrap -n trunk -k /your/repo/cache/path -r http://repo.meego.com/MeeGo/devel/trunk/repo/ia32/os/ -o /your/final/bootstrap
</pre>

-n is used to specify repository name, if you have its cache before, it can reduce runtime dramatically to use it with -k option, -k is used to specify your repository cache dir, -r is used to specify MeeGo main repository.

Once you created your bootstrap, you can use this bootstrap to run MIC2 as follows

<pre>
sudo mic-image-creator --bootstrap=/your/final/bootstrap --format=livecd --config=default.ks --cache=/your/repo/cache/path
</pre>

Alternatively, you can create and use bootstrap in one mic-image-creator run as follows

<pre>
sudo mic-image-creator --build-bootstrap --bootstrap=/your/final/bootstrap --format=livecd --config=default.ks --cache=/your/repo/cache/path
</pre>

== Running mic-image-writer ==

mic-image-writer writes a Meego image to a USB disk as an alternative to dd.

mic-image-writer can run in both console mode and GUI mode. It can decide which mode to run, according to current system environment. You can also use a given option to force it to run in some other mode. Run 'mic-image-writer --help' to get usage information:

<pre>
Usage: mic-image-writer [options] [image file]

Options:
-h, --help Show this help message and exit
-c, --console Run in console mode
-g, --gui Run in GUI mod
</pre>
Here is a run example in console mode:

<pre>
$ sudo mic-image-writer meego-xxx.img
Available usb disk:
[1] /dev/sdc: SanDisk USB Flash Drive
[2] /dev/sdb: SanDisk U3 Cruzer Micro
Please choice [1..2] ? 2
Source: /myhome/meego-xxx.img
Target: /dev/sdb
Image size: 559 MB
Estimated time: 55 seconds
Elapsed time: 64, progress: 100% 8944+0 records in
8944+0 records out
586153984 bytes (586 MB) copied, 63.0486 s, 9.3 MB/s
</pre>

mic-image-writer can estimate how long it will take to write the given image to your USB disk and reports current writing progress. It automatically unmounts your USB disk, if it is mounted. If your USB can't be unmounted, it will terminate.

If you love UI mode, you can run it in X enviroment. The command with the added -g flag:

<pre>
sudo mic-image-writer -g meego-xxx.img
</pre>

Image name is optional.

== Running mic-image-convertor ==

It's very easy to use:

<pre>
sudo mic-image-convertor --source-image=InputImage --target-format=Targegformat

sudo mic-image-convertor -I InputImage -T Targegformat
</pre>

For example, to translate a KVM raw image to livecd image, just type:

<pre>
sudo mic-image-convertor --source-image=meego-core-200902200545/meego-core-200902200545-sda.raw --target-format=livecd
</pre>

A new livecd image of meego-converted-from-raw-200902201804.iso is generated. The tool can detect the type of input image, either raw or vmdk.

This tool is very useful. For example, the developer can launch a virtual machine running MeeGo v2 and make whatever changes on the virtual system like yum install/remove a package, scp a source tarball to VM and build and try, and etc. Then with a simple "sync" or shutdown of VM, the VM image now contains his changes. With this tool, the VM image can be transformed to a live image and burned to a USB flash disk. Now developers can have final verifications in a target device, with changes in the live system.

== Running mic-chroot ==

There are two major usage models for mic-chroot for developers.

'''chroot directly into the image to use it as a development environment, then optionally create a new image based off of your changes'''
<pre>
sudo mic-chroot -c livecd meego-core-200903131337.iso
</pre>

The above command would present a chroot, using the livecd image, to developers with some bind mounts like /proc /sys /dev/pts and /parentroot. With those bind mounts, developers now can easily exchange files in chroot env with host /parentroot, and conduct yum install, yum remove and any other network related operations. After done and typing "exit", a new live ISO image is created from the chroot env with the changes developers made.

'''Unpack and modify the image's filesystem (which you can save), and create a new image based off of your changes'''

Sometimes developers want to keep the chroot env so that they can do multiple changes in that root file system at different times. So they want to execute following:

<pre>
sudo mic-chroot -s my-chroot-fs --unpack-only meego-core-200903131337.iso --bind-mounts=/proc:/proc;/:/parentroot;/sys:/sys;/dev/pts:/dev/pts
</pre>

The above command creates a folder called 'my-chroot-fs' in the current directory, using the chroot environment from the livecd image. Of course if one forgets to add the --bind-mounts options, you'll need to manually do the bind mounting yourself. Don't forget copying /etc/reslov.conf into my-chroot-fs if you need to use DNS. Should you wish to create an image from the chroot, just execute following to create a livecd image

<pre>
sudo mic-chroot -c livecd --convert-only my-chroot-fs/
</pre>

== Enabling Autoinstallation ==

You need to copy a kickstart file into /root/mic2-ks.cfg which is used for
automated installation of the image. To activate autoinstall mode, boot with autoinst on the command line
or add --menus=autoinst to the bootloader directive in the kickstart file you use to
create the image.

= Known issues =

* MIC2 is not compatible with Ubuntu 8.04 (Yum package compatibility)
* MIC2 is not compatible with the initial Ubuntu 9.04. Make sure you have package libsqlite3-0 of 3.6.10-1ubuntu0.2 or later.
* MIC2 has some issues on Debian, please refer to [[MIC on Debian]] to get installation instructions

= Troubleshooting =

You can file a bug on http://bugzilla.meego.com/enter_bug.cgi?product=Development%20Tools (Note: you should select MIC for component) if you run into any MIC2-related issue, bugzilla can track your issue faster and more efficiently.

===libgcc related issues===
<pre>
libgcc_s.so.1 must be installed for pthread_cancel to work"

"Error: failed to create image : '/sbin/mksquashfs /var/tmp/imgcreate-FKCSsk/iso-u8xCPh/LiveOS/osmin /var/tmp/imgcreate-FKCSsk/iso-u8xCPh/LiveOS/osmin.img' exited with error (-6)
</pre>

This error occurs when MIC2 is unable to find the proper version of libgcc. This usually happens on x86_64 systems - MIC2 is looking for the 32 bit version of libgcc, but only the 64 bit version is installed. Installing the 32 bit version of libgcc should resolve this.

===General squashfs issues===
<pre>
"Error: failed to create image : '/sbin/mksquashfs /var/tmp/imgcreate-FKCSsk/iso-u8xCPh/LiveOS/osmin /var/tmp/imgcreate-FKCSsk/iso-u8xCPh/LiveOS/osmin.img' exited with error (-6)
</pre>

This error can also be an issue with the syslinux package. Try updating to the latest version for your distro.

===device-mapper issues===
<pre>
unable to remove open device
</pre>

This is a race condition with device-mapper in Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=506644. Usually rerunning the MIC2 command will resolve this.

===python related issues===
<pre>
from urlgrabber.grabber import URLGrabber
ImportError: No module named urlgrabber.grabber
</pre>

Some people are using python they built themselves, so some python modules aren't under their python library path. For such error, only one way is not to use your own python but to use python your system installed.

===debian-based distros related issues===
On debian-based distros, we used pycentral to package mic2, but mic2 source installtion used distutils, so two kinds of installation have different installation path, if they exist there at the same time, it will result in some unpredictable errors to run mic2. In order to run it correctly, you can only keep just one installation, source or binary.

Remove binary installation
<pre>
sudo apt-get remove mic2
</pre>

Remove source installation

Get python lib path
<pre>
$ python
Python 2.5.2 (r252:60911, Sep 30 2008, 15:41:38)
[GCC 4.3.2 20080917 (Red Hat 4.3.2-4)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import distutils.sysconfig
>>> print distutils.sysconfig.get_python_lib()
<PYTHONLIBPATH>
>>>
$
</pre>

Remove mic2 files
<pre>
$ sudo rm -rf <PYTHONLIBPATH>/mic
$ sudo rm -rf <PYTHONLIBPATH>/mic-0.*
$ sudo rm -f /usr/bin/mic
$ sudo rm -f /usr/bin/mic-*
$ sudo rm -f /usr/bin/moblin-*
</pre>

Note: You must replace <PYTHONLIBPATH> with the above python lib path

===ARM related issues===
<pre>
Traceback (most recent call last):
File "/usr/bin/mic-image-creator", line 856, in <module>
ret = main()
File "/usr/bin/mic-image-creator", line 682, in main
run_in_bootstrap(options.bootstrap, argv, bindmounts, arch = options.arch)
File "/usr/bin/mic-image-creator", line 261, in run_in_bootstrap
ret = subprocess.call(args, preexec_fn = chroot_bootstrap)
File "/usr/lib/python2.5/subprocess.py", line 444, in call
return Popen(*popenargs, **kwargs).wait()
File "/usr/lib/python2.5/subprocess.py", line 594, in __init__
errread, errwrite)
File "/usr/lib/python2.5/subprocess.py", line 1149, in _execute_child
raise child_exception
OSError: [Errno 8] Exec format error
</pre>

This error occues when trying to build ARM images without passing ''--arch=armv7l'' to ''meego-image-creator''.

===Proxy cache===

See http://bugs.meego.com/show_bug.cgi?id=2343

Some servers (e.g. with squid as a proxy) may cache more aggressively than
others, and as a result repomd.xml is invalid (old copy) and
references out of date metadata files (primary, comps, filelists, etc). This is
because the server is returning a cached/old copy of repomd.xml.

Proxy cache should be disabled in mic and yum.

= Advanced Hacking Tips =

===replace kernel in live image===

<pre>
$sudo mic-image-convertor --source-image=<your-netbook.img> --target-format=livecd --shell
</pre>

This command will give you a chroot environment of MeeGo, you can follow the below steps to replace the default kernel with a new one.

1). remove the old kernel

<pre>
# rpm -e kernel-netbook
</pre>

NOTE: execute the above command in chroot environment.

2). copy new kernel to chroot environment of MeeGo

<pre>
$sudo cp /path/to/kernel-*.rpm /var/tmp/imgcreate-*/install_root/
</pre>

NOTE: execute the above command in your host system.

/path/to/kernel-*.rpm is your new kernel to install, /var/tmp/imgcreate-*/install_root/ is the directory where chroot MeeGo mounted on.

3). install the new kernel

<pre>
# rpm -ivh /kernel-*.rpm
# rm /kernel-*.rpm
</pre>

NOTE: execute the above command in chroot environment.

After that, you can find out the new kernel in directory /boot/.

4). update contents of isolinux

<pre>
$sudo cp /var/tmp/imgcreate-*/install_root/boot/initrd-*.img /var/tmp/imgcreate-*/iso-*/isolinux/initrd0.img
$sudo cp /var/tmp/imgcreate-*/install_root/boot/vmlinuz-* /var/tmp/imgcreate-*/iso-*/isolinux/vmlinuz0
</pre>

NOTE: execute the above command in your host system.

5. create an new image
<pre>
#exit
</pre>
NOTE: execute the above command in chroot environment.

After following all the above steps, you'll have a new image.

===build btrfs image===
From version 0.20.1 on, mic2 can support btrfs, you can create btrfs image by change fstype=ext3 in your kickstart file to fstype=btrfs. A successful creation will depend on btrfs-progs (btrfs-tools on debian-based distros, btrfsprogs on openSUSE) and btrfs kernel module in your local system, the known issue is we can't create btrfs image on Fedora 11, the issue is the default btrfs kernel module has some issue which will make kernel panic, so for this case, you must ensure you have a stable & latest kernel and btrfs-progs 0.19 on your system, this needs you to build your kernel by yourself and use it to boot your system.

Btrfs-progs is a prerequisite tool, it includes /sbin/mkfs.btrfs, but its version must match btrfs kernel module, so you must ensure this, mic2 repo http://repo.meego.com/MeeGo/tools/repos/ has an issue which will install btrfs-progs 0.19 when you install mic2, this is an repo sync error, so please ensure you have your distro's btrfs-progs after mic2 is installed, if your distro's btrfs-progs version is 0.19, this isn't an issue, otherwise you must remove btrfs-progs installation introduced by mic2 and reinstall your distro's btrfs-progs.

How to build btrfs image on Fedora 11 or lower version?

# Download kernel-2.6.34 or kernel-2.6.35
# Configure btrfs as module
# make; make modules; make install; make modules_install
# Reboot your system using this built-newly kernel
# Install btrfs-progs 0.19

Done, you're ready for creating btrfs image.

Image Creation

2010-12-22T17:38:59Z

Jeremiah: /* From Binary Packages */

= Overview =

This is the main Image Creator developer's guide. For a more simplistic, step-by-step document, go to: [[Image Creation For Beginners]].

The tool used to create MeeGo images is something called "MIC2" (for distinguishing from obsolete MIC - Moblin Image Creator). MIC is composed of a series of tools to create images, convert images and do some development work on MeeGo. MIC2 is based primarily on Fedora livecd-tools and appliance-tools.

With MIC2 tools, users can create different types of images for different purposes, including live CD images, live USB images, raw images for KVM, VMDK images for Vmware, vdi images for VirtualBox, loop images for IVI platforms, NAND images for Moorestown platforms, ubi images for N900, fs image for MeeGo developers. Also, users can use MIC2 tools to manipulate images like transforming an image from a virtual machine to a live image, and providing a chroot environment based on an existing live image. With these features, developers can do development work on a host virtual machine running MeeGo or a Meego chroot environment, and transfer the resulting new live image to a target device for final debug/verification.

This document discusses only features, usage guide, and known issues.

= Features =

MIC2 offers these major tools:
* mic-image-creator: create images.
* mic-image-convertor: convert a raw/vmdk/vdi/live image into a live image.
* mic-chroot: provide a MeeGo environment from a live/loop image for development, it also can translate that chroot file system into a live image.
* mic-image-writer: write a MeeGo image to a USB disk. This is a safe alternative to dd.

The following support is provided:

* Supports mainstream Linux distros. MIC2 has been thoroughly tested on these distributions:
** Meego
** Fedora (Fedora 10 and above)
** Opensuse (> OpenSUSE 11.1)
** and Ubuntu > 9.04
* Supports various types of images: livecd, liveusb, loop, raw, vmdk, nandmrst, vdi, fs, ubi
* Supports image coversion from virtual machine/live images to live images.
* Uses kickstart (.ks) files for image creation. Through this, users can specify which software repositories to use, which packages to install and basic system configuration directives. Please refer to http://fedoraproject.org/wiki/Anaconda/Kickstart for more information about kickstart configuration files.

= Usage =

== Requirements ==

To be able to use MIC2, your host machine to run mic2 must have Intel(r) Atom(tm) or Intel(r) Core(tm) 2 CPU (support for SSSE3), this is a hard requirement (ARM image is exceptional), the following packages must be available on your system. (Most of the packages are installed by default, depending on the distribution.):

* yum
* rpm
* kpartx
* parted
* syslinux
* isomd5sum
* kvm
* zlib-devel(for compiling)
* python-devel(for installation)

You should load these modules as well, if not loaded automatically by the kernel:
 (Use <code>lsmod</code> to list modules.)

* squashfs
* squashfs-tools
* dm_snapshot
* loop

Specific packages for Fedora:

* pykickstart
* device-mapper

Specific packages for Ubuntu 8.10:

* python-celementtree
* python-elementtree
* dmsetup

=== Installing requirements for Ubuntu 10.04 ===

sudo apt-get install yum rpm kpartx parted syslinux isomd5sum kvm zlib1g-dev squashfs-tools python2.6-dev

== Installation ==

We currently build MIC2 binary rpms/debs for many popular Linux distributions, including Fedora 11, Fedora 12, Ubuntu 9.10, Ubuntu 10.04, OpenSUSE 11.1, OpenSUSE 11.2, and Debian 5.0. Please go to http://repo.meego.com/tools/repos/ to get a repository URL corresponding to your Linux distribution, then add it into your repo or package source for installation and update later. If your distribution isn't in the support list, please install MIC2 from git source.

=== Binary Package installation ===

* '''Installation Steps For Fedora 11, Fedora 12 and Fedora 13'''

1. Add MIC2 repo as user root:

<pre>
# cat <<REPO > /etc/yum.repos.d/meego-tools.repo
[meego-tools]
name=MeeGo Tools for Fedora
baseurl=http://repo.meego.com/MeeGo/tools/repos/fedora/\$releasever
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-meego
REPO
</pre>

2. Add gpg key as user root:

<pre>
# gpg2 --keyserver subkeys.pgp.net --recv 0BC7BEC479FC1F8A
# gpg2 --export --armor 0BC7BEC479FC1F8A > /etc/pki/rpm-gpg/RPM-GPG-KEY-meego
</pre>

3. Install mic2 as user root:
<pre>
# yum install mic2
</pre>

if you get asked to import the key do so:
<pre>
warning: rpmts_HdrFromFdno: Header V3 DSA/SHA1 Signature, key ID 79fc1f8a: NOKEY
meego-fedora/gpgkey | 3.3 kB 00:00 ...
Importing GPG key 0x79FC1F8A:
Userid: "Moblin Build (Moblin Build User) <build@moblin.org>"
From : /etc/pki/rpm-gpg/RPM-GPG-KEY-meego
Is this ok [y/N]: y
</pre>

* '''Update Steps For Fedora 11, Fedora 12 and Fedora 13'''

You can use the below command to get the latest mic2 package.

<pre>
# yum update mic2
</pre>

* '''Installation Steps For Ubuntu 9.10, Ubuntu 10.04 and Debian 5.0'''

1. Add package source

For Ubuntu 9.10, add the below line to /etc/apt/sources.list

<pre>
deb http://repo.meego.com/MeeGo/tools/repos/ubuntu/9.10/ /
</pre>

For Ubuntu 10.04, add the below line to /etc/apt/sources.list

<pre>
deb http://repo.meego.com/MeeGo/tools/repos/ubuntu/10.04/ /
</pre>

For Ubuntu 10.10, add the below line to /etc/apt/sources.list

<pre>
deb http://repo.meego.com/MeeGo/tools/repos/ubuntu/10.10/ /
</pre>

For Debian 5.0, add the below line to /etc/apt/sources.list

<pre>
deb http://repo.meego.com/MeeGo/tools/repos/debian/5.0/ /
</pre>

mic2 is also available in Debian Testing which will become Debian 6.0.

2. sudo apt-get update

You should see the following error:
W: GPG error: http://repo.meego.com Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0BC7BEC479FC1F8A

To add the repository public key use the following command:
:gpg --keyserver subkeys.pgp.net --recv 0BC7BEC479FC1F8A
:gpg --export --armor 0BC7BEC479FC1F8A | sudo apt-key add -

Now redo sudo apt-get update

3. sudo apt-get install mic2

* '''Installation Steps For OpenSUSE 11.1, OpenSUSE 11.2 and OpenSUSE 11.3'''

1. Add repos

For OpenSUSE 11.1:

<pre>sudo zypper addrepo http://repo.meego.com/MeeGo/tools/repos/opensuse/11.1/ meego-tools</pre>

For OpenSUSE 11.2:

<pre>sudo zypper addrepo http://repo.meego.com/MeeGo/tools/repos/opensuse/11.2/ meego-tools</pre>

For OpenSUSE 11.3:

<pre>sudo zypper addrepo http://repo.meego.com/MeeGo/tools/repos/opensuse/11.3/ meego-tools</pre>

2. sudo zypper install mic2

* '''Update Steps For OpenSUSE 11.1, OpenSUSE 11.2 and OpenSUSE 11.3'''

<pre>
sudo zypper update mic2
</pre>

=== From Stable Git Source Releases ===

You can get the latest stable release of MIC2 from the tag section in http://meego.gitorious.org/meego-developer-tools/image-creator. Click on the "Source tree" link on the top of the screen. There will be a list of tags on the right hand side.

You should follow the below steps to install it:

<pre>
git clone git://gitorious.org/meego-developer-tools/image-creator.git
cd image-creator
git checkout 0.17 #check Gitorious for the most recent tag
make
sudo make install
</pre>

=== From Development Git Tree ===

Note: MIC2 GIT tree has latest-and-greatest source, so stability is not guaranteed. If you run into errors, please use a 'Stable Release' instead before filing a bug.

You need to follow the below steps to git clone MIC2:

<pre>
git clone git://gitorious.org/meego-developer-tools/image-creator.git
</pre>

Build and install:

<pre>
cd image-creator
make clean
make
sudo make install
</pre>

You should add the repo for mic2 then run

<pre>
sudo ./tools/mic-check-alldeps
</pre>

to check/install all the depended packages, otherwise mic2 can't work normally.

== Running mic-image-creator ==

Configuration of images is based on kickstart, the format used for unattended installation in Fedora and Redhat.

Super user privileges are needed. The tool is more or less self-documented, use the --help option to see options.
<pre>
sudo mic-image-creator --help
</pre>

=== Creating Supported Image Types ===

KickStart (.ks) configuration files are passed to MIC2 to create tailored images. KickStart files specify what repos to pull from, what packages to include, what post-scripts to run and what type of images to create.

To obtain the official Meego .ks files, go here: TO-DO-LINK

'''Create ARMv7 Images'''

When creating images for ARMv7 hardware, pass ''--arch=armv7l'' to ''mic-image-creator'' commands.

'''Create Livecd Image'''

<pre>
sudo mic-image-creator --config=default.ks --format=livecd --cache=mycache
</pre>

This tells image-creator to use the kickstart file default.ks to obtain info about which packages to download and include in the image, and --cache is the directory on your local machine which will host a cache of these packages. The cache is very useful if you are remote to the server and reduces the amount of downloaded packages next time you create an image. Next time the command is run, this cache will simply be 'updated' if there are changes, rather than re-downloading from the repositories again.

The output of this command will be a file named meego-1.0-default-XX.iso created. This ISO image is a hybrid image and can be either written to a disk device or burned onto a cd.

To burn it onto a USB stick, just run the following command, assuming the USB stick is /dev/sdb in your system:

<pre>
sudo mic-image-writer meego-1.0-default-XX.iso
</pre>

'''Create Moorestown NAND Image'''

<pre>
sudo mic-image-creator --config=default.ks --format=mrstnand

remove the first 512 bytes from the image to remove the partition information.
sudo dd bs=512 skip=1 if=meego-1.0-default-XX-sda.bin of= meego-1.0-default-XX-nand.img
</pre>

'''Create Liveusb Image'''

<pre>
sudo mic-image-creator --config=default.ks --format=liveusb --cache=mycache
</pre>

A file named meego-1.0-default-XX.usbimg will be created. To burn it onto a USB stick, run the following command, assuming the USB stick is /dev/sdb in your system:

<pre>
sudo mic-image-writer meego-1.0-default-XX.usbimg
</pre>

This image has a FAT file system and can be mounted easily on Windows and other OSes.

'''Create Liveusb Image Interactively'''

<pre>
sudo mic-image-creator --config=default.ks --format=liveusb --interactive --cache=mycache
</pre>

It directly creates a MeeGo live usb stick.

Liveusb image can be created in two different ways, interactive and non-interactive (default). When running MIC2 in a non-interactive mode, MIC2 creates a USB images file that can be copied directly into a USB stick. The non-interactive mode can be used for daily build or automated testing. The interactive mode will write the images onto a USB disk, it will detect if a USB stick is available and detects and verifies a partition is available. If two or more USB devices are present, you will be asked to select the target device. This way the contents of the existing USB stick won't be destroyed unless no appropriate partition is found, end user should use it to create the live USB.

'''Create Loop Image'''

This is the simplest image format available. Such images can be loop mounted and chrooted into, for example, to build applications or for debugging purposes.

<pre>
sudo mic-image-creator --config=default.ks --format=loop --cache=mycache
</pre>

A file named meego-1.0-default-XX.img is created. You can use below to mount it and chroot into it.

<pre>
sudo mount -o loop meego-1.0-default-XX.img /mnt
sudo chroot /mnt su -
</pre>

'''Create KVM Image'''

Can be used with QEMU or other VMM applications to launch MeeGo as a virtualized instance.

<pre>
sudo mic-image-creator --config=default.ks --format=raw --cache=mycache
</pre>

A file named meego-1.0-default-XX folder with a meego-1.0-default-XX-sda.raw image is created. For optimal results, use this feature in a machine with VT support and enable it in the BIOS.

If you use Fedora or openSUSE, run the following command to launch the image into MeeGo KVM virtual machine:

<pre>
sudo qemu-kvm -m 512 -boot c -hda meego-1.0-default-XX-sda.raw -std-vga
</pre>

If you use Ubuntu, run the following command launch image:

<pre>
sudo kvm -m 512 -boot c -hda meego-1.0-default-XX-sda.raw
</pre>

'''Create VMDK Image'''

VMDK images can be loaded into Vmware or Vmware player. MIC2 also generates a VMX file that has image configuration and can be used to launch the image in Vmware by just clicking the file. If you have vmplayer, it should open automatically.

<pre>
sudo mic-image-creator --config=default.ks --format=vmdk --cache=mycache
</pre>

A file named meego-1.0-default-XX folder with both meego-1.0-default-XX-sda.vmdk image and meego-1.0-default-XX-sda.vmx is created. Just run vmware or vmware player, and select the generated vmx file.

=== KickStart Files (configuration files used for image creation) ===

KickStart (.ks) configuration files are passed to MIC2 to create tailored images. KickStart files specify what repos to pull from, what packages to include, what post-scripts to run and what type of images to create.

For more details about the kickstart format, see http://fedoraproject.org/wiki/Anaconda/Kickstart.

Note that not all KickStart directives and options are supported for creating Meego images. MIC2 also adds some specific directives and options. More explained below.

====Official Meego .ks files====

The official Meego .ks files are here:

*For ARM based Nokia N900: http://repo.meego.com/MeeGo/builds/trunk/ <version>/handset/images/meego-handset-armv7l-n900/
*For Intel Atom based netbook and handset (Moorestown): http://repo.meego.com/MeeGo/builds/trunk/ <version>/{netbook,handset,ivi}/images/<respective directory>/

You can download and use them as a base for the Meego images you create. Modify these .ks files as you wish to create tailored images.

====Modifying your .ks====

Developers may want to modify the .ks files to create their own custom images. Here are the main options and sections within the .ks file.

You can also find in-depth .ks option information here: http://fedoraproject.org/wiki/Anaconda/Kickstart#Chapter_2._Kickstart_Options

'''''Partition, Setup and Bootloader options'''''

''Example''

<pre>
lang en_US.UTF-8
keyboard us
timezone --utc America/New_York
auth --useshadow --enablemd5
part / --size 1500 --ondisk sda --fstype=ext3
rootpw meego
xconfig --startxonboot
bootloader --timeout=0 --append="quiet"
desktop --autologinuser=meego --defaultdesktop=xfce
user --name meego --groups audio,video --password meego
</pre>

These are mostly self-explanatory and set up important things such as partition size, filesystem type, kernel paramters, etc. You can change these depending on what your needs are.

'''''Repos'''''

This is where you can specify the yum repositories that you want MIC2 to search and pull your packages from which to make up your image. You can add official Meego repos, other remote repos, or your own local repos on your dev machine.

''Example''

<pre>
# This is a comment

# My first repo
repo --name=trunk --baseurl=http://mytrunk.myrepo.com

# My second repo
#repo --name=<repo-name-2> --baseurl=< url | local-repo-dir >
</pre>

'''NOTE:''' --name of the repo can be any unique alphanumeric name you give your repo, it can be anything. Just make sure you don't use the same name twice for any of the listed repos, remember they have to be unique.

To create a repo you can point to on your local developer machine, you can run the following command:

<pre>
createrepo -d <local-dir>
</pre>

Where 'local-dir' is a local directory on your machine that contains the rpms you want include in your local directory.

'''''Adding Packages and Package Groups'''''

''Example''

<pre>
%packages

# Example adding pkg groups

@Core
@X for Netbooks
@Base
@Development Tools
@<my-PkgGroup1>
@<my-PkgGroup2>

# Example adding individual pkgs

kernel-netbook
xorg-x11-server-Xorg-setuid
carrick
xorg-x11-drv-evtouch
<my-pkg-1>
<my-pkg-2>
%end

</pre>

This specifies exactly what packages will be included in your image. Package groups can be specified with a "@" preceding it, as you can see from the examples above. Package groups are defined in the 'repodata' section of a repo, under a 'comps*.xml' file. Defined therein are package group names, and what packages are included in each package group. The Meego package groups are standard, and cannot be changed. You can, however, define your own package groups in your own non-Meego repos if you are using those.

Please see here for more info on defining package groups in repositories: TO-DO-LINK

You can also add individual package names to be included in the image as you can see from the second part in the above example.

'''''Important Note about how MIC2 picks a package when different versions are available'''''

A common problem is that, let's say, a packageA has more than one version residing in a repo(s) that your .ks is pointing to.

How will the MIC2 know which one to pick?

''Example''

There exists in the repo(s) these different versions of PackageA:

PackageA-1.0

PackageA-2.0

PackageA-3.0

MIC2 will pick the PackageA with the highest version number (PackageA-3.0 in this case).

There is one way to get around that, and that is to set the 'Epoch' version within a package .spec file.

<pre>
Example (works in both .spec and .yaml file)

Name: <name>
Summary: <summary>
Epoch: 1
Version: <version>

</pre>

MIC2 will first look to compare the 'Epoch' version of the packages. All Meego official packages do not include an 'Epoch' version, so if you set the 'Epoch' number within your .spec file to any positive integer, no matter if your package version is smaller, MIC2 will choose your package.

So back to our example.

''Example''

PackageA-1.0 (Epoch not set)

PackageA-2.0 (Epoch = 1)

PackageA-3.0 (Epoch not set)

MIC2 will choose PackageA-2.0 in this case. And it follow that:

''Example''

PackageA-1.0 (Epoch=100)

PackageA-2.0 (Epoch = 1)

PackageA-3.0 (Epoch not set)

MIC2 will choose PackageA-1.0.

Remember that Meego packages will not have 'Epoch' set, so chances are that if you set 'Epoch' in your own package to any positive integer, it will be the one MIC2 chooses to pull down and include in an image.

'''''Removing Packages'''''

If you would like to make sure that a pkg is _not_ included, you can specify that with a '-' preceding the package name.

''Example''
<pre>
%packages

# Example pkg groups

@Core

# Example adding individual pkgs

kernel-netbook

# Example removing individual pkgs

-carrick
-package-xyz

%end
</pre>

with the above example, packages 'carrick' and 'package-xyz' will _not_ be included in the image.

'''Note:''' all packages that depend on the package you want to remove should also be removed, or else MIC2 will ignore your request to remove that package from an image. For example, if 'carrick' depends on 'package-xyz', and you specified only to remove 'package-xyz', and keep carrick, MIC2 will ignore the request to remove package-xyz (since carrick depends on it), and it includes both of these pgks in the image.

'''''Post scripts'''''

You can also specify post-scripts to be run after the image is installed.

''Example''
<pre>
%post

# Example - saving some space
rm -f /boot/initrd*
rm -f /core*

# Example - Install working xorg.conf
if [ -f /usr/share/my.conf ]; then
cp /usr/share/my.conf /etc/X11/xorg.conf
fi

# Example - Tell alsa the correct audio card to use for your platform
echo -e "options snd-hda-intel index=0\noptions snd-timbi2s index=1" > /etc/modp
robe.d/alsa.conf

%end
</pre>

====Proxy settings for the repos in .ks====

An option you might find useful if you're behind a firewall is the --proxy flag for the "repo" definition. You can specify it in the .ks as follows:

repo --name=meego --baseurl=http://repo.meego.com/trunk/repo/ia32/os/ --proxy=http://proxyhost:proxyport/ --proxyuser=proxyusername
--proxypaswd=proxyuserpassword

If you are behind a firewall, you don't need to set proxyuser and proxypasswd, like:

repo --name=meego --baseurl=http://repo.meego.com/trunk/repo/ia32/os/ --proxy=http://proxyhost:proxyport

'''Note:''' You can also insert this in your sudoers config:

<pre>
$ sudo visudo

Add: Defaults env_keep += " no_proxy http_proxy ........."
</pre>
so sudo will adhere to the no_proxy and proxy settings.

=== MIC2 Configuration file ===

MIC2 options can be specified in a global configuration file ('''/etc/mic2/mic2.conf''') and local configuration file ('''$HOME/.mic2.conf''') where you can specify
* Repository configuration
* proxy settings
* cache directories and
* other variables
that you normally would have to re-type in your command-line.

The two configuration files have the same format, /etc/mic2/mic2.conf is global, no matter whoever is running MIC2, this configuration file will be read first, $HOME/.mic2.conf is just valid for current user, every user can have their own settings.
The final configuration is a combination of two configuration files, options in '''$HOME/.mic2.conf''' will override those from '''/etc/mic2/mic2.conf'''. Options from command line have the highest priority.
If an option is specified on the command line, the same option in both configuration files, global and local will be ignored.

Below is an example you can cut-and-paste, and reuse for your needs:

<pre>
[main]
cachedir=/home/user1/mycache
tmpdir=/home/user1/mystorage/tmp
outdir=/home/user1/mystorage
proxy=http://my.proxy.com:911/
no_proxy=localhost,127.0.0.0/8,.mysite.com,172.16.0.0/16
</pre>

''cachedir'' = directory where the cached repo(s) will reside. With this variable set, you do not need to pass the --cache flag in the command-line.

''tmpdir'' = temporary directory used by MIC2 when creating images. With this variable set, you do not need to pass the --tmpdir flag in the command-line.

''outdir'' = where your images will reside once they are created. With this variable set, you do not need to pass the --outdir flag in the command-line.

''proxy'' = specify your proxy if you're behind a behind a firewall.

''no_proxy'' = specify what domains should not sure the proxy setting.

''image_format'' = specify image format.

''default_ks'' = specify a default kickstart file, there are several kickstart files provided in repository http://repo.meego.com/MeeGo/devel/trunk/repo/ia32/os/

'''Note:''' When specifying proxy and no_proxy, you do not need to use the --proxy flag in your .ks files when referring to repos.

In configuration files, you also can specify one or multiple repositories, for example:

<pre>
[trunk]
name=trunk
baseurl=http://repo.meego.com/MeeGo/devel/trunk/repo/ia32/os/
enabled=1
</pre>

Once there is this repository info in your configuration files, and both image_format and default_ks are set, you can just run "sudo mic-image-creator" to create a image, there isn't any extra argument needed.

=== Use Bootstrap ===

MIC2 highly depends on yum and librpm, but different Linux distributions used diffrent yum and librpm versions, so MIC2 has some compatibility issues on OpenSUSE, Ubuntu and Debian, bootstrap is just for fixing these compatibility issues.

bootstrap is a minimal MeeGo file system, MIC2 can run very smoothly on it using chroot mode. You can use the below command to create a bootstrap:

<pre>
sudo mic-create-bootstrap -n trunk -k /your/repo/cache/path -r http://repo.meego.com/MeeGo/devel/trunk/repo/ia32/os/ -o /your/final/bootstrap
</pre>

-n is used to specify repository name, if you have its cache before, it can reduce runtime dramatically to use it with -k option, -k is used to specify your repository cache dir, -r is used to specify MeeGo main repository.

Once you created your bootstrap, you can use this bootstrap to run MIC2 as follows

<pre>
sudo mic-image-creator --bootstrap=/your/final/bootstrap --format=livecd --config=default.ks --cache=/your/repo/cache/path
</pre>

Alternatively, you can create and use bootstrap in one mic-image-creator run as follows

<pre>
sudo mic-image-creator --build-bootstrap --bootstrap=/your/final/bootstrap --format=livecd --config=default.ks --cache=/your/repo/cache/path
</pre>

== Running mic-image-writer ==

mic-image-writer writes a Meego image to a USB disk as an alternative to dd.

mic-image-writer can run in both console mode and GUI mode. It can decide which mode to run, according to current system environment. You can also use a given option to force it to run in some other mode. Run 'mic-image-writer --help' to get usage information:

<pre>
Usage: mic-image-writer [options] [image file]

Options:
-h, --help Show this help message and exit
-c, --console Run in console mode
-g, --gui Run in GUI mod
</pre>
Here is a run example in console mode:

<pre>
$ sudo mic-image-writer meego-xxx.img
Available usb disk:
[1] /dev/sdc: SanDisk USB Flash Drive
[2] /dev/sdb: SanDisk U3 Cruzer Micro
Please choice [1..2] ? 2
Source: /myhome/meego-xxx.img
Target: /dev/sdb
Image size: 559 MB
Estimated time: 55 seconds
Elapsed time: 64, progress: 100% 8944+0 records in
8944+0 records out
586153984 bytes (586 MB) copied, 63.0486 s, 9.3 MB/s
</pre>

mic-image-writer can estimate how long it will take to write the given image to your USB disk and reports current writing progress. It automatically unmounts your USB disk, if it is mounted. If your USB can't be unmounted, it will terminate.

If you love UI mode, you can run it in X enviroment. The command with the added -g flag:

<pre>
sudo mic-image-writer -g meego-xxx.img
</pre>

Image name is optional.

== Running mic-image-convertor ==

It's very easy to use:

<pre>
sudo mic-image-convertor --source-image=InputImage --target-format=Targegformat

sudo mic-image-convertor -I InputImage -T Targegformat
</pre>

For example, to translate a KVM raw image to livecd image, just type:

<pre>
sudo mic-image-convertor --source-image=meego-core-200902200545/meego-core-200902200545-sda.raw --target-format=livecd
</pre>

A new livecd image of meego-converted-from-raw-200902201804.iso is generated. The tool can detect the type of input image, either raw or vmdk.

This tool is very useful. For example, the developer can launch a virtual machine running MeeGo v2 and make whatever changes on the virtual system like yum install/remove a package, scp a source tarball to VM and build and try, and etc. Then with a simple "sync" or shutdown of VM, the VM image now contains his changes. With this tool, the VM image can be transformed to a live image and burned to a USB flash disk. Now developers can have final verifications in a target device, with changes in the live system.

== Running mic-chroot ==

There are two major usage models for mic-chroot for developers.

'''chroot directly into the image to use it as a development environment, then optionally create a new image based off of your changes'''
<pre>
sudo mic-chroot -c livecd meego-core-200903131337.iso
</pre>

The above command would present a chroot, using the livecd image, to developers with some bind mounts like /proc /sys /dev/pts and /parentroot. With those bind mounts, developers now can easily exchange files in chroot env with host /parentroot, and conduct yum install, yum remove and any other network related operations. After done and typing "exit", a new live ISO image is created from the chroot env with the changes developers made.

'''Unpack and modify the image's filesystem (which you can save), and create a new image based off of your changes'''

Sometimes developers want to keep the chroot env so that they can do multiple changes in that root file system at different times. So they want to execute following:

<pre>
sudo mic-chroot -s my-chroot-fs --unpack-only meego-core-200903131337.iso --bind-mounts=/proc:/proc;/:/parentroot;/sys:/sys;/dev/pts:/dev/pts
</pre>

The above command creates a folder called 'my-chroot-fs' in the current directory, using the chroot environment from the livecd image. Of course if one forgets to add the --bind-mounts options, you'll need to manually do the bind mounting yourself. Don't forget copying /etc/reslov.conf into my-chroot-fs if you need to use DNS. Should you wish to create an image from the chroot, just execute following to create a livecd image

<pre>
sudo mic-chroot -c livecd --convert-only my-chroot-fs/
</pre>

== Enabling Autoinstallation ==

You need to copy a kickstart file into /root/mic2-ks.cfg which is used for
automated installation of the image. To activate autoinstall mode, boot with autoinst on the command line
or add --menus=autoinst to the bootloader directive in the kickstart file you use to
create the image.

= Known issues =

* MIC2 is not compatible with Ubuntu 8.04 (Yum package compatibility)
* MIC2 is not compatible with the initial Ubuntu 9.04. Make sure you have package libsqlite3-0 of 3.6.10-1ubuntu0.2 or later.
* MIC2 has some issues on Debian, please refer to [[MIC on Debian]] to get installation instructions

= Troubleshooting =

You can file a bug on http://bugzilla.meego.com/enter_bug.cgi?product=Development%20Tools (Note: you should select MIC for component) if you run into any MIC2-related issue, bugzilla can track your issue faster and more efficiently.

===libgcc related issues===
<pre>
libgcc_s.so.1 must be installed for pthread_cancel to work"

"Error: failed to create image : '/sbin/mksquashfs /var/tmp/imgcreate-FKCSsk/iso-u8xCPh/LiveOS/osmin /var/tmp/imgcreate-FKCSsk/iso-u8xCPh/LiveOS/osmin.img' exited with error (-6)
</pre>

This error occurs when MIC2 is unable to find the proper version of libgcc. This usually happens on x86_64 systems - MIC2 is looking for the 32 bit version of libgcc, but only the 64 bit version is installed. Installing the 32 bit version of libgcc should resolve this.

===General squashfs issues===
<pre>
"Error: failed to create image : '/sbin/mksquashfs /var/tmp/imgcreate-FKCSsk/iso-u8xCPh/LiveOS/osmin /var/tmp/imgcreate-FKCSsk/iso-u8xCPh/LiveOS/osmin.img' exited with error (-6)
</pre>

This error can also be an issue with the syslinux package. Try updating to the latest version for your distro.

===device-mapper issues===
<pre>
unable to remove open device
</pre>

This is a race condition with device-mapper in Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=506644. Usually rerunning the MIC2 command will resolve this.

===python related issues===
<pre>
from urlgrabber.grabber import URLGrabber
ImportError: No module named urlgrabber.grabber
</pre>

Some people are using python they built themselves, so some python modules aren't under their python library path. For such error, only one way is not to use your own python but to use python your system installed.

===debian-based distros related issues===
On debian-based distros, we used pycentral to package mic2, but mic2 source installtion used distutils, so two kinds of installation have different installation path, if they exist there at the same time, it will result in some unpredictable errors to run mic2. In order to run it correctly, you can only keep just one installation, source or binary.

Remove binary installation
<pre>
sudo apt-get remove mic2
</pre>

Remove source installation

Get python lib path
<pre>
$ python
Python 2.5.2 (r252:60911, Sep 30 2008, 15:41:38)
[GCC 4.3.2 20080917 (Red Hat 4.3.2-4)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import distutils.sysconfig
>>> print distutils.sysconfig.get_python_lib()
<PYTHONLIBPATH>
>>>
$
</pre>

Remove mic2 files
<pre>
$ sudo rm -rf <PYTHONLIBPATH>/mic
$ sudo rm -rf <PYTHONLIBPATH>/mic-0.*
$ sudo rm -f /usr/bin/mic
$ sudo rm -f /usr/bin/mic-*
$ sudo rm -f /usr/bin/moblin-*
</pre>

Note: You must replace <PYTHONLIBPATH> with the above python lib path

===ARM related issues===
<pre>
Traceback (most recent call last):
File "/usr/bin/mic-image-creator", line 856, in <module>
ret = main()
File "/usr/bin/mic-image-creator", line 682, in main
run_in_bootstrap(options.bootstrap, argv, bindmounts, arch = options.arch)
File "/usr/bin/mic-image-creator", line 261, in run_in_bootstrap
ret = subprocess.call(args, preexec_fn = chroot_bootstrap)
File "/usr/lib/python2.5/subprocess.py", line 444, in call
return Popen(*popenargs, **kwargs).wait()
File "/usr/lib/python2.5/subprocess.py", line 594, in __init__
errread, errwrite)
File "/usr/lib/python2.5/subprocess.py", line 1149, in _execute_child
raise child_exception
OSError: [Errno 8] Exec format error
</pre>

This error occues when trying to build ARM images without passing ''--arch=armv7l'' to ''meego-image-creator''.

===Proxy cache===

See http://bugs.meego.com/show_bug.cgi?id=2343

Some servers (e.g. with squid as a proxy) may cache more aggressively than
others, and as a result repomd.xml is invalid (old copy) and
references out of date metadata files (primary, comps, filelists, etc). This is
because the server is returning a cached/old copy of repomd.xml.

Proxy cache should be disabled in mic and yum.

= Advanced Hacking Tips =

===replace kernel in live image===

<pre>
$sudo mic-image-convertor --source-image=<your-netbook.img> --target-format=livecd --shell
</pre>

This command will give you a chroot environment of MeeGo, you can follow the below steps to replace the default kernel with a new one.

1). remove the old kernel

<pre>
# rpm -e kernel-netbook
</pre>

NOTE: execute the above command in chroot environment.

2). copy new kernel to chroot environment of MeeGo

<pre>
$sudo cp /path/to/kernel-*.rpm /var/tmp/imgcreate-*/install_root/
</pre>

NOTE: execute the above command in your host system.

/path/to/kernel-*.rpm is your new kernel to install, /var/tmp/imgcreate-*/install_root/ is the directory where chroot MeeGo mounted on.

3). install the new kernel

<pre>
# rpm -ivh /kernel-*.rpm
# rm /kernel-*.rpm
</pre>

NOTE: execute the above command in chroot environment.

After that, you can find out the new kernel in directory /boot/.

4). update contents of isolinux

<pre>
$sudo cp /var/tmp/imgcreate-*/install_root/boot/initrd-*.img /var/tmp/imgcreate-*/iso-*/isolinux/initrd0.img
$sudo cp /var/tmp/imgcreate-*/install_root/boot/vmlinuz-* /var/tmp/imgcreate-*/iso-*/isolinux/vmlinuz0
</pre>

NOTE: execute the above command in your host system.

5. create an new image
<pre>
#exit
</pre>
NOTE: execute the above command in chroot environment.

After following all the above steps, you'll have a new image.

===build btrfs image===
From version 0.20.1 on, mic2 can support btrfs, you can create btrfs image by change fstype=ext3 in your kickstart file to fstype=btrfs. A successful creation will depend on btrfs-progs (btrfs-tools on debian-based distros, btrfsprogs on openSUSE) and btrfs kernel module in your local system, the known issue is we can't create btrfs image on Fedora 11, the issue is the default btrfs kernel module has some issue which will make kernel panic, so for this case, you must ensure you have a stable & latest kernel and btrfs-progs 0.19 on your system, this needs you to build your kernel by yourself and use it to boot your system.

Btrfs-progs is a prerequisite tool, it includes /sbin/mkfs.btrfs, but its version must match btrfs kernel module, so you must ensure this, mic2 repo http://repo.meego.com/MeeGo/tools/repos/ has an issue which will install btrfs-progs 0.19 when you install mic2, this is an repo sync error, so please ensure you have your distro's btrfs-progs after mic2 is installed, if your distro's btrfs-progs version is 0.19, this isn't an issue, otherwise you must remove btrfs-progs installation introduced by mic2 and reinstall your distro's btrfs-progs.

How to build btrfs image on Fedora 11 or lower version?

# Download kernel-2.6.34 or kernel-2.6.35
# Configure btrfs as module
# make; make modules; make install; make modules_install
# Reboot your system using this built-newly kernel
# Install btrfs-progs 0.19

Done, you're ready for creating btrfs image.

Changing desktops

2010-12-21T11:31:37Z

Jeremiah: Created page.

The default user interface is started automatically.

User:Jeremiah

2010-12-21T11:31:01Z

Jeremiah:

OHAI

This is the MeeGo wiki page for Jeremiah C. Foster. I am the MeeGo IVI Release Manger. I am a Free Software developer working for Pelagicore AB in Gothenburg, Sweden.

'''Work in progress'''

[[recompile_kernel|Recompiling the MeeGo kernel]] 
[[changing_desktops|Changing the UX on IVI]]

User:Jeremiah

2010-12-21T11:30:43Z

Jeremiah:

ARM/Meego IVI on Beagle

2010-12-21T11:28:37Z

Jeremiah: /* Executive Overview */

= MeeGo IVI on Beagleboard =

This page describes how one installs the MeeGo IVI image on a Beagleboard C4

== Overview ==

# Format your SD card
# Use mic2 to create an image
# Place image on SD card
# Boot Beagleboard from SD card

== Formatting your SD card ==

I recommend using an 8 Gig SD card. This gives you room to download new packages, compile software, and generally experiment right on the board itself.

[http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat Instructions on formatting your SD card for use on the Beagleboard can be found here.] This is the canonical source for card formatting and nothing I could add here would be more useful than that page.

== Creating a root file system ==

To create a root file system, or "userland", you can use the mic2 tool which is native to MeeGO. mic2 is a tool for creating "images" which are essentially snapshots of an entire file system. Using mic2 you download a set of binary packages built for your target architecture which you specify in a kickstart file. Here is is the command I used to create an image for the Beagleboard;

<pre>
sudo mic-image-creator --run-mode=0 --cache=x-cache --format=loop --arch=armv7l --release=daily --compress-disk-image=none --config=ivi-armv7l-beagle.ks
</pre>

You can change these parameters if you want a different type of image, read the [http://wiki.meego.com/Image_Creation instructions for mic2] for more information. It is worth noting that your cache holds lots of downloaded packages, so the next time you run this command you'll just pull down the delta of changes from the online repos making it fairly efficient for you to update your rootfs often.

== Transfer image to SD card ==

Texas Instruments (TI) provides drivers for 3D graphics acceleration. TI supplies these drivers under the Creative Commons Public License. These drivers are not supplied as a package that you can easily integrate, instead you'll have to run a program to download these drivers if you want them included in your root file system. To integrate the drivers [http://bazaar.launchpad.net/~beagleboard-kernel/%2Bjunk/2.6-stable/annotate/head:/create_sgx_package.sh you can use this script] designed to be run on an Intel platform. [http://wiki.meego.com/ARM/Meego_on_Beagleboard_from_scratch#Prepare_SGX.2FGLES_libs More information is here.]

Once you've installed the SGX drivers, you can move on to transferring your root file system (rootfs). The root file system is meant to be put on the second partition of your SD Card and contains all the executables aside from the kernel. To place the rootfs on your SD card, mount the image that mic2 created. You can do that this way;

<pre>
mkdir loopback
sudo mount -o loop ./daily/ivi/images/meego-ivi-armv7l-beagle/meego-ivi-armv7l-beagle-daily.img loopback/
</pre>

This attaches the rootfs physically onto the "loopback" location on your hard drive. You can then move into the "loopback/" directory and copy over the entire file system onto your mounted SD card. This command will do that for you;

<pre>
sudo rsync -aHx --progress --delete loopback/* /media/MeeGo/
</pre>

Some important things to note here:

* I am calling the partition on the SD disk "MeeGo", you can choose a different name when you partition your SD card
* I am calling my loop mounted directory "loopback", you can choose a different name
* rsync can be called with different options, or you can use another tool

== Troubleshooting ==

'''Error Message:''' "WARNING: GFX_3_01_00_06_libs.tar.gz does not exist, skipping PVR setup!" 
'''Cause:''' This message is coming directly from your kickstart file 
'''Fix:''' Make sure you have your GFX tarball in a location that the kickstart file can see it. Usually this means the same directory.

'''Error Message:''' "IOError: [Errno 9] Bad file descriptor" 
'''Cause:''' mic-image-creator does not work on Debian 
'''Fix:''' Use Ubuntu

== Other resources ==
[http://wiki.meego.com/Image_Creation MeeGo Image Creation] 
[http://wiki.meego.com/ARM/Meego_on_Beagleboard_from_scratch MeeGo on the Beagleboard from Scratch]