[ECOS] Thread model and software interrutps

["Samie Hassan Ghauri" <samiehg at hotmail dot com>]

In the eCos code repository, apart from the drivers written for ethernet, 
none is written as a thread. Seeing the driver from the hardware point of 
view, this is understandable that perhaps none require too complex a device 
handling that the driver had to be written as a thread.

1.   However, seeing the driver from application point of view, they only 
exist as function calls (I/O subsystem API). Why is this? Why cant an 
application pass some data to the driver for processing, through these API 
and then the driver would start running as a thread in parallel with the 
thread in the application (i.e. the thread that passed this data) ?

2.  Sometimes in operating systems the applications are interfaced with the 
kernel via software interrupts. eCos does not seem to provide constructs for 
any such implementation. Is it right?


Thanks
Samie

_________________________________________________________________
The new MSN 8: smart spam protection and 2 months FREE*  
http://join.msn.com/?page=features/junkmail


--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss