Marcin Juszkiewicz

Some time ago there was decision that BUG 1.x will not be supported with next version of BUG Linux. As a result I ended in situation when I worked on handling device which I never saw.

It was not first time — in OpenedHand times I had this quite often but it is not a problem because my “hardware park” covers nearly whole ARM family:

• armv4t (s3c2410 in Openmoko GTA01, EP3907 in Sim.One)
• armv5te (at91sam9263, at91sam9m10 on Atmel boards, PXA255 in Zaurus c760, Sheeva in Marvell Sheevaplug, omap1510 in Nokia 770 tablet, ST88n15 in NHK-15)
• armv6 (omap24xx in Nokia N810, i.mx31 in BUG 1.2/1.3)
• armv7a (omap3530 in BeagleBoard B7/C3 and in Nokia N900)

So I am able to test binaries on other hardware or even in QEMU.

But few days ago I got information that developer version of BUG 2.0 will be sent to me. To make me more happy I ordered few books from Amazon to get them with package (inside US I got free posting). And today package was delivered by FedEx courier (their tracking page said Friday as delivery day).

Package reminds why recycling is easy: UPS package from Amazon (the one with books which I ordered) was repacked and got FedEx papers:

But box itself is not interesting — stuff in matters. After taking books out I got lot of packing bubbles and my eyes were presented with first level of things:

And then second one:

Everything unboxed:

And again but this time without packaging. From left-top to right-left:

• BUGduino module
• camera module
• OMAP3 video module with HDMI and VGA outputs
• new LCD module
• LCD screen with touchscreen (for LCD module)
• battery
• BUG 2.0 dock with serial (miniUSB), Ethernet, USB host, JTAG connectors
• BUG 2.0 rev. A
• two BMI adapters
• BMI cable extender

Look at new modules. First goes BUGduino which is Arduino thing with BUG connection. I do not know how it works but I knew that John Connolly did some programming for it.

New LCD module — QVGA like before.

Video module with HDMI and VGA outputs. This one is BUG 2.0 only as it uses OMAP3 signals and needs BMI slot with video signals. Yes, new BUG has only one slot for video — two screens configuration is not possible anymore. But hey — you can even connect 150” LCD ;)

New camera module. I do not remember how many Mpx it has (old one had 2Mpx).

BUG 2.0 itself. Notice two microSD slots — one will be used for system, second is for user. There are just two buttons now, no LCD, no joystick. Also buzzer got removed in favour of headphone connector.

New hardware requires new BUGDock. What got changed? Serial is now present as miniUSB connector instead of DB9 so is easier to use with today computers (not everyone has 7 serial ports in desktop). Power and headphones connectors were removed because on-board ones are reachable. And JTAG connector is present. To tell the true I like old dock more then current one. But thats mostly because of angle connector instead of flat one. Anyway before BUG 2.0 will hit market there will be new dock for it.

And thats how system can look. BUG 2.0 with Dock and two modules connected by adapters.

Now I am waiting for Bug Labs guys to appear in the office to get informations how to boot it ;D

Few days ago I decided to migrate from Ångström to Debian on my Sheevaplug. Fetched installer images, booted them and installed system to 4GB microSD card. All was fine.

System was running nicely until today…

MicroSD card started to generate timeouts, read/write errors and other not nice messages. End effect: not booting system. Now I started Ångström and plan to rescue as much as possible from card. Next attempt will be with rootfs on USB stick.

Few days ago I found Gource — a software version control visualization tool. Software projects are displayed as an animated tree with the root directory of the project at its centre. Directories appear as branches with files as leaves. Developers can be seen working on the tree at the times they contributed to the project.

I started it against OpenEmbedded repository and was amazed. Looks really nice but also shows that we are too big project for that tool. After experimenting with arguments I generated short video which shows how we worked:

It took over 9 (nine!) hours to generate but was worth it. Especially I suggest to check moment when stable/2009 branch was created (1st April 2009) — it is best seen with frame by frame mode.

I have my own Protracker module player written for Maemo5. I used Qt because I am familiar with it and like it. But Maemo5 makes simple things harder…

First thing: which version of Qt? Yes — there are two of them:

• 4.5.3 which was ported by community, does not follow Maemo5 look & feel but is present on each Nokia N900 by default
• 4.6 ported by Nokia, follows Maemo5 look & feel as much as possible but present only in extras-devel repository

I used Qt 4.6 because of proper look and working Phonon.

Second problem: moving API. Ok, I know: it is extras-devel so not safe for devices but why I have to rebuild application after each “apt-get update/upgrade” cycle? First it was removal of QMaemo5KineticScroller, then rotation code changed.

