MeeGo wiki - User contributions [en]

http://wiki.meego.com/index.php?title=Special:Contributions/Suihkulokki&feed=atom&limit=50&target=Suihkulokki&year=&month= MeeGo wiki - User contributions [en] 2013-05-23T15:44:47Z From MeeGo wiki MediaWiki 1.16.2 http://wiki.meego.com/ARM/Meego_on_Qemu ARM/Meego on Qemu 2011-03-11T12:00:07Z

<p>Suihkulokki: kernel is too big these days</p> <hr /> <div>'''Under construction, experimental and unsupported'''<br /> <br /> QEMU offers one an easy way to try out MeeGo on ARM<br /> <br /> == Building QEMU ==<br /> <br /> === Prerequisites === <br /> * git (to get the source code)<br /> * build-essential<br /> * zlib (called zlib-bin and zlib1g-dev under Debian Squeeze)<br /> * SDL-devel libraries.<br /> * OsMesa (in case hardware opengl acceleration doesn't work).<br /> <br /> First we compile OpenGL ES to OpenGL acceleration library.<br /> <br /> git clone git://gitorious.org/qemu-maemo/gles-libs.git<br /> cd gles-libs/dgles2<br /> ./configure --enable-glx --enable-x11 --enable-osmesa --prefix=/opt/dgles2 --enable-offscreen<br /> make<br /> sudo make install<br /> <br /> Then we build MeeGo Qemu:<br /> <br /> git clone git://gitorious.org/qemu-maemo/qemu.git <br /> cd qemu<br /> ./configure --target-list="arm-softmmu" --enable-gles2 --gles2dir=/opt/dgles2<br /> make<br /> cp arm-softmmu/qemu-system-arm ~/bin/meego-qemu<br /> <br /> (Note: if you experience this message "cc1: warnings being treated as errors" during compilation, you can get around it with passing "--disable-werror" to "configure" as an argument)<br /> <br /> == Downloading MeeGo image ==<br /> <br /> Qemu tarball is found from:<br /> <br /> http://repo.meego.com/MeeGo/builds/trunk/latest/images/meego-handset-armv7l-qemu/<br /> <br /> get nolo-qemu and qflasher packages from non-oss repository:<br /> <br /> http://repo.meego.com/MeeGo/builds/trunk/latest/repos/non-oss/ia32/packages/i586/<br /> <br /> == Preparing MeeGo image for Qemu ==<br /> <br /> Since NAND images are missing from current autobuilds, one needs to create it manually. Replace VERSION with the version from the filename downloaded. extract qflasher and nolo-qemu rpm to current directory and: <br /> <br /> tar xvjf meego-handset-armv7l-qemu-VERSION-raw.tar.bz2<br /> cd meego-handset-armv7l-qemu-VERSION<br /> ./qflasher -m rx51 -p 3072 -x xloader-qemu.bin -s secondary-qemu.bin -k meego-handset-armv7l-qemu-vmlinuz-version-n900 -o meego-handset-armv7l-qemu-VERSION-nand.raw<br /> <br /> <br /> == Starting QEMU == <br /> <br /> When starting Qemu, you need decide if you want to use Hardware acceleration for graphics, or software rendering. Hardware rendering is known to crash qemu with Mesa-based Intel and Ati radeon drivers, While proprietary nvidia drivers are known to work. <br /> <br /> LD_LIBRARY_PATH=/opt/dgles2/lib DGLES_BACKEND=glx ~/bin/meego-qemu -M n900 \<br /> -mtdblock meego-handset-armv7l-qemu-VERSION-nand.raw -sd /dev/null -sd meego-handset-armv7l-qemu-VERSION-mmcblk0p.raw \<br /> -serial stdio -clock unix -redir tcp:5555:10.0.2.15:22<br /> <br /> If qemu crashes while initializing User interface, use DGLES_BACKEND=osmesa. The "-redir" option is for convinience, allowing you to ssh inside the qemu with ssh -p 5555 root@localhost.<br /> <br /> You can then log in with root/meego.</div>

Suihkulokki http://wiki.meego.com/ARM/Meego_on_Qemu ARM/Meego on Qemu 2011-03-11T11:30:01Z

<p>Suihkulokki: </p> <hr /> <div>'''Under construction, experimental and unsupported'''<br /> <br /> QEMU offers one an easy way to try out MeeGo on ARM<br /> <br /> == Building QEMU ==<br /> <br /> === Prerequisites === <br /> * git (to get the source code)<br /> * build-essential<br /> * zlib (called zlib-bin and zlib1g-dev under Debian Squeeze)<br /> * SDL-devel libraries.<br /> * OsMesa (in case hardware opengl acceleration doesn't work).<br /> <br /> First we compile OpenGL ES to OpenGL acceleration library.<br /> <br /> git clone git://gitorious.org/qemu-maemo/gles-libs.git<br /> cd gles-libs/dgles2<br /> ./configure --enable-glx --enable-x11 --enable-osmesa --prefix=/opt/dgles2 --enable-offscreen<br /> make<br /> sudo make install<br /> <br /> Then we build MeeGo Qemu:<br /> <br /> git clone git://gitorious.org/qemu-maemo/qemu.git <br /> cd qemu<br /> ./configure --target-list="arm-softmmu" --enable-gles2 --gles2dir=/opt/dgles2<br /> make<br /> cp arm-softmmu/qemu-system-arm ~/bin/meego-qemu<br /> <br /> (Note: if you experience this message "cc1: warnings being treated as errors" during compilation, you can get around it with passing "--disable-werror" to "configure" as an argument)<br /> <br /> == Downloading MeeGo image ==<br /> <br /> Qemu tarball is found from:<br /> <br /> http://repo.meego.com/MeeGo/builds/trunk/latest/images/meego-handset-armv7l-qemu/<br /> <br /> get nolo-qemu and qflasher packages from non-oss repository:<br /> <br /> http://repo.meego.com/MeeGo/builds/trunk/latest/repos/non-oss/ia32/packages/i586/<br /> <br /> == Preparing MeeGo image for Qemu ==<br /> <br /> Since NAND images are missing from current autobuilds, one needs to create it manually. Replace VERSION with the version from the filename downloaded. extract qflasher and nolo-qemu rpm to current directory and: <br /> <br /> tar xvjf meego-handset-armv7l-qemu-VERSION-raw.tar.bz2<br /> cd meego-handset-armv7l-qemu-VERSION<br /> ./qflasher -m rx51 -x xloader-qemu.bin -s secondary-qemu.bin -k meego-handset-armv7l-qemu-vmlinuz-version-n900 -o meego-handset-armv7l-qemu-VERSION-nand.raw<br /> <br /> <br /> == Starting QEMU == <br /> <br /> When starting Qemu, you need decide if you want to use Hardware acceleration for graphics, or software rendering. Hardware rendering is known to crash qemu with Mesa-based Intel and Ati radeon drivers, While proprietary nvidia drivers are known to work. <br /> <br /> LD_LIBRARY_PATH=/opt/dgles2/lib DGLES_BACKEND=glx ~/bin/meego-qemu -M n900 \<br /> -mtdblock meego-handset-armv7l-qemu-VERSION-nand.raw -sd /dev/null -sd meego-handset-armv7l-qemu-VERSION-mmcblk0p.raw \<br /> -serial stdio -clock unix -redir tcp:5555:10.0.2.15:22<br /> <br /> If qemu crashes while initializing User interface, use DGLES_BACKEND=osmesa. The "-redir" option is for convinience, allowing you to ssh inside the qemu with ssh -p 5555 root@localhost.<br /> <br /> You can then log in with root/meego.</div>

Suihkulokki http://wiki.meego.com/SDK/Qemu SDK/Qemu 2011-03-11T10:03:50Z

<p>Suihkulokki: </p> <hr /> <div>= MeeGo QEMU Team =<br /> <br /> MeeGo Qemu team maintains QEMU system emulator for MeeGo SDK and QEMU linux-user emulator for OBS builders. Legacy support for scratchbox and Nokia N900 Running Maemo5 is provided as well.<br /> <br /> == Users of QEMU ==<br /> <br /> Currently each and every consumer of QEMU under the MeeGo umbrella has their own version of Qemu. The plan is to migrate all this versions to a single repository, merge all code together, and then start tagging releases which will be same for all.<br /> <br /> * MeeGo ARM Qemu<br /> ** OpenGL ES 2.0 accelerated ARM [[ARM/Meego_on_Qemu| QEMU for N900]].<br /> ** Smoke test: Maemo5 and latest Meego N900 images boot and display UI<br /> * Qemugl<br /> ** OpenGL accelerated X86 [[SDK/Docs/1.1/Building_QEMU_Tools| QEMU for X86]] handset and netbook images.<br /> ** Smoke test: That x86 handset and netbook images boot and display UI<br /> * OBS Qemu<br /> ** Used internaly by OBS to build ARM packages<br /> ** url?<br /> ** Smoke test: arm build round without regressions<br /> * Scratchbox Qemu<br /> ** Used by scratchbox to allow building ARM packages<br /> ** url: merged with MeeGo Qemu.<br /> ** Smoke test: arm build round without regressions<br /> <br /> == Development ==<br /> <br /> The main repository For MeeGo Qemu is [http://meego.gitorious.org/qemu-maemo MeeGo Qemu on gitorious]. Upstream is at [http://www.qemu.org qemu.org].<br /> <br /> === Version control strategy ===<br /> <br /> In this documentation we shall refer to upstream git as "origin" and the the MeeGo QEMU gitorious repository as "meego". <br /> <br /> $ git clone git://git.qemu.org/qemu.git<br /> $ cd qemu<br /> $ git remote add meego git://gitorious.org/qemu-maemo/qemu.git<br /> $ git fetch meego<br /> <br /> The rule of thumb in development is "keep up to date with upstream". To achieve this, we rebase with upstream often. rebasing<br /> causes some pain, but that should be seen as an incentive to push the patches upstream.<br /> <br /> Qemu head (origin/master)<br /> |<br /> (periodic rebase)<br /> |<br /> MeeGo Qemu master (meego/master)<br /> |<br /> |<br /> Everyones working branches ^<br /> <br /> Where the working branches are "temporary" in nature. Eg once the code in the working branches have been applied (via git merge/cherry-pick/rebase or by hand), that working branch is thrown away and a new branch is created.<br /> <br /> Being branches on top of rebased branches means one cant just "merge" changes from upstream branches - one either must rebase their own branch, or cherrypick selected changes in.<br /> <br /> === Submitting merge requests to MeeGo QEMU ===<br /> <br /> Gitorious provides "request merge" functionality, which can be used to propose changes to MeeGo Qemu.<br /> <br /> Alternatively, people with commit access to MeeGo gitorious can push their branches for merging to MeeGo gitorious directly.git offers infinite amount of was to do that, but there is two that are probably most practical<br /> <br /> * Cherry-pick commits from your working branch<br /> <br /> $ git fetch meego # Make sure you are up to date<br /> $ git checkout -b temp-branch-name meego/master<br /> $ git log your-local-working-branch # pick the commit-id's of changes you want<br /> $ git cherry-pick commit-id<br /> $ vi foo.c # cleanup if necessary<br /> $ commit -a --amend # improve commit message if necessary<br /> $ git push meego temp-branch-name<br /> <br /> * rebase working branch on top of latest dvcs<br /> <br /> $ git fetch meego<br /> $ git checkout -b temp-branch-name your-local-working-branch<br /> $ git rebase -i meego/master<br /> $ # follow instructions on editor<br /> $ git push master temp-branch-name<br /> <br /> Where the working branches are "temporary" in nature. Eg once the code in the working branches have been applied (via git<br /> merge/cherry-pick/rebase or by hand), that working branch is thrown away and a new branch is created.<br /> <br /> Being branches on top of rebased branches means one cant just "merge"changes from upstream branches - one either must rebase their own branch, or cherrypick selected changes in.<br /> <br /> == Documentation ==<br /> <br /> === Building Qemu ===<br /> <br /> For ARM<br /> <br /> git clone git://gitorious.org/qemu-maemo/gles-libs.git<br /> cd gles-libs/dgles2<br /> ./configure --enable-glx --enable-x11 --enable-osmesa --prefix=/opt/dgles2<br /> make install<br /> <br /> git clone git://gitorious.org/qemu-maemo/qemu.git <br /> cd qemu<br /> ./configure --target-list="arm-softmmu arm-linux-user" --enable-gles2 --gles2dir=/opt/dgles2<br /> make<br /> <br /> === Creating MeeGo Qemu images ===<br /> <br /> * Meego [[SDK/Tutorials/Image_Creation| N900 Qemu Image instructions]] for 1.1.<br /> * Meego [[SDK/Docs/1.1/Building_QEMU_Tools| X86 Qemu Image instructions]] for 1.1.<br /> <br /> === Troubleshooting ===<br /> <br /> == The team and the work ==<br /> <br /> This QEMU adaptation team maintains and develops Qemu for MeeGo.<br /> <br /> The current team members are (in no particular order):<br /> <br /> {| border="1" cellspacing="0"<br /> |+<br /> ! Name<br /> ! Area<br /> ! Role<br /> ! Affiliation<br /> ! IRC nickname<br /> |- <br /> | Riku Voipio || Linux-user and Arm system || Maintainer || Nokia || suihkulokki<br /> |- <br /> | Juha Riihimäki || Arm system || Team member || Nokia || __jr<br /> |- <br /> | [http://meego.com/users/fabo Fathi Boudra] || || Package maintainer || Nokia || fabo<br /> |-<br /> | Haitao Feng || OpenGL and OpenGL ES enabling and acceleration || Team member || Intel || haitao<br /> |-<br /> | Zhiyuan Lv || OpenGL and OpenGL ES enabling and acceleration || Team member || Intel || zhiyuan<br /> |-<br /> | Jun Tian || Skin and Device simulation || Team member || Intel || juntian<br /> |- <br /> | Joonas Lahtinen || OpenGL ES acceleration framework design || Team member || Nomovok || dolphin<br /> |}<br /> <br /> Our collaboration spaces are:<br /> <br /> * [[SDK/Qemu/Tasks]] task tracker on wiki<br /> * [[SDK/Qemu/OpenGLES]] OpenGL ES plan for x86 handset on the wiki<br /> * [[SDK/Emulator]] MeeGo X86 Emulator device simulation task tracker<br /> * [[SDK/Emulator/Skin]] MeeGo Skin usage manual<br /> * [http://lists.meego.com/listinfo/meego-dev meego-dev@meego.com mailing list], please prefix with 'QEMU' for team related topics.<br /> * [http://webchat.freenode.net/?channels=meego-sdk #meego-qemu IRC channel on irc.freenode.net]([http://trac.tspre.org/merbot/freenode/%23meego-sdk/ IRC channel logs])<br /> * #qemu IRC channel on irc.oftc.net<br /> * Gitorious team, http://gitorious.org/+meego-qemu-developers and all repositories on http://meego.gitorious.org/qemu-maemo<br /> * [https://build.meego.com/project/monitor?project=Tools:SDK:Host Tools:SDK:Host project] on MeeGo OBS<br /> * xxx project on MeeGo OBS<br /> * This wiki area<br /> <br /> [[Category:SDK]]</div>

Suihkulokki http://wiki.meego.com/ARM/Meego_on_Qemu ARM/Meego on Qemu 2011-03-11T09:37:38Z

<p>Suihkulokki: add notes about creating nand image</p> <hr /> <div>'''Under construction, experimental and unsupported'''<br /> <br /> QEMU offers one an easy way to try out MeeGo on ARM<br /> <br /> == Building QEMU ==<br /> <br /> === Prerequisites === <br /> * git (to get the source code)<br /> * build-essential<br /> * zlib (called zlib-bin and zlib1g-dev under Debian Squeeze)<br /> * SDL-devel libraries.<br /> * OsMesa (in case hardware opengl acceleration doesn't work).<br /> <br /> First we compile OpenGL ES to OpenGL acceleration library.<br /> <br /> git clone git://gitorious.org/qemu-maemo/gles-libs.git<br /> cd gles-libs/dgles2<br /> ./configure --enable-glx --enable-x11 --enable-osmesa --prefix=/opt/dgles2 --enable-offscreen<br /> make<br /> sudo make install<br /> <br /> Then we build MeeGo Qemu:<br /> <br /> git clone git://gitorious.org/qemu-maemo/qemu.git <br /> cd qemu<br /> ./configure --target-list="arm-softmmu" --enable-gles2 --gles2dir=/opt/dgles2<br /> make<br /> cp arm-softmmu/qemu-system-arm ~/bin/meego-qemu<br /> <br /> (Note: if you experience this message "cc1: warnings being treated as errors" during compilation, you can get around it with passing "--disable-werror" to "configure" as an argument)<br /> <br /> == Downloading MeeGo image ==<br /> <br /> Qemu tarball is found from:<br /> <br /> http://repo.meego.com/MeeGo/builds/trunk/latest/images/meego-handset-armv7l-qemu/<br /> <br /> get nolo-qemu and qflasher packages from non-oss repository (e.g. http://repo.meego.com/MeeGo/builds/trunk/daily/non-oss/repos/ia32/packages/i586/)<br /> <br /> == Preparing MeeGo image for Qemu ==<br /> <br /> Since NAND images are missing from current autobuilds, one needs to create it manually. Replace VERSION with the version from the filename downloaded. extract qflasher and nolo-qemu rpm to current directory and: <br /> <br /> tar xvjf meego-handset-armv7l-qemu-VERSION-raw.tar.bz2<br /> cd meego-handset-armv7l-qemu-VERSION<br /> ./qflasher -m rx51 -x xloader-qemu.bin -s secondary-qemu.bin -k meego-handset-armv7l-qemu-vmlinuz-version-n900 -o meego-handset-armv7l-qemu-VERSION-nand.raw<br /> <br /> <br /> == Starting QEMU == <br /> <br /> When starting Qemu, you need decide if you want to use Hardware acceleration for graphics, or software rendering. Hardware rendering is known to crash qemu with Mesa-based Intel and Ati radeon drivers, While proprietary nvidia drivers are known to work. <br /> <br /> LD_LIBRARY_PATH=/opt/dgles2/lib DGLES_BACKEND=glx qemu-system-arm -M n900 \<br /> -mtdblock meego-handset-armv7l-qemu-VERSION-nand.raw -sd /dev/null -sd meego-handset-armv7l-qemu-VERSION-mmcblk0p.raw \<br /> -serial stdio -clock unix -redir tcp:5555:10.0.2.15:22<br /> <br /> If qemu crashes while initializing User interface, use DGLES_BACKEND=osmesa. The "-redir" option is for convinience, allowing you to ssh inside the qemu with ssh -p 5555 root@localhost.<br /> <br /> You can then log in with root/meego.</div>

Suihkulokki http://wiki.meego.com/ARM/Meego_on_Qemu ARM/Meego on Qemu 2011-03-10T16:03:12Z

<p>Suihkulokki: update to latest images</p> <hr /> <div>'''Under construction, experimental and unsupported'''<br /> <br /> QEMU offers one an easy way to try out MeeGo on ARM<br /> <br /> == Building QEMU ==<br /> <br /> === Prerequisites === <br /> * git (to get the source code)<br /> * build-essential<br /> * zlib (called zlib-bin and zlib1g-dev under Debian Squeeze)<br /> * SDL-devel libraries.<br /> * OsMesa (in case hardware opengl acceleration doesn't work).<br /> <br /> First we compile OpenGL ES to OpenGL acceleration library.<br /> <br /> git clone git://gitorious.org/qemu-maemo/gles-libs.git<br /> cd gles-libs/dgles2<br /> ./configure --enable-glx --enable-x11 --enable-osmesa --prefix=/opt/dgles2 --enable-offscreen<br /> make<br /> sudo make install<br /> <br /> Then we build MeeGo Qemu:<br /> <br /> git clone git://gitorious.org/qemu-maemo/qemu.git <br /> cd qemu<br /> ./configure --target-list="arm-softmmu" --enable-gles2 --gles2dir=/opt/dgles2<br /> make<br /> cp arm-softmmu/qemu-system-arm ~/bin/meego-qemu<br /> <br /> (Note: if you experience this message "cc1: warnings being treated as errors" during compilation, you can get around it with passing "--disable-werror" to "configure" as an argument)<br /> <br /> == Downloading MeeGo image ==<br /> <br /> Qemu tarball is found from:<br /> <br /> http://repo.meego.com/MeeGo/builds/trunk/latest/images/meego-handset-armv7l-qemu/<br /> <br /> == Starting QEMU == <br /> <br /> When starting Qemu, you need decide if you want to use Hardware acceleration for graphics, or software rendering. Hardware rendering is known to crash qemu with Mesa-based Intel and Ati radeon drivers, While proprietary nvidia drivers are known to work. Replace VERSION with the version from the filename downloaded.<br /> <br /> tar xvjf meego-handset-armv7l-qemu-VERSION-raw.tar.bz2<br /> cd meego-handset-armv7l-qemu-VERSION<br /> LD_LIBRARY_PATH=/opt/dgles2/lib DGLES_BACKEND=glx qemu-system-arm -M n900 \<br /> -mtdblock meego-handset-armv7l-qemu-VERSION-nand.raw -sd /dev/null -sd meego-handset-armv7l-qemu-VERSION-mmcblk0p.raw \<br /> -serial stdio -clock unix<br /> <br /> If qemu crashes while initializing User interface, use DGLES_BACKEND=osmesa.<br /> <br /> You can then log in with root/meego.</div>

Suihkulokki http://wiki.meego.com/ARM/N900/DeveloperEdition. ARM/N900/DeveloperEdition. 2011-03-03T14:16:00Z

<p>Suihkulokki: Redirected page to ARM/N900/DeveloperEdition</p> <hr /> <div>#REDIRECT [[ARM/N900/DeveloperEdition]]</div>

Suihkulokki http://wiki.meego.com/ARM/N900/DeveloperEdition. ARM/N900/DeveloperEdition. 2011-03-03T14:15:38Z

<p>Suihkulokki: Created page with "#REDIRCT ARM/N900/DeveloperEdition"</p> <hr /> <div>#REDIRCT [[ARM/N900/DeveloperEdition]]</div>

Suihkulokki http://wiki.meego.com/SDK/Qemu/Whiteboard SDK/Qemu/Whiteboard 2011-02-03T12:45:33Z

<p>Suihkulokki: </p> <hr /> <div>== Backlog ==<br /> <br /> * qemu project merge<br /> ** add current qemu-gl branch to merged repository<br /> ** rebase qemu-gl on top of merged repository<br /> ** add current OBS qemu branch to merged repository<br /> <br /> * x11 frontend for dgles2<br /> ** test functionality for qt creator simulator<br /> ** test functionality for x86 handset image<br /> <br /> * images<br /> ** mic should create qcow2 images for qemu, current images are 2.5G while qcow2's take < 1GB:<br /> qemu-img convert -f raw -O qcow2 -c meego-handset-armv7l-qemu-nand.img meego-handset-armv7l-qemu-nand.qcow2<br /> qemu-img convert -f raw -O qcow2 meego-handset-armv7l-qemu-mmcblk0p.raw meego-handset-armv7l-qemu-mmcblk0p.qcow2<br /> <br /> ** link [[SDK/Qemu]] page with latest known working arm handset image<br /> ** link [[SDK/Qemu]] page with latest known working x86 handset image<br /> ** link [[SDK/Qemu]] page with latest known working x86 netbook image<br /> ** links should come with commit ID's/git tags of knows working qemu versions<br /> <br /> * linux-user<br /> ** mutex lock-up issues https://bugs.launchpad.net/qemu/+bug/668799<br /> ** memory allocator issues<br /> ** refresh with latest syscall patches<br /> <br /> * bugs affecting us<br /> ** multitouch/xinput2 breaks Qt, no clicks work. https://bugs.meego.com/show_bug.cgi?id=12829<br /> <br /> <br /> <br /> == Under work ==<br /> <br /> == Done ==</div>

Suihkulokki http://wiki.meego.com/SDK/Qemu/Tasks SDK/Qemu/Tasks 2011-02-03T12:39:48Z

<p>Suihkulokki: moved SDK/Qemu/Tasks to SDK/Qemu/Whiteboard:&#32;Not really tasks but random stuff related to Qemu</p> <hr /> <div>#REDIRECT [[SDK/Qemu/Whiteboard]]</div>

Suihkulokki http://wiki.meego.com/SDK/Qemu/Whiteboard SDK/Qemu/Whiteboard 2011-02-03T12:39:48Z

<p>Suihkulokki: moved SDK/Qemu/Tasks to SDK/Qemu/Whiteboard:&#32;Not really tasks but random stuff related to Qemu</p> <hr /> <div>== Backlog ==<br /> <br /> * qemu project merge<br /> ** add current qemu-gl branch to merged repository<br /> ** rebase qemu-gl on top of merged repository<br /> ** add current OBS qemu branch to merged repository<br /> <br /> * x11 frontend for dgles2<br /> ** test functionality for qt creator simulator<br /> ** test functionality for x86 handset image<br /> <br /> * images<br /> ** link [[SDK/Qemu]] page with latest known working arm handset image<br /> ** link [[SDK/Qemu]] page with latest known working x86 handset image<br /> ** link [[SDK/Qemu]] page with latest known working x86 netbook image<br /> ** links should come with commit ID's/git tags of knows working qemu versions<br /> <br /> * linux-user<br /> ** mutex lock-up issues https://bugs.launchpad.net/qemu/+bug/668799<br /> ** memory allocator issues<br /> ** refresh with latest syscall patches<br /> <br /> * bugs affecting us<br /> ** multitouch/xinput2 breaks Qt, no clicks work. https://bugs.meego.com/show_bug.cgi?id=12829 <br /> <br /> == Under work ==<br /> <br /> == Done ==</div>

Suihkulokki http://wiki.meego.com/SDK/Qemu/Whiteboard SDK/Qemu/Whiteboard 2011-02-01T09:44:11Z

<p>Suihkulokki: </p> <hr /> <div>== Backlog ==<br /> <br /> * qemu project merge<br /> ** add current qemu-gl branch to merged repository<br /> ** rebase qemu-gl on top of merged repository<br /> ** add current OBS qemu branch to merged repository<br /> <br /> * x11 frontend for dgles2<br /> ** test functionality for qt creator simulator<br /> ** test functionality for x86 handset image<br /> <br /> * images<br /> ** link [[SDK/Qemu]] page with latest known working arm handset image<br /> ** link [[SDK/Qemu]] page with latest known working x86 handset image<br /> ** link [[SDK/Qemu]] page with latest known working x86 netbook image<br /> ** links should come with commit ID's/git tags of knows working qemu versions<br /> <br /> * linux-user<br /> ** mutex lock-up issues https://bugs.launchpad.net/qemu/+bug/668799<br /> ** memory allocator issues<br /> ** refresh with latest syscall patches<br /> <br /> * bugs affecting us<br /> ** multitouch/xinput2 breaks Qt, no clicks work. https://bugs.meego.com/show_bug.cgi?id=12829 <br /> <br /> == Under work ==<br /> <br /> == Done ==</div>

Suihkulokki http://wiki.meego.com/SDK/Qemu SDK/Qemu 2011-02-01T09:43:21Z

<p>Suihkulokki: </p> <hr /> <div>= MeeGo QEMU Team =<br /> <br /> MeeGo Qemu team maintains QEMU system emulator for MeeGo SDK and QEMU linux-user emulator for OBS builders. Legacy support for scratchbox and Nokia N900 Running Maemo5 is provided as well.<br /> <br /> == Consumers of QEMU ==<br /> <br /> Currently each and every consumer of QEMU under the MeeGo umbrella has their own version of Qemu. The plan is to migrate all this versions to a single repository, merge all code together, and then start tagging releases which will be same for all.<br /> <br /> * MeeGo Qemu<br /> ** OpenGL ES 2.0 accelerated QEMU<br /> ** http://wiki.meego.com/ARM/Meego_on_Qemu<br /> ** Smoke test: Maemo5 and latest Meego N900 images boot and display UI<br /> * Qemugl<br /> ** OpenGL accelerated Qemu for intel images<br /> ** http://wiki.meego.com/SDK/Docs/1.1/Building_QEMU_Tools<br /> ** Smoke test: That x86 handset and netbook images boot and display UI<br /> * OBS Qemu<br /> ** Used internaly by OBS to build ARM packages<br /> ** url?<br /> ** Smoke test: arm build round without regressions<br /> * Scratchbox Qemu<br /> ** Used by scratchbox to allow building ARM packages<br /> ** url: merged with MeeGo Qemu.<br /> ** Smoke test: arm build round without regressions<br /> <br /> == Development ==<br /> <br /> The main repository For MeeGo Qemu is [http://meego.gitorious.org/qemu-maemo MeeGo Qemu on gitorious]. Upstream is at [http://www.qemu.org qemu.org].<br /> <br /> === Version control strategy ===<br /> <br /> In this documentation we shall refer to upstream git as "origin" and the the MeeGo QEMU gitorious repository as "meego". <br /> <br /> $ git clone git://git.qemu.org/qemu.git<br /> $ cd qemu<br /> $ git remote add meego git://gitorious.org/qemu-maemo/qemu.git<br /> $ git fetch meego<br /> <br /> The rule of thumb in development is "keep up to date with upstream". To achieve this, we rebase with upstream often. rebasing<br /> causes some pain, but that should be seen as an incentive to push the patches upstream.<br /> <br /> Qemu head (origin/master)<br /> |<br /> (periodic rebase)<br /> |<br /> MeeGo Qemu master (meego/master)<br /> |<br /> |<br /> Everyones working branches ^<br /> <br /> Where the working branches are "temporary" in nature. Eg once the code in the working branches have been applied (via git merge/cherry-pick/rebase or by hand), that working branch is thrown away and a new branch is created.<br /> <br /> Being branches on top of rebased branches means one cant just "merge" changes from upstream branches - one either must rebase their own branch, or cherrypick selected changes in.<br /> <br /> === Submitting merge requests to MeeGo QEMU ===<br /> <br /> Gitorious provides "request merge" functionality, which can be used to propose changes to MeeGo Qemu.<br /> <br /> Alternatively, people with commit access to MeeGo gitorious can push their branches for merging to MeeGo gitorious directly.git offers infinite amount of was to do that, but there is two that are probably most practical<br /> <br /> * Cherry-pick commits from your working branch<br /> <br /> $ git fetch meego # Make sure you are up to date<br /> $ git checkout -b temp-branch-name meego/master<br /> $ git log your-local-working-branch # pick the commit-id's of changes you want<br /> $ git cherry-pick commit-id<br /> $ vi foo.c # cleanup if necessary<br /> $ commit -a --amend # improve commit message if necessary<br /> $ git push meego temp-branch-name<br /> <br /> * rebase working branch on top of latest dvcs<br /> <br /> $ git fetch meego<br /> $ git checkout -b temp-branch-name your-local-working-branch<br /> $ git rebase -i meego/master<br /> $ # follow instructions on editor<br /> $ git push master temp-branch-name<br /> <br /> Where the working branches are "temporary" in nature. Eg once the code in the working branches have been applied (via git<br /> merge/cherry-pick/rebase or by hand), that working branch is thrown away and a new branch is created.<br /> <br /> Being branches on top of rebased branches means one cant just "merge"changes from upstream branches - one either must rebase their own branch, or cherrypick selected changes in.<br /> <br /> == Documentation ==<br /> <br /> === Building Qemu ===<br /> <br /> For ARM<br /> <br /> git clone git://gitorious.org/qemu-maemo/gles-libs.git<br /> cd gles-libs/dgles2<br /> ./configure --enable-glx --enable-x11 --enable-osmesa --prefix=/opt/dgles2<br /> make install<br /> <br /> git clone git://gitorious.org/qemu-maemo/qemu.git <br /> cd qemu<br /> ./configure --target-list="arm-softmmu arm-linux-user" --enable-gles2 --gles2dir=/opt/dgles2<br /> make<br /> <br /> === Creating MeeGo Qemu images for N900 ===<br /> <br /> === Creating MeeGo Qemu images for Intel ===<br /> <br /> Meego [http://wiki.meego.com/SDK/Docs/1.1/Building_QEMU_Tools Qemu Image instructions] for 1.1.<br /> <br /> === Troubleshooting ===<br /> <br /> == The team and the work ==<br /> <br /> This QEMU adaptation team maintains and develops Qemu for MeeGo.<br /> <br /> The current team members are (in no particular order):<br /> <br /> {| border="1" cellspacing="0"<br /> |+<br /> ! Name<br /> ! Area<br /> ! Role<br /> ! Affiliation<br /> ! IRC nickname<br /> |- <br /> | Riku Voipio || Linux-user and Arm system || Maintainer || Nokia || suihkulokki<br /> |- <br /> | Juha Riihimäki || Arm system || Team member || Nokia || __jr<br /> |- <br /> | [http://meego.com/users/fabo Fathi Boudra] || || Package maintainer || Nokia || fabo<br /> |-<br /> | Haitao Feng || OpenGL and OpenGL ES enabling and acceleration || Team member || Intel || haitao<br /> |-<br /> | Zhiyuan Lv || OpenGL and OpenGL ES enabling and acceleration || Team member || Intel || zhiyuan<br /> |-<br /> | Jun Tian || Skin || Team member || Intel || juntian<br /> |}<br /> <br /> Our collaboration spaces are:<br /> <br /> * [[SDK/Qemu/Tasks]] task tracker on wiki<br /> * [[SDK/Qemu/OpenGLES]] OpenGL ES plan for x86 handset on the wiki<br /> * [http://lists.meego.com/listinfo/meego-dev meego-dev@meego.com mailing list], please prefix with 'QEMU' for team related topics.<br /> * [http://webchat.freenode.net/?channels=meego-sdk #meego-qemu IRC channel on irc.freenode.net]([http://trac.tspre.org/merbot/freenode/%23meego-sdk/ IRC channel logs])<br /> * #qemu IRC channel on irc.oftc.net<br /> * Gitorious team, http://gitorious.org/+meego-qemu-developers and all repositories on http://meego.gitorious.org/qemu-maemo<br /> * [https://build.meego.com/project/monitor?project=Tools:SDK:Host Tools:SDK:Host project] on MeeGo OBS<br /> * xxx project on MeeGo OBS<br /> * This wiki area<br /> <br /> [[Category:SDK]]</div>

Suihkulokki http://wiki.meego.com/SDK/Qemu SDK/Qemu 2011-02-01T09:42:15Z

<p>Suihkulokki: </p> <hr /> <div>= MeeGo QEMU Team =<br /> <br /> MeeGo Qemu team maintains QEMU system emulator for MeeGo SDK and QEMU linux-user emulator for OBS builders. Legacy support for scratchbox and Nokia N900 Running Maemo5 is provided as well.<br /> <br /> == Consumers of QEMU ==<br /> <br /> Currently each and every consumer of QEMU under the MeeGo umbrella has their own version of Qemu. The plan is to migrate all this versions to a single repository, merge all code together, and then start tagging releases which will be same for all.<br /> <br /> * MeeGo Qemu<br /> ** OpenGL ES 2.0 accelerated QEMU<br /> ** http://wiki.meego.com/ARM/Meego_on_Qemu<br /> ** Smoke test: Maemo5 and latest Meego N900 images boot and display UI<br /> * Qemugl<br /> ** OpenGL accelerated Qemu for intel images<br /> ** http://wiki.meego.com/SDK/Docs/1.1/Building_QEMU_Tools<br /> ** Smoke test: That x86 handset and netbook images boot and display UI<br /> * OBS Qemu<br /> ** Used internaly by OBS to build ARM packages<br /> ** url?<br /> ** Smoke test: arm build round without regressions<br /> * Scratchbox Qemu<br /> ** Used by scratchbox to allow building ARM packages<br /> ** url: merged with MeeGo Qemu.<br /> ** Smoke test: arm build round without regressions<br /> <br /> == Development ==<br /> <br /> The main repository For MeeGo Qemu is [http://meego.gitorious.org/qemu-maemo MeeGo Qemu on gitorious]. Upstream is at [http://www.qemu.org qemu.org].<br /> <br /> === Version control strategy ===<br /> <br /> In this documentation we shall refer to upstream git as "origin" and the the MeeGo QEMU gitorious repository as "meego". <br /> <br /> $ git clone git://git.qemu.org/qemu.git<br /> $ cd qemu<br /> $ git remote add meego git://gitorious.org/qemu-maemo/qemu.git<br /> $ git fetch meego<br /> <br /> The rule of thumb in development is "keep up to date with upstream". To achieve this, we rebase with upstream often. rebasing<br /> causes some pain, but that should be seen as an incentive to push the patches upstream.<br /> <br /> Qemu head (origin/master)<br /> |<br /> (periodic rebase)<br /> |<br /> MeeGo Qemu master (meego/master)<br /> |<br /> |<br /> Everyones working branches ^<br /> <br /> Where the working branches are "temporary" in nature. Eg once the code in the working branches have been applied (via git merge/cherry-pick/rebase or by hand), that working branch is thrown away and a new branch is created.<br /> <br /> Being branches on top of rebased branches means one cant just "merge" changes from upstream branches - one either must rebase their own branch, or cherrypick selected changes in.<br /> <br /> === Submitting merge requests to MeeGo QEMU ===<br /> <br /> Gitorious provides "request merge" functionality, which can be used to propose changes to MeeGo Qemu.<br /> <br /> Alternatively, people with commit access to MeeGo gitorious can push their branches for merging to MeeGo gitorious directly.git offers infinite amount of was to do that, but there is two that are probably most practical<br /> <br /> * Cherry-pick commits from your working branch<br /> <br /> $ git fetch meego # Make sure you are up to date<br /> $ git checkout -b temp-branch-name meego/master<br /> $ git log your-local-working-branch # pick the commit-id's of changes you want<br /> $ git cherry-pick commit-id<br /> $ vi foo.c # cleanup if necessary<br /> $ commit -a --amend # improve commit message if necessary<br /> $ git push meego temp-branch-name<br /> <br /> * rebase working branch on top of latest dvcs<br /> <br /> $ git fetch meego<br /> $ git checkout -b temp-branch-name your-local-working-branch<br /> $ git rebase -i meego/master<br /> $ # follow instructions on editor<br /> $ git push master temp-branch-name<br /> <br /> Where the working branches are "temporary" in nature. Eg once the code in the working branches have been applied (via git<br /> merge/cherry-pick/rebase or by hand), that working branch is thrown away and a new branch is created.<br /> <br /> Being branches on top of rebased branches means one cant just "merge"changes from upstream branches - one either must rebase their own branch, or cherrypick selected changes in.<br /> <br /> == Documentation ==<br /> <br /> === Building Qemu ===<br /> <br /> For ARM<br /> <br /> git clone git://gitorious.org/qemu-maemo/gles-libs.git<br /> cd gles-libs/dgles2<br /> ./configure --enable-glx --enable-x11 --enable-osmesa --prefix=/opt/dgles2<br /> make install<br /> <br /> git clone git://gitorious.org/qemu-maemo/qemu.git <br /> cd qemu<br /> ./configure --target-list="arm-softmmu arm-linux-user" --enable-gles2 --gles2dir=/opt/dgles2<br /> make<br /> <br /> === Creating MeeGo Qemu images for N900 ===<br /> <br /> === Creating MeeGo Qemu images for Intel ===<br /> <br /> Meego [http://wiki.meego.com/SDK/Docs/1.1/Building_QEMU_Tools Qemu Image instructions] for 1.1.<br /> <br /> === Troubleshooting ===<br /> <br /> == The team and the work ==<br /> <br /> This QEMU adaptation team maintains and develops Qemu for MeeGo.<br /> <br /> The current team members are (in no particular order):<br /> <br /> {| border="1" cellspacing="0"<br /> |+<br /> ! Name<br /> ! Area<br /> ! Role<br /> ! Affiliation<br /> ! IRC nickname<br /> |- <br /> | Riku Voipio || Linux-user and Arm system || Maintainer || Nokia || suihkulokki<br /> |- <br /> | Juha Riihimäki || Arm system || Team member || Nokia || __jr<br /> |- <br /> | [http://meego.com/users/fabo Fathi Boudra] || || Package maintainer || Nokia || fabo<br /> |-<br /> | Haitao Feng || OpenGL and OpenGL ES enabling and acceleration || Team member || Intel || haitao<br /> |-<br /> | Zhiyuan Lv || OpenGL and OpenGL ES enabling and acceleration || Team member || Intel || zhiyuan<br /> |-<br /> | Jun Tian || Skin || Team member || Intel || juntian<br /> |}<br /> <br /> Our collaboration spaces are:<br /> <br /> * [SDK/Qemu/Tasks task tracker] on wiki<br /> * [SDK/Qemu/OpenGLES OpenGL ES] fof x86 handset on the wiki<br /> * [http://lists.meego.com/listinfo/meego-dev meego-dev@meego.com mailing list], please prefix with 'QEMU' for team related topics.<br /> * [http://webchat.freenode.net/?channels=meego-sdk #meego-qemu IRC channel on irc.freenode.net]([http://trac.tspre.org/merbot/freenode/%23meego-sdk/ IRC channel logs])<br /> * #qemu IRC channel on irc.oftc.net<br /> * Gitorious team, http://gitorious.org/+meego-qemu-developers and all repositories on http://meego.gitorious.org/qemu-maemo<br /> * [https://build.meego.com/project/monitor?project=Tools:SDK:Host Tools:SDK:Host project] on MeeGo OBS<br /> * xxx project on MeeGo OBS<br /> * This wiki area<br /> <br /> [[Category:SDK]]</div>

Suihkulokki http://wiki.meego.com/SDK/Qemu/Whiteboard SDK/Qemu/Whiteboard 2011-02-01T09:39:41Z

<p>Suihkulokki: Created page with "== Backlog == * qemu project merge * add current qemu-gl branch to merged repository * rebase qemu-gl on top of merged repository * add current OBS qemu branch to merged r…"</p> <hr /> <div>== Backlog ==<br /> <br /> * qemu project merge<br /> * add current qemu-gl branch to merged repository<br /> * rebase qemu-gl on top of merged repository<br /> * add current OBS qemu branch to merged repository<br /> <br /> * x11 frontend for dgles2<br /> * test functionality for qt creator simulator<br /> * test functionality for x86 handset image<br /> <br /> * images<br /> * link [[SDK/Qemu]] page with latest known working arm handset image<br /> * link [[SDK/Qemu]] page with latest known working x86 handset image<br /> * link [[SDK/Qemu]] page with latest known working x86 netbook image<br /> * links should come with commit ID's/git tags of knows working qemu versions<br /> <br /> * linux-user<br /> * mutex lock-up issues https://bugs.launchpad.net/qemu/+bug/668799<br /> * memory allocator issues<br /> * refresh with latest syscall patches<br /> <br /> * bugs affecting us<br /> * multitouch/xinput2 breaks Qt, no clicks work. https://bugs.meego.com/show_bug.cgi?id=12829 <br /> <br /> == Under work ==<br /> <br /> == Done ==</div>

Suihkulokki http://wiki.meego.com/SDK/Qemu SDK/Qemu 2011-01-20T10:19:57Z

<p>Suihkulokki: </p> <hr /> <div>= MeeGo QEMU Team =<br /> <br /> MeeGo Qemu team maintains QEMU system emulator for MeeGo SDK and QEMU linux-user emulator for OBS builders. Legacy support for scratchbox and Nokia N900 Running Maemo5 is provided as well.<br /> <br /> == Consumers of QEMU ==<br /> <br /> Currently each and every consumer of QEMU under the MeeGo umbrella has their own version of Qemu. The plan is to migrate all this versions to a single repository, merge all code together, and then start tagging releases which will be same for all.<br /> <br /> * MeeGo Qemu<br /> ** OpenGL ES 2.0 accelerated QEMU<br /> ** http://wiki.meego.com/ARM/Meego_on_Qemu<br /> ** Smoke test: Maemo5 and latest Meego N900 images boot and display UI<br /> * Qemugl<br /> ** OpenGL accelerated Qemu for intel images<br /> ** http://wiki.meego.com/SDK/Docs/1.1/Building_QEMU_Tools<br /> ** Smoke test: That x86 handset and netbook images boot and display UI<br /> * OBS Qemu<br /> ** Used internaly by OBS to build ARM packages<br /> ** url?<br /> ** Smoke test: arm build round without regressions<br /> * Scratchbox Qemu<br /> ** Used by scratchbox to allow building ARM packages<br /> ** url: merged with MeeGo Qemu.<br /> ** Smoke test: arm build round without regressions<br /> <br /> == Development ==<br /> <br /> The main repository For MeeGo Qemu is [http://meego.gitorious.org/qemu-maemo MeeGo Qemu on gitorious]. Upstream is at [http://www.qemu.org qemu.org].<br /> <br /> === Version control strategy ===<br /> <br /> In this documentation we shall refer to upstream git as "origin" and the the MeeGo QEMU gitorious repository as "meego". <br /> <br /> $ git clone git://git.qemu.org/qemu.git<br /> $ cd qemu<br /> $ git remote add meego git://gitorious.org/qemu-maemo/qemu.git<br /> $ git fetch meego<br /> <br /> The rule of thumb in development is "keep up to date with upstream". To achieve this, we rebase with upstream often. rebasing<br /> causes some pain, but that should be seen as an incentive to push the patches upstream.<br /> <br /> Qemu head (origin/master)<br /> |<br /> (periodic rebase)<br /> |<br /> MeeGo Qemu master (meego/master)<br /> |<br /> |<br /> Everyones working branches ^<br /> <br /> Where the working branches are "temporary" in nature. Eg once the code in the working branches have been applied (via git merge/cherry-pick/rebase or by hand), that working branch is thrown away and a new branch is created.<br /> <br /> Being branches on top of rebased branches means one cant just "merge" changes from upstream branches - one either must rebase their own branch, or cherrypick selected changes in.<br /> <br /> === Submitting merge requests to MeeGo QEMU ===<br /> <br /> Gitorious provides "request merge" functionality, which can be used to propose changes to MeeGo Qemu.<br /> <br /> Alternatively, people with commit access to MeeGo gitorious can push their branches for merging to MeeGo gitorious directly.git offers infinite amount of was to do that, but there is two that are probably most practical<br /> <br /> * Cherry-pick commits from your working branch<br /> <br /> $ git fetch meego # Make sure you are up to date<br /> $ git checkout -b temp-branch-name meego/master<br /> $ git log your-local-working-branch # pick the commit-id's of changes you want<br /> $ git cherry-pick commit-id<br /> $ vi foo.c # cleanup if necessary<br /> $ commit -a --amend # improve commit message if necessary<br /> $ git push meego temp-branch-name<br /> <br /> * rebase working branch on top of latest dvcs<br /> <br /> $ git fetch meego<br /> $ git checkout -b temp-branch-name your-local-working-branch<br /> $ git rebase -i meego/master<br /> $ # follow instructions on editor<br /> $ git push master temp-branch-name<br /> <br /> Where the working branches are "temporary" in nature. Eg once the code in the working branches have been applied (via git<br /> merge/cherry-pick/rebase or by hand), that working branch is thrown away and a new branch is created.<br /> <br /> Being branches on top of rebased branches means one cant just "merge"changes from upstream branches - one either must rebase their own branch, or cherrypick selected changes in.<br /> <br /> == Documentation ==<br /> <br /> === Building Qemu ===<br /> <br /> For ARM<br /> <br /> git clone git://gitorious.org/qemu-maemo/gles-libs.git<br /> cd gles-libs/dgles2<br /> ./configure --enable-glx --enable-x11 --enable-osmesa --prefix=/opt/dgles2<br /> make install<br /> <br /> git clone git://gitorious.org/qemu-maemo/qemu.git <br /> cd qemu<br /> ./configure --target-list="arm-softmmu arm-linux-user" --enable-gles2 --gles2dir=/opt/dgles2<br /> make<br /> <br /> === Creating MeeGo Qemu images for N900 ===<br /> <br /> === Creating MeeGo Qemu images for Intel ===<br /> <br /> Meego [http://wiki.meego.com/SDK/Docs/1.1/Building_QEMU_Tools Qemu Image instructions] for 1.1.<br /> <br /> === Troubleshooting ===<br /> <br /> == The team and the work ==<br /> <br /> This QEMU adaptation team maintains and develops Qemu for MeeGo.<br /> <br /> The current team members are (in no particular order):<br /> <br /> {| border="1" cellspacing="0"<br /> |+<br /> ! Name<br /> ! Area<br /> ! Role<br /> ! Affiliation<br /> ! IRC nickname<br /> |- <br /> | Riku Voipio || Linux-user and Arm system || Maintainer || Nokia || suihkulokki<br /> |- <br /> | Juha Riihimäki || Arm system || Team member || Nokia || <br /> |- <br /> | [http://meego.com/users/fabo Fathi Boudra] || || Package maintainer || Nokia || fabo<br /> |-<br /> | Haitao Feng || OpenGL and OpenGL ES enabling and acceleration || Team member || Intel || haitao<br /> |-<br /> | Zhiyuan Lv || OpenGL and OpenGL ES enabling and acceleration || Team member || Intel || zhiyuan<br /> |-<br /> | Jun Tian || Skin || Team member || Intel || juntian<br /> |}<br /> <br /> Our collaboration spaces are:<br /> <br /> * [http://lists.meego.com/listinfo/meego-dev meego-dev@meego.com mailing list], please prefix with 'QEMU' for team related topics.<br /> * [http://webchat.freenode.net/?channels=meego-sdk #meego-qemu IRC channel on irc.freenode.net]([http://trac.tspre.org/merbot/freenode/%23meego-sdk/ IRC channel logs])<br /> * #qemu IRC channel on irc.oftc.net<br /> * Gitorious team, http://gitorious.org/+meego-qemu-developers and all repositories on http://meego.gitorious.org/qemu-maemo<br /> * [https://build.meego.com/project/monitor?project=Tools:SDK:Host Tools:SDK:Host project] on MeeGo OBS<br /> * xxx project on MeeGo OBS<br /> * This wiki area<br /> <br /> [[Category:SDK]]</div>

Suihkulokki http://wiki.meego.com/SDK/Qemu/OpenGLES SDK/Qemu/OpenGLES 2011-01-19T11:09:22Z

<p>Suihkulokki: Created page with "Currently two different approaches exist for providing hardware acceleration for OpenGL in qemu. = Today = == dgles2 == * EGL, OpenGL ES2, OpenGL ES 1.1 * Transport: custom *…"</p> <hr /> <div>Currently two different approaches exist for providing hardware acceleration for OpenGL in qemu. <br /> <br /> = Today = <br /> <br /> == dgles2 ==<br /> * EGL, OpenGL ES2, OpenGL ES 1.1<br /> * Transport: custom<br /> * Device interface: custom, arm-specific<br /> * Works on Handset UX arm<br /> <br /> Rough overview:<br /> <br /> * OpenGL ES application (MeeGo Handset UX for example)<br /> ** links against<br /> * fgles2 library (implements in libEGL, libGLESv2 and libGLES_CM ABI inside TARGET)<br /> ** passes requests to<br /> * kfgles2 kernel module<br /> ** writes message request to Qemu iomem area<br /> * QEMU reads the request parameters and copies memory buffers<br /> ** passes request to<br /> * dgles2 (implements in libEGL, libGLESv2 and libGLES_CM ABI on the HOST)<br /> ** translates to desktop OpenGL<br /> * host OpenGL library (glx on linux, wgl on windows, agl on apple, osmesa as fallback)<br /> <br /> == virtio-gl ==<br /> * glx, OpenGL<br /> * Transport: glx<br /> * Device interface: virtio<br /> * Works on x86 Netbook UX and older versions of x86 handset UX<br /> <br /> Rough overview:<br /> <br /> * OpenGL application (MeeGo Netbook UX for example)<br /> ** links against<br /> * meego-emulator-libgl-x86<br /> ** passes request to<br /> * meego-gl-virtiomem<br /> ** writes glx requests (with buffers) to<br /> * QEMU virtio-gl-pci reads requests<br /> ** passes to host glx libraries<br /> * host OpenGL library (glx on linux, wgl on windows<br /> <br /> = Future =<br /> <br /> In future we want to merge these to one approach. Several alternatives are considered:<br /> <br /> == Approach 1, dgles2-based virtual gpu ==<br /> <br /> * Refactor fgles/kfgles/qemu to use a "virtual gpu" with ram, io and interrupt<br /> ** On X86 change target from meego-emulator-libgl to the "new" fgles library<br /> ** On ARM, make attach the new virtual device to qemu omap<br /> <br /> *+ Architecturally cleaner<br /> *+ Slightly faster on Qemu ARM<br /> *+ Compositing can be done faster in the vgpu ram without memcopy<br /> *- More work<br /> *- Support needs to be added to Desktop GL if netbook UX is to be supported<br /> *- Impact on Xorg ?<br /> *- Protocol between guest and qemu needs to defined<br /> <br /> == Approach 2, glx-based transport ==<br /> <br /> * Run dgles2 _inside_ Qemu with glx backend<br /> ** On X86, use virtio-gl as-is<br /> ** On ARM, make virtio available<br /> <br /> *+ Faster to implement<br /> *+ Uses defined protocol (glx)<br /> *+ Desktop GL would continue to work as is.<br /> *- Architecturally slighty hacky<br /> *- Slightly slower on ARM as gles->gl translation is done inside Qemu<br /> <br /> Variant for this approach: instead of dgles2, use Mesa egl_glx backend.<br /> <br /> *- Works on EGL/GL, doesn't on EGL/GLES. work effort unkown.</div>

Suihkulokki http://wiki.meego.com/SDK/Qemu SDK/Qemu 2011-01-13T13:39:37Z

<p>Suihkulokki: First edition of the Qemu team page</p> <hr /> <div>= MeeGo QEMU Team =<br /> <br /> MeeGo Qemu team maintains QEMU system emulator for MeeGo SDK and QEMU linux-user emulator for OBS builders. Legacy support for scratchbox and Nokia N900 Running Maemo5 is provided as well.<br /> <br /> == Consumers of QEMU ==<br /> <br /> Currently each and every consumer of QEMU under the MeeGo umbrella has their own version of Qemu. The plan is to migrate all this versions to a single repository, merge all code together, and then start tagging releases which will be same for all.<br /> <br /> * MeeGo Qemu<br /> ** OpenGL ES 2.0 accelerated QEMU<br /> ** http://wiki.meego.com/ARM/Meego_on_Qemu<br /> ** Smoke test: Maemo5 and latest Meego N900 images boot and display UI<br /> * Qemugl<br /> ** OpenGL accelerated Qemu for intel images<br /> ** http://wiki.meego.com/SDK/Docs/1.1/Building_QEMU_Tools<br /> ** Smoke test: That x86 handset and netbook images boot and display UI<br /> * OBS Qemu<br /> ** Used internaly by OBS to build ARM packages<br /> ** url?<br /> ** Smoke test: arm build round without regressions<br /> * Scratchbox Qemu<br /> ** Used by scratchbox to allow building ARM packages<br /> ** url: merged with MeeGo Qemu.<br /> ** Smoke test: arm build round without regressions<br /> <br /> == Development ==<br /> <br /> The main repository For MeeGo Qemu is [http://meego.gitorious.org/qemu-maemo MeeGo Qemu on gitorious]. Upstream is at [http://www.qemu.org qemu.org].<br /> <br /> === Version control strategy ===<br /> <br /> In this documentation we shall refer to upstream git as "origin" and the the MeeGo QEMU gitorious repository as "meego". <br /> <br /> $ git clone git://git.qemu.org/qemu.git<br /> $ cd qemu<br /> $ git remote add meego git://gitorious.org/qemu-maemo/qemu.git<br /> $ git fetch meego<br /> <br /> The rule of thumb in development is "keep up to date with upstream". To achieve this, we rebase with upstream often. rebasing<br /> causes some pain, but that should be seen as an incentive to push the patches upstream.<br /> <br /> Qemu head (origin/master)<br /> |<br /> (periodic rebase)<br /> |<br /> MeeGo Qemu master (meego/master)<br /> |<br /> |<br /> Everyones working branches ^<br /> <br /> Where the working branches are "temporary" in nature. Eg once the code in the working branches have been applied (via git merge/cherry-pick/rebase or by hand), that working branch is thrown away and a new branch is created.<br /> <br /> Being branches on top of rebased branches means one cant just "merge" changes from upstream branches - one either must rebase their own branch, or cherrypick selected changes in.<br /> <br /> === Submitting merge requests to MeeGo QEMU ===<br /> <br /> Gitorious provides "request merge" functionality, which can be used to propose changes to MeeGo Qemu.<br /> <br /> Alternatively, people with commit access to MeeGo gitorious can push their branches for merging to MeeGo gitorious directly.git offers infinite amount of was to do that, but there is two that are probably most practical<br /> <br /> * Cherry-pick commits from your working branch<br /> <br /> $ git fetch meego # Make sure you are up to date<br /> $ git checkout -b temp-branch-name meego/master<br /> $ git log your-local-working-branch # pick the commit-id's of changes you want<br /> $ git cherry-pick commit-id<br /> $ vi foo.c # cleanup if necessary<br /> $ commit -a --amend # improve commit message if necessary<br /> $ git push meego temp-branch-name<br /> <br /> * rebase working branch on top of latest dvcs<br /> <br /> $ git fetch meego<br /> $ git checkout -b temp-branch-name your-local-working-branch<br /> $ git rebase -i meego/master<br /> $ # follow instructions on editor<br /> $ git push master temp-branch-name<br /> <br /> Where the working branches are "temporary" in nature. Eg once the code in the working branches have been applied (via git<br /> merge/cherry-pick/rebase or by hand), that working branch is thrown away and a new branch is created.<br /> <br /> Being branches on top of rebased branches means one cant just "merge"changes from upstream branches - one either must rebase their own branch, or cherrypick selected changes in.<br /> <br /> == Documentation ==<br /> <br /> === Building Qemu ===<br /> <br /> For ARM<br /> <br /> git clone git://gitorious.org/qemu-maemo/gles-libs.git<br /> cd gles-libs/dgles2<br /> ./configure --enable-glx --enable-x11 --enable-osmesa --prefix=/opt/dgles2<br /> make install<br /> <br /> git clone git://gitorious.org/qemu-maemo/qemu.git <br /> cd qemu<br /> ./configure --target-list="arm-softmmu arm-linux-user" --enable-gles2 --gles2dir=/opt/dgles2<br /> make<br /> <br /> === Creating MeeGo Qemu images for N900 ===<br /> <br /> === Creating MeeGo Qemu images for Intel ===<br /> <br /> Meego [http://wiki.meego.com/SDK/Docs/1.1/Building_QEMU_Tools Qemu Image instructions] for 1.1.<br /> <br /> === Troubleshooting ===<br /> <br /> == The team and the work ==<br /> <br /> This QEMU adaptation team maintains and develops Qemu for MeeGo.<br /> <br /> The current team members are (in no particular order):<br /> <br /> {| border="1" cellspacing="0"<br /> |+<br /> ! Name<br /> ! Area<br /> ! Role<br /> ! Affiliation<br /> ! IRC nickname<br /> |- <br /> | Riku Voipio || Linux-user and Arm system || Maintainer || Nokia || suihkulokki<br /> |- <br /> | Juha Riihimäki || Arm system || Team member || Nokia || <br /> |}<br /> <br /> Our collaboration spaces are:<br /> <br /> * [http://lists.meego.com/listinfo/meego-dev meego-dev@meego.com mailing list], please prefix with 'QEMU' for team related topics.<br /> * [http://webchat.freenode.net/?channels=meego-sdk #meego-sdk IRC channel on irc.freenode.net]([http://trac.tspre.org/merbot/freenode/%23meego-sdk/ IRC channel logs])<br /> * #qemu IRC channel on irc.oftc.net<br /> * Gitorious team, http://gitorious.org/+meego-qemu-developers and all repositories on http://meego.gitorious.org/qemu-maemo<br /> * MeeGo OBS xxx project<br /> * This wiki area<br /> <br /> [[Category:SDK]]</div>

Suihkulokki http://wiki.meego.com/ARM/Meego_on_Qemu ARM/Meego on Qemu 2010-05-25T10:27:31Z

<p>Suihkulokki: /* Downloading MeeGo image */</p> <hr /> <div>'''Under construction, experimental and unsupported'''<br /> <br /> QEMU offers one an easy way to try out MeeGo on ARM<br /> <br /> == Building QEMU ==<br /> <br /> Prerequisites: git, build-essential, zlib and sdl libraries.<br /> <br /> git clone git://gitorious.org/qemu-maemo/qemu.git <br /> cd qemu<br /> ./configure --target-list=arm-softmmu<br /> make<br /> <br /> The qemu binary will appear as arm-softmmu/qemu-system-arm<br /> (Kind note: if you shall experience this note "cc1: warnings being treated as errors" during compilation, you could get around it with feeding "--disable-werror" to "configure")<br /> <br /> == Downloading MeeGo image ==<br /> <br /> The MeeGo QEMU needs a NAND image prepared for QEMU ( meego_qemu_nand.img.gz ), which is available from:<br /> <br /> http://tablets-dev.nokia.com/meego-codedrop.php<br /> <br /> Uncompress the image with "gunzip" command.<br /> <br /> == Starting QEMU == <br /> <br /> qemu-system-arm -M n900 -mtdblock meego_qemu_nand.img -serial stdio -clock unix<br /> <br /> You can then login with root/meego.</div>

Suihkulokki http://wiki.meego.com/Talk:ARM/Meego_on_Qemu Talk:ARM/Meego on Qemu 2010-05-25T10:25:37Z

<p>Suihkulokki: </p> <hr /> <div>To the people posting below - the meego-codedrop-arm image is not for qemu, it will not work in qemu!<br /> <br /> - Riku<br /> <br /> With qemu <code>d18373181f3445f5a028ca18d0cd90a3d9c9ad8f</code> (Wed Mar 31 14:51:05 2010 +0300) getting:<br><br /> <code><br /> $ ./qemu/arm-softmmu/qemu-system-arm -M n900 -mtdblock meego-codedrop-arm-n900-201003311614.ubiimg -serial stdio -clock unix<br><br /> qemu: hardware error: no boot device found<br><br /> [...]<br><br /> Aborted (core dumped)<br><br /> </code><br /> I do not have IMEI to download <code>meego_qemu_nand.img</code> but I do not think it is the reason.<br /> <br /> * Comments from sylviaonlyone@gmail.com (27 Apr., 2010):<br /> Yes, I am facing the same problem. No IMEI code and no proper image to start on qemu.<br><br /> So I tried this: '''meego-codedrop-arm-developer-201003311152.img'''<br><br /> And here is what I got:<br><br><br /> <br /> <code><br /> qemu-system-arm -M n900 -mtdblock meego-codedrop-arm-developer-201003311152.img -serial stdio -clock unix<br><br /> qemu: fatal: Trying to execute code outside RAM or ROM at 0x00018020<br><br /> <br><br /> R00=40014044 R01=00018020 R02=00000000 R03=00000000<br><br /> R04=00000000 R05=00000000 R06=00000000 R07=00000000<br><br /> R08=00000000 R09=00000000 R10=00000000 R11=00000000<br><br /> R12=00000000 R13=40205cb0 R14=00000000 R15=00018020<br><br /> PSR=400001d3 -Z-- A svc32<br><br /> Aborted (core dumped)<br><br /> <br><br /> </code><br /> <br /> I found somebody said it might because the layout of the image is different from N900, so maybe we can try another machine type and see.</div>

Suihkulokki http://wiki.meego.com/Talk:ARM/Meego_on_Qemu Talk:ARM/Meego on Qemu 2010-05-25T10:25:22Z

<p>Suihkulokki: </p> <hr /> <div>To the people posting below - the meego-codedrop-arm image is not for qemu, it will not work qemu!<br /> <br /> - Riku<br /> <br /> With qemu <code>d18373181f3445f5a028ca18d0cd90a3d9c9ad8f</code> (Wed Mar 31 14:51:05 2010 +0300) getting:<br><br /> <code><br /> $ ./qemu/arm-softmmu/qemu-system-arm -M n900 -mtdblock meego-codedrop-arm-n900-201003311614.ubiimg -serial stdio -clock unix<br><br /> qemu: hardware error: no boot device found<br><br /> [...]<br><br /> Aborted (core dumped)<br><br /> </code><br /> I do not have IMEI to download <code>meego_qemu_nand.img</code> but I do not think it is the reason.<br /> <br /> * Comments from sylviaonlyone@gmail.com (27 Apr., 2010):<br /> Yes, I am facing the same problem. No IMEI code and no proper image to start on qemu.<br><br /> So I tried this: '''meego-codedrop-arm-developer-201003311152.img'''<br><br /> And here is what I got:<br><br><br /> <br /> <code><br /> qemu-system-arm -M n900 -mtdblock meego-codedrop-arm-developer-201003311152.img -serial stdio -clock unix<br><br /> qemu: fatal: Trying to execute code outside RAM or ROM at 0x00018020<br><br /> <br><br /> R00=40014044 R01=00018020 R02=00000000 R03=00000000<br><br /> R04=00000000 R05=00000000 R06=00000000 R07=00000000<br><br /> R08=00000000 R09=00000000 R10=00000000 R11=00000000<br><br /> R12=00000000 R13=40205cb0 R14=00000000 R15=00018020<br><br /> PSR=400001d3 -Z-- A svc32<br><br /> Aborted (core dumped)<br><br /> <br><br /> </code><br /> <br /> I found somebody said it might because the layout of the image is different from N900, so maybe we can try another machine type and see.</div>

Suihkulokki http://wiki.meego.com/ARM ARM 2010-04-01T12:22:31Z

<p>Suihkulokki: </p> <hr /> <div>'''Disclaimer: Please keep in mind that this is an early developer version of the MeeGo code, and after installation, you will have a terminal window, but no GUI. Only people actively working on MeeGo development should install it.'''<br /> <br /> = MeeGo ARM =<br /> <br /> '''This area is under construction'''<br /> <br /> This documentation tells how to install MeeGo on Nokia N900. Currently it only covers Nokia N900 but will eventually cover all things MeeGo ARM.<br /> <br /> == Obtaining MeeGo images for N900 ==<br /> [[ARM/Meego_images_for_N900|Pre-built images]]<br /> <br /> [[ARM/Creating ARM image using MeeGo Image Creator|Creating image using MeeGo Image Creator]]<br /> <br /> == Installing MeeGo on N900 ==<br /> [[ARM/Meego_native_install_on_N900|Native install]]<br /> <br /> Native installation method is intended only for experienced N900 hackers at this point. If you choose to try it, you are doing it completely on your own risk. <br /> <br /> [[ARM/Meego_chroot_install_on_N900|Chroot install]]<br /> <br /> Chroot install is safer way to try MeeGo without erasing Maemo 5 from your N900 device. Still, you need to know what you are doing.<br /> <br /> [[ARM/Meego_N900_alternative_installs|Alternative boot methods]]<br /> <br /> == Running MeeGo on Qemu ==<br /> <br /> [[ARMMeego_on_Qemu/|QEMU instructions]]<br /> <br /> Qemu allows you to try out MeeGo safely on your Desktop PC.<br /> <br /> == Troubleshooting ==<br /> [[ARM/Restoring_Maemo|Restoring Maemo]]</div>

Suihkulokki http://wiki.meego.com/ARM ARM 2010-04-01T12:22:14Z

<p>Suihkulokki: </p> <hr /> <div>'''Disclaimer: Please keep in mind that this is an early developer version of the MeeGo code, and after installation, you will have a terminal window, but no GUI. Only people actively working on MeeGo development should install it.'''<br /> <br /> = MeeGo ARM =<br /> <br /> '''This area is under construction'''<br /> <br /> This documentation tells how to install MeeGo on Nokia N900. Currently it only covers Nokia N900 but will eventually cover all things MeeGo ARM.<br /> <br /> == Obtaining MeeGo images for N900 ==<br /> [[ARM/Meego_images_for_N900|Pre-built images]]<br /> <br /> [[ARM/Creating ARM image using MeeGo Image Creator|Creating image using MeeGo Image Creator]]<br /> <br /> == Installing MeeGo on N900 ==<br /> [[ARM/Meego_native_install_on_N900|Native install]]<br /> <br /> Native installation method is intended only for experienced N900 hackers at this point. If you choose to try it, you are doing it completely on your own risk. <br /> <br /> [[ARM/Meego_chroot_install_on_N900|Chroot install]]<br /> <br /> Chroot install is safer way to try MeeGo without erasing Maemo 5 from your N900 device. Still, you need to know what you are doing.<br /> <br /> [[ARM/Meego_N900_alternative_installs|Alternative boot methods]]<br /> <br /> Qemu allows you to try out MeeGo safely on your Desktop PC.<br /> <br /> == Running MeeGo on Qemu ==<br /> <br /> [[ARMMeego_on_Qemu/|QEMU instructions]]<br /> <br /> == Troubleshooting ==<br /> [[ARM/Restoring_Maemo|Restoring Maemo]]</div>

Suihkulokki http://wiki.meego.com/ARM/Meego_on_Qemu ARM/Meego on Qemu 2010-04-01T10:54:47Z

<p>Suihkulokki: </p> <hr /> <div>'''Under construction, experimental and unsupported'''<br /> <br /> QEMU offers one an easy way to try out MeeGo on ARM<br /> <br /> == Building QEMU ==<br /> <br /> Prequistes: git, build-essential, zlib and sdl libraries.<br /> <br /> git clone git://gitorious.org/qemu-maemo/qemu.git <br /> ../configure --target-list=arm-softmmu<br /> make<br /> <br /> The qemu binary will appear as arm-softmmu/qemu-system-arm<br /> <br /> == Downloading MeeGo image ==<br /> <br /> The MeeGo QEMU nand image( meego_qemu_nand.img.gz ) is available from:<br /> <br /> http://tablets-dev.nokia.com/meego-codedrop.php<br /> <br /> Uncompress the image with "gunzip" command.<br /> <br /> == Starting QEMU == <br /> <br /> qemu-system-arm -M n900 -mtdblock meego_qemu_nand.img -serial stdio -clock unix</div>

Suihkulokki http://wiki.meego.com/ARM/Meego_on_Qemu ARM/Meego on Qemu 2010-04-01T10:54:23Z

<p>Suihkulokki: add Qemu instructions</p> <hr /> <div>'''Under construction, experimental and unsupported'''<br /> <br /> ''' QEMU offers one an easy way to try out MeeGo on ARM'''<br /> <br /> == Building QEMU ==<br /> <br /> Prequistes: git, build-essential, zlib and sdl libraries.<br /> <br /> git clone git://gitorious.org/qemu-maemo/qemu.git <br /> ../configure --target-list=arm-softmmu<br /> make<br /> <br /> The qemu binary will appear as arm-softmmu/qemu-system-arm<br /> <br /> == Downloading MeeGo image ==<br /> <br /> The MeeGo QEMU nand image( meego_qemu_nand.img.gz ) is available from:<br /> <br /> http://tablets-dev.nokia.com/meego-codedrop.php<br /> <br /> Uncompress the image with "gunzip" command.<br /> <br /> == Starting QEMU == <br /> <br /> qemu-system-arm -M n900 -mtdblock meego_qemu_nand.img -serial stdio -clock unix</div>

Suihkulokki