[ECOS] Kernel objects and eCos

["Michael Klock" <mklock at omegaband dot com>]

I'm looking at porting a virtual embedded OS API to eCos. It appears that
for eCos the user must allocate the space for some kernel objects
(cyg_thread, cyg_alarm, cyg_mempool_var, etc.) before calling eCos. The user
then never uses the kernel object and it is solely managed by the kernel.
The virtual embedded OS API assumes that the kernel manages the kernel
objects inside the kernel.

My question is: some of the kernel calls (like cyg_thread_create) note that
passing NULL for these kernel objects (in this case cyg_thread) will cause
the kernel to allocate the space themselves (which in my opinion is the way
to do it). But it also says that the "NULL" functionality is not yet
supported. Is anyone working on this "NULL" capability support? For my port,
I need the "NULL" functionality real bad...

Thanks,
Mike.

-------------------------------------------
  Michael Klock, OmegaBand Inc.
  (formerly Seagull Semiconductor)
  9020-I Capital of Texas Hwy N., Suite 270.
  (512)401-8208 x145
-------------------------------------------