> We have had the commits for Bootdata and Multiboot functionality for a
> number devices up on gerrit for ~6 months now
>
> By putting the multiboot bootloader in the mainline this will allow users
> with failing flash a way to still use their device or even to always run
> from their sd card
We have had the commits for Bootdata and Multiboot functionality for a
number devices up on gerrit for ~6 months now
By putting the multiboot bootloader in the mainline this will allow users
with failing flash a way to still use their device or even to always run
from their sd card
It also opens
>> 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.
>>
>>
>I think that's a potentially very useful feature for development on targets
>with SD card.
>I am globally okay with the description
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 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
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'
