Hello Jeff,

I tested it with:
- EMC2 current master
- Debian Lenny
- 2.6.30.5-rtai kernel
- 3.7.1 RTAI
- onboard parallel port
- add-in parallel ports
- mixed parallel ports (with onboard port and add-in ports in the same conf)


1,2,3) Old configurations still work with/without parport_pc
4) The configurations work with the port number instead of the port
address when parport_pc is loaded


There is no output for 'ls /dev/parport*' command in my system while
the module parport_pc is loaded. I could not see any device for the
parallel ports in /dev and its subdirectories.

And the outputs of the following commands:

$ lsmod | grep parport
parport_pc             22488  0
parport                31200  1 parport_pc

$ ls /dev/par*
ls: cannot access /dev/par*: No such file or directory

$ find /dev/ -name "par*"
(no output)

$ find /dev/ -name "lp*"
(no output)

$ grep parport /proc/ioports | uniq -f3
0378-037a : parport0

$ grep parport /proc/ioports
0378-037a : parport0
037b-037f : parport0
  b800-b802 : parport1
  c000-c002 : parport2


regards
acemi






On 9/21/09, Jeff Epler <[email protected]> wrote:
> 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&reg; 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&#45;12, 2009. Register now&#33;
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Emc-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/emc-developers
>

------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; 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&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to