This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
RE: How to debug synchronisation in the usbs.c in a new usb-driver for the ARM at91sam7s...
- From: "Robert Bryce" <rob at mobilia-os dot com>
- To: "'Nick Garnett'" <nickg at ecoscentric dot com>
- Cc: <ecos-discuss at ecos dot sourceware dot org>
- Date: Tue, 21 Feb 2006 10:57:07 -0800
- Subject: RE: [ECOS] How to debug synchronisation in the usbs.c in a new usb-driver for the ARM at91sam7s...
Hi Nick,
> If I had my way, mutexes and condition variables would be the only
> synchronization primitives available in the OS.
Hm. I will agree that one set of primitives is all that an OS needs to
provide. Keeps the model simpler. I'm really indifferent on which set,
though I do prefer semaphores. In the end, it's just not a big deal.
> In general, the OS on its own is not real time, only an entire system,
> OS+application, can be described as real time. [...]
> A real time OS cannot make non-real time code become real time.
Yes! Conversely, though, an (otherwise) real-time app isn't without a
real-time OS.
I did some work with hierarchical scheduling that could support both
real-time and non-real-time app's simultaneously - concerns are similar to
your example (IP stack) - inter-process dependencies. There's been some
interesting work in hybrid schedulers too.
Thanks for the discussions. Interesting.
--Rob
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss