It only can run after that thread completes (and then waits to
get rescheduled at a later time.
I know. That's how my threaded app works.
So I don't understand why you bother about "real" threads at all. some
50 Lines of C code will "schedule" your "threads" one after the other as
part of a single application/process, all running on the same stack,
without Linux interfering at all. (That is what my PicoOS does.) You
only need Linux's help with the interrupts. Here you need to write
device drivers (or use UIO which I don't know anything at all about),
which set some bits (e.g. in a memory region the user process accesses
via an mmaped file. An example for this is in the NIOSWiki).
-Michael
_______________________________________________
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
