Vincent Sanders: What is it with embedded computing?
Now I am a fairly competent engineer, I have worked with the ARM processors and SoC for many years. It should not therefor take me four days of almost continuous frustration to get a bootloader and kernel onto a system, but it has.
Firstly the system arrives and we look it over, the hardware design is not exactly elegant but seems like it will get the job done. That is at least a step up from several previous offerings which have been just plain broken. So I power it up and it boots into Fedora core 8, possibly not my first OS choice for a diskless system, but it does work.
Perhaps its worth mentioning that my experience with doing any Open Source development has caused me to have a severe aversion to software which is not upstream, especially kernels. The effort required to run your own patch series and keep it up to date is nothing short of Herculean.
Let us be honest, how many developers do you know who are talented enough to generate good code and patient enough to separately maintain it over a long period of time? I shall not belabor this point as others have repeatedly made it for me in much more eloquent ways. Lets us just say from my point of view. Upstream - good. Long term forks - bad.
With this in mind, the solutions Simtec develop are always with a view to our customers being able to simply download and use the standard upstream software wherever possible. Here is where the story stops being smooth and becomes a rant.
The system was running 2.6.22, one that was patched all which ways. "maybe they just shipped an old kernel" I thought. I opened the CD they provided and...oh, OK its just zips and tarballs of the binaries and source they used (actually that in itself is a minor miracle with a lot of vendors right now - see the almost continuous stream of copyright infringement litigation from the FSF) but sill stuck back in July 2007.
So i did teh normal thing, entered the URL printed on the outside of the box and went looking for the updates. No dice, just the same old stuff. So I contacted the company and recived the news that no there were no updates, that was what was published for the device, thats what I could have.
My initial reaction was of tired resignation...this would not be my first SoC port (probably around the fifth or sixth!) So I responded with cd linux-2.6;git checkout master;git pull and went to see what I could see. and lo and behold, there in the kernel, was full support for not only the SoC but for the other version of the very board I had.
Fortunately after mentioning this on IRC my giraffe loving friend. pointed me at the correct community git tree to find the tiny patch required to support my board.
So the vendor was not only shipping old code but actively dissuading customers from even looking for new stuff, which it turns out was mainline anyway! To add to this somewhere along the lines the company name on the box and contact information has changed and...well confusion reigned.
Right Plain sailing from here on? not quite...that would have been too easy. So you can build a mainline kernel...but you cannot boot it. you guessed it the bootloader they ship on the board is ancient, specifically a u-boot fork from December 2005. Having finally figured out how this was going to go, I went to the uboot repo, pulled the latest and built it for my target. And then I needed to upgrade the u-boot and joy of joys bricked the system.
Fortunately the system has a integrated FDTI serial/JTAG port so re-writing the flash should be as simple as running openOCD configured correctly. Of course this did not work...in the end I resorted to running their binary built versions from the CD (tarfile inside a zip inside a tarfile...whatever) and wrote their original image back to the board...which worked.
Long story short, next day I discover that i need a magic different uboot target (make u-boot.kwb for those that care) write this with the binary openocd build and...success
From then on its all been a bit anticlimactic and straightforward and I now have a system capable of starting a kernel over the network and a root fs on network, disc or flash.
My main complaint from all of this is what the hell are vendors doing shipping crap like this? Why do they all insist on taking a dreadful code drop from the SoC manufacturer when they first brought the part up and shipping that prototype junk until the part reaches the end of its life?!?
All the usual excuses about support etc. will come out, but seriously, you recive *no* support from vendors unless you pay for it and even then they will simply tell you whats on the CD is "it". Btw the diff for u-boot to support this board is larger than the original sources and the 2.6.22 is attacked with a 65MB diff which cannot be good.
The Open Source option is continuously innovating and improving, producing ever better software...but the embedded world seems to be forever stuck shipping crap. Is this just me? Does anyone have any solutions? Or am I stuck with this until I change profession?

