On Sun, Feb 26, 2012 at 12:29 PM, Frank Gevaerts <fr...@gevaerts.be> wrote: > The way I understand it (which could be wrong) is that the dualboot code > (i.e. the bit that decides which bit gets to boot) is *not* in the > bootloader as in the files that are downloaded, but in bits of code > that's embedded at build time into rbutil and/or mkamsboot. This has
I haven't followed the amsv2 bootloader / mkamsboot functionality. However, if this is true it's a bad thing because it embeds a dependency into Rockbox Utility. This means that depending on the version of Rockbox Utility used the bootloader (or rather dualboot code, but from a users point of view this doesn't make a difference) will behave differently, and this shouldn't happen. While there might be reasons for embedding the dualboot code into mkamsboot there should be a different approach for Rockbox Utility -- it won't be hard to download dualboot binary code from the server instead of having a binary blob in Rockbox Utility. Of course other ideas are always welcome. We had installation dependencies hardcoded in Rockbox Utility in the past (Rockbox release version) and it was a bad thing (since it required us to make a new release of Rockbox Utility on each new Rockbox release). We should really avoid adding such dependencies, and it looks like mkimxboot is doing something similar (though I have no idea if this involves dualboot decision). - Dominik