What I understand by that is that the remote does.
The Remote does not run Linux, too. (And don't trust nmap *g*)
Kernel used in firmware
- r3tex
- Thread is marked as Resolved.
-
-
I wouldn't worry about it, Timo. I'll bet these guys try to find out what the Secret Sauce is at McDonalds, too.
-
I vote for VxWorks
-
Rise Of The Ancient Thread.
(1) Linux can be real time. rtlinux for example.
(2) Even if the profiler did run linux, this doesn't mean the code that actually does any of the dsp or profiling needs to be open sourced.
(3) Since it doesn't, this point is moot.
(4) Linux previously used a O(n) ATT/BSD style scheduler up until Kernel 2.6, when it was replaced briefly with an O(1) scheduler - It was overhauled in kernel 2.6.23 and replaced with a CFS scheduler. Again, all of this is moot because of (1) and (3).
(5) Neat conversation though. I love kernel land. lol. Nerding out a bit.