On Thu, 2011-02-03 at 15:00 -0600, Jeff Epler wrote:
> 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"?
Not really.
> Absolutely not! The
> interface of hal_parpo
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 i
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 w
On Wed, Feb 02, 2011 at 07:58:56AM -0800, Kirk Wallace wrote:
> Should a parallel port comp claim and release a port(s) with parport?
> Usually the port addresses are assigned manually to each comp so claim
> jumping should not be a problem?
Ideally, you'd use the routines from "parport_common.h"
Should a parallel port comp claim and release a port(s) with parport?
Usually the port addresses are assigned manually to each comp so claim
jumping should not be a problem?
--
Kirk Wallace
http://www.wallacecompany.com/machine_shop/
http://www.wallacecompany.com/E45/index.html
California, USA
-
