Rockbox.org home
Downloads
Release release
Dev builds dev builds
Extras extras
themes themes
Documentation
Manual manual
Wiki wiki
Device Status device status
Support
Forums forums
Mailing lists mailing lists
IRC IRC
Development
Bugs bugs
Patches patches
Dev Guide dev guide
Search



Donate

Rockbox Technical Forums


Login with username, password and session length
Home Help Search Staff List Login Register
News:

Rockbox Ports are now being developed for various digital audio players!

+  Rockbox Technical Forums
|-+  Rockbox General
| |-+  Rockbox General Discussion
| | |-+  How does an OS f/w project like this get started?
« previous next »
  • Print
Pages: [1]

Author Topic: How does an OS f/w project like this get started?  (Read 1954 times)

Offline bind00

  • Member
  • *
  • Posts: 6
How does an OS f/w project like this get started?
« 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!  :)
Logged

Offline LambdaCalculus

  • Member
  • *
  • Posts: 2257
  • Dreaming of Turing Machines...
    • The Nostalgia Roadtrip
Re: How does an OS f/w project like this get started?
« Reply #1 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.
Logged
Former Rockbox dev. Rising from the ashes...

Players: iPod Video /w 128GB SSD mod, H320 /w 128GB SSD mod

Offline vsl2005

  • Member
  • *
  • Posts: 28
  • Humble User
Re: How does an OS f/w project like this get started?
« Reply #2 on: July 30, 2009, 07:42:42 AM »
Then shared it with the world. Fantastic!
Logged
Archos JB v2, Ipod 5.5g, Sansa e260, e280, Clip+

Offline Multiplex

  • Member
  • *
  • Posts: 440
Re: How does an OS f/w project like this get started?
« Reply #3 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.
Logged

Offline psycho_maniac

  • Member
  • *
  • Posts: 814
    • MyWebPage
Re: How does an OS f/w project like this get started?
« Reply #4 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 :(
Logged
Please SEARCH the wiki | Please read the Forum Guidelines | Please Read the Manual
I Own A Gigabeat F80

Offline bind00

  • Member
  • *
  • Posts: 6
Re: How does an OS f/w project like this get started?
« Reply #5 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?
Logged

Offline linuxstb

  • Developer
  • Member
  • *
  • Posts: 1163
Re: How does an OS f/w project like this get started?
« Reply #6 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
« Last Edit: July 31, 2009, 01:18:07 PM by linuxstb »
Logged

Offline Multiplex

  • Member
  • *
  • Posts: 440
Re: How does an OS f/w project like this get started?
« Reply #7 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...
Logged

  • Print
Pages: [1]
« previous next »
+  Rockbox Technical Forums
|-+  Rockbox General
| |-+  Rockbox General Discussion
| | |-+  How does an OS f/w project like this get started?
 

  • SMF 2.0.17 | SMF © 2019, Simple Machines
  • Rockbox Privacy Policy
  • XHTML
  • RSS
  • WAP2

Page created in 0.1 seconds with 15 queries.