From: Matthew Allum @ OpenedHand
Great :) Welcome aboard !
Do I have to write something more?
Random mumblings of ARM developer
From: Matthew Allum @ OpenedHand
Great :) Welcome aboard !
Do I have to write something more?
Today there was a sale in local MediaMarkt. I decided to go there to look how much it was destroyed by wild crowd.
When I was at the shop there were only a bit more people then usual — no signs of wild crowd, no destroyed stuff.. But they had one nice thing (which was also one of reasons why I was there): Samsung 205B Wide LCD monitor for 999 PLN (about 260 EUR) and I bought one.
At home I replaced my Samsung 17” CRT with this new 20” widescreen LCD and booted. 1280x1024 (my usual resolution) was not so good and after edition of xorg.conf
I got 1680x1050 resolution and this is it. More space for windows, more space during reading of documents etc.
And all of that without any problems with gfx card — I use ATI x200 integrated into mainboard chipset and closed fglrx
driver (did not checked does opensource driver support this resolution but I think that it should).
During Pingwinaria 2007 (15-18 March) I will lecture about OpenEmbedded project. My abstract was accepted and I suppose that opinion about sent paper will arrive to me during next few days.
One of other lectures during event will be about OpenMoko platform (Tomasz Zieliński will talk about it). When I saw this in agenda I decided that I will have to write to him to get some infos so we will not talk about same things. But suprise, suprise — he wrote to me first ;D
BTW — I will translate my article to English and put it online after Pingwinaria.
Yesterday during iPhone discussion I gave URL to OpenMoko phone to some people on IRC. After that I had to answer many questions about it. One of them was Webdesigner and put some critic on colorscheme used on screenshot:
Colorscheme is one of those awful ones. Why grey with orange???
Then I visited OM website and discovered that they started developer program finally. Now I wonder — do I have to write to Mickeyl regarding embedded Linux projects I had contributed to or not…
UPDATE: Koen told me that this info was there from start. So I had to miss it…
Yesterday I got official information that Sharp ended Zaurus line — last production will be in February 2007 and then nothing — no new models, no building of older models. Many people wrote that this is bad thing, that they will miss new toys with Zaurus name…
I am not one of them. Since SL-C3000 (called “spitz”) model I had a feeling that Sharp is not able to create new handheld device for mass market. There was few new things in it but basically it was old clamshell line on steroids. Palmtop built to be used as English<>Japanese dictionary rather then as PDA. Then they released SL-C1000 (“akita)” which was spitz without hard drive (in form of 4GB CompactFlash microdrive) but with 128MB of Flash memory like it was in end of previous clamshell line. Both models were selling quite good and one day Sharp merged Akita and 4GB microdrive and thats how SL-C3100 (“borzoi”) was created. Again nothing new… Some months ago they got out of stock of 4GB cards so SL-C3200 (“terrier”) was created — with 6GB microdrive.
But those models were much worse then other palmtops on market… Windows Mobile devices got Bluetooth as standard, more and more models got WiFi inside (now even 802.11g instead of old 802.11b standard). Sharp did not even tried to compete with them. There were rumours that there was a plan to release SL-C3500 which would get WiFi inside but knowing Sharp it would be some shitty wlan-ng USB stick with drivers lacking WPA and any good support.
Add to it their lack of any support to users… Can you imagine that 2006 models were sold with few years old software created for first Zaurus models? They only did some small modifications to get some of new features supported. Someone told one day:
Sharp should concentrate on building Zaurus models. But they should not touch software — OpenZaurus or pdaX teams do it in much better way.
So I think that it is good that they finally ended Zaurus line — it was visible that they do not have idea which way to go and how to support users of own toys.
BTW: some people asked what will OpenZaurus team do now — we are working on 3.5.5 release for all existing models (except SL-A300 as usual). After release most of us will probably concentrate on fixing bugs, adding software and will move to Ångström distribution as this is future of embedded distros.
Yesterday I finally found some time to test Ångström on progear. Kernel needed to be recompiled (I forgot to include ATA driver) and finally it boot.
Console in VGA mode on XGA screen does not looks good but I ignored it (this is something to fix later). WiFi works, USB keyboard works so I was ready to tweak.
I baked some recipes to get some extra modules and got AC, Battery and Backlight support. It was not ideal but working. I think that next step will be rewriting those drivers and including them in mainline kernel.
First step is done — I converted progear-lcd
module into progear_bl
which use backlight subsystem and send it to LKML. Got some comments, updated code and who knows — maybe 2.6.21 will get it included…
BTW — It is my first real code submitted into kernel.
2006 year was good. I did few releases as OpenZaurus maintainer, created own company for my paid OpenEmbedded work, got some job offers from respected companies.
task-base
way of building images in OpenEmbedded.During weekend I was working on getting self hosted build of OpenEmbedded.
I built Ångström-2007.1 for progear and chrooted into resulting image. Then installed some packages, copied OE metadata, archives for SRC_URI and did bitbake nano
build.
Some packages was needed to be installed — I added them into new task named task-self-hosting
which should contain everything needed to get self hosted build running.
But there were some problems:
rpcgen
from glibc-utils
require cpp
This can be solved by adding RDEPENDS_glibc-utils = "cpp"
into glibc.bb recipe. But this is theory because we need glibc
to build gcc
so dependency chain is result.
Few headers exists in both packages — I do not know which one are more important. In my build I forced glibc-dev ones.
This is reported already in OpenEmbedded bugtracker.
subversion has problems with building — I need to check do I have some not-yet-committed patches for apr(-util) and subversion.
Perl is too granulated — I installed all 861 perl packages to get quilt-native happy instead of checking which are needed.
But the best thing is that whole process can be done. This shows that OpenEmbedded based distributions are able to build them self using software from feeds.