11 Dec
2003
11 Dec
'03
5:02 a.m.
On Tue, Dec 09, 2003 at 01:05:51PM -0600, Jack O'Quin wrote:
Fernando Pablo Lopez-Lezcano
<nando(a)ccrma.stanford.edu> writes:
These are valid concerns. It's not hard to detect that the module is
loaded, `lsmod | grep realtime' works.
But, I don't know how to query the module parameters, and that would
certainly be useful.
setting up a proc readable file is not so hard.
but we could also printk it on module load.
but then it will become more complicated:
dmesg | grep "Realtime Security:" | tail -n 1
thats why
i dont consider it necessary. what do you need the proc entry
for fernando ?
Just asking, I guess it is not really needed, just unloading and loading
should be enough. It would be nice to have some sort of confirmation
from /proc that the module is there and which options are active. Maybe
that information is available somewhere after the module is loaded. --
joq
--
torben Hohn
http://galan.sourceforge.net -- The graphical Audio language