Re: Implementing a Counting Semaphore for RTOS

Do you have a question? Post it now! No Registration Necessary

Translate This Thread From English to

Threaded View
[F'up2 cut down --- neglected by OP]


Quoted text here. Click to load it

If you must ask, I'm afraid you're out of your depth.  So is your
client.  

If somebody believes they should be making their own proprietary RTOS,
yet feels the need to refer to outside expertise to implement such a
fundamental feature of an RTOS instead of doing it themselves, *and*
that outside expert doesn't have enough expertise on the subject to
trust his own judgement more than a random Usenet poll, those are at
least two strong signs of serious trouble in project management.

More bluntly put: if that thing doesn't already have fully functional
semaphores, it's probably not worth being called an RTOS to begin
with.  And if they need outside help to do it, they shouldn't be
trying to make their own RTOS.

Quoted text here. Click to load it

That IMHO has nothing to do with the implementation of the semaphore.
That only concerns how the RTOS *uses* the semaphore.  A semaphore can
be used by a scheduler --- it's not a scheduler in and of itself.

This looks like you're being asked to write the entire RTOS for them,
not just the semaphore.

Quoted text here. Click to load it
[...]

Impossible to tell from what little detail you gave.

Quoted text here. Click to load it

Which "this" group are you asking that about?  You posted to three.

--
Hans-Bernhard Broeker ( snipped-for-privacy@physik.rwth-aachen.de)
Even if all the snow were burnt, ashes would remain.

Re: Implementing a Counting Semaphore for RTOS
Op Sat, 31 Dec 2005 13:30:01 +0100 schreef Morten Reistad  

Quoted text here. Click to load it



Dijkstra, with a K please.  (No, not related ;)


--
Gemaakt met Opera's revolutionaire e-mailprogramma:  
http://www.opera.com/mail /

Site Timeline