2006-01-12 15:47:48 +01:00
|
|
|
/*
|
|
|
|
|
ti1225.c
|
|
|
|
|
|
|
|
|
|
Created: Dec 2005 by Philip Homburg
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#include "../drivers.h"
|
|
|
|
|
#include <ibm/pci.h>
|
|
|
|
|
#include <sys/vm.h>
|
2008-11-19 13:26:10 +01:00
|
|
|
#include <sys/vm_i386.h>
|
2006-01-12 15:47:48 +01:00
|
|
|
|
|
|
|
|
#include "ti1225.h"
|
|
|
|
|
#include "i82365.h"
|
|
|
|
|
|
|
|
|
|
/* The use of interrupts is not yet ready for prime time */
|
|
|
|
|
#define USE_INTS 0
|
|
|
|
|
|
|
|
|
|
#define NR_PORTS 2
|
|
|
|
|
|
|
|
|
|
PRIVATE struct port
|
|
|
|
|
{
|
|
|
|
|
unsigned p_flags;
|
|
|
|
|
int p_devind;
|
|
|
|
|
u8_t p_cb_busnr;
|
|
|
|
|
u16_t p_exca_port;
|
|
|
|
|
#if USE_INTS
|
|
|
|
|
int p_irq;
|
|
|
|
|
int p_hook;
|
|
|
|
|
#endif
|
|
|
|
|
char *base_ptr;
|
|
|
|
|
volatile struct csr *csr_ptr;
|
|
|
|
|
|
2008-11-19 13:26:10 +01:00
|
|
|
char buffer[2*I386_PAGE_SIZE];
|
2006-01-12 15:47:48 +01:00
|
|
|
} ports[NR_PORTS];
|
|
|
|
|
|
|
|
|
|
#define PF_PRESENT 1
|
|
|
|
|
|
|
|
|
|
struct pcitab
|
|
|
|
|
{
|
|
|
|
|
u16_t vid;
|
|
|
|
|
u16_t did;
|
|
|
|
|
int checkclass;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
PRIVATE struct pcitab pcitab_ti[]=
|
|
|
|
|
{
|
|
|
|
|
{ 0x104C, 0xAC1C, 0 }, /* TI PCI1225 */
|
|
|
|
|
|
|
|
|
|
{ 0x0000, 0x0000, 0 }
|
|
|
|
|
};
|
|
|
|
|
PRIVATE char *progname;
|
|
|
|
|
PRIVATE int debug;
|
|
|
|
|
|
|
|
|
|
FORWARD _PROTOTYPE( void hw_init, (struct port *pp) );
|
|
|
|
|
FORWARD _PROTOTYPE( void map_regs, (struct port *pp, u32_t base) );
|
|
|
|
|
FORWARD _PROTOTYPE( void do_int, (struct port *pp) );
|
|
|
|
|
FORWARD _PROTOTYPE( u8_t read_exca, (struct port *pp, int socket, int reg) );
|
|
|
|
|
FORWARD _PROTOTYPE( void do_outb, (port_t port, u8_t value) );
|
|
|
|
|
FORWARD _PROTOTYPE( u8_t do_inb, (port_t port) );
|
|
|
|
|
|
Basic System Event Framework (SEF) with ping and live update.
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.
2009-12-21 15:12:21 +01:00
|
|
|
/* SEF functions and variables. */
|
|
|
|
|
FORWARD _PROTOTYPE( void sef_local_startup, (void) );
|
Initialization protocol for system services.
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.
2010-01-08 02:20:42 +01:00
|
|
|
FORWARD _PROTOTYPE( int sef_cb_init_fresh, (int type, sef_init_info_t *info) );
|
|
|
|
|
EXTERN int env_argc;
|
|
|
|
|
EXTERN char **env_argv;
|
Basic System Event Framework (SEF) with ping and live update.
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.
2009-12-21 15:12:21 +01:00
|
|
|
|
Initialization protocol for system services.
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.
2010-01-08 02:20:42 +01:00
|
|
|
/*===========================================================================*
|
|
|
|
|
* main *
|
|
|
|
|
*===========================================================================*/
|
2006-01-12 15:47:48 +01:00
|
|
|
int main(int argc, char *argv[])
|
|
|
|
|
{
|
Initialization protocol for system services.
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.
2010-01-08 02:20:42 +01:00
|
|
|
int r;
|
2006-01-12 15:47:48 +01:00
|
|
|
message m;
|
|
|
|
|
|
Basic System Event Framework (SEF) with ping and live update.
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.
2009-12-21 15:12:21 +01:00
|
|
|
/* SEF local startup. */
|
Initialization protocol for system services.
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.
2010-01-08 02:20:42 +01:00
|
|
|
env_setargs(argc, argv);
|
Basic System Event Framework (SEF) with ping and live update.
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.
2009-12-21 15:12:21 +01:00
|
|
|
sef_local_startup();
|
|
|
|
|
|
2006-01-12 15:47:48 +01:00
|
|
|
for (;;)
|
|
|
|
|
{
|
Basic System Event Framework (SEF) with ping and live update.
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.
2009-12-21 15:12:21 +01:00
|
|
|
r= sef_receive(ANY, &m);
|
2006-01-12 15:47:48 +01:00
|
|
|
if (r != OK)
|
Basic System Event Framework (SEF) with ping and live update.
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.
2009-12-21 15:12:21 +01:00
|
|
|
panic("ti1225", "sef_receive failed", r);
|
2006-01-12 15:47:48 +01:00
|
|
|
printf("ti1225: got message %u from %d\n",
|
|
|
|
|
m.m_type, m.m_source);
|
|
|
|
|
}
|
|
|
|
|
return 0;
|
|
|
|
|
}
|
|
|
|
|
|
Basic System Event Framework (SEF) with ping and live update.
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.
2009-12-21 15:12:21 +01:00
|
|
|
/*===========================================================================*
|
|
|
|
|
* sef_local_startup *
|
|
|
|
|
*===========================================================================*/
|
|
|
|
|
PRIVATE void sef_local_startup()
|
|
|
|
|
{
|
Initialization protocol for system services.
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.
2010-01-08 02:20:42 +01:00
|
|
|
/* Register init callbacks. */
|
|
|
|
|
sef_setcb_init_fresh(sef_cb_init_fresh);
|
|
|
|
|
sef_setcb_init_lu(sef_cb_init_fresh);
|
|
|
|
|
sef_setcb_init_restart(sef_cb_init_fresh);
|
|
|
|
|
|
Basic System Event Framework (SEF) with ping and live update.
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.
2009-12-21 15:12:21 +01:00
|
|
|
/* Register live update callbacks. */
|
|
|
|
|
sef_setcb_lu_prepare(sef_cb_lu_prepare_always_ready);
|
|
|
|
|
sef_setcb_lu_state_isvalid(sef_cb_lu_state_isvalid_standard);
|
|
|
|
|
|
|
|
|
|
/* Let SEF perform startup. */
|
|
|
|
|
sef_startup();
|
|
|
|
|
}
|
|
|
|
|
|
Initialization protocol for system services.
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.
2010-01-08 02:20:42 +01:00
|
|
|
/*===========================================================================*
|
|
|
|
|
* sef_cb_init_fresh *
|
|
|
|
|
*===========================================================================*/
|
|
|
|
|
PRIVATE int sef_cb_init_fresh(int type, sef_init_info_t *info)
|
2006-01-12 15:47:48 +01:00
|
|
|
{
|
Initialization protocol for system services.
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.
2010-01-08 02:20:42 +01:00
|
|
|
/* Initialize the ti1225 driver. */
|
|
|
|
|
int c, i, r, first, devind, port;
|
2006-01-12 15:47:48 +01:00
|
|
|
u16_t vid, did;
|
|
|
|
|
|
Initialization protocol for system services.
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.
2010-01-08 02:20:42 +01:00
|
|
|
(progname=strrchr(env_argv[0],'/')) ? progname++
|
|
|
|
|
: (progname=env_argv[0]);
|
|
|
|
|
|
2010-01-14 16:24:16 +01:00
|
|
|
if((r=tsc_calibrate()) != OK)
|
|
|
|
|
panic("ti1225", "tsc_calibrate failed", r);
|
Initialization protocol for system services.
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.
2010-01-08 02:20:42 +01:00
|
|
|
|
|
|
|
|
debug= 0;
|
|
|
|
|
while (c= getopt(env_argc, env_argv, "d?"), c != -1)
|
|
|
|
|
{
|
|
|
|
|
switch(c)
|
|
|
|
|
{
|
|
|
|
|
case '?': panic("ti1225", "Usage: ti1225 [-d]", NO_NUM);
|
|
|
|
|
case 'd': debug++; break;
|
|
|
|
|
default: panic("ti1225", "getopt failed", NO_NUM);
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2006-01-12 15:47:48 +01:00
|
|
|
pci_init1(progname);
|
|
|
|
|
|
|
|
|
|
first= 1;
|
|
|
|
|
port= 0;
|
|
|
|
|
for (;;)
|
|
|
|
|
{
|
|
|
|
|
if (first)
|
|
|
|
|
{
|
|
|
|
|
first= 0;
|
|
|
|
|
r= pci_first_dev(&devind, &vid, &did);
|
|
|
|
|
}
|
|
|
|
|
else
|
|
|
|
|
r= pci_next_dev(&devind, &vid, &did);
|
|
|
|
|
if (r != 1)
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
for (i= 0; pcitab_ti[i].vid != 0; i++)
|
|
|
|
|
{
|
|
|
|
|
if (pcitab_ti[i].vid != vid)
|
|
|
|
|
continue;
|
|
|
|
|
if (pcitab_ti[i].did != did)
|
|
|
|
|
continue;
|
|
|
|
|
if (pcitab_ti[i].checkclass)
|
|
|
|
|
{
|
|
|
|
|
panic("ti1225",
|
|
|
|
|
"fxp_probe: class check not implemented",
|
|
|
|
|
NO_NUM);
|
|
|
|
|
}
|
|
|
|
|
break;
|
|
|
|
|
}
|
|
|
|
|
if (pcitab_ti[i].vid == 0)
|
|
|
|
|
continue;
|
|
|
|
|
|
|
|
|
|
pci_reserve(devind);
|
|
|
|
|
|
|
|
|
|
if (debug)
|
|
|
|
|
printf("ti1225: found device %04x/%04x\n", vid, did);
|
|
|
|
|
ports[port].p_devind= devind;
|
|
|
|
|
ports[port].p_flags |= PF_PRESENT;
|
|
|
|
|
port++;
|
|
|
|
|
if (port >= NR_PORTS)
|
|
|
|
|
break;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
for (i= 0; i<NR_PORTS; i++)
|
|
|
|
|
{
|
|
|
|
|
if (!(ports[i].p_flags & PF_PRESENT))
|
|
|
|
|
continue;
|
|
|
|
|
hw_init(&ports[i]);
|
|
|
|
|
}
|
Initialization protocol for system services.
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.
2010-01-08 02:20:42 +01:00
|
|
|
|
|
|
|
|
return(OK);
|
2006-01-12 15:47:48 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
PRIVATE void hw_init(pp)
|
|
|
|
|
struct port *pp;
|
|
|
|
|
{
|
|
|
|
|
int i, r, devind, irq, socket;
|
|
|
|
|
u8_t v8;
|
|
|
|
|
u16_t v16;
|
|
|
|
|
u32_t v32;
|
|
|
|
|
|
|
|
|
|
devind= pp->p_devind;
|
|
|
|
|
if (debug)
|
|
|
|
|
printf("hw_init: devind = %d\n", devind);
|
|
|
|
|
|
|
|
|
|
if (debug)
|
|
|
|
|
{
|
|
|
|
|
v16= pci_attr_r16(devind, PCI_CR);
|
|
|
|
|
printf("ti1225: command register 0x%x\n", v16);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
v32= pci_attr_r32(devind, TI_CB_BASEADDR);
|
|
|
|
|
if (debug)
|
|
|
|
|
printf("ti1225: Cardbus/ExCA base address 0x%x\n", v32);
|
|
|
|
|
map_regs(pp, v32);
|
|
|
|
|
pp->csr_ptr= (struct csr *)pp->base_ptr;
|
|
|
|
|
|
|
|
|
|
if (debug)
|
|
|
|
|
{
|
|
|
|
|
v8= pci_attr_r8(devind, TI_PCI_BUS_NR);
|
|
|
|
|
printf("ti1225: PCI bus number %d\n", v8);
|
|
|
|
|
}
|
|
|
|
|
v8= pci_attr_r8(devind, TI_CB_BUS_NR);
|
|
|
|
|
pp->p_cb_busnr= v8;
|
|
|
|
|
if (debug)
|
|
|
|
|
{
|
|
|
|
|
printf("ti1225: CardBus bus number %d\n", v8);
|
|
|
|
|
v8= pci_attr_r8(devind, TI_SO_BUS_NR);
|
|
|
|
|
printf("ti1225: Subordinate bus number %d\n", v8);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
#if USE_INTS
|
|
|
|
|
irq= pci_attr_r8(devind, PCI_ILR);
|
|
|
|
|
pp->p_irq= irq;
|
|
|
|
|
printf("ti1225 using IRQ %d\n", irq);
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
v32= pci_attr_r32(devind, TI_LEGACY_BA);
|
|
|
|
|
v32 &= ~1;
|
|
|
|
|
if (debug)
|
|
|
|
|
{
|
|
|
|
|
printf("ti1225: PC Card 16-bit legacy-mode base address 0x%x\n",
|
|
|
|
|
v32);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
if (v32 == 0)
|
|
|
|
|
panic("ti1225", "bad lagacy-mode base address 0x%x\n", v32);
|
|
|
|
|
pp->p_exca_port= v32;
|
|
|
|
|
|
|
|
|
|
if (debug)
|
|
|
|
|
{
|
|
|
|
|
v32= pci_attr_r32(devind, TI_MF_ROUTE);
|
|
|
|
|
printf("ti1225: Multifunction routing 0x%08x\n", v32);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
#if USE_INTS
|
|
|
|
|
pp->p_hook = pp->p_irq;
|
|
|
|
|
r= sys_irqsetpolicy(pp->p_irq, 0, &pp->p_hook);
|
|
|
|
|
if (r != OK)
|
|
|
|
|
panic("ti1225","sys_irqsetpolicy failed", r);
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
/* Clear CBB_BC_INTEXCA */
|
|
|
|
|
v16= pci_attr_r16(devind, CBB_BRIDGECTRL);
|
|
|
|
|
if (debug)
|
|
|
|
|
printf("ti1225: Bridge control 0x%04x\n", v16);
|
|
|
|
|
v16 &= ~CBB_BC_INTEXCA;
|
|
|
|
|
pci_attr_w16(devind, CBB_BRIDGECTRL, v16);
|
|
|
|
|
|
|
|
|
|
if (debug)
|
|
|
|
|
{
|
|
|
|
|
v32= pci_attr_r32(devind, TI_SYSCTRL);
|
|
|
|
|
printf("ti1225: System Control Register 0x%08x\n", v32);
|
|
|
|
|
|
|
|
|
|
v8= pci_attr_r8(devind, TI_CARD_CTRL);
|
|
|
|
|
printf("ti1225: Card Control 0x%02x\n", v8);
|
|
|
|
|
|
|
|
|
|
v8= pci_attr_r8(devind, TI_DEV_CTRL);
|
|
|
|
|
printf("ti1225: Device Control 0x%02x\n", v8);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* Enable socket interrupts */
|
|
|
|
|
pp->csr_ptr->csr_mask |= CM_PWRMASK | CM_CDMASK | CM_CSTSMASK;
|
|
|
|
|
|
|
|
|
|
do_int(pp);
|
|
|
|
|
|
|
|
|
|
#if USE_INTS
|
|
|
|
|
r= sys_irqenable(&pp->p_hook);
|
|
|
|
|
if (r != OK)
|
|
|
|
|
panic("ti1225","unable enable interrupts", r);
|
|
|
|
|
#endif
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
PRIVATE void map_regs(pp, base)
|
|
|
|
|
struct port *pp;
|
|
|
|
|
u32_t base;
|
|
|
|
|
{
|
|
|
|
|
int r;
|
|
|
|
|
vir_bytes buf_base;
|
|
|
|
|
|
|
|
|
|
buf_base= (vir_bytes)pp->buffer;
|
2008-11-19 13:26:10 +01:00
|
|
|
if (buf_base % I386_PAGE_SIZE)
|
|
|
|
|
buf_base += I386_PAGE_SIZE-(buf_base % I386_PAGE_SIZE);
|
2006-01-12 15:47:48 +01:00
|
|
|
pp->base_ptr= (char *)buf_base;
|
|
|
|
|
if (debug)
|
|
|
|
|
{
|
|
|
|
|
printf("ti1225: map_regs: using %p for %p\n",
|
|
|
|
|
pp->base_ptr, pp->buffer);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* Clear low order bits in base */
|
|
|
|
|
base &= ~(u32_t)0xF;
|
|
|
|
|
|
2008-11-19 13:26:10 +01:00
|
|
|
#if 0
|
2006-01-12 15:47:48 +01:00
|
|
|
r= sys_vm_map(SELF, 1 /* map */, (vir_bytes)pp->base_ptr,
|
2008-11-19 13:26:10 +01:00
|
|
|
I386_PAGE_SIZE, (phys_bytes)base);
|
|
|
|
|
#else
|
|
|
|
|
r = ENOSYS;
|
|
|
|
|
#endif
|
2006-01-12 15:47:48 +01:00
|
|
|
if (r != OK)
|
|
|
|
|
panic("ti1225", "map_regs: sys_vm_map failed", r);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
PRIVATE void do_int(pp)
|
|
|
|
|
struct port *pp;
|
|
|
|
|
{
|
|
|
|
|
int i, r, devind, vcc_5v, vcc_3v, vcc_Xv, vcc_Yv,
|
|
|
|
|
socket_5v, socket_3v, socket_Xv, socket_Yv;
|
|
|
|
|
clock_t t0, t1;
|
|
|
|
|
u32_t csr_event, csr_present, csr_control;
|
|
|
|
|
u8_t v8;
|
|
|
|
|
u16_t v16;
|
|
|
|
|
|
|
|
|
|
devind= pp->p_devind;
|
|
|
|
|
v8= pci_attr_r8(devind, TI_CARD_CTRL);
|
|
|
|
|
if (v8 & TI_CCR_IFG)
|
|
|
|
|
{
|
2008-02-21 17:09:58 +01:00
|
|
|
printf("ti1225: got functional interrupt\n");
|
2006-01-12 15:47:48 +01:00
|
|
|
pci_attr_w8(devind, TI_CARD_CTRL, v8);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
if (debug)
|
|
|
|
|
{
|
|
|
|
|
printf("Socket event: 0x%x\n", pp->csr_ptr->csr_event);
|
|
|
|
|
printf("Socket mask: 0x%x\n", pp->csr_ptr->csr_mask);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
csr_present= pp->csr_ptr->csr_present;
|
|
|
|
|
csr_control= pp->csr_ptr->csr_control;
|
|
|
|
|
|
|
|
|
|
if ((csr_present & (CP_CDETECT1|CP_CDETECT2)) != 0)
|
|
|
|
|
{
|
|
|
|
|
if (debug)
|
|
|
|
|
printf("do_int: no card present\n");
|
|
|
|
|
return;
|
|
|
|
|
}
|
|
|
|
|
if (csr_present & CP_BADVCCREQ)
|
|
|
|
|
{
|
|
|
|
|
printf("do_int: Bad Vcc request\n");
|
|
|
|
|
/* return; */
|
|
|
|
|
}
|
|
|
|
|
if (csr_present & CP_DATALOST)
|
|
|
|
|
{
|
|
|
|
|
/* Do we care? */
|
|
|
|
|
if (debug)
|
|
|
|
|
printf("do_int: Data lost\n");
|
|
|
|
|
/* return; */
|
|
|
|
|
}
|
|
|
|
|
if (csr_present & CP_NOTACARD)
|
|
|
|
|
{
|
|
|
|
|
printf("do_int: Not a card\n");
|
|
|
|
|
return;
|
|
|
|
|
}
|
|
|
|
|
if (debug)
|
|
|
|
|
{
|
|
|
|
|
if (csr_present & CP_CBCARD)
|
|
|
|
|
printf("do_int: Cardbus card detected\n");
|
|
|
|
|
if (csr_present & CP_16BITCARD)
|
|
|
|
|
printf("do_int: 16-bit card detected\n");
|
|
|
|
|
}
|
|
|
|
|
if (csr_present & CP_PWRCYCLE)
|
|
|
|
|
{
|
|
|
|
|
if (debug)
|
|
|
|
|
printf("do_int: powered up\n");
|
|
|
|
|
return;
|
|
|
|
|
}
|
|
|
|
|
vcc_5v= !!(csr_present & CP_5VCARD);
|
|
|
|
|
vcc_3v= !!(csr_present & CP_3VCARD);
|
|
|
|
|
vcc_Xv= !!(csr_present & CP_XVCARD);
|
|
|
|
|
vcc_Yv= !!(csr_present & CP_YVCARD);
|
|
|
|
|
if (debug)
|
|
|
|
|
{
|
|
|
|
|
printf("do_int: card supports:%s%s%s%s\n",
|
|
|
|
|
vcc_5v ? " 5V" : "", vcc_3v ? " 3V" : "",
|
|
|
|
|
vcc_Xv ? " X.X V" : "", vcc_Yv ? " Y.Y V" : "");
|
|
|
|
|
}
|
|
|
|
|
socket_5v= !!(csr_present & CP_5VSOCKET);
|
|
|
|
|
socket_3v= !!(csr_present & CP_3VSOCKET);
|
|
|
|
|
socket_Xv= !!(csr_present & CP_XVSOCKET);
|
|
|
|
|
socket_Yv= !!(csr_present & CP_YVSOCKET);
|
|
|
|
|
if (debug)
|
|
|
|
|
{
|
|
|
|
|
printf("do_int: socket supports:%s%s%s%s\n",
|
|
|
|
|
socket_5v ? " 5V" : "", socket_3v ? " 3V" : "",
|
|
|
|
|
socket_Xv ? " X.X V" : "", socket_Yv ? " Y.Y V" : "");
|
|
|
|
|
}
|
|
|
|
|
if (vcc_5v && socket_5v)
|
|
|
|
|
{
|
|
|
|
|
csr_control= (csr_control & ~CC_VCCCTRL) | CC_VCC_5V;
|
|
|
|
|
pp->csr_ptr->csr_control= csr_control;
|
|
|
|
|
if (debug)
|
|
|
|
|
printf("do_int: applying 5V\n");
|
|
|
|
|
}
|
|
|
|
|
else if (vcc_3v && socket_3v)
|
|
|
|
|
{
|
|
|
|
|
csr_control= (csr_control & ~CC_VCCCTRL) | CC_VCC_3V;
|
|
|
|
|
pp->csr_ptr->csr_control= csr_control;
|
|
|
|
|
if (debug)
|
|
|
|
|
printf("do_int: applying 3V\n");
|
|
|
|
|
}
|
|
|
|
|
else if (vcc_Xv && socket_Xv)
|
|
|
|
|
{
|
|
|
|
|
csr_control= (csr_control & ~CC_VCCCTRL) | CC_VCC_XV;
|
|
|
|
|
pp->csr_ptr->csr_control= csr_control;
|
|
|
|
|
printf("do_int: applying X.X V\n");
|
|
|
|
|
}
|
|
|
|
|
else if (vcc_Yv && socket_Yv)
|
|
|
|
|
{
|
|
|
|
|
csr_control= (csr_control & ~CC_VCCCTRL) | CC_VCC_YV;
|
|
|
|
|
pp->csr_ptr->csr_control= csr_control;
|
|
|
|
|
printf("do_int: applying Y.Y V\n");
|
|
|
|
|
}
|
|
|
|
|
else
|
|
|
|
|
{
|
|
|
|
|
printf("do_int: socket and card are not compatible\n");
|
|
|
|
|
return;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
csr_event= pp->csr_ptr->csr_event;
|
|
|
|
|
if (csr_event)
|
|
|
|
|
{
|
|
|
|
|
if (debug)
|
|
|
|
|
printf("clearing socket event\n");
|
|
|
|
|
pp->csr_ptr->csr_event= csr_event;
|
|
|
|
|
if (debug)
|
|
|
|
|
{
|
|
|
|
|
printf("Socket event (cleared): 0x%x\n",
|
|
|
|
|
pp->csr_ptr->csr_event);
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
devind= pp->p_devind;
|
|
|
|
|
v8= pci_attr_r8(devind, TI_CARD_CTRL);
|
|
|
|
|
if (v8 & TI_CCR_IFG)
|
|
|
|
|
{
|
|
|
|
|
printf("ti1225: got functional interrupt\n", v8);
|
|
|
|
|
pci_attr_w8(devind, TI_CARD_CTRL, v8);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
if (debug)
|
|
|
|
|
{
|
|
|
|
|
v8= pci_attr_r8(devind, TI_CARD_CTRL);
|
|
|
|
|
printf("TI_CARD_CTRL: 0x%02x\n", v8);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
getuptime(&t0);
|
|
|
|
|
do {
|
|
|
|
|
csr_present= pp->csr_ptr->csr_present;
|
|
|
|
|
if (csr_present & CP_PWRCYCLE)
|
|
|
|
|
break;
|
2008-11-19 13:26:10 +01:00
|
|
|
} while (getuptime(&t1)==OK && (t1-t0) < micros_to_ticks(100000));
|
2006-01-12 15:47:48 +01:00
|
|
|
|
|
|
|
|
if (!(csr_present & CP_PWRCYCLE))
|
|
|
|
|
{
|
|
|
|
|
printf("do_int: not powered up?\n");
|
|
|
|
|
return;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* Reset device */
|
|
|
|
|
v16= pci_attr_r16(devind, CBB_BRIDGECTRL);
|
|
|
|
|
v16 |= CBB_BC_CRST;
|
|
|
|
|
pci_attr_w16(devind, CBB_BRIDGECTRL, v16);
|
|
|
|
|
|
|
|
|
|
/* Wait one microsecond. Is this correct? What are the specs? */
|
|
|
|
|
micro_delay(1);
|
|
|
|
|
|
|
|
|
|
/* Clear CBB_BC_CRST */
|
|
|
|
|
v16= pci_attr_r16(devind, CBB_BRIDGECTRL);
|
|
|
|
|
v16 &= ~CBB_BC_CRST;
|
|
|
|
|
pci_attr_w16(devind, CBB_BRIDGECTRL, v16);
|
|
|
|
|
|
|
|
|
|
/* Wait one microsecond after clearing the reset line. Is this
|
|
|
|
|
* correct? What are the specs?
|
|
|
|
|
*/
|
|
|
|
|
micro_delay(1);
|
|
|
|
|
|
|
|
|
|
pci_rescan_bus(pp->p_cb_busnr);
|
|
|
|
|
|
|
|
|
|
#if USE_INTS
|
|
|
|
|
r= sys_irqenable(&pp->p_hook);
|
|
|
|
|
if (r != OK)
|
|
|
|
|
panic("ti1225","unable enable interrupts", r);
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
PRIVATE u8_t read_exca(pp, socket, reg)
|
|
|
|
|
struct port *pp;
|
|
|
|
|
int socket;
|
|
|
|
|
int reg;
|
|
|
|
|
{
|
|
|
|
|
u16_t port;
|
|
|
|
|
|
|
|
|
|
port= pp->p_exca_port;
|
|
|
|
|
if (port == 0)
|
|
|
|
|
panic("ti1225", "read_exca: bad port", NO_NUM);
|
|
|
|
|
do_outb(port, socket * 0x40 + reg);
|
|
|
|
|
return do_inb(port+1);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
PRIVATE u8_t do_inb(port_t port)
|
|
|
|
|
{
|
|
|
|
|
int r;
|
|
|
|
|
u32_t value;
|
|
|
|
|
|
|
|
|
|
r= sys_inb(port, &value);
|
|
|
|
|
if (r != OK)
|
|
|
|
|
panic("ti1225","sys_inb failed", r);
|
|
|
|
|
return value;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
PRIVATE void do_outb(port_t port, u8_t value)
|
|
|
|
|
{
|
|
|
|
|
int r;
|
|
|
|
|
|
|
|
|
|
r= sys_outb(port, value);
|
|
|
|
|
if (r != OK)
|
|
|
|
|
panic("ti1225","sys_outb failed", r);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