There are few things I really hate. One of them is regressions. Regressions are bad because they usually take away things we are used to rely on, and leave us with the idea that perhaps the technical improvements didn t really improve our lifes as a user, despite putting less burden on the developers. Software is made for users, after all.
As part of my work on WebKitGTK+, I always keep an eye on regressions, both from previous WebKitGTK+ releases, and those imposed on embedding applications on their migration away from Gecko, and try to focus some of my efforts into lowering their numbers, whenever I can.
In recent times I have worked on removing a few very user-visible regressions in Epiphany, which I see as the most demanding WebKitGTK+ user in GNOME, such as
Barnes and Noble's new nook ebook reader is now shipping to people. Mine[1] is due to turn up tomorrow, but the instruction manual is available for
Transforming data is hard. When I joined my current company, there were stupendous amounts of Perl/PHP/Bash/<insert random programming language here> scripts that would run on a cron job and do magic things to our data. They d create reports, they d tell the purchasers when we were running out of stock, they d synchronise data between our Frontend and backend databases, they d collect, they d collate, they d do everything and anything.
Except, with all these scripts, in all these random languages, written by a multitude of previous developers (at different skill levels), they weren t particularly maintainable (and sometimes, they weren t particularly readable or understandable either imagine a 6000 line perl script that pretty much ran different permutations of the same data over and over again)
Enter Pentaho, and specifically it s
I'd like to make
Some time ago we decided in phpMyAdmin team to create yet another team meeting
(after five years) at FOSDEM 2010. It took some time, but now I should have
all travel things arranged (thanks to my employer who sends me there).
So if anybody wants to meet there, just drop me an email and I will try to put
you on my schedule.
This post is about
Well that all happened rather quickly.
This morning, we met with our agent to go through all of the offer
paperwork, at the bright and early time of 7:30am after (for me at least) a
bad night's sleep staring at the ceiling.
It wasn't that bad. A lot of disclosures, a lot of initialling and signing.
Here's what the stack of paperwork looked like:
Biggest, in terms of money involved, piece of equipment is a nice piece of glass to put in front of our camera.
Since my wife had been using a Canon SLR since forever (and we stayed with that when moving from the
I got a new computer at home a week ago and finally got around to assemble all the parts. Which wasn t as easy as expected, especially fitting the CPU cooler was a hard fight.
Specs
For the curious, here are the specs:
In fact, this is more useful than one can imagine, because a
considerable amount of time in periodic RC squashing is taken by
triaging the RC bug list to choose your targets. Of course there is
no guarantee that I'll be willing/able to fix handed-over bugs but,
as a RM, Luk has evidently well-trained feelings about how hard
would be to fix a given bug. All in all, for this week it worked
well: 4 of the above 7 came from
The story behind it
Recently, I decided to set up a subscription with a VoIP provider, Phonzo, here in Norway. On their webpage, Phonzo advertised a VoIP service which actually gave you the SIP information and allowed the user to connect their own equipment to this service. That s really cool , I thought. I can play with Asterisk on the PSTN now! . They also advertised an offer with rent of a Linksys SPA2102 included, at a very affordable rate.
Now, I suspected that the box might be locked as I d heard they were with some providers so I searched all over their webpage for any hint that it might be. None was to be found and since they included the specific model designation of the adapter rather than mentioning a generic Analogue Telephone Adapter , I basically assumed it wouldn t be crippled.
But when it did arrive (impeccable delivery time, and telephony worked out of the box, btw), I found to my dismay that the box was indeed locked. So I sent a polite email to customer service, saying basically that I know this is a matter mostly interesting to enthusiasts, but they ve advertised an SPA2102 , and what I have receieved is a crippled SPA2102 . They basically replied It says rent , so it belongs to us. I replied Renting does not exempt you from marketing laws; you ve sold me something else than what I paid for . I got the reply: We can t open it, it contains sensitive information and it s not crippled, it s optimized for Phonzo service[sic] (!). Yeah, that s really what they said.
A few more emails back and forth, and nothing of value came forth. When I received a letter from customer service saying Stop your nonsense, we re providing you a service and the adapter is a part of it I realized I wasn t getting anywhere there. I ve sent an email to the address in the SSL certificate (who also seems to be one of the founders) hoping I d get in touch with someone of relevance, but I don t have great hopes. (There s a