Open Source, Free Software, and similar
iFixit ripped apart an iPod touch.
Unfortunately these guys continue to just publish lores camera images instead of hires scans, but this pic shows the (Samsung) chip with the Apple logo on it.
Apparently this has a Wolfson codec while the new iPod Classics use a Cirrus chip!
The touch and the iphone seems to have a lot in common internally. Not too surprising really…
The touch is a whopping 120 grams beast, while I thought the SanDisk Sansa e200 players were heavy with their 75 grams…
Rockbox was a participating mentor organization of Google’s Summer of Code 2007, and I was the organization administrator in our end. It turned out to be a rather easy job and in the end I didn’t end up mentoring anyone.
Now they’re arranging a Summit in Mountain View, California in the beginning of October (like they obviously did last year) and Rockbox as organization is invited to send three representatives. They are even graciously funding people to go there, and they pay for a night at a hotel and food. Very grand indeed.
If my life had been different at this point I would’ve been thrilled to go there. Now, with two small kids it’s just not practically possible. I’ve already stretched my “allowance” from my family by the upcoming week-long trip to China in mid-October. So while it wouldn’t cost me personally much money-wise, it unfortunately doesn’t fit right now.
Just a short while ago I uploaded the 7.17.0 packages to the curl site, updated the front page, mailed the announcement and submitted an update on freshmeat.
The previous release (7.16.4) was done in haste due to the security issue we got reported, but this time we took our time and I think we’ve done a pretty good job. The upcoming weeks will tell for sure…
Changes this time include the new OS/400 port, the fact that curl_easy_setopt() now will copy all strings passed to it (previously it referred to the strings the application still had to keep around), SCP and SFTP support now requires libssh2 0.16 or later, the LDAP libraries are now build-time linked like all other third part libs and no longer run-time dlopen() like before and LDAPS is now supported. We also have at least 27 mentioned bug fixes, and possibly a few more actually done but not detailed in the release notes.
There’s no soname bump this time, although there have been a fair amount of return code name changes (with backwards compatible #defines added to make older programs still possible to compile), but we have started to add stuff in the TODO that we want to do the next time we actually decide to bump again. The previous bump did cause some havoc so I’ve learned to not use that card too often…
Unless something bad creeps up, I’m hoping for a good two months or so until 7.17.1 is due. With my autumn plans it might just take a little while longer as well. Time will have to tell.
Enjoy!
I find it very amusing that Windows users all so often refer to the command line as DOS, and I’ve tried to figure out how we still today frequently get to read users refer to the ancient operating system.
It was in fact still called “MS-DOS prompt” back in windows 98, as shown in this little picture:
I found that even Microsoft themselves refer to the commands you use on the command line as “MS-DOS commands“, so perhaps this is a primary reason? Even the producers of Windows confuse and mix the terms “command line” and “MS-DOS”…
When they launched Windows XP they no longer called it MS-DOS Prompt, it was then plain and simple “Command Prompt”:
We’ve also seen end users in the Rockbox project refer to the interface as DOS or DOS-style, and there is really nothing what so ever in common with MS-DOS in Rockbox. It is just (by default) a basic text-style interface. It is clear that to many people, a text-based interface be it a music player or a command line window, means DOS.
People are weird.
I’m the maintainer and admin of a few different open source packages, perhaps most notable in the curl project but I also poke on c-ares and libssh2 and I do a fair amount of work on Rockbox and hang around in a few other projects as well.
I write around 400-500 emails a month, the majority of them to the mailing lists of the projects I’m involved in. I try to respond to questions I know the answer to.
I’m not sure if I’ve grown even more grumpy recently or if the world is going downwards, but I’ve recently been called rude and a scammer in public mailing lists after having answered to mails with a meaning that the guys asking the question isn’t exactly trying hard to read up on this, understand the area nor are they reading my answers very good. So what if I’m not always the perfect gentleman or say the right “social” words, I am a hard core tech guy and I answer and talk technical stuff and specific details all day long. That’s what I do and that’s who I am.
So, I just wanted to let the rest of you know: I am rude and mean and you should know better than to ask anything in a forum I frequent. Or then you can of course stand up against the whiners and help educate the world on how to ask questions and why spoon-feeding users on mailing lists isn’t a good idea.
Sticking out your chin in the harsh internet reality, one should expect to get hit like this every now and then and you need to grow pretty thick skin to not let the bad guys get to you. Nonetheless, people in general are nice but it is just too easy for people to get upset and send away very rude mails without any kind of aftermath.
(But I must admit I found the threat to discuss me at a future Zend conference hilarious!)
Obviously the CHDK guys have working code for Canon‘s (and other’s) Digic II powered cameras, and reading their wiki they use plain arm-elf for the job and… yeah so does Rockbox and… yeah, well it certainly at least opens a possibility for a Rockbox branch for these toys!
Of course there would be porting involved and I don’t know how these cameras have on the audio front, but those are all just details…
Wherever there are mailing lists, some people eventually bring up the suggestion to move to or to at least offer a web forum alternative as well.
As a subscriber to over 100 mailing lists, receiving several thousands of emails every day I’m a violent opponent of web forums. Why? I’ll entertain you by stating a few reasons for my opinion on this:
By reading thousands of mails per day, I’ve worked out a system on how to deal with them all. Like I filter them in 20+ inboxes on arrival and I read them in a prioritized order and I mark interesting mails as “important” to deal with them later in case I don’t have time at the moment to reply or catch all details.
Several of my inboxes are automatically (renamed and) archived every month to make them not grow inconveniently large.
So please, don’t start more forums. Use mailing lists. Oh, and don’t top-post and/or full-quote on those lists…
The initial way of installing Rockbox on the Sansa e200R series seriously scare away lots of people, and some of those who have attempted to perform the install really should better have been scared, judging from their desperate cries for help in the forum etc.
Another downside of the initial procedure was that it required the user to download a binary-patched version of the original bootloader, a bootloader that is the property of SanDisk that we have no rights to redistribute – especially not a modified one.
The current work-in-progress method is to build an installer program that can be uploaded to the player and then it does the necessary patching live in the target, removing the need to download anything that isn’t clearly a product of the Rockbox project.
We still lack a working way for this on Windows though, so the current plan is to initially provide a live CD with Linux and the e200R installer on for the Windows crowd, but we’ll see how things evolve…
I’ve been involved in the Rockbox project since before it was named Rockbox and in fact long before the first code as written. I’ve contributed to it pretty much over the years and I have a fair insight in how most of the ports have been made and what efforts that are behind them. Today, Rockbox runs on around 25 different digital music players.
The first ports of Rockbox was (in retrospect) rather easy since we took it to architectures what were made with circuits and chips for which we could find documentation online.
Recently, music players as well as other consumer electronics are being made using products and circuits from companies that blatantly refuse to hand out documentation. Companies such as PortalPlayer (now Nvidia), Austrian Micro Systems, Samsung, ALI, NEC, Broadcom, Telechip, Texas Instruments, Sigmatel (to name a few) all make interesting and fun hardware but…
Let’s say I am looking into alternatives when creating new hardware. I want to build something new and cool. Something not done before, that would be portable and feature sound and an LCD and whatnot. I see what cool manufacturers there are out there and I can read their propaganda on their fancy web sites. So, I want to compare company A’s fancy chip with company B’s. I contact them in order to get to know as much as possible to be able to compare these beauties.
No, you cannot get any docs. We will not tell you how our products are used until you sign up for a huge contract. These companies don’t only require NDAs to be signed and similar, they simply won’t let you get the docs no matter what if you’re a small player and are just interested in comparing and evaluating products.
I’ve contacted several companies with this purpose in mind. I work with embedded products for companies doing products using such chips, so I would assume I should be the kind of person these companies would respond to with an open mind and a will to sell me their stuff. But they clearly hate customers.
This problem is of course also tightly related with the eternal discussion of manufacturers not wanting to hand out docs to hardware they sell for PCs, such as graphic cards (AMD/ATI, Nvidia, etc) and network cards (Broadcom, etc). These companies usually hide behind a blurry statement about protecting their intellectual property and being afraid of ending up in the hands of the competition but that always and unconditionally end up with the arguments:
I sometimes wonder if the chip manufacturers do this on demand from their bigger customers, the consumer electronics companies, to help them keep things hidden so that we – the general public – will have a harder time to modify and/or reverse engineer their products, which may lead to additional support issues for them.
We see this development of secret-docs going in the wrong direction. Samsung used to publish a lot of docs for their ARM-core based microcontrollers, but they no longer do so. Marvell bought the Xscale family from Intel and recently they took away all the public docs for them…
We see “open source” projects (like Neuros uses TI chips) go with these companies so that they can’t reveal all source code.
Luckily, not everything is darkness. There are occasional bright spots, as the other day when AMD announced their intention of bringing their open source ATI drivers up to speed with what could be expected of them..
So what is there to do about this? What can we “little people” do to change these big evil corporations? There’s really only one way: put the money where the docs is! Buy stuff from the good companies. Recommend your clients to release docs openly. Recommend your clients to buy hardware (parts) from companies that host their documentation publicly.
