On Thu, 2011-02-03 at 13:37 -0600, Jeff Epler wrote: ... snip > Ideally, you'd use the routines from "parport_common.h" in the source > distribution. These routines can cooperate with Linux parport detection > (which means the user can specify 0 to use parport0, etc) as well as the > traditional way (by base address). In either case, the I/O ports are > registered for emc2's exclusive use while it's running (by parport_claim > or rtapi_request_region, as appropriate).
I guess what I'm getting at is, EMC2 compatible hardware usually gets assigned a port manually with a config string and it seems even a printer would need a manual configuration. I think the manual assignments block any sharing by their nature, so I wonder if being parport compliant really adds any value. It looks like Hostmot already breaks compliance. Although ppmc looks like it needs it to share more than one card on a single port. (uhg, my brain hurts) -- Kirk Wallace http://www.wallacecompany.com/machine_shop/ http://www.wallacecompany.com/E45/index.html California, USA ------------------------------------------------------------------------------ The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
