- From: Frank Mori Hess <fmhess_at_users.sourceforge.net>
- Date: Thu, 3 Jul 2003 16:53:45 -0500
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 03 July 2003 04:24 pm, Calin A. Culianu wrote: > AO subdevices, and possibly the DIO, but not supporting commands)... I > was wondering what the best approach would be to 'lock' these devices so > that the user can't unconfigure them. I could increase the module use > count on each of the device's modules, and decrease it once the bonding > driver is unloaded, or I could use comedi_device.use_count, or perhaps > set the comedi_subdevice.busy (or comedi_subdevice.lock) field? I am > not sure though what these fields mean semantically, and even if I did > what the best approach would be.. how do I most safely do this while > cooperating with comedi_lock() semantics? > > Any quick suggestions would be appreciated.. or I should just "use the > source, Luke"? Use comedi_open() from kcomedilib, like comedi_rt_timer.o does. - -- Frank -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE/BKXp5vihyNWuA4URAviLAKCpihtSBSQB2jJWIeycT9haOdPK7QCfW5FY STiWNfwLgt0vRMzyDU9tfzQ= =Ke7z -----END PGP SIGNATURE-----
Received on 2003-07-03Z20:53:45