MeeGo wiki - User contributions [en]

Tizen IVI

2012-05-24T12:55:51Z

Gvancuts: /* Start OBS Light GUI */

== Creation of a Tizen IVI with OBS Light ==
Note this page needs to be moved to Tizen Wiki and image snapshot addition.
=== Install OBS Light ===
Select you installation depending of your PC OS.
[[OBS Light Installation]]
=== Download a valid Kick Start file ===
Check which release you want to build an image with.
Note that new build repo are available every day but they may not be operational.
See : http://download.tizen.org/snapshots/

Recover a .ks file. The following can be used as example:
http://download.tizen.org/snapshots/tizen_20120523.4/images/ivi-min-auto/ivi-min-auto-tizen_20120523.4.ks

''Note:'' the more generic kickstart files found in builddata/image-configs (e.g. http://download.tizen.org/snapshots/tizen_20120523.4/builddata/image-configs/ivi-min-auto.ks) include a @BUILD_ID@ in the baseurl. Such tag is automatically replaced by a string passed to mic with the option --release=<build_id>. In the example above, the option would have been --release=tizen_20120523.4. If one wants to work with the very latest then use --release=latest.

=== Start OBS Light GUI ===
We will not configure any OBS as we are only interested in image creation.

[[File:OBSLightMIC.png]]

* To activate the mode MIC, Click on the second Tab on Top left of the screen
* Create a new project with the button 'New' on the bottom left of the screen
* Import the .ks file using the button 'Import Kickstart file'
* Select your image type (default is fs for file system)
* You can check the various option by clicking on the various tab.
* Click 'Create Image'
* Click 'Show Log' -> Wait about 10mn - once that the cache is created it's quicker

If your .ks file is valid you will have an image located in your project directory.
OBS Light integrates an option to export of that image via TFTP/NFS for quick test.

''Note:'' The Tizen IVI kernels have the NFS option turned off by default so you will need to reconfigure your kernel before you can use that option.

Change your config and play with the .ks option as much as desired.

Enjoy.

Tizen IVI

2012-05-24T12:55:08Z

Gvancuts: /* Start OBS Light GUI */

== Creation of a Tizen IVI with OBS Light ==
Note this page needs to be moved to Tizen Wiki and image snapshot addition.
=== Install OBS Light ===
Select you installation depending of your PC OS.
[[OBS Light Installation]]
=== Download a valid Kick Start file ===
Check which release you want to build an image with.
Note that new build repo are available every day but they may not be operational.
See : http://download.tizen.org/snapshots/

Recover a .ks file. The following can be used as example:
http://download.tizen.org/snapshots/tizen_20120523.4/images/ivi-min-auto/ivi-min-auto-tizen_20120523.4.ks

''Note:'' the more generic kickstart files found in builddata/image-configs (e.g. http://download.tizen.org/snapshots/tizen_20120523.4/builddata/image-configs/ivi-min-auto.ks) include a @BUILD_ID@ in the baseurl. Such tag is automatically replaced by a string passed to mic with the option --release=<build_id>. In the example above, the option would have been --release=tizen_20120523.4. If one wants to work with the very latest then use --release=latest.

=== Start OBS Light GUI ===
We will not configure any OBS as we are only interested in image creation.

[[File:OBSLightMIC.png]]

* To activate the mode MIC, Click on the second Tab on Top left of the screen
* Create a new project with the button 'New' on the bottom left of the screen
* Import the .ks file using the button 'Import Kickstart file'
* Select your image type (default is fs for file system)
* You can check the various option by clicking on the various tab.
* Click 'Create Image'
* Click 'Show Log' -> Wait about 10mn - once that the cache is created it's quicker

If your .ks file is valid you will have an image located in your project directory.
OBS Light integrates an option to export of that image via TFTP/NFS for quick test.
''Note:'' The Tizen IVI kernels have the NFS option turned off by default so you will need to reconfigure your kernel before you can use that option.

Change your config and play with the .ks option as much as desired.

Enjoy.

Tizen IVI

2012-05-24T12:50:30Z

Gvancuts: /* Download a valid Kick Start file */

== Creation of a Tizen IVI with OBS Light ==
Note this page needs to be moved to Tizen Wiki and image snapshot addition.
=== Install OBS Light ===
Select you installation depending of your PC OS.
[[OBS Light Installation]]
=== Download a valid Kick Start file ===
Check which release you want to build an image with.
Note that new build repo are available every day but they may not be operational.
See : http://download.tizen.org/snapshots/

Recover a .ks file. The following can be used as example:
http://download.tizen.org/snapshots/tizen_20120523.4/images/ivi-min-auto/ivi-min-auto-tizen_20120523.4.ks

''Note:'' the more generic kickstart files found in builddata/image-configs (e.g. http://download.tizen.org/snapshots/tizen_20120523.4/builddata/image-configs/ivi-min-auto.ks) include a @BUILD_ID@ in the baseurl. Such tag is automatically replaced by a string passed to mic with the option --release=<build_id>. In the example above, the option would have been --release=tizen_20120523.4. If one wants to work with the very latest then use --release=latest.

=== Start OBS Light GUI ===
We will not configure any OBS as we are only interested in image creation.

[[File:OBSLightMIC.png]]

* To activate the mode MIC, Click on the second Tab on Top left of the screen
* Create a new project with the button 'New' on the bottom left of the screen
* Import the .ks file using the button 'Import Kickstart file'
* Select your image type (default is fs for file system)
* You can check the various option by clicking on the various tab.
* Click 'Create Image'
* Click 'Show Log' -> Wait about 10mn - once that the cache is created it's quicker

If your .ks file is valid you will have an image located in your project directory.
OBS Light integrates an option to export of that image via TFTP/NFS for quick test.

Change your config and play with the .ks option as much as desired.

Enjoy.

Tizen IVI

2012-05-24T12:49:31Z

Gvancuts: /* Download a valid Kick Start file */

== Creation of a Tizen IVI with OBS Light ==
Note this page needs to be moved to Tizen Wiki and image snapshot addition.
=== Install OBS Light ===
Select you installation depending of your PC OS.
[[OBS Light Installation]]
=== Download a valid Kick Start file ===
Check which release you want to build an image with.
Note that new build repo are available every day but they may not be operational.
See : http://download.tizen.org/snapshots/

Recover a .ks file. The following can be used as example:
http://download.tizen.org/snapshots/tizen_20120523.4/images/ivi-min-auto/ivi-min-auto-tizen_20120523.4.ks

''Note:'' the more generic kickstart file found in builddata/image-configs (e.g. http://download.tizen.org/snapshots/tizen_20120523.4/builddata/image-configs/ivi-min-auto.ks) do include a @BUILD_ID@ in the baseurl. Such tag is automatically replaced by a string passed to mic with the option --release=<build_id>, in the example above, the option would have been --release=tizen_20120523.4. If one wants to work with the very latest then use --release=latest

=== Start OBS Light GUI ===
We will not configure any OBS as we are only interested in image creation.

[[File:OBSLightMIC.png]]

* To activate the mode MIC, Click on the second Tab on Top left of the screen
* Create a new project with the button 'New' on the bottom left of the screen
* Import the .ks file using the button 'Import Kickstart file'
* Select your image type (default is fs for file system)
* You can check the various option by clicking on the various tab.
* Click 'Create Image'
* Click 'Show Log' -> Wait about 10mn - once that the cache is created it's quicker

If your .ks file is valid you will have an image located in your project directory.
OBS Light integrates an option to export of that image via TFTP/NFS for quick test.

Change your config and play with the .ks option as much as desired.

Enjoy.

Umms

2011-11-23T16:37:09Z

Gvancuts:

= Universal Multimedia Service (UMMS) =

1 Short expression of the need
--------------------------------
Linux in general including MeeGo in particular lacks a unified solution to play Multimedia content. Almost each application has created its own solution limiting the opportunity to benefit from new hardware capabilities provided by modern chipsets on non PC platforms and reducing the scope of usability of high value Multimedia content which is often protected of use licensed Codec for Linux environment.
It is not the first time than Linux had to break boundary and change established solutions to drastically improve its support for new services. In a recent past we have seen the adoption of CUPS (1999-2002) for printing and Sane (2000-2005) for scanning enabling the use of Linux in office environment what before these two, seemed only possible for the geek in search of long night enjoying a deep troubleshooting fun.
The current proposition has no less of an outrageous ambition than to offer creating a Unified Multi Media Service (UMMS) which will enable to play Audio and Video (AV) from an application on any Linux platform (starting by MeeGo) without having to worry about anything more than it's position on the screen and its possible initial transparency over the User Interface graphics.
2 Purpose/audience
--------------------
The purpose of this document is to provide an understanding of a solution which could be used to deliver a unified service to enable a large community of developers to benefit from the best possible Audio and Video capabilities provided by various Linux implementations without having to worry about the supporting HW.
It addresses the managers who wish to understand the requirements and the constraints required for such a solution, as well as the developers who will have to deliver a working implementation.
It does focus on an initial application for MeeGo TV but it has been designed with the vision of an expansion to all MeeGo verticals in a second phase, starting by the Tablets and further, its generic adoption by a larger Linux community. Only MeeGo needs are described in this initial document.
3 Overview
------------
MeeGo is an open source version of Linux which targets Netbooks, Tablets, Mobiles, Connected TV and Automotive domains, and which has the goals of both delivering an optimized user experience and also enabling a community of developers to service applications across domains.
Unfortunately not only does Linux not have a standard set of APIs to play Audio Video (AV) but also the existing main Linux AV Player APIs (Mplayer and Totem) do not cater for TV needs :
Programming language independence
Management of protected high value content (Pay TV)
GPL license isolation
Support of TV features (broadcast, sub-title, language selection, aspect ratio, trick play, …)
Sophisticated transport independence (smooth streaming, forward error correction, ...)
Multiple back-end video pipe support
Support of new generation HW feature (e.g. video as an OpenGL texture)
This document explains the constraints introduced by these requirements and provides possible solutions and recommendations.

4 Documentation
----------------------------

Specifications [[File:Meego_Unified_MultiMedia_Service_V0.4.odt]] 
[[UMMS_Architecture | General Architecture]] 
[[UMMS_User_Manual | User Manual and Sample code]] 
[[media:LinuxCon_2011_umms_introduction.pdf|Slides from Linux Conference Oct11 and Nov 11]]

5 Where is the code
-----------------
Visit MeeGo OBS and search for UMMS
https://build.meego.com

Umms

2011-11-23T16:35:14Z

Gvancuts:

= Universal Multimedia Service (UMMS) =

1 Short expression of the need
--------------------------------
Linux in general including MeeGo in particular lacks a unified solution to play Multimedia content. Almost each application has created its own solution limiting the opportunity to benefit from new hardware capabilities provided by modern chipsets on non PC platforms and reducing the scope of usability of high value Multimedia content which is often protected of use licensed Codec for Linux environment.
It is not the first time than Linux had to break boundary and change established solutions to drastically improve its support for new services. In a recent past we have seen the adoption of CUPS (1999-2002) for printing and Sane (2000-2005) for scanning enabling the use of Linux in office environment what before these two, seemed only possible for the geek in search of long night enjoying a deep troubleshooting fun.
The current proposition has no less of an outrageous ambition than to offer creating a Unified Multi Media Service (UMMS) which will enable to play Audio and Video (AV) from an application on any Linux platform (starting by MeeGo) without having to worry about anything more than it's position on the screen and its possible initial transparency over the User Interface graphics.
2 Purpose/audience
--------------------
The purpose of this document is to provide an understanding of a solution which could be used to deliver a unified service to enable a large community of developers to benefit from the best possible Audio and Video capabilities provided by various Linux implementations without having to worry about the supporting HW.
It addresses the managers who wish to understand the requirements and the constraints required for such a solution, as well as the developers who will have to deliver a working implementation.
It does focus on an initial application for MeeGo TV but it has been designed with the vision of an expansion to all MeeGo verticals in a second phase, starting by the Tablets and further, its generic adoption by a larger Linux community. Only MeeGo needs are described in this initial document.
3 Overview
------------
MeeGo is an open source version of Linux which targets Netbooks, Tablets, Mobiles, Connected TV and Automotive domains, and which has the goals of both delivering an optimized user experience and also enabling a community of developers to service applications across domains.
Unfortunately not only does Linux not have a standard set of APIs to play Audio Video (AV) but also the existing main Linux AV Player APIs (Mplayer and Totem) do not cater for TV needs :
Programming language independence
Management of protected high value content (Pay TV)
GPL license isolation
Support of TV features (broadcast, sub-title, language selection, aspect ratio, trick play, …)
Sophisticated transport independence (smooth streaming, forward error correction, ...)
Multiple back-end video pipe support
Support of new generation HW feature (e.g. video as an OpenGL texture)
This document explains the constraints introduced by these requirements and provides possible solutions and recommendations.

4 Documentation
----------------------------

Specifications [[File:Meego_Unified_MultiMedia_Service_V0.4.odt]] 
[[UMMS_Architecture | General Architecture]] 
[[UMMS_User_Manual | User Manual and Sample code]] 
Slides from Linux Conference Oct11 and Nov 11 [[media:LinuxCon_2011_umms_introduction.pdf|LinuxCon 2011: Introduction to UMMS]]

5 Where is the code
-----------------
Visit MeeGo OBS and search for UMMS
https://build.meego.com

File:LinuxCon 2011 umms introduction.pdf

2011-11-23T16:22:57Z

Gvancuts: uploaded a new version of "File:LinuxCon 2011 umms introduction.pdf": New links in 'Resources' Adjusted to new service name

This file contains the slides presented to introduce UMMS during Linux conferences in Pragues (Oct 11) and Brazil Sao Polo (Nov 11).

OBS Light

2011-10-17T09:37:45Z

Gvancuts:

If you have (or are thinking about) selecting MeeGo but you cannot put all the code you want to build on OBS, the public, cloud-based MeeGo building tool, or if you are more comfortable with the tradition of local build tools based on a chroot than with a full cloud-based system like OBS, you might find the learning curve a bit steep.

While OBS will provide you with a very powerful and adapted tool for your long-term needs, the entry cost can be perceived to be too high.
This issue is particularly strongly perceived in the TV or IVI segments where recompilation of the Linux kernel and adding drivers is required even during the very early phases of a project and compiling in the public domain is out of the question.

You can find a obs appliance, build in suse studio:
http://susegallery.com/a/e0uuBG/meego-obs

The project proposed is called 'OBS Light' (or also obslight) and creates an encapsulation of OBS which presents a lighter face of OBS that we have called OBS light which could be delivered (if desired) with a pre-packaged MeeGo TV stack (or any other MeeGo vertical) released on a DVD image.

You can Download the boot strap of Meego 1.2.0 here (saveOBS.tar.aa -> saveOBS.tar.ba).
http://www.cc-e.co.uk/Meego/MeeGo-1.2.0/
reassembled the file
cat saveOBS.tar.* >> saveOBS.tar.gz
Thanks to Julien Snell and Cocom for the ftp server.
http://www.cc-e.co.uk

Note that under the hood, OBS light still is 100% OBS code and the building process is the same as what you could achieve by running your own private OBS.
OBS Light mainly pre-configures an OBS with a few osc plugins to ease the learning curve. Note that some OBS feature are hidden to simplify the learning phase. As the service is run locally, you can mix Open Source and private code should you need to do so.

OBS light provides a image builder too, called Imager.
You can find an Imager appliance, built in suse studio:
http://susegallery.com/a/e0uuBG/meego-imager
IMG (Image Me Give) is a project initiated by Nokia. It is a small python
client/server application suite which manages the supervision of the MIC2 image
creation following the submission of a ks file by the user.
http://wiki.meego.com/Release_Infrastructure/IMG_Installation_for_OpenSuse_11.4#Start_IMG

In a second phase we hope to add a simple UI to it. It reuses the osc command line tools delivered with OBS to which a set of extra plugins have been added, including an extension of mic2. All this remains compatible with a full implementation of OBS. It will be published under License: GPLv2.

The osc plugin for automatic patch creation are designed to be reusable in a full OBS environment.

The coding is under work and changes are likely to occur during the development process.

Current progress an deliveries can be found [[ ObsLighDeliverable |here ]]

{|
| || '''OBS Light''' || '''Full OBS'''
|-
| Cross compilation || Yes || Yes
|-
| Local and remote reference || Yes || Yes
|-
| Automatic creation of patch || Yes || Not Yet (will if the same osc plugin is loaded)
|-
| Bootable Image creation || Yes || Add on
|-
| Integrated version control || Hidden || Yes
|-
| Multi-user || Hidden || Yes
|-
| Multi-target by project || Hidden || Yes
|-
| Auto built || Hidden || Yes
|-
| Signing service || Hidden || Yes
|}

GIT: https://meego.gitorious.org/meego-developer-tools/obs-light

OBS:https://build.pub.meego.com/project/show?project=home%3Aronan%3AOBS_Light

Initial Specifications (final implementation are likely differ from the initial concept) :[[https://meego.gitorious.org/meego-developer-tools/obs-light/blobs/master/Doc/SpecOBSLight-1_V-0-6.pdf SpecOBSLight-1_V-0-6]]

All discussions are run on the MeeGo-distribution-tools mailing list.
http://lists.meego.com/listinfo/meego-distribution-tools

3Dconnexion

2011-07-07T12:13:27Z

Gvancuts: /* MeeGo native drivers */

This is the device in question:
== Info ==
http://www.3dconnexion.com/products/spacenavigator.html

== More info ==
http://www.3dconnexion.com/service/software-developer.html is a good source of info. Windows is better documented than Linux.

== Linux/MeeGo support ==
There are basically three options (mutually exclusive) to use this device under Linux/MeeGo:
# Use 3Dconnexion drivers and libraries (SDK available after registering on their website)
# Use open-source spacenav library/daemon <-- this seems to be a very good/stable option
# Use MeeGo native drivers (in which case the mouse is no more than a standard 2D mouse with 2 buttons)

=== spacenavd ===
http://spacenav.sourceforge.net/
tar xvf spacenavd-0.5.tar.gz
cd spacenavd-0.5
./configure
make

This creates a socket-based server you app can connect to.
For examples, please check the example included in the SDK: http://sourceforge.net/projects/spacenav/files/spacenav%20library%20%28SDK%29/

=== MeeGo native drivers ===
As soon as you connect this device to your MeeGo system, the native driver (evdev) will pick it up and add it to the list of pointer device (i.e. a mouse). You can check this using xinput as follows:

Install xinput first (not installed by default)
zypper in xorg-x11-utils-xinput (in MeeGo 1.2, slightly different name in MeeGo 1.0)

xinput --list
Virtual core pointer id=2 [master pointer (3)]
? Virtual core XTEST pointer id=4 [slave pointer (2)]
? CHESEN USB Keyboard id=9 [slave pointer (2)]
? 3Dconnexion Space Navigator '''id=10''' [slave pointer (2)]
? Dell Dell USB Mouse id=11 [slave pointer (2)]
? EVTouch TouchScreen id=12 [slave pointer (2)]
Virtual core keyboard id=3 [master keyboard (2)]
? Virtual core XTEST keyboard id=5 [slave keyboard (3)]
? Video Bus id=6 [slave keyboard (3)]
? Power Button id=7 [slave keyboard (3)]
? CHESEN USB Keyboard id=8 [slave keyboard (3)]

At that point, the mouse is essentially functional but extremely sensitive. To correct this, you can play with the device properties named ''Device Accel Constant Deceleration (237)'' and/or ''Device Accel Adaptive Deceleration (239)''. I've had some good luck setting property '237' between 20 and 50.
xinput --list-props 10
Device '3Dconnexion Space Navigator':
Device Enabled (118): 1
Device Accel Profile (236): 0
Device '''Accel Constant Deceleration (237)''': 1.000000
Device Accel Adaptive Deceleration (239): 1.000000
Device Accel Velocity Scaling (240): 10.000000
Evdev Reopen Attempts (234): 10
Evdev Axis Inversion (241): 0, 0
Evdev Axes Swap (243): 0
Axis Labels (244): "Rel X" (126), "Rel Y" (127), "Rel Z" (256), "Rel Rotary X" (257), "Rel Rotary Y" (258), "Rel Rotary Z" (259)
Button Labels (245): "Button 0" (254), "Button 1" (255), "Button Unknown" (235), "Button Wheel Up" (122), "Button Wheel Down" (123)
Evdev Middle Button Emulation (246): 2
Evdev Middle Button Timeout (247): 50
Evdev Wheel Emulation (248): 0
Evdev Wheel Emulation Axes (249): 0, 0, 4, 5
Evdev Wheel Emulation Inertia (250): 10
Evdev Wheel Emulation Timeout (251): 200
Evdev Wheel Emulation Button (252): 4
Evdev Drag Lock Buttons (253): 0

xinput --set-prop 10 237 20

'''In MeeGo 1.2:'''
*Create a new file called 3Dconnexion.conf in <code>/etc/X11/xorg.conf.d/</code> (i.e. no need to use a script anymore)
*Copy and past the following text in this new file and restart X.
Section "InputClass"
Identifier "evdev 3Dconnexion"
MatchProduct "3Dconnexion|Space Navigator"
Driver "evdev"
Option "ConstantDeceleration" "30"
EndSection

Note: something *very* similar should also work in '''MeeGo 1.0''' by adding the same section in <code>/etc/X11/xorg.conf</code> but I have not tested it yet. In the meantime an easy work around is to add this line to a script file that runs when system boots up (i.e. <code>/usr/bin/startivi</code>):
'''xinput set-prop "3Dconnexion Space Navigator" 237 20'''

In-vehicle

2011-07-04T16:15:24Z

Gvancuts: /* Other Scroll Wheels */

= In-vehicle Infotainment (IVI) =

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

== Organization ==

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

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

=== Working Group ===

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

* Working Group Chair
** Represents and promotes the Working Group.
** Leads strategic discussions on requirements, direction, policies.
** Commitment: full-time role.
** Current Working Group Chair: '''[http://meego.com/users/RudolfStreif Rudi Streif (Linux Foundation)]'''

* Working Group Representative (the number is not limited, others participants to be invited)
** Represents his/her organization in the Working Group.
** Collects, organizes, prioritizes, and contributes requirements from his/her organization.
** Commitment: 20% - 50% dependent on how actively the organization wants to contribute requirements.
** Current Working Group Representatives:
*** Intel: '''[http://meego.com/users/jahoffmann Joel Hoffmann]'''
*** LG Electronics: '''[https://meego.com/users/hyungjin Hyungjin Jeon]'''
*** Nokia: '''[http://meego.com/users/alistair Alistair Adams]'''
*** Pelagicore: '''[http://meego.com/users/mikael Mikael Soderberg]'''
*** Visteon: '''[http://meego.com/users/PavelKonopelko Pavel Konopelko]'''

* Product Manager (cross-function across Working Group and Project Team)
** Unifies and prioritizes overall requirements set.
** Owns the roadmap.
** co-leads the Project Team and defines the release schedule together with the Project Manager.
** Accountable to the Working Group for delivery of agreed upon requirements.
** Commitment: full-time role.
** Full job description: [[Media:MeeGo_IVI_PDM.pdf]]
** Current Product Manager:

* Program Manager (cross-functional across Working Group and Project Team)
** Works with the Lead Architects and Lead Designers on effort estimates and schedules.
** co-leads the Project Team together with the Product Manager.
** Accountable to the Working Group for deliverables and schedule.
** Commitment: full-time role.
** Full job description: [[Media:MeeGo_IVI_PJM.pdf]]
** Current Program Manager: '''[http://meego.com/users/joel Joel Clark (Intel)]'''

==== Working Group Meetings and Minutes ====
The Working Group meets regularly. Information on current and past meetings can be found on [[in-vehicle/working-group|IVI Working Group]].

=== Project Team ===

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

* Lead Architect
** Defines technical architecture to meet the requirements n terms of functionality, performance, etc.
** Defines interfaces between modules and components together with other Lead Architects within the same and/or other Project Teams.
** Performs feasibility studies and provides feedback to product manager on technical challenges, difficulties, “show stoppers”.
** Commitment: > 50% dependent on sub-project complexity.
** Current Lead Architect: '''[http://meego.com/users/tomcounihan Tom Counihan (Intel)]'''

* Lead Designer (multiple roles)
** Responsible for the detailed implementation design of the architecture.
** Estimates the effort necessary for implementation.
** Leads implementation team comprised of engineering resources of his/her organization.
** Commitment: full-time role.
** Current Lead Designers
***
***

* QA Lead (multiple roles)
** Transforms requirements into functionality test plans.
** Develops interface and compliance test procedures according to the architecture.
** Implements black box and white box test tools through the resources of his/her organization.
** Executes test plans and provides test reports.
** Commitment: full-time role.
** Current QA Leads:
***
***

* Release Manager
** Coordinates bug tracking, build and release with the design and QA leads.
** Develops and manages build tools.
** Leads build and release engineering team.
** Commitment: full-time role.
** Current Release Manager: '''[http://meego.com/users/jeremiah Jeremiah Foster (Pelagicore)]'''

* Engineers for Development and QA (many roles)
** Implement and test the required functionality.
** Qualification varies with sub-project.
** Commitment: full-time role.

== Shipping MeeGo IVI Products ==

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

== MeeGo IVI Demos ==

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

== MeeGo IVI UI (HMI)==

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

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

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

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

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

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

* [[3Dconnexion|3Dconnexion SpaceNavigator ]]

== Roadmap ==

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

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

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

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

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

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

More details on the long term direction and short term Release plan may be found in the [[In-vehicle/Roadmap|IVI roadmap]].

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

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

Each weekly build directory is named with a version number and date. IVI live .iso images are found under the ''images'' link in each weekly build directory. A list of every package included a live image is found in the same directory as the image. RPM packages are found under the ''oss'' and ''non-oss'' links under ''repos'' in the weekly build directory.

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

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

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

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

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

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

===Meego 1.3===

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

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

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

===MeeGo IVI Trunk Prototype Platforms===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! status
|-
|meego-ivi-ia32-conx
|Stephenville/Northville/Crossville
|Intel Atom E6xx Series for Embedded (Tunnel Creek)
|ST Microelectronics ConneXt STA2x11
|GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, GigE, EMGD, Video-in, MMC, '''CAN''', USB-OTG, MSP, BT, FM-Radio
|in development, several issues open, visit [[IVI Images for ConneXt IOH]] for more information
|}

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

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

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

;ARM

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

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

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

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

[[Category:IVI]]

In-vehicle

2011-07-04T16:12:26Z

Gvancuts: /* Other Scroll Wheels */

= In-vehicle Infotainment (IVI) =

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

== Organization ==

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

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

=== Working Group ===

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

* Working Group Chair
** Represents and promotes the Working Group.
** Leads strategic discussions on requirements, direction, policies.
** Commitment: full-time role.
** Current Working Group Chair: '''[http://meego.com/users/RudolfStreif Rudi Streif (Linux Foundation)]'''

* Working Group Representative (the number is not limited, others participants to be invited)
** Represents his/her organization in the Working Group.
** Collects, organizes, prioritizes, and contributes requirements from his/her organization.
** Commitment: 20% - 50% dependent on how actively the organization wants to contribute requirements.
** Current Working Group Representatives:
*** Intel: '''[http://meego.com/users/jahoffmann Joel Hoffmann]'''
*** LG Electronics: '''[https://meego.com/users/hyungjin Hyungjin Jeon]'''
*** Nokia: '''[http://meego.com/users/alistair Alistair Adams]'''
*** Pelagicore: '''[http://meego.com/users/mikael Mikael Soderberg]'''
*** Visteon: '''[http://meego.com/users/PavelKonopelko Pavel Konopelko]'''

* Product Manager (cross-function across Working Group and Project Team)
** Unifies and prioritizes overall requirements set.
** Owns the roadmap.
** co-leads the Project Team and defines the release schedule together with the Project Manager.
** Accountable to the Working Group for delivery of agreed upon requirements.
** Commitment: full-time role.
** Full job description: [[Media:MeeGo_IVI_PDM.pdf]]
** Current Product Manager:

* Program Manager (cross-functional across Working Group and Project Team)
** Works with the Lead Architects and Lead Designers on effort estimates and schedules.
** co-leads the Project Team together with the Product Manager.
** Accountable to the Working Group for deliverables and schedule.
** Commitment: full-time role.
** Full job description: [[Media:MeeGo_IVI_PJM.pdf]]
** Current Program Manager: '''[http://meego.com/users/joel Joel Clark (Intel)]'''

==== Working Group Meetings and Minutes ====
The Working Group meets regularly. Information on current and past meetings can be found on [[in-vehicle/working-group|IVI Working Group]].

=== Project Team ===

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

* Lead Architect
** Defines technical architecture to meet the requirements n terms of functionality, performance, etc.
** Defines interfaces between modules and components together with other Lead Architects within the same and/or other Project Teams.
** Performs feasibility studies and provides feedback to product manager on technical challenges, difficulties, “show stoppers”.
** Commitment: > 50% dependent on sub-project complexity.
** Current Lead Architect: '''[http://meego.com/users/tomcounihan Tom Counihan (Intel)]'''

* Lead Designer (multiple roles)
** Responsible for the detailed implementation design of the architecture.
** Estimates the effort necessary for implementation.
** Leads implementation team comprised of engineering resources of his/her organization.
** Commitment: full-time role.
** Current Lead Designers
***
***

* QA Lead (multiple roles)
** Transforms requirements into functionality test plans.
** Develops interface and compliance test procedures according to the architecture.
** Implements black box and white box test tools through the resources of his/her organization.
** Executes test plans and provides test reports.
** Commitment: full-time role.
** Current QA Leads:
***
***

* Release Manager
** Coordinates bug tracking, build and release with the design and QA leads.
** Develops and manages build tools.
** Leads build and release engineering team.
** Commitment: full-time role.
** Current Release Manager: '''[http://meego.com/users/jeremiah Jeremiah Foster (Pelagicore)]'''

* Engineers for Development and QA (many roles)
** Implement and test the required functionality.
** Qualification varies with sub-project.
** Commitment: full-time role.

== Shipping MeeGo IVI Products ==

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

== MeeGo IVI Demos ==

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

== MeeGo IVI UI (HMI)==

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

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

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

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

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

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

* [ http://wiki.meego.com/3Dconnexion ]

== Roadmap ==

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

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

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

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

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

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

More details on the long term direction and short term Release plan may be found in the [[In-vehicle/Roadmap|IVI roadmap]].

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

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

Each weekly build directory is named with a version number and date. IVI live .iso images are found under the ''images'' link in each weekly build directory. A list of every package included a live image is found in the same directory as the image. RPM packages are found under the ''oss'' and ''non-oss'' links under ''repos'' in the weekly build directory.

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

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

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

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

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

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

===Meego 1.3===

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

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

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

===MeeGo IVI Trunk Prototype Platforms===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! status
|-
|meego-ivi-ia32-conx
|Stephenville/Northville/Crossville
|Intel Atom E6xx Series for Embedded (Tunnel Creek)
|ST Microelectronics ConneXt STA2x11
|GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, GigE, EMGD, Video-in, MMC, '''CAN''', USB-OTG, MSP, BT, FM-Radio
|in development, several issues open, visit [[IVI Images for ConneXt IOH]] for more information
|}

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

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

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

;ARM

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

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

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

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

[[Category:IVI]]

3Dconnexion

2011-07-04T16:11:13Z

Gvancuts: How-to run/configure the 3Dconnexion SpaceNavigator in MeeGo IVI

This is the device in question:
== Info ==
http://www.3dconnexion.com/products/spacenavigator.html

== More info ==
http://www.3dconnexion.com/service/software-developer.html is a good source of info. Windows is better documented than Linux.

== Linux/MeeGo support ==
There are basically three options (mutually exclusive) to use this device under Linux/MeeGo:
# Use 3Dconnexion drivers and libraries (SDK available after registering on their website)
# Use open-source spacenav library/daemon <-- this seems to be a very good/stable option
# Use MeeGo native drivers (in which case the mouse is no more than a standard 2D mouse with 2 buttons)

=== spacenavd ===
http://spacenav.sourceforge.net/
tar xvf spacenavd-0.5.tar.gz
cd spacenavd-0.5
./configure
make

This creates a socket-based server you app can connect to.
For examples, please check the example included in the SDK: http://sourceforge.net/projects/spacenav/files/spacenav%20library%20%28SDK%29/

=== MeeGo native drivers ===
As soon as you connect this device to your MeeGo system, the native driver (evdev) will pick it up and add it to the list of pointer device (i.e. a mouse). You can check this using xinput as follows:

Install xinput first (not installed by default)
zypper in xorg-x11-utils-xinput (in MeeGo 1.2, slightly different name in MeeGo 1.0)

xinput --list
Virtual core pointer id=2 [master pointer (3)]
? Virtual core XTEST pointer id=4 [slave pointer (2)]
? CHESEN USB Keyboard id=9 [slave pointer (2)]
? 3Dconnexion Space Navigator '''id=10''' [slave pointer (2)]
? Dell Dell USB Mouse id=11 [slave pointer (2)]
? EVTouch TouchScreen id=12 [slave pointer (2)]
Virtual core keyboard id=3 [master keyboard (2)]
? Virtual core XTEST keyboard id=5 [slave keyboard (3)]
? Video Bus id=6 [slave keyboard (3)]
? Power Button id=7 [slave keyboard (3)]
? CHESEN USB Keyboard id=8 [slave keyboard (3)]

At that point, the mouse is essentially functional but extremely sensitive. To correct this, you can play with the device properties named ''Device Accel Constant Deceleration (237)'' and/or ''Device Accel Adaptive Deceleration (239)''. I've had some good luck setting property '237' between 20 and 50.
xinput --list-props 10
Device '3Dconnexion Space Navigator':
Device Enabled (118): 1
Device Accel Profile (236): 0
Device '''Accel Constant Deceleration (237)''': 1.000000
Device Accel Adaptive Deceleration (239): 1.000000
Device Accel Velocity Scaling (240): 10.000000
Evdev Reopen Attempts (234): 10
Evdev Axis Inversion (241): 0, 0
Evdev Axes Swap (243): 0
Axis Labels (244): "Rel X" (126), "Rel Y" (127), "Rel Z" (256), "Rel Rotary X" (257), "Rel Rotary Y" (258), "Rel Rotary Z" (259)
Button Labels (245): "Button 0" (254), "Button 1" (255), "Button Unknown" (235), "Button Wheel Up" (122), "Button Wheel Down" (123)
Evdev Middle Button Emulation (246): 2
Evdev Middle Button Timeout (247): 50
Evdev Wheel Emulation (248): 0
Evdev Wheel Emulation Axes (249): 0, 0, 4, 5
Evdev Wheel Emulation Inertia (250): 10
Evdev Wheel Emulation Timeout (251): 200
Evdev Wheel Emulation Button (252): 4
Evdev Drag Lock Buttons (253): 0

xinput --set-prop 10 237 20

It should be possible to set this directly in xorg.conf.d but no real luck yet so far. In the meantime an easy work around is to add this line to a script file that runs when system boots up:
'''xinput set-prop "3Dconnexion Space Navigator" 237 20'''

SDK/Docs/1.1/Building QEMU Tools

2010-10-22T17:15:47Z

Gvancuts: /* Build QEMUGL from source */

[[category:Meego-1.1]]

This page describes how to build the [http://wiki.meego.com/MeeGo_SDK_with_QEMU MeeGo SDK QEMU] tools from source, including QEMU binary, patched kernel module, and stub libGL.

== Build QEMUGL from source ==

''Verified on Linux (Fedora 13) on 2010-10-11 by [[User:Elliot|Elliot Smith]]''

'''An alternative to building from source is to install a qemugl package from one of the repositories at http://download.meego.com/live/Tools:/SDK:/Host/'''

Check out http://wiki.meego.com/MeeGo_SDK_with_QEMU#Installing_qemugl_on_64-bit_ubuntu_10.04 for more details.

'''If you still prefer to build QEMUGL from sources, proceed with these steps:'''

Checkout the QEMU GL source code (this is basically QEMU with some patches to enable GL acceleration):

git clone git://gitorious.org/meego-developer-tools/meego-emulator-qemugl-x86.git

Checkout the qemu-gl branch:

cd meego-emulator-qemugl-x86
git checkout -b qemu-gl --track origin/qemu-gl

Make sure that there is KVM enabled and that the following libraries (development package) are installed on the host machine:

* zlib
* libSDL
* Xcomposite.

Configure qemugl:

./configure --target-list=i386-softmmu --enable-gl

Check the output from <code>configure</code> contains the strings below:

SDL support yes
......
KVM support yes

Build qemugl:

make
sudo make install

This installs various QEMU binaries (default prefix is <code>/usr/local</code>), including <code>qemugl</code> and <code>qemu-img</code> used in this tutorial.

== Create netbook image for QEMU with GL acceleration ==

''Verified on Linux (Fedora 13) on 2010-10-13 by [[User:Elliot|Elliot Smith]] using this netbook image: ''
''http://repo.meego.com/MeeGo/builds/trunk/1.1.80.1.20101012.1/netbook/images/meego-netbook-ia32/meego-netbook-ia32-1.1.80.1.20101012.1.img''

This section explains how to make a standard MeeGo netbook image run in QEMU with GL acceleration.

=== Install MeeGo netbook to QEMU raw disk image ===

Create raw image file for MeeGo to install on. The <code>qemu-img</code> command is part of the [[#Build_QEMUGL_from_source|QEMU build]]:
qemu-img create -f raw meego-netbook.raw 3.5G

Install MeeGo to the raw hard disk, using the downloaded .img file as the installation CDROM:
qemugl -m 1024 -vga std -boot d -hda meego-netbook.raw -cdrom meego-netbook-ia32-1.1.80.1.20101012.1.img

Boot into the image:
qemugl -m 1024 -vga std -boot c -hda meego-netbook.raw

Go through the installation steps to set up a meego user. The password you set here is also used as the root password, which we'll use below.

Note: occasionally I've halted the system before the meego user is setup. When I then try to boot into the UX, it fails because the user is missing. In this case, you can manually create the user from a root prompt (inside the QEMU image) with:
useradd -d /home/meego -M -s /bin/bash meego

Halt the system.

Now boot it again (this time with networking enabled; type the command below, press return, then press tab like crazy so you can get to the boot menu):
qemugl -m 1024 -vga std -net user,hostfwd=tcp:127.0.0.1:6666-:22 -net nic,model=e1000 -boot c -hda meego-netbook.raw

Next, edit the kernel command line on the boot menu screen so it looks like this:
vmlinuz-2.6.35.3-8.5-netbook ro root=/dev/sda2 vga=current s

This will get you a root prompt.

=== Install and start openssh server ===

Then install ssh server (this makes the following steps easier, as you can cut and paste into the ssh prompt):
zypper install openssh-server
chkconfig --add sshd
/etc/init.d/sshd start

Use can now use ssh to login to the image with:

ssh -p 6666 root@127.0.0.1

(password is the same as you entered for your normal user when configuring the system)

=== Set suid bit on Xorg binary ===

Once logged in over ssh, set suid on the Xorg binary (so a normal user can start X):

chmod u+s /usr/bin/Xorg

=== Install packages from the SDK repo ===

Then install the SDK addons. First, add the MeeGo SDK repo:

zypper addrepo http://download.meego.com/live/devel:/tools:/sdk:/target/Trunk/ meego-sdk

(you may need to use a different repo, depending on the netbook image you have)

'''Another alternative is to [[#Manually build packages for an image running under QEMU GL|manually build the addons, kernel and virtiogl module in a chroot]], then install them into the image.'''

==== Install QEMU addons ====

Install the qemugl addon package into the image:

zypper install meego-sdk-qemugl-addon-netbook

==== Install kernel and virtiogl module ====

Install a current kernel and virtiogl module for it:

zypper install kernel-netbook-2.6.35.3-13.2
zypper install kmod-virtiogl

This kernel is currently (2010-10-13) the only one available in the SDK repo, but other versions should be available soon. If you need to build the SDK addons or a kernel and its modules, [[#Manually build packages for an image running under QEMU GL|instructions are given below]].

=== Run the image under QEMU with GL acceleration ===

The image should now be ready. It can be started in QEMU with this command:

qemugl -m 1024 -net user,hostfwd=tcp:127.0.0.1:6666-:22 -net nic,model=e1000 -enable-kvm -vga std -enable-gl -device virtio-gl-pci -boot c -hda meego-netbook.raw

Note that you should still be able to ssh to this image as above.

== Create handset image for QEMU with GL acceleration ==

If you have a handset image downloaded, follow these instructions to enable it to run in QEMU with GL acceleration.

Download a handset tarball (e.g. from http://meego.com/downloads/releases/1.0.80.8/meego-handset-day1-developer-preview), and untar the file:

tar xjvf meego-handset-ia32-aava-mtf-1.0.80.8.20100629.1-mrstnand.tar.bz2

(Note that this procedure should work for other images from http://repo.meego.com/MeeGo/builds/trunk/ too.)

Build kernel and modules version 2.6.35 from below section [[#Build packages for image running under QEMU GL]], to get a kernel file and module directory. Supppose the kernel file is "bzImage".

qemugl -m 1024 -boot c -hda meego-handset-ia32-aava-mtf-1.0.80.8.20100629.1-sda.bin -vga std -kernel bzImage \
--append "root=/dev/sda1 init s"

Inside the emulated image, install these packages:
zypper install xorg-x11-drv-vesa
zypper install mesa-dri-swrast-driver
zypper install openssh-server
zypper install gdb-gdbserver

Copy the kernel modules into the image. Suppose that there have been modules.tgz in host machine built from kernel build step above:
scp host@ipaddress:modules.tgz .
tar xzvf modules.tgz
mv module_directory /lib/modules/

Add a new repo file to "/etc/zypp/repos.d/". File name could be "meego-sdk.repo", and content is as below:
[meego-sdk]
name=meego-sdk
failovermethod=priority
baseurl=http://download.meego.com/live/Tools:/SDK/Trunk/
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-meego
gpgcheck=1
enabled=1

Run "zypper" to install qemugl addon package to the image:
zypper install meego-sdk-qemugl-addon-handset

We are done now. The new image could be started in QEMU with below command:
qemugl -m 1024 -boot c -hda meego-handset-ia32-aava-mtf-1.0.80.8.20100629.1-sda.bin -net user,hostfwd=tcp:127.0.0.1:6666-:22 -net \
nic,model=e1000 -vga std -enable-gl -enable-kvm -device virtio-gl-pci -kernel bzImage --append "root=/dev/sda1"

== Manually build packages for an image running under QEMU GL ==

''Verified on Linux (Fedora 13) on 2010-10-14 by [[User:Elliot|Elliot Smith]] using this netbook image: ''
''http://repo.meego.com/MeeGo/builds/trunk/1.1.80.1.20101012.1/netbook/images/meego-netbook-ia32/meego-netbook-ia32-1.1.80.1.20101012.1.img''

You can manually build the software required to run an image (netbook or handset) under QEMU with GL acceleration. But this is only recommended if a pre-built package for the software you want doesn't already exist (up-to-date packages should be available for both handset and netbook soon).

The steps below should be followed from ''inside'' a MeeGo image intended to run under QEMU. You could try this inside an emulated image, or by [[Building a MeeGo chroot on Linux|building a chroot]] from the raw disk image and working inside that (the latter is the only reasonable approach for building the kernel).

For building both the qemugl addon and the kernel+modules, you will need to install a toolchain first (either into the QEMU image, the toolchain, or both):
zypper install make gcc git patch diffutils

Alternatively, this command will get you ''all'' the MeeGo developer tools:
zypper install -t pattern development-tools

=== Build qemugl addon ===

The addon package installed in above section can also be built from source. These steps are fairly easy to do inside the QEMU image itself.

You don't need to do this if you already installed a <code>meego-sdk-qemugl-addon-*</code> package (see [[#Install QEMU addons, kernel and virtiogl module|above]]).

Install required packaged first:
zypper install libXfixes-devel libX11-devel

Checkout stub libGL source code:
git clone git://gitorious.org/meego-developer-tools/meego-emulator-libgl-x86.git

Build:
cd meego-emulator-libgl-x86
make
make install

=== Build and install kernel and modules ===

The approach we take for this is to use a chroot to build an RPM package for the new kernel and modules. This can then be easily transferred to the QEMU image and installed. Building the new kernel directly inside the QEMU image is too slow to be practical.

The first thing you'll need is a MeeGo chroot, built from the same image you're using under QEMU. See [[Building a MeeGo chroot on Linux|this page]] for instructions.

Enter the chroot.

Install <code>rpmbuild</code> (used to build the RPM from the kernel source):
zypper install rpm-build

Get the MeeGo kernel-source (this contains configuration files for building MeeGo kernels):
git clone git://gitorious.org/meego-os-base/kernel-source.git

Get the virtio patches for the kernel:
git clone git://gitorious.org/meego-developer-tools/meego-emulator-virtiogl-x86.git

Copy the virtio patch into the patches dir of kernel-source:
cp meego-emulator-virtiogl-x86/linux-2.6.35-virtio-for-qemu-gl-acceleration.patch kernel-source/patches

Download the kernel source tarball (NB you want the plain series version, not one with a patch number); in this case, I used a 2.6.35 kernel:
cd kernel-source
curl -o linux-2.6.35.tar.bz2 http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.35.tar.bz2

Remain in the <code>kernel-source</code> directory.

Edit the <code>series</code> file to add the virtiogl patch to the list of patches to apply:
# Add Virtio-mem module for QEMU GL acceleration
linux-2.6.35-virtio-for-qemu-gl-acceleration.patch

Edit the <code>config-netbook</code> file (used for both handset and netbook) to enable VIRTIOGL as a module:
CONFIG_VIRTIO_PCI=m
CONFIG_VIRTIOGL=m
# CONFIG_VIRTIO_BLK is not set
# CONFIG_VIRTIO_NET is not set
# CONFIG_VIRTIO_CONSOLE is not set
# CONFIG_HW_RANDOM_VIRTIO is not set

Delete this line from the same file (we want to set a value and it could be confusing otherwise):

# CONFIG_VIRTIO_PCI is not set

Generate spec files and config files:
make
make -f Makefile.config

This generates config files with names in the format <code>kernel-xxx.config</code>.

Patch the kernel:
./scripts/install-git-hooks
./scripts/sequence-patch.sh --quilt

Copy kernel config file into the source tree:
cp kernel-netbook.config tmp/linux-2.6.35-master/.config

Build a kernel RPM package (takes a long time):
cd tmp/linux-2.6.35-master
make oldconfig (at each prompt, accept the default)
make rpm-pkg

The resulting package is in <code>/root/rpmbuild/RPMS/i386/kernel-2.6.35.3+-1.i386.rpm</code>.

Copy this to the QEMU image over ssh or equivalent, for example:
scp -P 6666 /root/rpmbuild/RPMS/i386/kernel-2.6.35.3+-1.i386.rpm root@127.0.0.1:/root/

Get a root prompt in the QEMU image (either by booting into single user mode or logging in via ssh) and install the RPM:
rpm -ivh /root/kernel-2.6.35.3+-1.i386.rpm

Build and install the new initrd (a RAM disk image) for the kernel and modify the boot loader:
new-kernel-pkg --mkinitrd --install --make-default --depmod 2.6.35.3+
(replace 2.6.35.3+ with the version for your new kernel)

Next time you [[#Run the image under QEMU with GL acceleration|boot the image]], it should default to using the new kernel with the virtiogl module.

User:Gvancuts

2010-10-22T17:13:05Z

Gvancuts:

Geoffroy Van Cutsem

MeeGo Technical Marketing Engineer at Intel

User:Gvancuts

2010-10-22T17:11:44Z

Gvancuts: Created page with "Name: Geoffroy Van Cutsem"

Name: Geoffroy Van Cutsem

SDK/Docs/1.1/Building QEMU Tools

2010-10-22T17:11:21Z

Gvancuts:

[[category:Meego-1.1]]

This page describes how to build the [http://wiki.meego.com/MeeGo_SDK_with_QEMU MeeGo SDK QEMU] tools from source, including QEMU binary, patched kernel module, and stub libGL.

== Build QEMUGL from source ==

''Verified on Linux (Fedora 13) on 2010-10-11 by [[User:Elliot|Elliot Smith]]''

'''An alternative to building from source is to install a qemugl package from one of the repositories at http://download.meego.com/live/Tools:/SDK:/Host/'''

'''If you still prefer to build QEMUGL from sources, proceed with these steps:'''

Checkout the QEMU GL source code (this is basically QEMU with some patches to enable GL acceleration):

git clone git://gitorious.org/meego-developer-tools/meego-emulator-qemugl-x86.git

Checkout the qemu-gl branch:

cd meego-emulator-qemugl-x86
git checkout -b qemu-gl --track origin/qemu-gl

Make sure that there is KVM enabled and that the following libraries (development package) are installed on the host machine:

* zlib
* libSDL
* Xcomposite.

Configure qemugl:

./configure --target-list=i386-softmmu --enable-gl

Check the output from <code>configure</code> contains the strings below:

SDL support yes
......
KVM support yes

Build qemugl:

make
sudo make install

This installs various QEMU binaries (default prefix is <code>/usr/local</code>), including <code>qemugl</code> and <code>qemu-img</code> used in this tutorial.

== Create netbook image for QEMU with GL acceleration ==

''Verified on Linux (Fedora 13) on 2010-10-13 by [[User:Elliot|Elliot Smith]] using this netbook image: ''
''http://repo.meego.com/MeeGo/builds/trunk/1.1.80.1.20101012.1/netbook/images/meego-netbook-ia32/meego-netbook-ia32-1.1.80.1.20101012.1.img''

This section explains how to make a standard MeeGo netbook image run in QEMU with GL acceleration.

=== Install MeeGo netbook to QEMU raw disk image ===

Create raw image file for MeeGo to install on. The <code>qemu-img</code> command is part of the [[#Build_QEMUGL_from_source|QEMU build]]:
qemu-img create -f raw meego-netbook.raw 3.5G

Install MeeGo to the raw hard disk, using the downloaded .img file as the installation CDROM:
qemugl -m 1024 -vga std -boot d -hda meego-netbook.raw -cdrom meego-netbook-ia32-1.1.80.1.20101012.1.img

Boot into the image:
qemugl -m 1024 -vga std -boot c -hda meego-netbook.raw

Go through the installation steps to set up a meego user. The password you set here is also used as the root password, which we'll use below.

Note: occasionally I've halted the system before the meego user is setup. When I then try to boot into the UX, it fails because the user is missing. In this case, you can manually create the user from a root prompt (inside the QEMU image) with:
useradd -d /home/meego -M -s /bin/bash meego

Halt the system.

Now boot it again (this time with networking enabled; type the command below, press return, then press tab like crazy so you can get to the boot menu):
qemugl -m 1024 -vga std -net user,hostfwd=tcp:127.0.0.1:6666-:22 -net nic,model=e1000 -boot c -hda meego-netbook.raw

Next, edit the kernel command line on the boot menu screen so it looks like this:
vmlinuz-2.6.35.3-8.5-netbook ro root=/dev/sda2 vga=current s

This will get you a root prompt.

=== Install and start openssh server ===

Then install ssh server (this makes the following steps easier, as you can cut and paste into the ssh prompt):
zypper install openssh-server
chkconfig --add sshd
/etc/init.d/sshd start

Use can now use ssh to login to the image with:

ssh -p 6666 root@127.0.0.1

(password is the same as you entered for your normal user when configuring the system)

=== Set suid bit on Xorg binary ===

Once logged in over ssh, set suid on the Xorg binary (so a normal user can start X):

chmod u+s /usr/bin/Xorg

=== Install packages from the SDK repo ===

Then install the SDK addons. First, add the MeeGo SDK repo:

zypper addrepo http://download.meego.com/live/devel:/tools:/sdk:/target/Trunk/ meego-sdk

(you may need to use a different repo, depending on the netbook image you have)

'''Another alternative is to [[#Manually build packages for an image running under QEMU GL|manually build the addons, kernel and virtiogl module in a chroot]], then install them into the image.'''

==== Install QEMU addons ====

Install the qemugl addon package into the image:

zypper install meego-sdk-qemugl-addon-netbook

==== Install kernel and virtiogl module ====

Install a current kernel and virtiogl module for it:

zypper install kernel-netbook-2.6.35.3-13.2
zypper install kmod-virtiogl

This kernel is currently (2010-10-13) the only one available in the SDK repo, but other versions should be available soon. If you need to build the SDK addons or a kernel and its modules, [[#Manually build packages for an image running under QEMU GL|instructions are given below]].

=== Run the image under QEMU with GL acceleration ===

The image should now be ready. It can be started in QEMU with this command:

qemugl -m 1024 -net user,hostfwd=tcp:127.0.0.1:6666-:22 -net nic,model=e1000 -enable-kvm -vga std -enable-gl -device virtio-gl-pci -boot c -hda meego-netbook.raw

Note that you should still be able to ssh to this image as above.

== Create handset image for QEMU with GL acceleration ==

If you have a handset image downloaded, follow these instructions to enable it to run in QEMU with GL acceleration.

Download a handset tarball (e.g. from http://meego.com/downloads/releases/1.0.80.8/meego-handset-day1-developer-preview), and untar the file:

tar xjvf meego-handset-ia32-aava-mtf-1.0.80.8.20100629.1-mrstnand.tar.bz2

(Note that this procedure should work for other images from http://repo.meego.com/MeeGo/builds/trunk/ too.)

Build kernel and modules version 2.6.35 from below section [[#Build packages for image running under QEMU GL]], to get a kernel file and module directory. Supppose the kernel file is "bzImage".

qemugl -m 1024 -boot c -hda meego-handset-ia32-aava-mtf-1.0.80.8.20100629.1-sda.bin -vga std -kernel bzImage \
--append "root=/dev/sda1 init s"

Inside the emulated image, install these packages:
zypper install xorg-x11-drv-vesa
zypper install mesa-dri-swrast-driver
zypper install openssh-server
zypper install gdb-gdbserver

Copy the kernel modules into the image. Suppose that there have been modules.tgz in host machine built from kernel build step above:
scp host@ipaddress:modules.tgz .
tar xzvf modules.tgz
mv module_directory /lib/modules/

Add a new repo file to "/etc/zypp/repos.d/". File name could be "meego-sdk.repo", and content is as below:
[meego-sdk]
name=meego-sdk
failovermethod=priority
baseurl=http://download.meego.com/live/Tools:/SDK/Trunk/
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-meego
gpgcheck=1
enabled=1

Run "zypper" to install qemugl addon package to the image:
zypper install meego-sdk-qemugl-addon-handset

We are done now. The new image could be started in QEMU with below command:
qemugl -m 1024 -boot c -hda meego-handset-ia32-aava-mtf-1.0.80.8.20100629.1-sda.bin -net user,hostfwd=tcp:127.0.0.1:6666-:22 -net \
nic,model=e1000 -vga std -enable-gl -enable-kvm -device virtio-gl-pci -kernel bzImage --append "root=/dev/sda1"

== Manually build packages for an image running under QEMU GL ==

''Verified on Linux (Fedora 13) on 2010-10-14 by [[User:Elliot|Elliot Smith]] using this netbook image: ''
''http://repo.meego.com/MeeGo/builds/trunk/1.1.80.1.20101012.1/netbook/images/meego-netbook-ia32/meego-netbook-ia32-1.1.80.1.20101012.1.img''

You can manually build the software required to run an image (netbook or handset) under QEMU with GL acceleration. But this is only recommended if a pre-built package for the software you want doesn't already exist (up-to-date packages should be available for both handset and netbook soon).

The steps below should be followed from ''inside'' a MeeGo image intended to run under QEMU. You could try this inside an emulated image, or by [[Building a MeeGo chroot on Linux|building a chroot]] from the raw disk image and working inside that (the latter is the only reasonable approach for building the kernel).

For building both the qemugl addon and the kernel+modules, you will need to install a toolchain first (either into the QEMU image, the toolchain, or both):
zypper install make gcc git patch diffutils

Alternatively, this command will get you ''all'' the MeeGo developer tools:
zypper install -t pattern development-tools

=== Build qemugl addon ===

The addon package installed in above section can also be built from source. These steps are fairly easy to do inside the QEMU image itself.

You don't need to do this if you already installed a <code>meego-sdk-qemugl-addon-*</code> package (see [[#Install QEMU addons, kernel and virtiogl module|above]]).

Install required packaged first:
zypper install libXfixes-devel libX11-devel

Checkout stub libGL source code:
git clone git://gitorious.org/meego-developer-tools/meego-emulator-libgl-x86.git

Build:
cd meego-emulator-libgl-x86
make
make install

=== Build and install kernel and modules ===

The approach we take for this is to use a chroot to build an RPM package for the new kernel and modules. This can then be easily transferred to the QEMU image and installed. Building the new kernel directly inside the QEMU image is too slow to be practical.

The first thing you'll need is a MeeGo chroot, built from the same image you're using under QEMU. See [[Building a MeeGo chroot on Linux|this page]] for instructions.

Enter the chroot.

Install <code>rpmbuild</code> (used to build the RPM from the kernel source):
zypper install rpm-build

Get the MeeGo kernel-source (this contains configuration files for building MeeGo kernels):
git clone git://gitorious.org/meego-os-base/kernel-source.git

Get the virtio patches for the kernel:
git clone git://gitorious.org/meego-developer-tools/meego-emulator-virtiogl-x86.git

Copy the virtio patch into the patches dir of kernel-source:
cp meego-emulator-virtiogl-x86/linux-2.6.35-virtio-for-qemu-gl-acceleration.patch kernel-source/patches

Download the kernel source tarball (NB you want the plain series version, not one with a patch number); in this case, I used a 2.6.35 kernel:
cd kernel-source
curl -o linux-2.6.35.tar.bz2 http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.35.tar.bz2

Remain in the <code>kernel-source</code> directory.

Edit the <code>series</code> file to add the virtiogl patch to the list of patches to apply:
# Add Virtio-mem module for QEMU GL acceleration
linux-2.6.35-virtio-for-qemu-gl-acceleration.patch

Edit the <code>config-netbook</code> file (used for both handset and netbook) to enable VIRTIOGL as a module:
CONFIG_VIRTIO_PCI=m
CONFIG_VIRTIOGL=m
# CONFIG_VIRTIO_BLK is not set
# CONFIG_VIRTIO_NET is not set
# CONFIG_VIRTIO_CONSOLE is not set
# CONFIG_HW_RANDOM_VIRTIO is not set

Delete this line from the same file (we want to set a value and it could be confusing otherwise):

# CONFIG_VIRTIO_PCI is not set

Generate spec files and config files:
make
make -f Makefile.config

This generates config files with names in the format <code>kernel-xxx.config</code>.

Patch the kernel:
./scripts/install-git-hooks
./scripts/sequence-patch.sh --quilt

Copy kernel config file into the source tree:
cp kernel-netbook.config tmp/linux-2.6.35-master/.config

Build a kernel RPM package (takes a long time):
cd tmp/linux-2.6.35-master
make oldconfig (at each prompt, accept the default)
make rpm-pkg

The resulting package is in <code>/root/rpmbuild/RPMS/i386/kernel-2.6.35.3+-1.i386.rpm</code>.

Copy this to the QEMU image over ssh or equivalent, for example:
scp -P 6666 /root/rpmbuild/RPMS/i386/kernel-2.6.35.3+-1.i386.rpm root@127.0.0.1:/root/

Get a root prompt in the QEMU image (either by booting into single user mode or logging in via ssh) and install the RPM:
rpm -ivh /root/kernel-2.6.35.3+-1.i386.rpm

Build and install the new initrd (a RAM disk image) for the kernel and modify the boot loader:
new-kernel-pkg --mkinitrd --install --make-default --depmod 2.6.35.3+
(replace 2.6.35.3+ with the version for your new kernel)

Next time you [[#Run the image under QEMU with GL acceleration|boot the image]], it should default to using the new kernel with the virtiogl module.

Talk:SDK/Docs/1.1/Building QEMU Tools

2010-10-22T17:10:30Z

Gvancuts:

[[User:Elliot|Elliot Smith]] - I'd prefer the stuff about installing from a package manager to be split into its own section: it doesn't seem to sit right in the part about build QEMU. Previously there was just a note about using packages instead, not full instructions.

[[User:Gvancuts|Geoffroy]] That makes sense, I have moved this specific section to this page: http://wiki.meego.com/MeeGo_SDK_with_QEMU#Installing_qemugl_on_64-bit_ubuntu_10.04. Do you agree this is the right place?

SDK/Docs/1.1/Building QEMU Tools

2010-10-21T14:45:58Z

Gvancuts: /* Build QEMUGL from source */

[[category:Meego-1.1]]

This page describes how to build the [http://wiki.meego.com/MeeGo_SDK_with_QEMU MeeGo SDK QEMU] tools from source, including QEMU binary, patched kernel module, and stub libGL.

== Build QEMUGL from source ==

''Verified on Linux (Fedora 13) on 2010-10-11 by [[User:Elliot|Elliot Smith]]''

'''An alternative to building from source is to install a qemugl package from one of the repositories at http://download.meego.com/live/Tools:/SDK:/Host/'''

Example of how to add this repository in Ubuntu 10.04, two steps:
* From ''Software Sources'' -> ''Other Software''; click ''Add'' and insert this line: <code>deb http://download.meego.com/live/Tools:/SDK:/Host/Ubuntu_10.04 /</code>
* Import the key from the following file (save it on your HDD first): http://download.meego.com/live/Tools:/SDK:/Host/Ubuntu_10.04/Release.key using the ''Import Key File...'' in the ''Authentication'' tab
Although I have not verified it, I assume the procedure would be similar for other distributions/versions.

''Note'': this package '''only''' installs <code>qemugl</code>, you should install the ''qemu-kvm'' package in Ubuntu to have tools such as <code>qemu-img</code> available too (this is needed if you want/need to build your own MeeGo image to be run by the emulator.

''Note2'': the QEMUGL package gets installed in <code>/opt/meego/qemu-gl/</code> by default. You should therefore modify the launch script [http://download3.meego.com/sep09/meego-qemu-start meego-qemu-start] by editing both <code>QEMU_BIN</code> and <code>QEMU_PATH</code> variables as follows:
QEMU_BIN="/opt/meego/qemu-gl/bin"
QEMU_PATH="/opt/meego/qemu-gl/share/qemugl/"

'''If you still prefer to build QEMUGL from sources, proceed with these steps:'''

Checkout the QEMU GL source code (this is basically QEMU with some patches to enable GL acceleration):

git clone git://gitorious.org/meego-developer-tools/meego-emulator-qemugl-x86.git

Checkout the qemu-gl branch:

cd meego-emulator-qemugl-x86
git checkout -b qemu-gl --track origin/qemu-gl

Make sure that there is KVM enabled and that the following libraries (development package) are installed on the host machine:

* zlib
* libSDL
* Xcomposite.

Configure qemugl:

./configure --target-list=i386-softmmu --enable-gl

Check the output from <code>configure</code> contains the strings below:

SDL support yes
......
KVM support yes

Build qemugl:

make
sudo make install

This installs various QEMU binaries (default prefix is <code>/usr/local</code>), including <code>qemugl</code> and <code>qemu-img</code> used in this tutorial.

== Create netbook image for QEMU with GL acceleration ==

''Verified on Linux (Fedora 13) on 2010-10-13 by [[User:Elliot|Elliot Smith]] using this netbook image: ''
''http://repo.meego.com/MeeGo/builds/trunk/1.1.80.1.20101012.1/netbook/images/meego-netbook-ia32/meego-netbook-ia32-1.1.80.1.20101012.1.img''

This section explains how to make a standard MeeGo netbook image run in QEMU with GL acceleration.

=== Install MeeGo netbook to QEMU raw disk image ===

Create raw image file for MeeGo to install on. The <code>qemu-img</code> command is part of the [[#Build_QEMUGL_from_source|QEMU build]]:
qemu-img create -f raw meego-netbook.raw 3.5G

Install MeeGo to the raw hard disk, using the downloaded .img file as the installation CDROM:
qemugl -m 1024 -vga std -boot d -hda meego-netbook.raw -cdrom meego-netbook-ia32-1.1.80.1.20101012.1.img

Boot into the image:
qemugl -m 1024 -vga std -boot c -hda meego-netbook.raw

Go through the installation steps to set up a meego user. The password you set here is also used as the root password, which we'll use below.

Note: occasionally I've halted the system before the meego user is setup. When I then try to boot into the UX, it fails because the user is missing. In this case, you can manually create the user from a root prompt (inside the QEMU image) with:
useradd -d /home/meego -M -s /bin/bash meego

Halt the system.

Now boot it again (this time with networking enabled; type the command below, press return, then press tab like crazy so you can get to the boot menu):
qemugl -m 1024 -vga std -net user,hostfwd=tcp:127.0.0.1:6666-:22 -net nic,model=e1000 -boot c -hda meego-netbook.raw

Next, edit the kernel command line on the boot menu screen so it looks like this:
vmlinuz-2.6.35.3-8.5-netbook ro root=/dev/sda2 vga=current s

This will get you a root prompt.

=== Install and start openssh server ===

Then install ssh server (this makes the following steps easier, as you can cut and paste into the ssh prompt):
zypper install openssh-server
chkconfig --add sshd
/etc/init.d/sshd start

Use can now use ssh to login to the image with:

ssh -p 6666 root@127.0.0.1

(password is the same as you entered for your normal user when configuring the system)

=== Set suid bit on Xorg binary ===

Once logged in over ssh, set suid on the Xorg binary (so a normal user can start X):

chmod u+s /usr/bin/Xorg

=== Install packages from the SDK repo ===

Then install the SDK addons. First, add the MeeGo SDK repo:

zypper addrepo http://download.meego.com/live/devel:/tools:/sdk:/target/Trunk/ meego-sdk

(you may need to use a different repo, depending on the netbook image you have)

'''Another alternative is to [[#Manually build packages for an image running under QEMU GL|manually build these packages in a chroot]] and install them into the image.'''

==== Install QEMU addons ====

Install the qemugl addon package into the image:

zypper install meego-sdk-qemugl-addon-netbook

==== Install kernel and virtiogl module ====

Install a current kernel and virtiogl module for it:

zypper install kernel-netbook-2.6.35.3-13.2
zypper install kmod-virtiogl

This kernel is currently (2010-10-13) the only one available in the SDK repo, but other versions should be available soon. If you need to build the SDK addons or a kernel and its modules, [[#Manually build packages for an image running under QEMU GL|instructions are given below]].

=== Run the image under QEMU with GL acceleration ===

The image should now be ready. It can be started in QEMU with this command:

qemugl -m 1024 -net user,hostfwd=tcp:127.0.0.1:6666-:22 -net nic,model=e1000 -enable-kvm -vga std -enable-gl -device virtio-gl-pci -boot c -hda meego-netbook.raw

Note that you should still be able to ssh to this image as above.

== Create handset image for QEMU with GL acceleration ==

If you have a handset image downloaded, follow these instructions to enable it to run in QEMU with GL acceleration.

Download a handset tarball (e.g. from http://meego.com/downloads/releases/1.0.80.8/meego-handset-day1-developer-preview), and untar the file:

tar xjvf meego-handset-ia32-aava-mtf-1.0.80.8.20100629.1-mrstnand.tar.bz2

(Note that this procedure should work for other images from http://repo.meego.com/MeeGo/builds/trunk/ too.)

Build kernel and modules version 2.6.35 from below section [[#Build packages for image running under QEMU GL]], to get a kernel file and module directory. Supppose the kernel file is "bzImage".

qemugl -m 1024 -boot c -hda meego-handset-ia32-aava-mtf-1.0.80.8.20100629.1-sda.bin -vga std -kernel bzImage \
--append "root=/dev/sda1 init s"

Inside the emulated image, install these packages:
zypper install xorg-x11-drv-vesa
zypper install mesa-dri-swrast-driver
zypper install openssh-server
zypper install gdb-gdbserver

Copy the kernel modules into the image. Suppose that there have been modules.tgz in host machine built from kernel build step above:
scp host@ipaddress:modules.tgz .
tar xzvf modules.tgz
mv module_directory /lib/modules/

Add a new repo file to "/etc/zypp/repos.d/". File name could be "meego-sdk.repo", and content is as below:
[meego-sdk]
name=meego-sdk
failovermethod=priority
baseurl=http://download.meego.com/live/Tools:/SDK/Trunk/
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-meego
gpgcheck=1
enabled=1

Run "zypper" to install qemugl addon package to the image:
zypper install meego-sdk-qemugl-addon-handset

We are done now. The new image could be started in QEMU with below command:
qemugl -m 1024 -boot c -hda meego-handset-ia32-aava-mtf-1.0.80.8.20100629.1-sda.bin -net user,hostfwd=tcp:127.0.0.1:6666-:22 -net \
nic,model=e1000 -vga std -enable-gl -enable-kvm -device virtio-gl-pci -kernel bzImage --append "root=/dev/sda1"

== Manually build packages for an image running under QEMU GL ==

''Verified on Linux (Fedora 13) on 2010-10-14 by [[User:Elliot|Elliot Smith]] using this netbook image: ''
''http://repo.meego.com/MeeGo/builds/trunk/1.1.80.1.20101012.1/netbook/images/meego-netbook-ia32/meego-netbook-ia32-1.1.80.1.20101012.1.img''

You can manually build the software required to run an image (netbook or handset) under QEMU with GL acceleration. But this is only recommended if a pre-built package for the software you want doesn't already exist (up-to-date packages should be available for both handset and netbook soon).

The steps below should be followed from ''inside'' a MeeGo image intended to run under QEMU. You could try this inside an emulated image, or by [[Building a MeeGo chroot on Linux|building a chroot]] from the raw disk image and working inside that (the latter is the only reasonable approach for building the kernel).

For building both the qemugl addon and the kernel+modules, you will need to install a toolchain first (either into the QEMU image, the toolchain, or both):
zypper install make gcc git patch diffutils

Alternatively, this command will get you ''all'' the MeeGo developer tools:
zypper install -t pattern development-tools

=== Build qemugl addon ===

The addon package installed in above section can also be built from source. These steps are fairly easy to do inside the QEMU image itself.

You don't need to do this if you already installed a <code>meego-sdk-qemugl-addon-*</code> package (see [[#Install QEMU addons, kernel and virtiogl module|above]]).

Install required packaged first:
zypper install libXfixes-devel libX11-devel

Checkout stub libGL source code:
git clone git://gitorious.org/meego-developer-tools/meego-emulator-libgl-x86.git

Build:
cd meego-emulator-libgl-x86
make
make install

=== Build and install kernel and modules ===

The approach we take for this is to use a chroot to build an RPM package for the new kernel and modules. This can then be easily transferred to the QEMU image and installed. Building the new kernel directly inside the QEMU image is too slow to be practical.

The first thing you'll need is a MeeGo chroot, built from the same image you're using under QEMU. See [[Building a MeeGo chroot on Linux|this page]] for instructions.

Enter the chroot.

Install <code>rpmbuild</code> (used to build the RPM from the kernel source):
zypper install rpm-build

Get the MeeGo kernel-source (this contains configuration files for building MeeGo kernels):
git clone git://gitorious.org/meego-os-base/kernel-source.git

Get the virtio patches for the kernel:
git clone git://gitorious.org/meego-developer-tools/meego-emulator-virtiogl-x86.git

Copy the virtio patch into the patches dir of kernel-source:
cp meego-emulator-virtiogl-x86/linux-2.6.35-virtio-for-qemu-gl-acceleration.patch kernel-source/patches

Download the kernel source tarball (NB you want the plain series version, not one with a patch number); in this case, I used a 2.6.35 kernel:
cd kernel-source
curl -o linux-2.6.35.tar.bz2 http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.35.tar.bz2

Remain in the <code>kernel-source</code> directory.

Edit the <code>series</code> file to add the virtiogl patch to the list of patches to apply:
# Add Virtio-mem module for QEMU GL acceleration
linux-2.6.35-virtio-for-qemu-gl-acceleration.patch

Edit the <code>config-netbook</code> file (used for both handset and netbook) to enable VIRTIOGL as a module:
CONFIG_VIRTIO_PCI=m
CONFIG_VIRTIOGL=m
# CONFIG_VIRTIO_BLK is not set
# CONFIG_VIRTIO_NET is not set
# CONFIG_VIRTIO_CONSOLE is not set
# CONFIG_HW_RANDOM_VIRTIO is not set

Delete this line from the same file (we want to set a value and it could be confusing otherwise):

# CONFIG_VIRTIO_PCI is not set

Generate spec files and config files:
make
make -f Makefile.config

This generates config files with names in the format <code>kernel-xxx.config</code>.

Patch the kernel:
./scripts/install-git-hooks
./scripts/sequence-patch.sh --quilt

Copy kernel config file into the source tree:
cp kernel-netbook.config tmp/linux-2.6.35-master/.config

Build a kernel RPM package (takes a long time):
cd tmp/linux-2.6.35-master
make oldconfig (at each prompt, accept the default)
make rpm-pkg

The resulting package is in <code>/root/rpmbuild/RPMS/i386/kernel-2.6.35.3+-1.i386.rpm</code>.

Copy this to the QEMU image over ssh or equivalent, for example:
scp -P 6666 /root/rpmbuild/RPMS/i386/kernel-2.6.35.3+-1.i386.rpm root@127.0.0.1:/root/

Get a root prompt in the QEMU image (either by booting into single user mode or logging in via ssh) and install the RPM:
rpm -ivh /root/kernel-2.6.35.3+-1.i386.rpm

Build and install the new initrd (a RAM disk image) for the kernel and modify the boot loader:
new-kernel-pkg --mkinitrd --install --make-default --depmod 2.6.35.3+
(replace 2.6.35.3+ with the version for your new kernel)

Next time you [[#Run the image under QEMU with GL acceleration|boot the image]], it should default to using the new kernel with the virtiogl module.

SDK/Docs/1.1/Building QEMU Tools

2010-10-21T14:40:13Z

Gvancuts: /* Build QEMUGL from source */

[[category:Meego-1.1]]

This page describes how to build the [http://wiki.meego.com/MeeGo_SDK_with_QEMU MeeGo SDK QEMU] tools from source, including QEMU binary, patched kernel module, and stub libGL.

== Build QEMUGL from source ==

''Verified on Linux (Fedora 13) on 2010-10-11 by [[User:Elliot|Elliot Smith]]''

'''An alternative to building from source is to install a qemugl package from one of the repositories at http://download.meego.com/live/Tools:/SDK:/Host/'''

Example of how to add this repository in Ubuntu 10.04, two steps:
* From ''Software Sources'' -> ''Other Software''; click ''Add'' and insert this line: <code>deb http://download.meego.com/live/Tools:/SDK:/Host/Ubuntu_10.04 /</code>
* Import the key from the following file (save it on your HDD first): http://download.meego.com/live/Tools:/SDK:/Host/Ubuntu_10.04/Release.key using the ''Import Key File...'' in the ''Authentication'' tab
Although I have not verified it, I assume the procedure would be similar for other distributions/versions.

''Note'': this package '''only''' installs <code>qemugl</code>, you should install the ''qemu-kvm'' package in Ubuntu to have tools such as <code>qemu-img</code> available too (this is needed if you want/need to build your own MeeGo image to be run by the emulator.

''Note2'': <code>qemugl</code> gets installed in <code>/opt/meego/qemu-gl/bin</code> by default. You therefore should either copy it across to <code>/usr/bin</code> or modify the launch script [http://download3.meego.com/sep09/meego-qemu-start meego-qemu-start] by editing the <code>QEMU_BIN</code> variable.

'''If you still prefer to build QEMUGL from sources, proceed with these steps:'''

Checkout the QEMU GL source code (this is basically QEMU with some patches to enable GL acceleration):

git clone git://gitorious.org/meego-developer-tools/meego-emulator-qemugl-x86.git

Checkout the qemu-gl branch:

cd meego-emulator-qemugl-x86
git checkout -b qemu-gl --track origin/qemu-gl

Make sure that there is KVM enabled and that the following libraries (development package) are installed on the host machine:

* zlib
* libSDL
* Xcomposite.

Configure qemugl:

./configure --target-list=i386-softmmu --enable-gl

Check the output from <code>configure</code> contains the strings below:

SDL support yes
......
KVM support yes

Build qemugl:

make
sudo make install

This installs various QEMU binaries (default prefix is <code>/usr/local</code>), including <code>qemugl</code> and <code>qemu-img</code> used in this tutorial.

== Create netbook image for QEMU with GL acceleration ==

''Verified on Linux (Fedora 13) on 2010-10-13 by [[User:Elliot|Elliot Smith]] using this netbook image: ''
''http://repo.meego.com/MeeGo/builds/trunk/1.1.80.1.20101012.1/netbook/images/meego-netbook-ia32/meego-netbook-ia32-1.1.80.1.20101012.1.img''

This section explains how to make a standard MeeGo netbook image run in QEMU with GL acceleration.

=== Install MeeGo netbook to QEMU raw disk image ===

Create raw image file for MeeGo to install on. The <code>qemu-img</code> command is part of the [[#Build_QEMUGL_from_source|QEMU build]]:
qemu-img create -f raw meego-netbook.raw 3.5G

Install MeeGo to the raw hard disk, using the downloaded .img file as the installation CDROM:
qemugl -m 1024 -vga std -boot d -hda meego-netbook.raw -cdrom meego-netbook-ia32-1.1.80.1.20101012.1.img

Boot into the image:
qemugl -m 1024 -vga std -boot c -hda meego-netbook.raw

Go through the installation steps to set up a meego user. The password you set here is also used as the root password, which we'll use below.

Note: occasionally I've halted the system before the meego user is setup. When I then try to boot into the UX, it fails because the user is missing. In this case, you can manually create the user from a root prompt (inside the QEMU image) with:
useradd -d /home/meego -M -s /bin/bash meego

Halt the system.

Now boot it again (this time with networking enabled; type the command below, press return, then press tab like crazy so you can get to the boot menu):
qemugl -m 1024 -vga std -net user,hostfwd=tcp:127.0.0.1:6666-:22 -net nic,model=e1000 -boot c -hda meego-netbook.raw

Next, edit the kernel command line on the boot menu screen so it looks like this:
vmlinuz-2.6.35.3-8.5-netbook ro root=/dev/sda2 vga=current s

This will get you a root prompt.

=== Install and start openssh server ===

Then install ssh server (this makes the following steps easier, as you can cut and paste into the ssh prompt):
zypper install openssh-server
chkconfig --add sshd
/etc/init.d/sshd start

Use can now use ssh to login to the image with:

ssh -p 6666 root@127.0.0.1

(password is the same as you entered for your normal user when configuring the system)

=== Set suid bit on Xorg binary ===

Once logged in over ssh, set suid on the Xorg binary (so a normal user can start X):

chmod u+s /usr/bin/Xorg

=== Install packages from the SDK repo ===

Then install the SDK addons. First, add the MeeGo SDK repo:

zypper addrepo http://download.meego.com/live/devel:/tools:/sdk:/target/Trunk/ meego-sdk

(you may need to use a different repo, depending on the netbook image you have)

'''Another alternative is to [[#Manually build packages for an image running under QEMU GL|manually build these packages in a chroot]] and install them into the image.'''

==== Install QEMU addons ====

Install the qemugl addon package into the image:

zypper install meego-sdk-qemugl-addon-netbook

==== Install kernel and virtiogl module ====

Install a current kernel and virtiogl module for it:

zypper install kernel-netbook-2.6.35.3-13.2
zypper install kmod-virtiogl

This kernel is currently (2010-10-13) the only one available in the SDK repo, but other versions should be available soon. If you need to build the SDK addons or a kernel and its modules, [[#Manually build packages for an image running under QEMU GL|instructions are given below]].

=== Run the image under QEMU with GL acceleration ===

The image should now be ready. It can be started in QEMU with this command:

qemugl -m 1024 -net user,hostfwd=tcp:127.0.0.1:6666-:22 -net nic,model=e1000 -enable-kvm -vga std -enable-gl -device virtio-gl-pci -boot c -hda meego-netbook.raw

Note that you should still be able to ssh to this image as above.

== Create handset image for QEMU with GL acceleration ==

If you have a handset image downloaded, follow these instructions to enable it to run in QEMU with GL acceleration.

Download a handset tarball (e.g. from http://meego.com/downloads/releases/1.0.80.8/meego-handset-day1-developer-preview), and untar the file:

tar xjvf meego-handset-ia32-aava-mtf-1.0.80.8.20100629.1-mrstnand.tar.bz2

(Note that this procedure should work for other images from http://repo.meego.com/MeeGo/builds/trunk/ too.)

Build kernel and modules version 2.6.35 from below section [[#Build packages for image running under QEMU GL]], to get a kernel file and module directory. Supppose the kernel file is "bzImage".

qemugl -m 1024 -boot c -hda meego-handset-ia32-aava-mtf-1.0.80.8.20100629.1-sda.bin -vga std -kernel bzImage \
--append "root=/dev/sda1 init s"

Inside the emulated image, install these packages:
zypper install xorg-x11-drv-vesa
zypper install mesa-dri-swrast-driver
zypper install openssh-server
zypper install gdb-gdbserver

Copy the kernel modules into the image. Suppose that there have been modules.tgz in host machine built from kernel build step above:
scp host@ipaddress:modules.tgz .
tar xzvf modules.tgz
mv module_directory /lib/modules/

Add a new repo file to "/etc/zypp/repos.d/". File name could be "meego-sdk.repo", and content is as below:
[meego-sdk]
name=meego-sdk
failovermethod=priority
baseurl=http://download.meego.com/live/Tools:/SDK/Trunk/
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-meego
gpgcheck=1
enabled=1

Run "zypper" to install qemugl addon package to the image:
zypper install meego-sdk-qemugl-addon-handset

We are done now. The new image could be started in QEMU with below command:
qemugl -m 1024 -boot c -hda meego-handset-ia32-aava-mtf-1.0.80.8.20100629.1-sda.bin -net user,hostfwd=tcp:127.0.0.1:6666-:22 -net \
nic,model=e1000 -vga std -enable-gl -enable-kvm -device virtio-gl-pci -kernel bzImage --append "root=/dev/sda1"

== Manually build packages for an image running under QEMU GL ==

''Verified on Linux (Fedora 13) on 2010-10-14 by [[User:Elliot|Elliot Smith]] using this netbook image: ''
''http://repo.meego.com/MeeGo/builds/trunk/1.1.80.1.20101012.1/netbook/images/meego-netbook-ia32/meego-netbook-ia32-1.1.80.1.20101012.1.img''

You can manually build the software required to run an image (netbook or handset) under QEMU with GL acceleration. But this is only recommended if a pre-built package for the software you want doesn't already exist (up-to-date packages should be available for both handset and netbook soon).

The steps below should be followed from ''inside'' a MeeGo image intended to run under QEMU. You could try this inside an emulated image, or by [[Building a MeeGo chroot on Linux|building a chroot]] from the raw disk image and working inside that (the latter is the only reasonable approach for building the kernel).

For building both the qemugl addon and the kernel+modules, you will need to install a toolchain first (either into the QEMU image, the toolchain, or both):
zypper install make gcc git patch diffutils

Alternatively, this command will get you ''all'' the MeeGo developer tools:
zypper install -t pattern development-tools

=== Build qemugl addon ===

The addon package installed in above section can also be built from source. These steps are fairly easy to do inside the QEMU image itself.

You don't need to do this if you already installed a <code>meego-sdk-qemugl-addon-*</code> package (see [[#Install QEMU addons, kernel and virtiogl module|above]]).

Install required packaged first:
zypper install libXfixes-devel libX11-devel

Checkout stub libGL source code:
git clone git://gitorious.org/meego-developer-tools/meego-emulator-libgl-x86.git

Build:
cd meego-emulator-libgl-x86
make
make install

=== Build and install kernel and modules ===

The approach we take for this is to use a chroot to build an RPM package for the new kernel and modules. This can then be easily transferred to the QEMU image and installed. Building the new kernel directly inside the QEMU image is too slow to be practical.

The first thing you'll need is a MeeGo chroot, built from the same image you're using under QEMU. See [[Building a MeeGo chroot on Linux|this page]] for instructions.

Enter the chroot.

Install <code>rpmbuild</code> (used to build the RPM from the kernel source):
zypper install rpm-build

Get the MeeGo kernel-source (this contains configuration files for building MeeGo kernels):
git clone git://gitorious.org/meego-os-base/kernel-source.git

Get the virtio patches for the kernel:
git clone git://gitorious.org/meego-developer-tools/meego-emulator-virtiogl-x86.git

Copy the virtio patch into the patches dir of kernel-source:
cp meego-emulator-virtiogl-x86/linux-2.6.35-virtio-for-qemu-gl-acceleration.patch kernel-source/patches

Download the kernel source tarball (NB you want the plain series version, not one with a patch number); in this case, I used a 2.6.35 kernel:
cd kernel-source
curl -o linux-2.6.35.tar.bz2 http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.35.tar.bz2

Remain in the <code>kernel-source</code> directory.

Edit the <code>series</code> file to add the virtiogl patch to the list of patches to apply:
# Add Virtio-mem module for QEMU GL acceleration
linux-2.6.35-virtio-for-qemu-gl-acceleration.patch

Edit the <code>config-netbook</code> file (used for both handset and netbook) to enable VIRTIOGL as a module:
CONFIG_VIRTIO_PCI=m
CONFIG_VIRTIOGL=m
# CONFIG_VIRTIO_BLK is not set
# CONFIG_VIRTIO_NET is not set
# CONFIG_VIRTIO_CONSOLE is not set
# CONFIG_HW_RANDOM_VIRTIO is not set

Delete this line from the same file (we want to set a value and it could be confusing otherwise):

# CONFIG_VIRTIO_PCI is not set

Generate spec files and config files:
make
make -f Makefile.config

This generates config files with names in the format <code>kernel-xxx.config</code>.

Patch the kernel:
./scripts/install-git-hooks
./scripts/sequence-patch.sh --quilt

Copy kernel config file into the source tree:
cp kernel-netbook.config tmp/linux-2.6.35-master/.config

Build a kernel RPM package (takes a long time):
cd tmp/linux-2.6.35-master
make oldconfig (at each prompt, accept the default)
make rpm-pkg

The resulting package is in <code>/root/rpmbuild/RPMS/i386/kernel-2.6.35.3+-1.i386.rpm</code>.

Copy this to the QEMU image over ssh or equivalent, for example:
scp -P 6666 /root/rpmbuild/RPMS/i386/kernel-2.6.35.3+-1.i386.rpm root@127.0.0.1:/root/

Get a root prompt in the QEMU image (either by booting into single user mode or logging in via ssh) and install the RPM:
rpm -ivh /root/kernel-2.6.35.3+-1.i386.rpm

Build and install the new initrd (a RAM disk image) for the kernel and modify the boot loader:
new-kernel-pkg --mkinitrd --install --make-default --depmod 2.6.35.3+
(replace 2.6.35.3+ with the version for your new kernel)

Next time you [[#Run the image under QEMU with GL acceleration|boot the image]], it should default to using the new kernel with the virtiogl module.

SDK/Docs/1.1/Building QEMU Tools

2010-10-21T14:10:17Z

Gvancuts: /* Build QEMUGL from source */

[[category:Meego-1.1]]

This page describes how to build the [http://wiki.meego.com/MeeGo_SDK_with_QEMU MeeGo SDK QEMU] tools from source, including QEMU binary, patched kernel module, and stub libGL.

== Build QEMUGL from source ==

''Verified on Linux (Fedora 13) on 2010-10-11 by [[User:Elliot|Elliot Smith]]''

'''An alternative to building from source is to install a qemugl package from one of the repositories at http://download.meego.com/live/Tools:/SDK:/Host/'''

Example of how to add this repository in Ubuntu 10.04, two steps:
* From ''Software Sources'' -> ''Other Software''; click ''Add'' and insert this line: <code>deb http://download.meego.com/live/Tools:/SDK:/Host/Ubuntu_10.04 /</code>
* Import the key from the following file (save it on your HDD first): http://download.meego.com/live/Tools:/SDK:/Host/Ubuntu_10.04/Release.key using the ''Import Key File...'' in the ''Authentication'' tab
Although I have not verified it, I assume the procedure would be similar for other distributions/versions.

'''If you still prefer to build QEMUGL from sources, proceed with these steps:'''

Checkout the QEMU GL source code (this is basically QEMU with some patches to enable GL acceleration):

git clone git://gitorious.org/meego-developer-tools/meego-emulator-qemugl-x86.git

Checkout the qemu-gl branch:

cd meego-emulator-qemugl-x86
git checkout -b qemu-gl --track origin/qemu-gl

Make sure that there is KVM enabled and that the following libraries (development package) are installed on the host machine:

* zlib
* libSDL
* Xcomposite.

Configure qemugl:

./configure --target-list=i386-softmmu --enable-gl

Check the output from <code>configure</code> contains the strings below:

SDL support yes
......
KVM support yes

Build qemugl:

make
sudo make install

This installs various QEMU binaries (default prefix is <code>/usr/local</code>), including <code>qemugl</code> and <code>qemu-img</code> used in this tutorial.

== Create netbook image for QEMU with GL acceleration ==

''Verified on Linux (Fedora 13) on 2010-10-13 by [[User:Elliot|Elliot Smith]] using this netbook image: ''
''http://repo.meego.com/MeeGo/builds/trunk/1.1.80.1.20101012.1/netbook/images/meego-netbook-ia32/meego-netbook-ia32-1.1.80.1.20101012.1.img''

This section explains how to make a standard MeeGo netbook image run in QEMU with GL acceleration.

=== Install MeeGo netbook to QEMU raw disk image ===

Create raw image file for MeeGo to install on. The <code>qemu-img</code> command is part of the [[#Build_QEMUGL_from_source|QEMU build]]:
qemu-img create -f raw meego-netbook.raw 3.5G

Install MeeGo to the raw hard disk, using the downloaded .img file as the installation CDROM:
qemugl -m 1024 -vga std -boot d -hda meego-netbook.raw -cdrom meego-netbook-ia32-1.1.80.1.20101012.1.img

Boot into the image:
qemugl -m 1024 -vga std -boot c -hda meego-netbook.raw

Go through the installation steps to set up a meego user. The password you set here is also used as the root password, which we'll use below.

Note: occasionally I've halted the system before the meego user is setup. When I then try to boot into the UX, it fails because the user is missing. In this case, you can manually create the user from a root prompt (inside the QEMU image) with:
useradd -d /home/meego -M -s /bin/bash meego

Halt the system.

Now boot it again (this time with networking enabled; type the command below, press return, then press tab like crazy so you can get to the boot menu):
qemugl -m 1024 -vga std -net user,hostfwd=tcp:127.0.0.1:6666-:22 -net nic,model=e1000 -boot c -hda meego-netbook.raw

Next, edit the kernel command line on the boot menu screen so it looks like this:
vmlinuz-2.6.35.3-8.5-netbook ro root=/dev/sda2 vga=current s

This will get you a root prompt.

=== Install and start openssh server ===

Then install ssh server (this makes the following steps easier, as you can cut and paste into the ssh prompt):
zypper install openssh-server
chkconfig --add sshd
/etc/init.d/sshd start

Use can now use ssh to login to the image with:

ssh -p 6666 root@127.0.0.1

(password is the same as you entered for your normal user when configuring the system)

=== Set suid bit on Xorg binary ===

Once logged in over ssh, set suid on the Xorg binary (so a normal user can start X):

chmod u+s /usr/bin/Xorg

=== Install packages from the SDK repo ===

Then install the SDK addons. First, add the MeeGo SDK repo:

zypper addrepo http://download.meego.com/live/devel:/tools:/sdk:/target/Trunk/ meego-sdk

(you may need to use a different repo, depending on the netbook image you have)

'''Another alternative is to [[#Manually build packages for an image running under QEMU GL|manually build these packages in a chroot]] and install them into the image.'''

==== Install QEMU addons ====

Install the qemugl addon package into the image:

zypper install meego-sdk-qemugl-addon-netbook

==== Install kernel and virtiogl module ====

Install a current kernel and virtiogl module for it:

zypper install kernel-netbook-2.6.35.3-13.2
zypper install kmod-virtiogl

This kernel is currently (2010-10-13) the only one available in the SDK repo, but other versions should be available soon. If you need to build the SDK addons or a kernel and its modules, [[#Manually build packages for an image running under QEMU GL|instructions are given below]].

=== Run the image under QEMU with GL acceleration ===

The image should now be ready. It can be started in QEMU with this command:

qemugl -m 1024 -net user,hostfwd=tcp:127.0.0.1:6666-:22 -net nic,model=e1000 -enable-kvm -vga std -enable-gl -device virtio-gl-pci -boot c -hda meego-netbook.raw

Note that you should still be able to ssh to this image as above.

== Create handset image for QEMU with GL acceleration ==

If you have a handset image downloaded, follow these instructions to enable it to run in QEMU with GL acceleration.

Download a handset tarball (e.g. from http://meego.com/downloads/releases/1.0.80.8/meego-handset-day1-developer-preview), and untar the file:

tar xjvf meego-handset-ia32-aava-mtf-1.0.80.8.20100629.1-mrstnand.tar.bz2

(Note that this procedure should work for other images from http://repo.meego.com/MeeGo/builds/trunk/ too.)

Build kernel and modules version 2.6.35 from below section [[#Build packages for image running under QEMU GL]], to get a kernel file and module directory. Supppose the kernel file is "bzImage".

qemugl -m 1024 -boot c -hda meego-handset-ia32-aava-mtf-1.0.80.8.20100629.1-sda.bin -vga std -kernel bzImage \
--append "root=/dev/sda1 init s"

Inside the emulated image, install these packages:
zypper install xorg-x11-drv-vesa
zypper install mesa-dri-swrast-driver
zypper install openssh-server
zypper install gdb-gdbserver

Copy the kernel modules into the image. Suppose that there have been modules.tgz in host machine built from kernel build step above:
scp host@ipaddress:modules.tgz .
tar xzvf modules.tgz
mv module_directory /lib/modules/

Add a new repo file to "/etc/zypp/repos.d/". File name could be "meego-sdk.repo", and content is as below:
[meego-sdk]
name=meego-sdk
failovermethod=priority
baseurl=http://download.meego.com/live/Tools:/SDK/Trunk/
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-meego
gpgcheck=1
enabled=1

Run "zypper" to install qemugl addon package to the image:
zypper install meego-sdk-qemugl-addon-handset

We are done now. The new image could be started in QEMU with below command:
qemugl -m 1024 -boot c -hda meego-handset-ia32-aava-mtf-1.0.80.8.20100629.1-sda.bin -net user,hostfwd=tcp:127.0.0.1:6666-:22 -net \
nic,model=e1000 -vga std -enable-gl -enable-kvm -device virtio-gl-pci -kernel bzImage --append "root=/dev/sda1"

== Manually build packages for an image running under QEMU GL ==

''Verified on Linux (Fedora 13) on 2010-10-14 by [[User:Elliot|Elliot Smith]] using this netbook image: ''
''http://repo.meego.com/MeeGo/builds/trunk/1.1.80.1.20101012.1/netbook/images/meego-netbook-ia32/meego-netbook-ia32-1.1.80.1.20101012.1.img''

You can manually build the software required to run an image (netbook or handset) under QEMU with GL acceleration. But this is only recommended if a pre-built package for the software you want doesn't already exist (up-to-date packages should be available for both handset and netbook soon).

The steps below should be followed from ''inside'' a MeeGo image intended to run under QEMU. You could try this inside an emulated image, or by [[Building a MeeGo chroot on Linux|building a chroot]] from the raw disk image and working inside that (the latter is the only reasonable approach for building the kernel).

For building both the qemugl addon and the kernel+modules, you will need to install a toolchain first (either into the QEMU image, the toolchain, or both):
zypper install make gcc git patch diffutils

Alternatively, this command will get you ''all'' the MeeGo developer tools:
zypper install -t pattern development-tools

=== Build qemugl addon ===

The addon package installed in above section can also be built from source. These steps are fairly easy to do inside the QEMU image itself.

You don't need to do this if you already installed a <code>meego-sdk-qemugl-addon-*</code> package (see [[#Install QEMU addons, kernel and virtiogl module|above]]).

Install required packaged first:
zypper install libXfixes-devel libX11-devel

Checkout stub libGL source code:
git clone git://gitorious.org/meego-developer-tools/meego-emulator-libgl-x86.git

Build:
cd meego-emulator-libgl-x86
make
make install

=== Build and install kernel and modules ===

The approach we take for this is to use a chroot to build an RPM package for the new kernel and modules. This can then be easily transferred to the QEMU image and installed. Building the new kernel directly inside the QEMU image is too slow to be practical.

The first thing you'll need is a MeeGo chroot, built from the same image you're using under QEMU. See [[Building a MeeGo chroot on Linux|this page]] for instructions.

Enter the chroot.

Install <code>rpmbuild</code> (used to build the RPM from the kernel source):
zypper install rpm-build

Get the MeeGo kernel-source (this contains configuration files for building MeeGo kernels):
git clone git://gitorious.org/meego-os-base/kernel-source.git

Get the virtio patches for the kernel:
git clone git://gitorious.org/meego-developer-tools/meego-emulator-virtiogl-x86.git

Copy the virtio patch into the patches dir of kernel-source:
cp meego-emulator-virtiogl-x86/linux-2.6.35-virtio-for-qemu-gl-acceleration.patch kernel-source/patches

Download the kernel source tarball (NB you want the plain series version, not one with a patch number); in this case, I used a 2.6.35 kernel:
cd kernel-source
curl -o linux-2.6.35.tar.bz2 http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.35.tar.bz2

Remain in the <code>kernel-source</code> directory.

Edit the <code>series</code> file to add the virtiogl patch to the list of patches to apply:
# Add Virtio-mem module for QEMU GL acceleration
linux-2.6.35-virtio-for-qemu-gl-acceleration.patch

Edit the <code>config-netbook</code> file (used for both handset and netbook) to enable VIRTIOGL as a module:
CONFIG_VIRTIO_PCI=m
CONFIG_VIRTIOGL=m
# CONFIG_VIRTIO_BLK is not set
# CONFIG_VIRTIO_NET is not set
# CONFIG_VIRTIO_CONSOLE is not set
# CONFIG_HW_RANDOM_VIRTIO is not set

Delete this line from the same file (we want to set a value and it could be confusing otherwise):

# CONFIG_VIRTIO_PCI is not set

Generate spec files and config files:
make
make -f Makefile.config

This generates config files with names in the format <code>kernel-xxx.config</code>.

Patch the kernel:
./scripts/install-git-hooks
./scripts/sequence-patch.sh --quilt

Copy kernel config file into the source tree:
cp kernel-netbook.config tmp/linux-2.6.35-master/.config

Build a kernel RPM package (takes a long time):
cd tmp/linux-2.6.35-master
make oldconfig (at each prompt, accept the default)
make rpm-pkg

The resulting package is in <code>/root/rpmbuild/RPMS/i386/kernel-2.6.35.3+-1.i386.rpm</code>.

Copy this to the QEMU image over ssh or equivalent, for example:
scp -P 6666 /root/rpmbuild/RPMS/i386/kernel-2.6.35.3+-1.i386.rpm root@127.0.0.1:/root/

Get a root prompt in the QEMU image (either by booting into single user mode or logging in via ssh) and install the RPM:
rpm -ivh /root/kernel-2.6.35.3+-1.i386.rpm

Build and install the new initrd (a RAM disk image) for the kernel and modify the boot loader:
new-kernel-pkg --mkinitrd --install --make-default --depmod 2.6.35.3+
(replace 2.6.35.3+ with the version for your new kernel)

Next time you [[#Run the image under QEMU with GL acceleration|boot the image]], it should default to using the new kernel with the virtiogl module.

SDK/Docs/1.1/Building QEMU Tools

2010-08-25T17:34:53Z

Gvancuts: /* Build QEMUGL from source */

This page describes how to build the [http://wiki.meego.com/MeeGo_SDK_with_QEMU MeeGo SDK QEMU] tools from source, including QEMU binary, patched kernel module, and stub libGL.

== Build QEMUGL from source ==
Checkout the QEMU GL source code
git clone git://gitorious.org/meego-developer-tools/meego-emulator-qemugl-x86.git
Switch to qemu-gl branch
cd meego-emulator-qemugl-x86
git branch qemu-gl --track origin/qemu-gl
git checkout qemu-gl
Configure qemu-gl. Make sure that there is KVM enabled and that the following libraries (development package) are installed on the host machine: zlib, libSDL, Xcomposite.
./configure --target-list=i386-softmmu --enable-gl
Check the output of configure has below strings:
SDL support yes
......
KVM support yes
build the qemu-gl
make
sudo make install
The /usr/local/bin/qemugl will be generated

== Create images for QEMU with GL acceleration ==
=== Convert normal MeeGo netbook image for MeeGo SDK ===

If you have had formal released netbook images in hand, for instance, the image from http://meego.com/downloads/releases/1.0/meego-v1.0-netbooks, below describes how to make them run in QEMU with GL acceleration.

Create raw image file for MeeGo to install on. "qemu-img" is available after install a normal qemu image on host:
qemu-img create -f raw meego1.0-netbook.raw 3.5G

Install MeeGo to raw image from the live image:
qemugl -m 1024 -enable-kvm -boot d -hda meego1.0-netbook.raw -cdrom meego-netbook-chromium-ia32-1.0-20100524.1.img -vga std

Start the MeeGo into single user mode. (Press "Tab" in booting up, and add "s" in kernel arguments), and run below command:
chmod u+s /usr/bin/Xorg
Add a new repo file to "/etc/yum.repos.d/" (if you are using yum) or "/etc/zypp/repos.d/" (if you are using zypper). File name could be "meego-sdk.repo", and content is as below:
[meego-sdk]
name=meego-sdk
failovermethod=priority
baseurl=http://download.meego.com/live/Tools:/SDK/Trunk/
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-meego
gpgcheck=1
enabled=1
Run "yum" or "zypper" to install qemugl addon package to the image:
sudo yum install meego-sdk-qemugl-addon-netbook
or
sudo zypper install meego-sdk-qemugl-addon-netbook

The packages could be downloaded directly from http://download.meego.com/live/Tools:/SDK/Trunk/i586/ and installed manually with "rpm -i" command.

Build kernel and modules version 2.6.33 from below section "Build kernel with virtio-gl kernel module". After those steps, install the new kernel into the image.

We are done now. The new image could be started in QEMU with below command:
qemugl -m 1024 -boot c -hda meego1.0-netbook.raw -net user,hostfwd=tcp:127.0.0.1:6666-:22 -net nic,model=e1000 -enable-kvm \
-vga std -enable-gl -device virtio-gl-pci

=== Convert DAY1 handset image for MeeGo SDK ===
If you have had DAY1 handset image downloaded, below describes how to make them run in QEMU with GL acceleration.

download DAY1 tarball from http://meego.com/downloads/releases/1.0.80.8/meego-handset-day1-developer-preview, and untar the file
tar xjvf meego-handset-ia32-aava-mtf-1.0.80.8.20100629.1-mrstnand.tar.bz2
Build kernel and modules version 2.6.35 from below section "Build kernel with virtio-gl kernel module", to get a kernel file and module directory. Supppose the kernel file is "bzImage".
qemugl -m 1024 -boot c -hda meego-handset-ia32-aava-mtf-1.0.80.8.20100629.1-sda.bin -vga std -kernel bzImage \
--append "root=/dev/sda1 init s"
Install some packages as follow:
zypper install xorg-x11-drv-vesa
zypper install mesa-dri-swrast-driver
zypper install openssh-server
zypper install gdb-gdbserver
Copy the kernel modules into the image. Suppose that there have been modules.tgz in host machine built from kernel build step above:
scp host@ipaddress:modules.tgz .
tar xzvf modules.tgz
mv module_directory /lib/modules/
Add a new repo file to "/etc/zypp/repos.d/". File name could be "meego-sdk.repo", and content is as below:
[meego-sdk]
name=meego-sdk
failovermethod=priority
baseurl=http://download.meego.com/live/Tools:/SDK/Trunk/
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-meego
gpgcheck=1
enabled=1
Run "zypper" to install qemugl addon package to the image:
zypper install meego-sdk-qemugl-addon-handset
We are done now. The new image could be started in QEMU with below command:
qemugl -m 1024 -boot c -hda meego-handset-ia32-aava-mtf-1.0.80.8.20100629.1-sda.bin -net user,hostfwd=tcp:127.0.0.1:6666-:22 -net \
nic,model=e1000 -vga std -enable-gl -enable-kvm -device virtio-gl-pci -kernel bzImage --append "root=/dev/sda1"

== Build packages for image running with QEMU GL ==
=== Build kernel with virtio-gl kernel module ===
In order to use GL acceleration in QEMU, Kernel needs to be rebuilt with the virtio-gl kernel module. The "virtio-gl" module is responsible for data communication between client OS and QEMU host for GL acceleration. The README in below link could be followed to build a new kernel and modules. The "kernel-netbook.config" should be used in step 8.c in README:

http://meego.gitorious.org/meego-developer-tools/meego-emulator-virtiogl-x86/trees/master

After those steps, the kernel is available in "/boot/vmlinuz-xxx" and modules are in "/lib/modules/".

=== Build qemugl addon ===
The addon package installed in above section could be built from source as well. This step is not needed if you have followed above steps to use the pre-built package already.

Checkout stub libGL source code
git clone git://gitorious.org/meego-developer-tools/meego-emulator-libgl-x86.git
Switch to chroot environment, or copy the source to a netbook running MeeGo, then run make
make