d1fd04e72a
SYSLIB CHANGES: - SEF framework now supports a new SEF Init request type from RS. 3 different callbacks are available (init_fresh, init_lu, init_restart) to specify initialization code when a service starts fresh, starts after a live update, or restarts. SYSTEM SERVICE CHANGES: - Initialization code for system services is now enclosed in a callback SEF will automatically call at init time. The return code of the callback will tell RS whether the initialization completed successfully. - Each init callback can access information passed by RS to initialize. As of now, each system service has access to the public entries of RS's system process table to gather all the information required to initialize. This design eliminates many existing or potential races at boot time and provides a uniform initialization interface to system services. The same interface will be reused for the upcoming publish/subscribe model to handle dynamic registration / deregistration of system services. VM CHANGES: - Uniform privilege management for all system services. Every service uses the same call mask format. For boot services, VM copies the call mask from init data. For dynamic services, VM still receives the call mask via rs_set_priv call that will be soon replaced by the upcoming publish/subscribe model. RS CHANGES: - The system process table has been reorganized and split into private entries and public entries. Only the latter ones are exposed to system services. - VM call masks are now entirely configured in rs/table.c - RS has now its own slot in the system process table. Only kernel tasks and user processes not included in the boot image are now left out from the system process table. - RS implements the initialization protocol for system services. - For services in the boot image, RS blocks till initialization is complete and panics when failure is reported back. Services are initialized in their order of appearance in the boot image priv table and RS blocks to implements synchronous initialization for every system service having the flag SF_SYNCH_BOOT set. - For services started dynamically, the initialization protocol is implemented as though it were the first ping for the service. In this case, if the system service fails to report back (or reports failure), RS brings the service down rather than trying to restart it. |
||
|---|---|---|
| .. | ||
| 3c501.c | ||
| 3c501.h | ||
| 3c503.c | ||
| 3c503.h | ||
| 3c509.c | ||
| 3c509.h | ||
| 8390.c | ||
| 8390.h | ||
| devio.c | ||
| dp.c | ||
| dp.h | ||
| Makefile | ||
| ne.c | ||
| ne.h | ||
| netbuff.c | ||
| README | ||
| wd.c | ||
| wd.h | ||
This is my implementation of a new network task for the Minix kernel. I did it initially to handle a 3c501 board (Etherlink), but those board are so unstable that it is not worth using them except for learning how to implement a driver. When I got a 3c509b board (Etherlink III) it was easier to write the code to handle them. The Minix code in 'dp8390.c' is too specific for the National chip set, so what I did was to remove as much as I needed of the code dependant from the chip and produce a generic task that, I hope, will be able to handle many more cards. $Log$ Revision 1.1 2005/06/29 10:16:46 beng Import of dpeth 3c501/3c509b/.. ethernet driver by Giovanni Falzoni <fgalzoni@inwind.it>. Revision 1.3 2004/04/14 12:49:07 lsodgf0 Changes for porting to Minix 2.0.4 run on BOCHS Revision 1.2 2002/03/25 14:16:09 lsodgf0 The driver for the NEx000 has been rewritten to be operational with the ACCTON 18xx (an NE1000 clone) The I/O routines for 16 bit cards are still untested.. Revision 1.1 2002/02/09 09:35:09 lsodgf0 Initial revision The package is not fully tested, i.e. I had only 3Com boards (3c501, 3c503, 3c503/16 and 3c509b) and WD8003. I got also a NE1000 clone but it was not fully operational and I could not appreciate the results. For this reason the changes done to the interface to I/O for 8 and 16 bits are not tested. $Id$