From: Jonathan Gordon <jdgordy_at_gmail.com>
Date: Tue, 20 May 2008 21:09:18 +1000

2008/5/20 Steven Gilberd <steve_at_erayd.net>:
> On Mon, 2008-05-19 at 22:29 -0500, Paul Louden wrote:
>> Con #2: Plugin buffer can't be used for settings and a TSR plugin
>> simultaneously leaving settings unchangeable. If you reserve a separate
>> buffer for the settings plugin, outsourcing them is pointless.
>
> What about implementing a semi-dynamic buffer system (no malloc()
> though, as I understand rb doesn't have this available)?
>
> Admittedly I don't do dev work on Rockbox (so take my ideas with a very
> big grain of salt), but wouldn't allowing each plugin to specify how
> much buffer it needs help this? Then you could run as many plugins
> simultaneously as you had room for in ram... and if you try to start one
> when there isn't enough ram left, present a menu of running plugins and
> ask which one to kill.
>
> Cheers,
> Steve
>

the buffer is used as somewhere in RAM to load the actual binary into
as well as giving it some RAM to work with. Doint it this way means
the plugin loader can be pretty simple which means savings in the core
(which is deemed much more important).
Received on 2008-05-20