Rockbox Technical Forums

Rockbox General => Rockbox General Discussion => Topic started by: bind00 on July 29, 2009, 11:52:49 AM

Title: How does an OS f/w project like this get started?
Post by: bind00 on July 29, 2009, 11:52:49 AM: Hi
I'd be really interested to know how you guys went about building this firmware.
Not so much the programming but what input did you get from the hardware manufacturers?
Did you need their permission?
Did you need technical information about the players' inner workings?
What other logistical issues were there?

I own a music keyboard with terrible firmware and other members at that forum agree that OS would be a great option but are pessimistic about the chances of success.

Any comments welcome.

And thanks for Rockbox! :)
Title: Re: How does an OS f/w project like this get started?
Post by: LambdaCalculus on July 29, 2009, 12:15:51 PM: Rockbox just started out as an itch that needed to be scratched. Namely, the original Archos Jukebox 6000 firmware was utterly awful, so one Bjorn Stenberg took it upon himself to write a much better firmware. Thus, Rockbox was born.

Most of the work was done simply by reverse engineering and reading datasheets wherever possible. A couple of companies, like Austria Microsystems (the manufacturers of the sound chips in the e200 and c200) supplied us with information about those chips, but not every manufacturer has been so friendly.

We did this sort of work entirely on our own, with little input from other companies.
Title: Re: How does an OS f/w project like this get started?
Post by: vsl2005 on July 30, 2009, 07:42:42 AM: Then shared it with the world. Fantastic!
Title: Re: How does an OS f/w project like this get started?
Post by: Multiplex on July 30, 2009, 09:04:44 AM: THere is, or used to be, a document/Wiki page that gave the origins of the project, including the name. I've had a quick look but can't spot anything now...

It would be a shame to lose the history - I'll have a better dig around when time permits and if necessary start something on the Wiki.
Title: Re: How does an OS f/w project like this get started?
Post by: psycho_maniac on July 30, 2009, 11:17:58 AM: Quote from: LambdaCalculus379 on July 29, 2009, 12:15:51 PM
A couple of companies, like Austria Microsystems (the manufacturers of the sound chips in the e200 and c200) supplied us with information about those chips, but not every manufacturer has been so friendly.

for example...take a look at the video chips on the ipods :(
Title: Re: How does an OS f/w project like this get started?
Post by: bind00 on July 31, 2009, 12:33:16 PM: Interesting stuff. Thanks guys.

It's hard to see why a company would object if they're not charging for the firmware.
Of course it might create support issues but that can be addressed.
I wonder if the company has any legal redress if it were reverse engineered. And, if the company released the technical details required to build the firmware, would it be of use to their competitors?
Title: Re: How does an OS f/w project like this get started?
Post by: linuxstb on July 31, 2009, 01:15:36 PM: Quote from: Multiplex on July 30, 2009, 09:04:44 AM
THere is, or used to be, a document/Wiki page that gave the origins of the project, including the name. I've had a quick look but can't spot anything now...

Are you thinking about the docs/HISTORY file in the source?

http://svn.rockbox.org/viewvc.cgi/trunk/docs/HISTORY?view=markup (http://"http://svn.rockbox.org/viewvc.cgi/trunk/docs/HISTORY?view=markup")
Title: Re: How does an OS f/w project like this get started?
Post by: Multiplex on August 02, 2009, 02:45:21 PM: Ah that's one of them - I saw it wasn't part of the usual install any more, should have thought of SVN...