Rockbox.org home
release
dev builds
extras
themes manual
wiki
device status forums
mailing lists
IRC bugs
patches
dev guide



Rockbox mail archive

Subject: Re: Multiboot Bootloaders

Re: Multiboot Bootloaders

From: Michael Carr via rockbox-dev <rockbox-dev_at_cool.haxx.se>
Date: Mon, 13 Feb 2017 23:05:23 -0500

I imagine multiboot would be very useful if one, say, had a stable
version of Rockbox on the internal memory and a development version on
an SD card. It might also be useful for someone trying to minimize
writes to internal NAND - install once on the NAND, and install
on/boot from an SD card copy from then on.

That's all I can think of, though.

On Mon, Feb 13, 2017 at 4:43 PM, Steph yahoo via rockbox-dev
<rockbox-dev_at_cool.haxx.se> wrote:
> From my user point of view & so I can learn something : what would be the
> reason or advantage of having such multiboot ?
>
> I own a Cowon D2 which I'd love to boot from hardware drive instead of SD
> card but multiboot ? Maybe so I would be able to copy/paste cfg files on any
> microSD or SD card and boot from them with similar settings "preloaded"…
> --
> Tshaw !!
>
> Steph
>
> Envoyé de mon aPhone
>
>
> On 13 février 2017 04:49:33 HNEC, Wilgus William via rockbox-dev
> <rockbox-dev_at_cool.haxx.se> wrote:
>>
>> Hi all,
>>
>> I've been working on adding multiboot functionality to
>> bootloaders on players that support multiple drives/volumes.
>> currently, I have a pretty good system laid out with the addition
>> of bootdata.h from Amaury I'm able to pass back the boot volume
>> to the firmware where we can use jhMikeS' 'mount any directory as
>> root' to allow redirect.
>>
>> The current functionality is as such:
>> rockbox_main.<playername> (clip+, fuze+ etc..) is placed in the root of
>> the
>> volume you would like the firmware to be loaded from if this file is blank
>> then
>> FW is loaded from /.rockbox in the root of this volume.
>> If instead a path is specified in the file then the firmware is loaded
>> from /<new path>/.rockbox, If the file is not found or doesn't contain the
>> bootdata header in the image then firmware loading falls back to standard
>> behavior.
>>
>> If anyone has suggestions / objections I look forward to your reply
>> though be aware, some of these targets have very little free space
>> in the bootloader fw images.
>>
>>
>>
>>
>>
>
Received on 2017-02-14


Page was last modified "Jan 10 2012" The Rockbox Crew
aaa