We have coordinated this issue with emdebian's team, and are glad to announce that everything seems to be back in order.
If you have been upgrading your hackable:1 cross-compilation environment during this window, there is a simple way to get it to work again:
# apt-get remove --purge libgcc1-armel-cross
# apt-get install gcc-4.3-arm-linux-gnueabi g++-4.3-arm-linux-gnueabi
Then you should be able to cross-compile again!
I'm being a little bit silent lately.
The good news is that i've not been quiet :)
What i've been doing? Well, first of all i'm being too busy with a lot of tuxbrain stuff :)
I put a smile because they are giving me the opportunity to develop/hack a lot of devices and they give e the opportunity to hardware hacking, that is not an easy one :)
- I've been doing some buzz fixes    .
- I've been hacking some devices  .
- I've been hacking some OE recipes (Porting some shr recipes from import/shr to org.openembedded.dev), and putting some patches .
- I've been following new interesting companies .
And off course i've been having a lot of fun, a real life, a paid job and a wonderful wife that supports me ;) until one holiday week :)
I put this post because i've one specific blog with some new stuff  An i.MX515  development platform that i'm going to start to hack.
I'm reading my mails from the last weeks (now last month), and i'm getting up to date.
Stay tunned to know what i've been doing in next weeks :)
Hope to write here soon.
I'm not a fan of the iPhone, because of its proprietary software and Digital Restrictions Management (DRM).
Sometimes people e-mail me from iPhones, and so I see that little "Sent from my iPhone" note at the bottom of their messages.
While I would prefer that people change that note (if Apple allows them to do that) to say something like, "The iPhone is Defective by Design (http://defectivebydesign.org).", my second choice would be to just not see the note. Fortunately, in Gnus — my favorite free software e-mail client — it's easy to "wash" messages.
Today to my .gnus file I added:(setq gnus-parameters '((".*" (banner . iphone)))) (setq gnus-article-banner-alist '((iphone . "\\(^Sent from my iPhone$\\)")))
Now I don't have to see those notes.
No new version, no new devellopment ( I was very busy at the end of august ) but :
- New domain : http://www.qalee.org !
- New website in construction :
- As you can see we have now a mailing list, a wiki, a bugtracker !!
What’s next ? ( near furure )
- Finishing network manager panel
- Create a plugin manager ( download community proposed plugins and creator ( for devellopers )
- Make a generic list view in libqalee
- Finish first version of qalee-core ( maybe this month we will have a first beta of qalee core )
Fell free to edit the wiki !!
If you want to help, propose it on the mailing list
Remember when Nokia wanted to give a lesson regarding software patents to Free Software people? Like «they’re ‘m’kay? We know best, m’kay?»
Well, I was really anxious about the Nokia N900, the 4th Nokia GNU/Linux internet device which now has the ability to make phone calls! It’s an impressive device… cell phone (3G, yay), camera with enough resolution, GPS, wifi, decent graphics card, powerful processor, a half-decent amount of memory, more than decent storage, etc…
It is also being branded as so “open” that software freedom lovers would love it. This seemed like really good news, no? Well, like the saying goes… when it’s too good to be true… it most probably ain’t.
I tried to figure out how “open” the device is, and wasn’t really happy. After more than 70 comments, Quim (who works at Nokia) spills the guts:
Nobody claims Maemo is the 100% free mobile OS and the N900 is the 100% free mobile device. I claim is currently the most interesting combination for a free software lover thanks to its standard Linux stack, possibility to modify the platform and access to the root. The % closed helps Nokia getting a sustainable business model and reaching consumer appeal.
Well, nice claim, but it is the idea that you (and Nokia) are selling. And worse of all, you seem to pretend that in 100% of an operating system, all % are of equal value. They’re not. The minimum percentage that is proprietary is essential for Nokia’s GNU/Linux devices to work. Take it away, and they won’t work, or might even burn in your pocket. Period.
If 100% freedom is your goal Maemo 5 and N900 is a good starting point.
No it’s not. There’s better if you want 100% freedom, what OpenMoko started. The company may now only be selling Freerunners to resellers who want to keep on with the business, but there’s new sources of hardware showing up (thanks go mainly to John ‘MadDog’ Hall who’s been in talks with the University of São Paulo, in Brasil), so no, the phone is not dead. It is actually growing a lot better and faster now it’s free from the corporate strings of OpenMoko, which partly restricted the flow of things.
But I digress, let’s get back to Nokia and its bullshit and insults to the Free Software community (I use Free Software because I prefer to talk about freedom, but these insults and bulshit also apply to you, Open Source guys, so pay attention).
There’s a wiki page in Maemo explaining why there are some proprietary software. That page needs to be passed by the bullshit filter, like I said in my comment, Nokia is far from being friendly to Free Software. They’re actually quite aggressive and strongly lobby for the legalization of software patents in Europe. Don’t be fooled by the sugar coating, they are not your friend. So what is in the wiki page after you pass the bullshit filter?
- Brand We think that “open source” reduces our brand value
- Differentiation Proprietary software is much better, just use it
- Legacy We don’t want to be shamed by the garbage we forcefeed upon you
- IPR & licensing issues Software Patents are good, just buy the freaking licenses from us.
- Security Since we sell dangerous products, we take your freedom away so you don’t make the mistake of getting proof they’re crap (like their batteries, which the phones must know the limits of)
- Third party Just accept that we know best and choose from the best
While the “security” aspect could be of some value for some people, let me give you an example of how much crap it is:
Nokia’s batteries are dumb. So dumb, in fact, that their phones have to know what batteries they carry in order to not overcharge.
What if the battery was smarter, and had a way to tell the operating system it’s full? If a little company like OpenMoko had it, why wouldn’t Nokia have it? It’s one of the most dangerous equipments in the phone, so I guess that’s what they refer to when they talk about security and some of the energy related software is *closed*.
That’s evidence of crappy hardware.
Sorry, disappointing. Will wait for the competition unless this changes.
«There’s a difference between closed firmware providing a standard protocol and a proprietary ASIC providing a closed-source binary driver using a proprietary command language to talk to the hardware.
None of the Nxx tablets are fully functional with free software. The FreeRunner is.»
Indeed it is!root@om-gta02 ~ $ cat /proc/sys/kernel/tainted 0
So there you go! There’s much better, in terms of freedom, so don’t settle for less just because it’s fancier.
Demand more! It’s your right as a software user, and your power as a consumer.
This here is the new Nokia N900 phone, running Maemo5, a Linux distribution. Wow!
(the downside is the ~high price and there’re chances that some bits of it are still closed)Tags: linux, mobile, planet-openmoko, planet-ubuntu, planet-vapaasuomi
If you don't know about it already, its form-factor will remind you of the Nokia Communicator: from the outside, it looks like a regular candy-bar phone, but it also reveals a full keyboard and wide-screen display when opened. What interests us here is that its inside is open, too :)
The device is not in production yet, but they have been so kind as to let me borrow a sample for a while, which I demonstrated during my hackable:Device workshops at HAR2009 by the way. This is where I managed to install hackable:1 on the phone.
On the hardware side, it was difficult to let it be easier to test. Let me stress first that this was a pre-production device, and all of this may be subject to changes! So here we are:
- the phone has an internal flash memory but can also boot on an SD card, which is conveniently replaceable without opening the phone or even removing the battery,
- the first partition of the SD card must be formatted as a FAT filesystem,
- I was provided with two second-stage bootloaders: one that boots the phone from flash, and the other which updates it.
About the software now, this device happens to use the same architecture as the Openmoko Freerunner within Debian, "armel". One only has then to choose the right packages, configure them accordingly and generate a filesystem archive.
First, I have added a generic device definition file in trunk/build/profiles/ROAD-Officer.include:
The "STRIP" line is necessary because of the way we are currently cross-compiling Debian packages: the native tools are unable to strip the binaries cross-compiled. Therefore, strap:1 is currently doing it instead, while generating the images.
#this device is a phone
#add bluetooth support
#add GPS support
#add touchscreen support
#add wifi support
This should be self-explanatory :)
Unlike the Openmoko Freerunner, which has its own dedicated X server, we are using the generic framebuffer-based X server. It just works :)
#FIXME still needs to be packaged
In order to gain space, we are blacklisting this meta-package: xserver-xorg-core dependencies are actually satisfied with at least one video driver installed, which is the case here.
Next comes the actual profile definition, in trunk/build/profiles/ROAD-Officer-user.profile:
#blacklist packages to gain space
#additional dependencies adjustments
This was directly taken from the Openmoko Neo1973 profile, which has tough space constraints on the flash. Here we do not have such limitations, however it made the testing process slightly faster.
Anyway, after some more tuning in trunk/build/packages, it was time to generate the filesystem archive:
$ ./build.sh VENDOR=ROAD MODEL=Officer PURPOSE=user archive
At this stage, the only missing bit was the kernel. I simply used the one already flashed onto the device, but I still needed some modules. They were of course provided to me in source and binary forms, but I don't think this kernel tree is available publicly at the moment. I am sure it will be as soon as the ROAD developers can manage.
Unfortunately, I could only get this far yet. It boots all the way to the graphical user interface, where the Om2007.2 design does not really fit the rather wide screen. We are currently working hard on the next release, rev5, and focusing on the Openmoko Freerunner first, but I will be resuming this work soon enough!
Yesterday I decided to go to their lab to hack with Matt on the Cortex-A8 support in OpenOCD. After downloading the datasheets, we started to poke the code and tried to get a picture of how things are supposed to work. We have fixed various candidates for failures, like not waiting for the previous instruction to be finished when executing, not waiting for data to be there before reading.
Our symptoms were that after typing "halt" a lot of "invalid mode" messages got printed. After some tracing we ended at the execution of one instruction. The Cortex-A8 supports a mode were an ARM instruction can be written to a register and this instruction will be executed when being in debug mode. Now for a debugger the instruction is copying registers and other data to a special channel that can be read from the debugger. After looking further every register dumped liked this had the value 0x0...After this we were sure to have found the place were things go wrong. All we needed to find out why this instruction is not properly executed.
After studying the datasheet some more, going through the bits of DSCR and DCCR, and looking at the value of DSCR we have, it was clear that we just need to enable execution of instructions from the ITR (Instruction Transfer Register).
After this debugging session I still have little knowledge about ADI and the related things and this is why Free Software is so great, I can spend one afternoon, and can make a big change, and I can do it because I build on support from previous developers!
It’s a long time since I’ve written anything about Openmoko Freerunner, the open linux phone . Some nice things have happened very recently in the community so I thought I’d write a little update. Ready? GO!Community Updates
After Openmoko stopped supporting software development for Openmoko phones and concentrate on producing Freerunner phones and their mysterious ‘project B’, also their support for Community Updates stopped. About a month ago the community took over the task and now the updates are published every second week.
There’s a poll open asking you for the distro you use most of your time.
It’s vital for the community to be able to show their coolest apps in an appealing way: screenshot, description, comments etc. Since opkg.org has some major problems, some people got interested in setting up a new site to do this. At the moment the most promising existing platform is apt-portal - and it actually looks very nice and suitable for our needs, and it’s developers are also interested and willing to help Openmoko community.
I believe that a showroom like this will help users to try apps and developers to write apps as they’re able to promote their apps and get comments easily.
Glamo is the display accelerator of Freerunner. It’s been an annoyance only making our life more difficult and slowing things done - until now: Thomas White started the race against the flow and writes a working driver for it. This means that one day we will have somekind of graphic acceleration on our Freerunners. What’s cool about that? It makes it easier again to impress other people with Freerunner
After Openmoko stopped financing software development for Openmoko phones, the development of OM2009 (the next Openmoko-distro) and Paroli (phone application) started suffering, as the guys working on those left the office and started to do something else full-time. I’ve personally suffered from this a lot and today I heard something great: Paroli runs on SHR!
This might attract more people to work on Paroli and give it a new boost.
To me, being able to run Paroli on SHR means that there’re no reasons to keep OM2009 alive, both being Openembedded-based distributions. See the poll, SHR is what people use. We have a One Distro to Rule Them All.
For a sec this might sound bad but I personally like it a lot and have been waiting for it a looong time. Now we have only one distro in the community that everyone can contribute to instead of competing distros. I believe this can now take us far. I only wish this would’ve happened a loong time ago.
Debian of course will never die and I’m happy about it - I also have Debian on my uSD card. Android, QT, OpenWRT and so on will live their own lives but I don’t expect them to be big on Freerunner in the near future.Conclusions
After some kind of recession (don’t know, maybe they call it ‘Summer’) the community is finally waking up and things start to happen. Can’t wait to see where we’re in 6 months from now!Tags: freerunner, linux, mobile, planet-fnoss, planet-openmoko, planet-vapaasuomi
I've recently spent quite a bit of time looking at 3G protocol traces and I already hate them. Why do they have to use ASN.1 PER everywhere? The 2G / 2.5G protocols are much easier to understand. You can look at the hexdump and decode it in your head. You can read the spec and understand what they do. You can implement them without thinking too much. But 3G with all its ASN.1 crap, sometimes even unaligned PER encoded? Simply impossible.
Why do people want to save a couple of bits, especially on the back-haul interfaces in the core network that shouldn't matter - at least not if you can reduce the computational complexity for the involved network entities _and_ lower the R&D cost due to easier debugging for everyone who ever implements or deploys such protocols.
Voici quelques information diverses glanées sur le web.
- L'équipe de Hackable:1 travaille sur h1settings qui sera doté d'une nouvelle fonctionnalité permettant de simplifier la gestion des paramètres du neo.
- Rubrique bricolage : un tutoriel photo de création d'un support vertical pour neo.
- Intel a finalisé le rachat de Wind River pour "renforcer sa présence sur les créneaux des systèmes embarqués et de la pico-informatique nomade".
- Nokia lance PySide, un nouveau binding Python/Qt sous licence LGPL, concurrençant ainsi le PyQt de Riverbank Computing.
- Insolite : un concept de météo-phone très original
- L'interface de Apathy a été améliorée (c'est un client jabber / msn / Gtalk / SIP / SMS / GSM)
Bonne lecture !
I thought I better give an update on the work I’ve been doing on Apathy.
I have been working on various GUI and back-end elements. We decided to remove the Call and Send message icons from the toolbar and instead when a contact is selected on the list a menu will appear, when you do this, Telepathy will query what options the contact supports such as at the moment voice and text chat. This works well as it clears up the toolbar for contacts and other non contact specific pages and it means as more functionality comes along it won’t further clog up that toolbar and we can hide/show the options available to the users of different protocols. Speaking of protocols, MSN is now supported which is great!
Anyway, enough talking and more screen shots:
and a video it is alittle outdated but it still gives the general idea:
DiouxX, l'un des contributeurs du forum, a publié deux tutoriels vidéos pour expliquer comment flasher un Openmoko.
Le premier montre le principe en ligne de commande :
Le second utilise l'outil graphique neotool :
flasher OpenMoko Neotool
Une bonne initiative qui sera bien utile aux débutants car toutes les manipulations sont soigneusement commentées.
I finally got feed up with having my FreeRunner laying flat on the table.
So I decided that it was time to construct a stand for it.
I had some 3mm extruded polystyrene laying around (which I use for building model R/C planes).
It is actually just floor insulating material…
Created a simple design for a cradle/stand for the Freerunner.
Sources are include, batteries are not needed.
The parts glued together.
(Using “UHU Por”, but regular wood glue would have worked as well.)
The paper was intentionally left on as the floor insulation has groves on one side.
Painted the stand to hide the paper and give it a more uniform look.
h1settings is a library which handles the global settings of the phone. It is a basic wrapper upon some gconf keys and has functions to :
- read and update key values
- listen to gconf key changes
Device states :
- gprs on/off : /desktop/h1/phone/enable_gprs
- gsm on/off : /desktop/h1/phone/enable_gsm
- gps on/off : /desktop/h1/gps/enable_gps
- wifi on/off : /desktop/h1/phone/enable_wifi
- bluetooth on/off : /desktop/h1/phone/enable_bluetooth
- power management enabled / disabled
Currently, all the actions related to key states except gsm are handled by neod, the central daemon. It registers itself for these keys changes and sets the state of the devices. For the gsm part, it is handled by the gsm applet because it has already everything needed to switch on/off the antenna.
Another advantage is that an independant settings app can be built very easily without any dependencies with the underlying system, and this app already exists : h1settings.
See some screenshots below :
As you may know, we are willing to migrate to FSO. As part of it, we made ogsmd running on H:1 and we will rewrite phone-kit to use libfso-glib instead of libgsmd.
Until we get all the stuff packaged, here are the step to make ogsmd running on a Hackable:1 rev4 installation.Install the framework
We will use a git version that I know working. On your computer: git clone git://git.freesmartphone.org/framework.git cd framework git checkout 17898fc0f73453c11d1b1e8db57f8e8a0cfbc943 . cd .. scp -r framework email@example.com: # I assume that it is you FR's IP
SSH into your freerunner and: cd framework python setup.py install cd ..Install the muxer
We will use SHR packages which a copy of them is on our trac. wget "http://trac.hackable1.org/trac/raw-attachment/wiki/ogsmd/fso-abyss_0.3.5+gitr67+ff68be1581069ca494a559e85f6299246888d3b5-r0_armv4t.ipk" ar -x fso-abyss_0.3.5+gitr67+ff68be1581069ca494a559e85f6299246888d3b5-r0_armv4t.ipk tar -xvzf data.tar.gz -C / wget "http://trac.hackable1.org/trac/raw-attachment/wiki/ogsmd/libgsm0710mux0_0.3.5+gitr35+8e3e7533b286d8086bce8fa09bce23bb9f18bb98-r1_armv4t.ipk" ar -x libgsm0710mux0_0.3.5+gitr35+8e3e7533b286d8086bce8fa09bce23bb9f18bb98-r1_armv4t.ipk tar -xvzf data.tar.gz -C / wget "http://trac.hackable1.org/trac/raw-attachment/wiki/ogsmd/libgsm0710-0_1.1.1+gitr15+3bb80ba6cc9f86ed3996f88bfa2986cc572489d6-r1_armv4t.ipk" ar -x libgsm0710-0_1.1.1+gitr15+3bb80ba6cc9f86ed3996f88bfa2986cc572489d6-r1_armv4t.ipk tar -xvzf data.tar.gz -C / wget "http://trac.hackable1.org/trac/raw-attachment/wiki/ogsmd/libfsotransport0_0.9.3+gitr367+3c3e1b862cdde806cef8f502dfe79f1d48f1c5d7-r6.1_armv4t.ipk" ar -x libfsotransport0_0.9.3+gitr367+3c3e1b862cdde806cef8f502dfe79f1d48f1c5d7-r6.1_armv4t.ipk tar -xvzf data.tar.gz -C / wget "http://trac.hackable1.org/trac/raw-attachment/wiki/ogsmd/libfsobasics0_0.8.1.0+gitr367+3c3e1b862cdde806cef8f502dfe79f1d48f1c5d7-r6.1_armv4t.ipk" ar -x libfsobasics0_0.8.1.0+gitr367+3c3e1b862cdde806cef8f502dfe79f1d48f1c5d7-r6.1_armv4t.ipk tar -xvzf data.tar.gz -C /
We will use SHR frameworkd.conf: wget "http://git.shr-project.org/git/?p=shr-themes.git;a=blob_plain;f=frameworkd/frameworkd-config-shr/om-gta02/frameworkd.conf;hb=HEAD" -O /etc/frameworkd.conf
If the following file doesn't exists, libgsm0710mux segfaults (see http://trac.freesmartphone.org/ticket/467) cat << __EOF > /etc/abyss.conf [omuxerd] autoopen = 1 autoclose = 1 autoexit = 1 [session] mode = 1 framesize = 98 port = /dev/ttySAC0 speed = 115200 [device] wakeup_threshold = 6 wakeup_waitms = 200 __EOF
And if this one doesn't exists, fso-abyss claims it doesn't provide any channel touch /etc/cornucopia.conf
A file may have permissions problem, first check it: ls -l /usr/lib/dbus-1.0/dbus-daemon-launch-helper
If the group isn't messagebus: chgrp messagebus /usr/lib/dbus-1.0/dbus-daemon-launch-helper chmod u+s /usr/lib/dbus-1.0/dbus-daemon-launch-helper # because chgrp removes the SUIDLaunch Ogsmd
Let's kill the old stuff... killall -9 ogsmd ...and launch te framework: frameworkd -s ogsmd If no error (Python Traceback) occurs, we can move on:
wget "http://trac.hackable1.org/trac/raw-attachment/wiki/libfso-glib/libfso-glib0_0.2.0-gitrx44+9d292508739452b55b80ec40ec57405a5de2159f-r0_armv4t.ipk" ar -x libfso-glib0_0.2.0-gitrx44+9d292508739452b55b80ec40ec57405a5de2159f-r0_armv4t.ipk tar -xvzf data.tar.gz -C /
Install the sample (See the sources)wget http://trac.hackable1.org/trac/raw-attachment/wiki/libfso-glib/sample-libfso-glib_0.1-1_armel.deb dpkg -i sample-libfso-glib_0.1-1_armel.deb sample-w You will be asked for your PIN (unless you are already authentified) and you will be registered.
Then, it will catch several signals. after that, you can call yourself and see the signals "CallStatus" be matched. These signals are sent whenever the status of a call (which ID is specified, i.e. "1") change. (ie "incoming" or "release"). See FSO doc for further information.
And now what ? You can already, by reading freesmartphone.h, find any interesting function you need and write nice applications.
Any question ?
If you have any question about this manipulation or about Hackable:1, feel free to ask in the comments.
Un bref article sur Le Monde Informatique fait le constat suivant :
il existe de nombreuses plates-formes Linux pour mobiles mais chacune se développe dans son coin.
L'article liste :
- Moblin (Intel)
- Android (Google)
- Maemo (Motorola, Nokia)
- WebOS (Palm)
- LiMo (Motorola, NEC, NTT DoCoMo, Panasonic, Samsung, ...)
- Mobilinux (MontaVista sur ARM)
- et, enfin, Openmoko Linux, le plus libre et de tous
Le point de vue sur cette regrettable fragmentation est partagé par beaucoup (voir aussi cet article sur businessmobile.fr)
Mais n'est-ce pas une conséquence du manque d'ouverture des mobile eux-même ?
En éternel optimiste, je reste persuadé que la diversité peut aussi devenir une force.
L'information relayée par PCInpact provient du site chinois 163.com : le futur smartphone de Dell est désormais une réalité.
- système OMS (dérivé de Android)
- pas de wifi
- pas de GPS
- pas de clavier physique
- 2G (pas de 3G)
- écran 3,5" 640 x 360 pixels
- APN 3,2Mpx
- écran tactile
- port mini-USB
- port micro-SD
Certains choix laissent dubitatifs, le plus surprenant étant tout de même l'absence de wifi !
Reste 2 questions : est-ce qu'une version mieux pourvue sera prévue en europe ? et à quel prix ?