Hello,
I'm programming and will turn my kernel in a real-time fashion, so I have a question for you, which features do you want in a RTOS?
Imagine that everything can be done, just dream, what do you want to achieve with a RTOS?
The real-time OS of your dreams
The real-time OS of your dreams
OS for PowerPC Macs: https://github.com/narke/Einherjar
Operating system: colorForth computing environment for x86.: https://github.com/narke/Roentgenium
Operating system: colorForth computing environment for x86.: https://github.com/narke/Roentgenium
Re: The real-time OS of your dreams
Not much - RTOSes are generally for quite specific purposes (real-time data flow or hard/soft latency constraints).
I have none of those in my generally working environment, although I would like the OS on the microcontroller in my ABS braking system to respond in time!
I have none of those in my generally working environment, although I would like the OS on the microcontroller in my ABS braking system to respond in time!
-
Combuster
- Member
- Posts: 9301
- Joined: Wed Oct 18, 2006 3:45 am
- Libera.chat IRC: [com]buster
- Location: On the balcony, where I can actually keep 1½m distance
- Contact:
Re: The real-time OS of your dreams
While you can write a generic RTOS kernel, you can't simply write an entire OS. The things you will want eventually are very much tailored to the application at hand.
That question as-is begs the query to modify the linux kernel so that you can prove upper bounds on usage and latency for all system calls and userspace signals, as well as making guarantees about time allocation. Then you can go blame BIOS developers for making it impossible.
That question as-is begs the query to modify the linux kernel so that you can prove upper bounds on usage and latency for all system calls and userspace signals, as well as making guarantees about time allocation. Then you can go blame BIOS developers for making it impossible.