Thinus Viljoen wrote: > Jan > > Calling rtdm_in_rt_context() returns the following values in the following > functions: > init_module(): 0 > recv_msg(): 1 > send_msg(): 1 > This is correct, I assume?
Yep, all fine. That would have been too easy... > > Regarding the rt_assign_irq_to_cpu: I am not too sure what it is for, I am > ashamed to say - it is used in some RTAI showroom examples, and in particular > one that I copied&pasted some code from. I removed it, and it didn't seem to > make any difference. As you are on UP anyway, this IRQ assignment makes surely no sense here. But it /shouldn't/ cause harm as well. > > Another question - is it necessary to include rtdm/rtdm.h? Nope, rtnet.h does so. > > Some facts that might be relevant: > > 1. When compiling I get the following warning: > /usr/realtime/include/rtai_sanity.h:24:2: warning: #warning : You are likely > using an unsuported GCC version! Please read GCC-WARNINGS carefully. > I can't find this GCC-WARNINGS file (a post on the net refers to the RTAI > source tree, but I can't find it there). I am using GCC 4.1.0. Oh, may explain some weirdness, don't know if also the -38 error. Do you have some other compiler at hand to cross-check? I don't know why RTAI has to warn about recent compilers. The only bug I've seen in the wild so far was a freaky corner case (in combination with kgdb). It will be fixed in 4.1.1 and should not affect RTAI anyway. > > 2. Every now and then I get the following message: > UNEXPECTED FPU TRAP FROM HARD PID = xxxx (The PID is for "insmod > rtai_lxrt.ko") > > 3. Sometimes, after multiple module load/unload/recompile etc. cycles, every > key that I press is repeated about 20 times (or the PC hangs). I then have to > reboot. Sometimes after the reboot the PC hangs during the boot process, but > then boots OK after a further reboot. > > 4. My machine is a AMD Athlon 1.4GHz, with a AMD761 K7 chipset. That three issues can be related to RTAI's issues with the compiler (RTnet is proven to be fine with 4.1). But the -ENOSYS issue remains unexplainable to me. In any case, this very much looks like a RTAI-related issue now. Maybe someone can jump in here, or you could post your findings (with code) on the RTAI list. I'm sorry that I cannot help, but there are too many RTAI-unknowns for me. Jan
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ RTnet-users mailing list RTnet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rtnet-users
