dev builds
themes manual
device status forums
mailing lists
IRC bugs
dev guide

Rockbox mail archive

Subject: Re: ROLO / two-stage booting for rockbox

Re: ROLO / two-stage booting for rockbox

From: Björn Stenberg <>
Date: Sat, 18 Jan 2003 23:16:44 +0100

roland wrote:
> What about making "independent" ROLO an Rockbox option, i.e. moving
> ROLO out of rockbox code ???

That was the idea with ROLO from the beginning. But we quickly realized the current model is superior. Most people want to load one firmware 95% of the time and just have the option of running another.

> Independent ROLO would start very quickly IMHO ,because there is much
> less code for being loaded.

No. The long boot time is because the Archos firmware spends a lot of time on other things before loading the Rockbox file. Not because Rockbox is big.

> Currently, when I want to boot original Archos Firmware or other Rockbox
> Version, I need to boot rockbox, browse rootdir and find the appropriate
> file - this takes some time because I have lots of dirs and files in rootdir

I would say that is your problem. The easy solution is to clean out your root dir, or create a "-firmware" dir where you store all alternate firmwares. It will show up at the top in your browser.

> Another advantage could be, that this "1st Stage Rolo with boot menu"
> could do backup/restore of RTC settings, so every Firmware could have
> it`s unique set of settings.

Rockbox already does this, by means of a checksom for the RTC contents. If the checksum is bad, the settings are loaded from disk. Of course, this doesn't help the Archos firmware.

You are free to make a stand-alone ROLO, of course. It's simply a matter of taking Rockbox and stripping out all the unneeded parts. But I personally don't think it's very useful.

Received on 2003-01-18

Page template was last modified "Tue Sep 7 00:00:02 2021" The Rockbox Crew -- Privacy Policy