Today I pushed a series of changes that affects all parport drivers --
hal_parport, hal_ppmc, hm2_7i43, pluto_step, and pluto_servo. It
improves the drivers so that they can cooperate with the Linux parport
driver; the biggest advantage of this is that parport numbers can be
specified as 0, 1, 2, etc instead of looking at lspci output and
guessing at I/O addresses.
Dewey Garret and I were able to do a bit of testing on each of these
drivers, but it could use further testing. If you use one of these
drivers, please read on to see how you can help test this change. I am
particularly eager for reports about systems where there is more than
one parallel port present.
1. After upgrading to the latest master, make sure your configuration
still works
2. Execute
sudo modprobe -i parport_pc
to load the Linux parport driver (the effect of this will go away
when you reboot)
3. make sure your configuration still works
4. find the place in your configuration to specify the parport as a
number instead of a port address. On each system I tested the
onboard port is 0; the first add-in card is presumably 1. For
example, with hal_parport, this is
loadrt hal_parport cfg="0"
and a two-port configuration would be
loadrt hal_parport cfg="0 1"
This style of port specification only works when the Linux parport
driver is loaded. This will be the case when emc2.4 is packaged,
but when a 2.3.x package is installed the Linux parport driver is
disabled. (this is required for 2.3 to use parports at all)
If you run into trouble, rebuild with each instance of RTAPI_MSG_INFO
changed to RTAPI_MSG_ERR. In the information you include, please give
the dmesg output from when you did the 'sudo modprobe -i parport_pc'
and the dmesg output from running emc2.
Chris M., I think this has the potential to improve parport detection in
stepgen/pncconf. For now I think the user can just enter 0/1/2 for port
addresses, but probably there's some way to list the ports and their
basic information (I/O addresses and maybe onboard vs pci) that would
make it even better. Two ideas I'm not thrilled about are looking
at ioports:
$ grep parport /proc/ioports | uniq -f3
0378-037a : parport0
or dev:
$ ls /dev/parport*
/dev/parport0
but maybe there's a better way.
thanks,
Jeff
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
