This is a strange question, but please bear with me. I want to write a hal realtime component that only runs init code. (I have an application where being in kernel space with an active rtapi and the hm2 drivers loaded makes the task in hand much easier than otherwise)
However, after running the rtapi_app_main loop I want to quit, cleanly, with no errors, and in such a away that I can loadrt the same module again without an error. Would anyone like to speculate on which sequence of hal_init, hal_ready and hal_exit are needed. If I have none of the above then it seems that the component doesn't manage to exist, though perhaps that is fixable with Makefile magic Skipping hal_init and hal_ready and returning -1 actually works as needed, apart from a bunch of error messages. Skipping both and returning 0 is quiet the first time, then fails, breaks rtapi, and needs a reboot. I was discussing earlier privately how I could probably save myself ours or days by finding out how to make halrun -U actually work as documented. -- atp If you can't fix it, you don't own it. http://www.ifixit.com/Manifesto ------------------------------------------------------------------------------ WINDOWS 8 is here. Millions of people. Your app in 30 days. Visit The Windows 8 Center at Sourceforge for all your go to resources. http://windows8center.sourceforge.net/ join-generation-app-and-make-money-coding-fast/ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
