[WARNING] Switching the trunk to ChibiOS 3.0

[Giovanni]

Hello,

ChibiOS 3.0 is already good enough for experimental use. I am thinking to switch the trunk to the 3.0 branch in next weeks but there are some points to be considered:

- The current trunk will be renamed to ./trunk_old and frozen, those using the current unstable may switch their checkouts there.

- I know there is already a lot of users using 3.0 so the code must be handled correctly (tickets etc).

- The 3.0 architecture and files organization should be stable already, you may notice that the OS files tree is quite different now. It has been designed to be "multi product", so not just ChibiOS/RT but a series of connected products (RT, NIL and HAL so far).

- The version 3.0 code is good already but not everything has been ported yet: ARM7, AVR, MSP ports. LPC, AVR, MSP, AT91, STM8 HALs. lwIP, FatFS bindings and demos. Simulators. Documentation.
Basically only the STM32 and SPC5 HALs have been ported. Making 3.0 the current version will open the new trunk to the maintainers that could start considering the port of their code to 3.0, I know there is a lot of code waiting.

- The branch 2.6.x will be actively developed/maintained until the final version 3.0 will be ready for release.

- I want to make 3.0 more available because it is filled with new amazing features. It also have subtle differences that need some time to get used to.

I am thinking to an end of March switch, thoughts?

Giovanni

[ErikZalm]

Hello Giovanni,

What are the needed changes for switch ChibiOS 2.6 to 3.0.

[Giovanni]

Several functions have been renamed, some others have an X after the name (a new class). When porting an existing project it is important to take configuration files and Makefiles from the new version.

Then, of course, there are all the enhancements.

Giovanni