AW: AW: [En-Nut-Discussion] Ethernut Docu Improvements

[Oliver Schulz]

Hi Ralph,

I had a look to your code yesterday evening and started to implement your features to Nut/OS. 

In my opinion it is a smarter way to add exactly one message queue to each thread (directly in NUTTHREADINFO). So every thread has its own message queue and there is no need to define some global message queues.
In my first implementation the memory for the message queue is allocated just in time. Means, if a thread doesn't use the message queue, only the space for one pointer (2bytes) is wasted.

Today I got your new versions of the files. These message timers are also very interessing, but on the first look, it seems that your implementation is very complicated.

But anyway, after the next official release of Nut/OS 3.4 (which must come today, I think), I would like to work with you together about this topic. This weekend I commit my files into CVS and we can discuss about it... 

Cheers,
Oliver.



> -----Ursprüngliche Nachricht-----
> Von: en-nut-discussion-bounces at egnite.de
> [mailto:en-nut-discussion-bounces at egnite.de]Im Auftrag von Ralph Mason
> Gesendet: Freitag, 30. Januar 2004 08:30
> An: Ethernut User Chat (English)
> Betreff: Re: AW: [En-Nut-Discussion] Ethernut Docu Improvements
> 
> 
> Oliver Schulz wrote:
> 
> >>a simple question: does anybody need or did implement 
> messsage queues
> >>or message passing?
> >>    
> >>
> >Very interessing topic. I also thought about it and in 
> release 3.5 of Nut/OS I'll try to add some code for simple 
> message passing (like in win32) and message queueing.
> >  
> >
> I did this a few months back, I think I posted it already.  
> It works well, excellent for simulating a wait on multiple 
> events (Each event has a thread waiting that posts a message 
> to the que with a main thread waiting)
> 
> Tried and tested (and approved?)
> 
> Regards
> Ralph
> 
>