[En-Nut-Discussion] NutHeapRealloc

[Ole Reinhardt]

Hi Morty,

> Hmm looks like this wasn't such a smart idea because enter & switch 
> frame are Arch dependent. Maybe I did it the wrong way round: Keep 
> NutThreadCreate in arch and add a NutThreadTdInit to the os/thread.c.

Perhaps I've missed a part of this thread. What do you exactly plan? I
have implemented a private memory possebility for every thread by simply
adding a new pointer to the thread structure. This way you can assign /
query any chunk of memory / variable you like to this thread. I just did
not check this code in. So did we plan the same?

I would not move NutThreadCreate anywhere else than into the arch
directory. All these thread specific funktions are highly architecture
specific and therefore should not be moved away. Addind new functions
that will be calles instead from a global NutThreadCreate function would
only add extra jumps and code size and does not make things cleaner.

Could you perhaps explain me in a few short headlines what you plan to
do? (Perhaps you simply write me a private mail in german)

Regards,

Ole Reinhardt

-- 
 _____________________________________________________________
|                                                             |
| Embedded-IT          Hard- und Softwarelösungen             |
|                                                             |
| Ole Reinhardt        Tel. / Fax:        +49 (0)271  7420433 |
| Luisenstraße 29      Mobil:             +49 (0)177  7420433 |
| 57076 Siegen         eMail:    ole.reinhardt at embedded-it.de |
| Germany              Web:         http://www.embedded-it.de |
|                      UstID / VAT:       DE198944716         |
|_____________________________________________________________|