Rotation is 3rd problem. In recent packages there is support for automatic rotation without any code other then setting window attribute for it. It is even documented. But it does not work — even in official example. From one commit to qt/maemo5 repo I got a feeling that automatic rotation needs to wait for next firmware update :(

Good thing is that my application is small so adapting to changes takes small amount of time. And I hope that PR1.2 will finally give working Qt without many changes.

During last few days I was offline for most of time. Those who follow me on Twitter noticed that I was traveling. Imagine how surprised I was when I read about Maemo + Moblin -> MeeGo movement.

First I thought that finally Nokia decided to get rid of terribly maintained base system used for Maemo5 in favor of something working. But wait… Maemo5 is already buried — Maemo6 is on a way. But wait… what is Maemo6? MeeGo rather etc, etc, etc…

After some reading (on N900 by GPRS mostly + some public hotspots) it looked more clearly but added new questions. What about Nokia N900 support? Will it be added by vendor and supported or rather let community do it? Done by company would be better as this would obligate them to keep development alive (and merge kernel stuff into mainline).

One is sure: MeeGo will bring many changes. Base system will be updated (good), packaging will be changed to RPM (not so good but acceptable), Qt instead of GTK+ (good), less Nokia developers (very good). Too bad that whole rush to get it done before MWC made few things unclear and that there is nothing to download to play with. There is no information how much code will be free and open (Maemo5 has lot of closed components) and what is a policy for closed components.

What do I feel after reading blog posts, mailing lists? Time will show. Looks like N900 can have nice future, new applications backported from MeeGo but for it we need to wait as for now nothing is known yet (no code to look at).

During FOSDEM I attended few talks in Openmoko devroom. During one of them Mickey ‘mickeyl’ Lauer was using his ‘mdbus’ tool to inspect and play with DBus services and methods. As tool looked interesting I decided to try it.

Same day I played a bit with it on Nokia N900. Results were nicer then with using “dbus-monitor” or “dbus-send” but speed was a bit slow (due to Python used). But there was a hope: Mickeyl already started rewriting “mickeydbus” in Vala which should give speed boost.

Yesterday I built “mickeydbus2” for Maemo5 using OpenEmbedded (more about it in next posts) and played with it. Few bugs appeared, but I fixed some, Mickeyl did rest and coded few improvements.

But what this app really do? It has 2 modes basically: listener and method inspector/caller. Example listen session:

Nokia-N900-42-11:~# mdbus2 -sl
[SIGNAL] org.freedesktop.DBus.NameAcquired  /org/freedesktop/DBus  org.freedesktop.DBus
( ":1.928" )
[SIGNAL] com.nokia.mce.signal.tklock_mode_ind  /com/nokia/mce/signal  :1.8
( "locked" )
[SIGNAL] org.freedesktop.Hal.Device.PropertyModified  /org/freedesktop/Hal/devices/platform_slide  :1.12
( 1, [ ( "button.state.value", false, false ) ] )
[SIGNAL] org.freedesktop.Hal.Device.Condition  /org/freedesktop/Hal/devices/platform_slide  :1.12
( "ButtonPressed", "cover" )
[SIGNAL] org.freedesktop.Hal.Device.PropertyModified  /org/freedesktop/Hal/devices/platform_kb_lock  :1.12
( 1, [ ( "button.state.value", false, false ) ] )
[SIGNAL] org.freedesktop.Hal.Device.Condition  /org/freedesktop/Hal/devices/platform_kb_lock  :1.12
( "ButtonPressed", "cover" )
[SIGNAL] com.nokia.mce.signal.tklock_mode_ind  /com/nokia/mce/signal  :1.8
( "unlocked" )
[SIGNAL] com.nokia.mce.signal.system_inactivity_ind  /com/nokia/mce/signal  :1.8
( false )
[SIGNAL] com.nokia.mce.signal.display_status_ind  /com/nokia/mce/signal  :1.8
( "on" )
[SIGNAL] org.freedesktop.Hal.Device.PropertyModified  /org/freedesktop/Hal/devices/bme  :1.12
( 2, [ ( "battery.reporting.current", false, false ), ( "battery.charge_level.percentage", false, false ) ] )
[SIGNAL] org.freedesktop.Hal.Device.PropertyModified  /org/freedesktop/Hal/devices/platform_kb_lock  :1.12
( 1, [ ( "button.state.value", false, false ) ] )
[SIGNAL] org.freedesktop.Hal.Device.Condition  /org/freedesktop/Hal/devices/platform_kb_lock  :1.12
( "ButtonPressed", "cover" )

Asking for bus and methods:

Nokia-N900-42-11:~# mdbus2 -s org.bluez
/
/com
/com/nokia
/com/nokia/MaemoTelephony
/org
/org/bluez
/org/bluez/899
/org/bluez/899/any
/org/bluez/899/hci0
/org/bluez/899/hci0/dev_00_1D_82_32_0A_22
Nokia-N900-42-11:~# mdbus2 -s org.bluez /com/nokia/MaemoTelephony
[METHOD]    org.freedesktop.DBus.Introspectable.Introspect() -> ( s:none )
[METHOD]    com.nokia.MaemoTelephony.SetCallerId( s:none ) -> ()

And there is also interactive mode with tab completion:

Nokia-N900-42-11:~# mdbus2 -i -s
MDBUS2> org.bluez /com/nokia
/com/nokia                 /com/nokia/MaemoTelephony
MDBUS2> org.bluez /com/nokia/MaemoTelephony
[METHOD]    org.freedesktop.DBus.Introspectable.Introspect() -> ( s:none )
[METHOD]    com.nokia.MaemoTelephony.SetCallerId( s:none ) -> ()
MDBUS2>

How to get it on your N900? Enable “extras-devel” repository and install “mdbus2” package. Report bugs, send us fixes, ideas, improvements. Git tree is available.

Returning home now — sitting in the EasyJet plane somewhere over Germany and sipping coffee.

Tenth FOSDEM is past now. We had a stand as usual but this year it looked much better then ever: white sheet, less cables floating everywhere (one central power extender with 8 sockets helps), interesting devices on table… We had:

• EVBeagle (German Beagleboard clone with blue PCB)
• 2 BUGs showing different things (camera view on mine, dual screen X11 on Denis one)
• Ulf bring new Atmel AT91SAM9M10 board (more on it in next days as it is in my bag above my head), there was also raffle in which other one was a price
• Archos 7 media player
• Psion netbook (with ‘Prototype’ text on it)
• Openmoko Freerunner
• HTC Dream (running OpenEmbedded distro instead of Android)
• FriendlyARM with WVGA screen
• Toshiba topas
• Atmel NGW100 which uses AVR32 cpu
• and some more which I forgot about

For next year it would be great to have power supply which would provide several +5V and +12V cables so there would be less plugs in use. Someone wants to donate such one? We probably need to think about creating kind of ‘standard stand stuff box’ which would be used on next events so no more grabbing power extenders, USB cables etc. This is a thing to discuss.

At stand there were many people asking different questions. Some thought that we are selling hardware, some known already what OE is.

But FOSDEM was not only OE stand. This year I decided that there are talks which I want to attend and did that. I saw (titles are not original ones):

• ‘20 minutes about Openmoko history’ by Mickeyl Lauer. I got there a bit late to check did he mentioned ‘super secret project’ name
• ‘Freesmartphone.org — what it is and why it is cool’ also by Mickeyl. He shown few of his DBus related tools — I need to package them for Maemo5 as they should be useful. Talk was interesting and worth being there.
• ‘Cross building systems: who we are and what our plans are’ panel was set of presentations from Ptxdist, OpenWRT, Crosstool NG, Buildroot, OpenEmbedded, cegcc projects. Everybody said that we need to share patches and help people to fix their software.
• ‘Maemo Community Counsil: who, why, what for’ was nice talk by Dave Neary (sorry man, that we did not met for talk). MCC is between community and Nokia and they do good job.
• ‘How to be good upstream’ by Gentoo developer was interesting as they have similar problems that we have in OE.
• ‘MINIX 3: system which do not want to die’ was the best entertainment during whole trip. Author was blaming Linux for being terrible buggy while his ‘baby’ was nearly bug free. But maybe because of very small user base? Not that I have something against microkernel idea — I used AmigaOS which chosen that way and know how it works.

Met some people, some planned to but time was too short as usual… Some of new faces were nice surprise: Martin Guy (the only one who understand Cirrus Logic EP93xx FPU hardware bugs) or Bluelighting from OPIE project. Tias (author of XInput calibrator tool for making touchscreens work as they should) hunted me during whole event and finally we had occasion to discuss about changes which he did due to my suggestions or problems. I shown BUG with two screens for him and he understood why I need device parameter. And next year I need to catch one guy from staff and talk with him as this year again he told that he know me and I do not know him (something like that anyway).

There was one change when it comes to stands — this year we were not next to PostgreSQL because MariaDB was between. I hope that next year we will be still nearby as I got used to the youngest person in their team :)

