Hi, following our attempt to make a competitive realtime soem library under RTnet and Xenomai we are blocked now by some conceptual problems. Or simple, we don't know more :-(
After checking why it changes the context, looking on the code, etc we have found that if we open a RTnet device it's problematic to use it in two different context (RT and NRT). Our original idea was to encapsulate all the Ethercat functions in a class decoupling all the RT from the NRT part. We don't need (want) that all this code works on RT, just an small part. The permanent part is solved with the xddp communications, but not the transitory (the configuration). We need to access to the device to configure it, and to wrap all this stuff with xddp it's too complicate. So, my questions now are about intertask communications. I understand that from a NRT program, I can create a rt_task and be RT. But, from the RT world, can I create a NRT thread?. I mean, if I make my current program rt_shadow can I create a NRT thread? Can I call a function to be executed in a RT context? I mean to create a bunch of functions that could be called from a NRT program but this functions be executed in a RT context. I know that I can create a rt_task for each function, but if for example that configure a device, I would like some kind of persistence, not that when it finish the task, the context would be deleted. Reading more I think that what we would like really it's the xenomm project. To have an instance of a class executed in a RT context. Thanks in advance, Leopold -- -- Linux User 152692 Catalonia -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: <http://www.xenomai.org/pipermail/xenomai/attachments/20140218/8271a597/attachment.sig> _______________________________________________ Xenomai mailing list [email protected] http://www.xenomai.org/mailman/listinfo/xenomai
