I tested for the hal_parport "device or resource busy" problem but was
unable to reproduce it.
I tested on a debian 7 system recently installed from the hybrid.iso. I
tested at a master branch revision which describes as
"v2.6.3-659-gce43af0" (today's master branch) using a standalone test
script in the file pp.hal
loadrt hal_parport cfg=0
loadrt threads period1=1000000
loadrt not
net x not.0.out => not.0.in parport.0.pin-01-out
addf not.0 thread1
addf parport.0.write thread1
start
which I ran multiple times in succession with
halrun pp.hal
I did not receive any errors in the terminal or in dmesg.
On my system, the "install parport_pc /bin/true" line is commented out
in /etc/modprobe.d/linuxcnc.conf, so hal_parport is working in
cooperatin with the linux parallel port driver. My parallel port is on
a PCI card.
If you can, please test with the standalone hal script (modifying cfg=
if necessary) to see whether that produces the problem for you. But the
most basic explanation (that I completely botched the unregistration
process for rtai when adding uspace) seems to be discounted at this
point.
Jeff
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users
