Editing User:Stskeeps/Draft Mer Blueprint

Warning: You are not logged in. Your IP address will be recorded in this page's edit history.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Learn more about Contributing to the wiki.

The Mer platform is a Linux distribution for mobile devices based on the Maemo platform from Nokia. Mer goals include:

*Improving and developing parts of Maemo that are of interest to the Maemo community.
*Making it easier to port existing desktop applications by hildonizing and adjusting them to the tablet form factor.
*Encouraging third party experimentation and development.
*Supporting tablet hardware no longer receiving updated OS software by Nokia.
*Making Maemo a generic platform for all tablet devices, including non-Nokia ones.
*Focusing Maemo community efforts in platform-related areas

Mer platform development will be done in the open, with public SCM repository, bugtrackers, and Wiki-based blueprint discussion.

We should stop seeing the tablets as strictly under-powered embedded systems, and see them for what they really are: powerful, power-efficient, economical handheld computers.

Historically, the Mer platform came from a discussion on [[Maemo_Reconstructed|reconstructing Maemo]] and a desire to make a proof of concept system of the thoughts in this proposal (M-R PoC), which developed into Mer after realization that it was a viable direction of development.

== Sprints ==

Most Mer development talk goes on in #maemo on irc.freenode.net. If you do not have an IRC client, use www.mibbit.com. We currently use https://launchpad.net/m-r for collaboration, but will move to maemo.org eventually. Our current status is that we have a N8x0 image with nm-applet, advanced backlight, load-applet on top of a hildon-desktop using Fremantle components, on top of Xorg and Ubuntu Jaunty. Previous progress can be viewed at http://jaiku.com/channel/reconstructedPOC

We have fringe projects in 770, Zaurus, x86, Wii ports, and as such, code will be built first on x86 to ensure cross-platform, and then in our cross-compilers.

= Sprint January 2008 and before: Basic installable image =

The purpose of this milestone:
* To provide a basic installable firmware image, both through installer and through flashing, for N8x0 tablets. 
* The image must include a basic user interface and ability to connect to Wi-Fi networks.
* To provide a installer and image for 770 tablets.
* To provide initial developer tools so we can start developing for the tablets.
* Begin initial talks with Nokia and maemo.org on how to distribute full firmware images.
* Prepare for next milestone in terms of collaborative technologies.

If you have a task that needs to be done to fullfill the purposes of this milestone, add it to the table below, set it to 'Just standing' status, and with no commit date and owner.

If you want to take on a task, set the initial commit date, your nickname, and update your progress as you go, and update highlights of your work (including what gets added) as you work on it. Update your activity log each day you've performed something related to Mer.

If you encounter any bugs in Maemo platform software while developing for Maemo, report them on bugs.maemo.org , and add the bug number to the sprint bug overview.

{| class="wikitable"
| style="background:LightGreen" | Completed
| style="background:LightBlue" | Good progress
| Just standing
| style="background:Orange" | Some help needed!
| style="background:Tomato" | Really stuck/delayed
|}

