Please do a combined build of testing protocols

CX-10 Blue is already in nightly builds.
For the other protocols, drop a message in the corresponding threads if you've tested them successfully, this may speed up the pull requests

Oh right, I'm still on 2014 Q1 (gcc 4.8.3) and I can still build for 7e.

I'm about to create a pull request for EAchine H7, MT9912, MT9916.

Wow, we're really on the limits with the 7e, even with an older toolchain.

I merged my MT99xx branch with latest default, then if I name my new protocol "MT99" in protocol.h, I can build for 7e, but if I add only 1 character to this name then it doesn't build anymore because it doesn't fit in ROM !

... and my build doesn't have the Bayang protocol

I want that someone test the M9916 before creating the request, but you can merge this branch if you want to make a test build:
bitbucket.org/goebish/deviationtx/branch/EAchine_H7

I'll also take care of updating the manual.

More protocols may need to wait until after the 4.1 release. In my side branch, I have ripped out the ini handler for the 7e builds, and it will probably give us between 4k and 8k to play with. The downside is that you need to do ini conversion on the PC, and since we'll be storing the files as a dump of the structure, you need to read them off, convert them to a new format and re-upload them every time you change the firmware. the Deviation-Uploader will make this transparent (you will still interact with ini files, and won't have additional steps for upgrading), but (a) it is more error prone (a bad write will corrupt your model irrevocably), (b) it is very hard to debug, and (c) it takes a lot longer to install a new firmware. Anyhow, that is all coming after 4.1 is released. For 4.1 it is likely we'll just need to squeeze a little. The code has already been squeezed many times, and I'm running out of fat to trim (it took me 5 minutes to find 4 bytes to remove for the last change).

Note this is not a thread to discuss the merits of my decision to remove ini handling, and I'll probably delete any complaints I see about it here (go start a new thread if you have something constructive to say). I am just giving an update on what can be done about additional protocols short term (not very much).

Alternatively, if we want to wait a bit more for 4.1, it is likely possible to deal with protocols like we do icons, and not hard-code the list into Deviation. Then adding protocols will not change Deviation's size. The downside is that the module code is really hairy, and such an invasive change would likely take a while to debug and get working reliably.

I just did a commit that should free up about 240 bytes just by aligning some structs properly. It may give you enough room to add new protocols.

Awesome, thanks

SeByDocKy can you try the MT99 test build with M9916 so I can create a pull request please ?