On 12/19/2012 10:39 AM, alex alex wrote:
Infact I thought "rtdm_dev_register" worked exclusively in the _init
function as indicated by the documentation. Following your advice I have
tested "rtdm_dev_register" in another function of my RTDM driver (ioctl)
and it works well.
I think you might change the doc of rtdm_dev_register to :
This service can be called from:
- Kernel module initialization/cleanup code
- Kernel-based task
Same for rtdm_dev_unregister
Nope. Kernel-based task in the context of Xenomai means a primary mode
context over a lightweight Xenomai task, which is not what you want.
Kernel module init/cleanup code implies secondary mode, this is the gist
of the matter. This may be made clearer in the doc though.
Alex.
2012/12/18 Gilles Chanteperdrix <[email protected]>
On 12/18/2012 03:38 PM, alex alex wrote:
Thanks for your answer, I have corrected the example program.
What I would like to do is add x devices after that the module be loaded
and without naming these devices statically in the module, so am I forced
to call x times rtdm_dev_register with x declarations of the rtdm_device
structure in test.c?
If there is an other way, please tell me what it is.
What about creating a first static device with an ioctl allowing to create
other devices?
--
Gilles.
______________________________**_________________
Xenomai mailing list
[email protected]
http://www.xenomai.org/**mailman/listinfo/xenomai<http://www.xenomai.org/mailman/listinfo/xenomai>
_______________________________________________
Xenomai mailing list
[email protected]
http://www.xenomai.org/mailman/listinfo/xenomai
--
Philippe.
_______________________________________________
Xenomai mailing list
[email protected]
http://www.xenomai.org/mailman/listinfo/xenomai