{| class="wikitable sortable"
|-
! Committed
! Task
! Owner
! %
! Highlights
|- style="background:LightBlue"
| December || [[Task:Community_firmware_image_distribution|Proposal for distribution of firmware images including closed-source bits needed for community editions]] || Stskeeps || 10% || First proposal involving initfs bits proposed through maemo-community.
|- style="background:LightGreen"
| December || Initial imager - script to debootstrap and putting Mer on top of Ubuntu Jaunty minbase (x86, armel) for Mer/x86, Mer/armv5te (770,n8x0) || Stskeeps || 100% || [https://code.launchpad.net/~mer-committers/m-r/imager Provided here]
|- style="background:LightGreen"
| December || Basic hildon-desktop up on Xorg, running with advanced-backlight and load-applet || Stskeeps, johnx, etc. || 100% || In repository
|- style="background:LightGreen"
| December || Initial Scratchbox1 SDK for Mer/armv5te || Stskeeps || 100% || [[#SDK|Provided here]]
|- style="background:LightBlue"
| 2008-15-12 || [[#Mer_Installer|Installer for Mer on Diablo]] || b-man || 70% || [http://trac.tspre.org/meiz Initial versions]
|- style="background:LightGreen"
| 2008-17-12 || cx3110x-umac-module (symlink to umac.ko module || qwerty12 || 100% || Now in repository
|- style="background:LightGreen"
| 2008-17-12 || nokia-n8x0-firmware (symlink to firmwares in initfs) || qwerty12 || 100% || Now in repository
|- style="background:LightGreen"
| 2008-17-12 || hildon-desktop-env with hildon-input-method setup || qwerty12 || 100% || Now in repository
|- style="background:LightGreen"
| January || Diablo kernel that boots from rootfs instead of initfs, and runs /sbin/tablet-init instead of init || qwerty12 || 100% || [http://trac.tspre.org/qwerty12 Provided here]
|- style="background:LightGreen"
| January || Mer logo, (rescue menu) artwork, wallpaper, theme (titan) || wazd, Stskeeps || 100% || Now in repository (mer-omap-fb-splash, mer-rescue-menu, titan), also see [http://tabletui.wordpress.com/2009/01/12/repos-a-la-mer/ here]
|- style="background:LightBlue"
| January || Missing localization strings in Hildon, (#4001) || Stskeeps || 50% ||
|- style="background:LightGreen"
| January || Document how to get packages included in repository || Stskeeps || 100% || [[#Getting_your_package_included_in_the_Repository|provided here]]
|- style=""
| || [[#qemu-eabi_cputransp_for_Scratchbox|qemu-eabi cputransp for Scratchbox]]|| none || 0% ||
|- style=""
| || Fix backspace and enter kills Xorg bug || none || 0% ||
|- style=""
| || Upload new themes to repository (we only have titan and plankton atm) || none || 0% ||
|- style=""
| || Open system sounds (startup chime, touchscreen tap, etc) || none || 0% ||
|- style=""
| || Replacing SDK icons with more modern ones || none || 0% ||
|- style=""
| || Include dsme-tools from Deblet || none || 0% ||
|- style=""
| || Include wifi power saving from Deblet || none || 0% ||
|- style=""
| || Working X-terminal with hildon input method working || none || 0% ||
|}

Bug reports in bugzilla discovered through or related to Mer development in this sprint:

{{#bugzilla:id=4001,3858,3939,3997
  |columns=id,severity,product,status,resolution,summary,to
}}

=== Activity log ===

16th January

* stskeeps: remade Mer blueprint to fit more into maemo.org processes

= Documentation and tasks =

== SDK ==

First, install Fremantle SDK, and add yourself as a user to scratchbox.

As user:
* wget -c http://stskeeps.subnetmask.net/mer/arm-linux-cs2008q3-72-libtool2_1.0.11_i386.deb
* sudo dpkg -i arm-linux-cs2008q3-72-libtool2_1.0.11_i386.deb (run as root)
* wget -c http://stskeeps.subnetmask.net/mer/scratchbox-devkit-mer_1.0.11_i386.deb
* sudo dpkg -i scratchbox-devkit-mer_1.0.11_i386.deb
**You can optionally get qemu-arm-eabi and use that here instead. It is very good for your use of the SDK
* sb-conf setup MER-ARMEL --compiler=arm-linux-cs2008q3-72-libtool2 --devkits=debian-etch:cputransp:perl:mer --cputransp=qemu-arm-cvs-m -f
* sb-conf reset -f MER-ARMEL
* sb-conf select MER-ARMEL
* sb-conf rootstrap MER-ARMEL http://stskeeps.subnetmask.net/mer/mer-armel-rootstrap-v8.tar.gz
* sb-conf install MER-ARMEL --etc --devkits --fakeroot

ISSUES:
* You might have to do export PKG_CONFIG_PATH=/usr/share/pkgconfig:/usr/lib/pkgconfig to get some pkg-config stuff going
* You might have to set cpu right and such to target armv5el (no vfp)
* You probably need to get EABI cpu transparency target too
* 'not safe for cross-compilation' warnings (not true, i think)
* fakeroot apt-get dist-upgrade is good once in a while to keep up to date.

== Mer Installer ==

Make installer for Maemo/Diablo that does the following:

* Depends on bootmenu (bootmenu with bootmenu.d item)
* Allows simple installation (partition my internal/external MMC to 50mb FAT, 128mb swap, rest linux), or advanced (choose my own partition)
* Partitions, mkfs.ext3's and unpacks a downloaded tar.gz (built by the imager, uploaded to some http.). Should support resume of dls (wget -c?)
* Sets up the bootmenu item for Mer.

== qemu-eabi cputransp for Scratchbox ==

See http://maemogeek.blogspot.com/2007/11/installing-qemu-arm-eabi-patch-into.html

Make a debian package with this binary (for i386), installing into /scratchbox/devkits/cputransp/bin/qemu-arm-eabi-sb2 
and adding 'qemu-arm-eabi-sb2' to /scratchbox/devkits/cputransp/etc/cputransp-methods when installing, and removing when
removing (sed -i?)

Edit [[#SDK||SDK]] to make instructions use qemu-arm-eabi-sb2 instead, and getting your .deb package.

== Getting your package included in the Repository ==

* Make sure it compiles after getting your build dependancies, dpkg-buildpackage. 
* Ideally test both dpkg-buildpackage -S -us -uc, dpkg-buildpackage -b -us -uc, dpkg-buildpackage -B (some packages may not build any arch-dep packages, so that's ok. Microdocument it on Jaiku.)
* bzr export <source package name> lp:~yourusername/m-r/<source package name> (gives you a checked out version, without metadata)
* cd <source package name>
* dpkg-buildpackage -S -us -uc, to generate a source package
* Upload the resulting source package (*.changes, *.tar.gz, possibly *.diff.gz) to your ~/incoming on the repo server.
* ssh yourlogin@reposerver /import-new-packages

(This will add the source package to repository)

* You need access to merbuilder & repository upload for the following, ask Stskeeps on Jaiku/IRC for this. Or refer on Jaiku to the source package and some may pick it up
* On http://jaiku.com/channel/merbuilder , write "build <SOURCE PACKAGE NAME>=<package version>"
* Monitor progress at http://merbuilder.jaiku.com
* An LP player notes that it has picked up a package for building at a certain builder
* A toast means it baked properly on this architecture. And is uploaded to repository.
* A heart means it built properly on all architectures. And is uploaded to the repository
* A bomb means it failed to build on an architecture.
* A shopping wagon means it has noticed your build request and queued it.

Please note that all contributions to maemo.org wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see maemo.org wiki:Copyrights for details). Do not submit copyrighted work without permission!

Summary:

Cancel | Editing help (opens in new window)

Retrieved from "http://wiki.maemo.org/User:Stskeeps/Draft_Mer_Blueprint"

Personal tools

Navigation

Views

Editing User:Stskeeps/Draft Mer Blueprint

@@ Line 16: / Line 16: @@
 == Sprints ==
-We employ the [[Maemo.org_Sprints|Maemo.org sprints]] method as development method for Mer. That means, get yourself a maemo.org account, and read this document through if you would like to contribute :)
 Most Mer development talk goes on in #maemo on irc.freenode.net. If you do not have an IRC client, use www.mibbit.com. We currently use https://launchpad.net/m-r for collaboration, but will move to maemo.org eventually. Our current status is that we have a N8x0 image with nm-applet, advanced backlight, load-applet on top of a hildon-desktop using Fremantle components, on top of Xorg and Ubuntu Jaunty. Previous progress can be viewed at http://jaiku.com/channel/reconstructedPOC