MAS start/stop

The only persistent application in MAS is the logging daemon, maslog. To unload MAS, you should stop maslog and then unload the MAS driver.

maslog

The only persistent application in MAS is the logging daemon, maslog_server. To see if it is running, run

$ ps -e |grep maslog_server

To bring it down cleanly, use the maslog application with the exit command:

$ maslog stop

To start the server up again, do

$ maslog start

driver

The MAS driver, when loaded, will register itself as "mce_dsp". You can check for its presence in the list of modules:

$ cat /proc/modules |grep mce
mce_dsp 36564 0 - Live 0xf8c1e000

To look at the driver status, type:

$ cat /proc/mce_dsp

and you should see:

   fakemce:  no
   realtime: no
   bigphys:  yes
 data buffer:
   virtual:  0xc1833000
   bus:      0x01833000
   count:          1627
   head:              0
   tail:              0
   drops:             0
   size:         0x1800
   data:         0x1530
   mode:     quiet mode
 mce commander:
   state:    idle
 dsp commander:
   state:    idle
 dsp pci registers:
   hstr:     0x0003
   hctr:     0x0900

To unload the driver, run

$ sudo rmmod mce_dsp

If you get a message "can't remove, the driver is busy", then ???????

To load it again, run

$ sudo modprobe mce_dsp

device files

Once the driver is installed it is necessary to create access points in /dev. This is done with the script mknodes in the driver source directory (this will be made better...)

$ /home/mce/mas/driver/mknodes

These nodes can be removed, if desired, with a normal rm command:

$ sudo rm /dev/mce_*