1f5841c8ed
SYSLIB CHANGES: - SEF must be used by every system process and is thereby part of the system library. - The framework provides a receive() interface (sef_receive) for system processes to automatically catch known system even messages and process them. - SEF provides a default behavior for each type of system event, but allows system processes to register callbacks to override the default behavior. - Custom (local to the process) or predefined (provided by SEF) callback implementations can be registered to SEF. - SEF currently includes support for 2 types of system events: 1. SEF Ping. The event occurs every time RS sends a ping to figure out whether a system process is still alive. The default callback implementation provided by SEF is to notify RS back to let it know the process is alive and kicking. 2. SEF Live update. The event occurs every time RS sends a prepare to update message to let a system process know an update is available and to prepare for it. The live update support is very basic for now. SEF only deals with verifying if the prepare state can be supported by the process, dumping the state for debugging purposes, and providing an event-driven programming model to the process to react to state changes check-in when ready to update. - SEF should be extended in the future to integrate support for more types of system events. Ideally, all the cross-cutting concerns should be integrated into SEF to avoid duplicating code and ease extensibility. Examples include: * PM notify messages primarily used at shutdown. * SYSTEM notify messages primarily used for signals. * CLOCK notify messages used for system alarms. * Debug messages. IS could still be in charge of fkey handling but would forward the debug message to the target process (e.g. PM, if the user requested debug information about PM). SEF would then catch the message and do nothing unless the process has registered an appropriate callback to deal with the event. This simplifies the programming model to print debug information, avoids duplicating code, and reduces the effort to print debug information. SYSTEM PROCESSES CHANGES: - Every system process registers SEF callbacks it needs to override the default system behavior and calls sef_startup() right after being started. - sef_startup() does almost nothing now, but will be extended in the future to support callbacks of its own to let RS control and synchronize with every system process at initialization time. - Every system process calls sef_receive() now rather than receive() directly, to let SEF handle predefined system events. RS CHANGES: - RS supports a basic single-component live update protocol now, as follows: * When an update command is issued (via "service update *"), RS notifies the target system process to prepare for a specific update state. * If the process doesn't respond back in time, the update is aborted. * When the process responds back, RS kills it and marks it for refreshing. * The process is then automatically restarted as for a buggy process and can start running again. * Live update is currently prototyped as a controlled failure. |
||
|---|---|---|
| .. | ||
| 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$