Speaking about future: it was last year with Astrid for me. It is in nice location (direct bus to FOSDEM place, near to Delirium Cafe) but no free wifi available in XXI century starts to be an issue. And no more going to tourist area for dinner — it was too costly I think.

Now I am in a bus which is my last way of transport today. plan to be at home before midnight. Post has to wait for Monday.

Year ago when I was going to FOSDEM I took my Nokia E66 phone preloaded with Belgium maps to not get lost in Brussels. It was working quite good. This year I took Nokia N900 as the only device to use (no laptop, no other phone) and BUG to show something.

How did N900 worked as navigation device? Terrible! The problem started before travel. I installed whole set of map applications which were available:

• Ovi Maps
• Maemo Mapper
• Maep
• Mapbuddy
• Navit

Only first one had support to preloading map data (by using Nokia Map Loader under MS Windows). Maemo Mapper had such functionality in OS2008 but newer version has something totally broken. Navit required use of extra tool for conversion but after looking at UI I decided that will not even try. Maep and Mapbuddy always fetch from network so roaming costs would kill me.

So I used Ovi Maps as less bad then others. Lacks of offline POI support suxx, lack of adding own ones suxx even more as in Symbian version I just added few interesting places at home and used them during walking on streets of Brussels. Nokia needs to spend lot of money and developer time if they want to make it usable.

So software was more or less disaster but I managed to get to the ‘peeing boy’ so (after seeing’ peeing girl’ year ago) that part of tourist attractions is done. Would be nice to have some way of preloading AGPS data as without network connection it takes ages to get fix.