[En-Nut-Discussion] Nut/OS Initialization

Ole Reinhardt ole.reinhardt at embedded-it.de
Tue Sep 16 09:36:43 CEST 2008


Hi!

> a function called NutInit() or something ... could do whatever is needed 
> and create a thread to do initializations that take a considerable time, 
> like DHCP or ethernet if a cable is disconected. Such thread could 
> detect at any time when the cable is reconected.
> 
> Such structure could be easely be modified for any specific need, as 
> long as basic structuture like ioctl and appropriate fucntions are 
> available.

I would differentiate between low level hardware initialisation and the
application / network / protocoll specific stuff. 

So a board definition like I suggested in my last mail would only
register the available and needed devices and bring the hardware,
IO-Ports, Interrups, available Memory etc. in a sane state.

Everything else, like Network setup, DHCP request and so on should be
done in your application. 

This approach will allow you to define a singe board definition file
common to all your projects, but you can do different startup tasks for
whatever application you write.

Bye,

Ole

-- 
 _____________________________________________________________
|                                                             |
| 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         |
|_____________________________________________________________|




More information about the En-Nut-Discussion mailing list