Category Archives: Open Source

Open Source, Free Software, and similar

Sansa Fuze AMS reuse

Anythingbutipod.com published a Sansa Fuze disassembly today and allow me to offer a visual comparison of the SanDisk-branded main chips in the Sansa Fuze (top) compared to the one in the Sansa e280 v2 (bottom):

Sansa Fuze chip branded SanDisk

SanDisk marked chip, an AMS AS3525

And since we know the e200v2 one is an AS3525, there is little doubt that the Fuze one is as well. Of course we can confirm this for real once we get our hands on a firmware update file for the Fuze – I’m not aware of the existence of any yet at least.

So where does this put the Fuze Rockbox-wise? About at the same position all the other “Sansa v2 architecture” targets: we basically know the firmware file format, we have data sheet for the AS3525 but there aren’t any particular efforts going on and we don’t know if they have any means to recover from being flashed with a broken firmware!

Update: because some less intelligent people decided that facts I wrote in this article back in 2008 would still be the truth several years later, I urge you all you check the date for things your read on the internets. And in this particular case, Rockbox runs very good these days on several SanDisk players that use the AMS chipsets. See the http://www.rockbox.org/wiki/SansaAMS page for details

lugradio s5e14

sansa e200RI listened to lugradio’s season 5 epsisode 14 podcast today and I thought I’d share that at roughly 1:20 into the show there’s a brief mentioning and discussion around Rockbox. The subject came up thanks to a listener’s email explaining how he got his Sansa e200 player to play ogg by installing it.

Unintentionally, it was also quite ironical how Adam (one of the podcast hosts) just minutes before this mentioned how he has an iAudio X5 that can play ogg vorbis (and flac) natively (as a response to a user asking what players the guys would recommend) – without mentioning a single word about Rockbox even though Rockbox worked on the X5 long before it worked on the Sansa and I would think that any Linux- liking Open Source geek should know about Rockbox and use it on their mp3 players at least as long as they have targets that Rockbox is already ported to and working fine on… and when asked, I can only recommend getting any player that can run Rockbox before one that can’t. Of course these days this is somewhat of a dilemma since none of the players Rockbox supports are manufactured anymore…

I also liked in a elbow-poking sort of way how they referred to the ipodlinux project as one of the most pointless projects in existence. Of course, that may very well also be one of the reasons why that project is now more or less dead. This also makes me think of this lwn.net post by debacle, who argues that having Linux on a portable music player is better than Rockbox simply because “there’s where the developers are”. As the ipodlinux example shows, the reality is not that simple.

Two for the price of one

As probably one of the last humans on earth, I got my paper version of Linux Journal’s April 2008 issue in my mailbox today. While I’ve felt that the magazine has slowly degraded over the last years, this issue certainly made me all warm and fuzzy inside since it contains not one but two articles on subjects very dear to me. A three-page article was dedicated to a Rockbox review (subscription-required-to-read link) named “iPod + Rockbox =Linux Journal April 2008 issue 168 Entertainment Extravaganza” and there was a two-page article on how to use curl (another paid-subscription-required link)to fiddle with a web interface named “Twittering from the Command Line”.

I have a hard time to put a finger on exactly why I feel that the magazine has lost some of its past qualities but I’ve noticed that I finish the magazine much faster these days and I generally skip over more uninteresting articles. I haven’t really investigated this, but it may very well be because a shift in focus in the magazine. I tend to be interested in low-level, kernel, OS, hardware-touching, libraries and related stuff. Not so much in high-level applications or web frameworks and more user and desktop oriented fluff.

I should also add that the Rockbox review was pretty good. Not perfect in any way since it contained errors, was for an old boring grayscale-ipod target and suggested that the original OS is better suited for playing music… The article that mentioned curl wasn’t really about curl but only showed how it can be used but it was mentioned in positive terms at least!

curl ten years today

Birthdaycake

On March 20th 1998 curl 4 was released. It was the first curl release ever even if already at version 4 since we kept the version number from the previous projects we did before curl – using other names. We started it all with having the tool named httpget (which was an existing small tool written by Rafael Sagula), soon changed name to urlget to end up with curl – all renames happening due to shifting features and focus.

Like many other projects, this started because of an itch. I wanted to get currency rates off the internet to allow an IRC bot to be able to provide an “exchange service” for users with accurate up-to-date rates. I thought the existing projects I found all did too much or did the wrong thing. That bot and service is now gone since long.

curl has been a truly portable project from day 1, and the first windows build was already urlget 2.1 (pre-curl). autoconf support for the build process was added in October 1998.

Unfortunately I don’t have the original release 4 tarball left anymore, the closest one I have is curl 4.8 (dated August 31 1998). curl 4.8 is about 3400 lines of code. Today we’re totaling in well over 100K source lines, so it has grown over 30 times!

I had no big plans for curl nor did I think very much about the future of the project. I just added the features I and my fellow contributors wanted to have for the moment. That’s actually pretty much how the project has continued to work. We don’t have many long-term plans for what to do with it, we mostly look just inches ahead of our noses and act accordingly.

During the version 6 period (Sep 1999 – Mar 2000) we learned that curl was getting popular, was useful and worked rather well, so the work on providing a libcurl started. We wanted to offer other applications the ability to use curl’s file transfer powers. Version 7.1 was released in August 2000 and thus libcurl was officially born.

curl and libcurl remained being a rather low-key project, I just work on it on my spare time and there are no full-time developers paid to work on this project – apart from some occasional sub-projects now and then that have been sponsored by companies and organizations. (See later on for an example.)

Slowly but surely more and more people started using libcurl and contributed with bug reports and patches. When the project turned 5 years in 2003 I collected all the names of all contributors so far and I reached the number 270. I found the number very high and I was mostly kidding when I said I hoped we would double that amount by the time we celebrate our tenth anniversary. Of course we’ve more than doubled that amount today when we have more than 620 named contributors so far – and continuously adding new ones with every release.

During this journey of a decade, I’ve remained the lead developer and project leader but we’re now some 10 developers with commit access (that also use it) and I try to be open and responsive in order to attract more developers to come aboard, to listen to their advice and ideas and to be sensitive on what our users want from us.

In 2005 I was lucky enough to get a grant from the Swedish IIS organization for the purpose of developing a new event-based API for libcurl to better deal with very large amount of connections, the problem so nicely called c10k.

In the days when our humble project turns 10, I spend about two hours spare time per day on the project and it is my primary hobby, we make 5-6 releases per year, we get about 7000 unique visitors on the web site a normal day, about one million curl packages are downloaded per year – from our servers.

Today, libcurl is feature-rich, portable, very widely used, very fast, well supported and there are no signs of stagnation in release nor development pace. In fact, looking at the source-code growth over the last couple of years we can see a pretty stable and continuous growth:

curl source code growth

Just as I never looked ahead and planned for the future much in the past, I don’t do that now either so I really don’t know and can’t tell what the future will hold for us. We’ll just continue to develop the world’s best client-side file transfer library, to make it even more solid for the foreseeable future, to make it do the things users and developers out there think it should do. Possibly that involves adding support for more protocols, removing some of the less popular ones or simply by enhancing how we support the existing ones.

Join the mailing lists and join us for the next ten years to come!

Neuros OSD 2.0

For you who are into things like open source hardware for your videos, it can be interesting to note Neuros‘ recent posting of their planned specs for their upcoming OSD 2.0 player that I guess then will replace the current Neuros OSD model.Neuros OSD 2.0

In hard techy interesting terms: they plan to upgrade to Texas Instruments Davinci 6446 chipset, which is a 300MHz ARM9 with a C64x DSP core embedded. Pretty much like the existing DM320 one, but it seems with a great deal of more horse power under the hood. Given their specs paper, it will support a lot of formats and at least partially up to HD resolutions. It’ll also support internal harddrive and offer 256MB RAM and 256MB internal NAND flash.

Personally I don’t care that much as I don’t even have analogue TV and don’t download/have many movies to watch and my existing DVB-T box has fine recording abilities and my DVD is good enough for my kids to repeatedly watch the same animated films over and over and over…

Oh btw, if this sounds like your kind of backyard and other things combine well, Neuros is hiring Linux developers for what I believe is this hardware.

(sorry for the crappy quality of the pic but I nicked it from the PDF)

Snaxx v18

Me and my fellows of the Haxx tribe have been arranging the Snaxx series of gatherings for about eight years by now and on this Wednesday the 19th of March 2008 it is time for the 18th meeting. We gather up in a dark pub in Stockholm to talk tech, work, open source and similar crap with similar-minded people while going through the beers of the place.

Since several of us in Haxx are pretty much into ales, porters and stouts we tend to prefer places with a large selection of that kind of beer, both on draft and on bottle.

We tend to be somewhere around 10 to 15 friends, but I really prefer if you mail me and tell me if you intend to come so that we can arrange properly to deal with the amount of people that show up. We’re basically all friends and friends of friends.

So if you’re a friend and in Stockholm, welcome!

Secrets are hard to keep

On the web, it seems more or less everything is eventually getting out and gets accessible for people to download and see. You can fight hard and make a real effort but as we keep seeing, lots of secrets get revealed in the end anyway.Data Sheet for a technical thing

The other day a friendly fellow joined the Rockbox IRC channel and pointed out a russian site full of iriver goodies such as service manuals, firmwares and perhaps most importantly: circuit diagrams for just about all (somewhat older) iriver models, including the H10, H100, H300 series and more.

I wish we had these before when the Rockbox ports for these targets were younger, but I’m sure they’ll still come handy to some people now as well.

(Now I won’t reproduce the link here just to not make the traffic too hard on that site and to avoid getting into problems for linking to content that is clearly dubious legal-wise, but you don’t have to be a genius to find the link yourself.)

Rockbox on iAudio M3

iAudio M3This player’s been out for quite some time and most certainly won’t be found anywhere to be bought as new. Still, Jens Arnold’s been working hard on this port lately and just minutes ago he mentioned that he got sound working on it – and the build table subsequently has all three kinds of the M3 build added to it.

The M3 is roughly an M5 but without any LCD on the main unit, there’s only that one on the LCD! And of course the M5 was almost an X5 but with a greyscale LCD… So it is another one of them Coldfire 5249 based targets. The LCD on the remote is 128×96 2bit greyscale,

The M3 comes with 20 or 40GB harddisk and there’s an M3L around with a larger capacity battery

How many Rockbox ports are there now? It’s hard to tell as it really depends on what level of maturity and how much functionality you require before you count it as an actual port, but the configure script in our source tree has 38 different ones mentioned. I believe some of them are not more than embryos, but there are also other initial efforts not yet added to this script.

Cowon’s spec page on the M3.