John Kasunich wrote: >Jon Elson wrote: > > > >>If you are doing this for motion control (ie. more stepper axes) then >>you don't need to >>worry about the Linux driver, as the real-time code doesn't use it. It >>just has to have the >>data and status ports at a known offset, and you need to search the PCI >>config info to >>see what the plug-n-play set the address to. >> >>If you need it for additional status and control I/O, then it may need >>the low-level >>parport driver. But, I think these boards are compatible enough that >>the basic functions >>are at the standard addresses. >> >> > >There is no distinction between "motion control" and "status and control >I/O" in EMC2. You load the parport driver, and tell it which ports you >want to use. The driver makes all the pins of all the ports available >in HAL, and then you connect any signal to any pin on any parport. > >The distinction between motion control parport (realtime) and >control/status parport (non-realtime) is ancient history. > > > OK, so is this all done now in the real-time code? By "You load the parport driver" do you mean the EMC2/HAL parport driver? If so, then the OP shouldn't need the Linux driver, except possibly to set the mode of the port before starting EMC.
Jon ------------------------------------------------------------------------- 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 _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
