3 ms·

Coming from professional environment, my only question is: where's FreeRTOS integration?

by kosma 9y ago

samlittlewood 9y ago
I have not used it yet, but maybe: https://github.com/hashmismatch/freertos.rs https://github.com/hashmismatch/freertos.rs ?
TuringTest 9y ago
Offtopic, but does anyone know what's going on with the FreeRTOS license? They add a GPL incompatible restriction to benchmarking, but they also use license GPL v2 "or later", which allows the users to remove such restrictions. Do they have a clue about their licensing model?
- abstractbeliefs 9y ago
  They don't have a clue, no, they're mostly just turbomad about having poor benchmark results published in the past.
  - mcguire 9y ago
    "The FreeRTOS GPL exception text follows: "Any FreeRTOS source code, whether modified or in it's original release form, or whether in whole or in part, can only be distributed by you under the terms of the GNU General Public License plus this exception. An independent module is a module which is not derived from or based on FreeRTOS. "Clause 1: "Linking FreeRTOS with other modules is making a combined work based on FreeRTOS. Thus, the terms and conditions of the GNU General Public License V2 cover the whole combination. "As a special exception, the copyright holders of FreeRTOS give you permission to link FreeRTOS with independent modules to produce a statically linked executable, regardless of the license terms of these independent modules, and to copy and distribute the resulting executable under terms of your choice, provided that you also meet, for each linked independent module, the terms and conditions of the license of that module. An independent module is a module which is not derived from or based on FreeRTOS. "Clause 2: "FreeRTOS may not be used for any competitive or comparative purpose, including the publication of any form of run time or compile time metric, without the express permission of Real Time Engineers Ltd. (this is the norm within the industry and is intended to ensure information accuracy)." Yeah. Nice. Without pondering it too much (& IANAL), clause 1 seems ok, but 2 is going to contradict the GPL. Calling their license "GPL plus exceptions" is probably going to get them yelled at by the FSF.
thenewwazoo 9y ago
I’m currently working in my very limited free time on Rust targeted at the CMSIS RTOS v1 interface. I think that may be as close as is reasonable to expect. The Rust stdlib is pretty agnostic, it just expects certain primitives to be implemented. FreeRTOS is one way to accomplish those primitives amongst many.

Coming from professional environment, my only question is: where's FreeRTOS integration?

by kosma 9y ago

Coming from professional environment, my only question is: where's FreeRTOS integration?

I have not used it yet, but maybe: https://github.com/hashmismatch/freertos.rs https://github.com/hashmismatch/freertos.rs ?

TuringTest 9y ago

Offtopic, but does anyone know what's going on with the FreeRTOS license? They add a GPL incompatible restriction to benchmarking, but they also use license GPL v2 "or later", which allows the users to remove such restrictions. Do they have a clue about their licensing model?

abstractbeliefs 9y ago
They don't have a clue, no, they're mostly just turbomad about having poor benchmark results published in the past.
- mcguire 9y ago
  "The FreeRTOS GPL exception text follows: "Any FreeRTOS source code, whether modified or in it's original release form, or whether in whole or in part, can only be distributed by you under the terms of the GNU General Public License plus this exception. An independent module is a module which is not derived from or based on FreeRTOS. "Clause 1: "Linking FreeRTOS with other modules is making a combined work based on FreeRTOS. Thus, the terms and conditions of the GNU General Public License V2 cover the whole combination. "As a special exception, the copyright holders of FreeRTOS give you permission to link FreeRTOS with independent modules to produce a statically linked executable, regardless of the license terms of these independent modules, and to copy and distribute the resulting executable under terms of your choice, provided that you also meet, for each linked independent module, the terms and conditions of the license of that module. An independent module is a module which is not derived from or based on FreeRTOS. "Clause 2: "FreeRTOS may not be used for any competitive or comparative purpose, including the publication of any form of run time or compile time metric, without the express permission of Real Time Engineers Ltd. (this is the norm within the industry and is intended to ensure information accuracy)." Yeah. Nice. Without pondering it too much (& IANAL), clause 1 seems ok, but 2 is going to contradict the GPL. Calling their license "GPL plus exceptions" is probably going to get them yelled at by the FSF.

thenewwazoo 9y ago

I’m currently working in my very limited free time on Rust targeted at the CMSIS RTOS v1 interface. I think that may be as close as is reasonable to expect. The Rust stdlib is pretty agnostic, it just expects certain primitives to be implemented. FreeRTOS is one way to accomplish those primitives amongst many.