Oh, I think I understand better what you're asking now. Are you asking whether a hardware driver that uses a parport must be built on the hal component called "hal_parport"? Absolutely not! The interface of hal_parport (17 or so 'bit' pins that can be read or written once per period) is pretty inconvenient for lots of sophisticated parport-attached devices, such as any EPP device.
However, your driver *should* use a port registration method (the best being hal_parport_get, which internally uses whichever lower-level method is appropriate, parport_find+parport_claim or request_region) in order to make sure that while emc is running, only one device is trying to access those low-level port addresses. Jeff ------------------------------------------------------------------------------ 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
