Re: [PARPORT] searching example for ppdev and interupt

From: Tim Waugh (
Date: Wed Feb 27 2002 - 09:52:51 EST

  • Next message: norman: "Re: [PARPORT] searching example for ppdev and interupt"

    On Wed, Feb 27, 2002 at 03:35:41PM +0100, norman wrote:

    > > They're short-hand for signal names. Use PARPORT_CONTROL_...,
    > > PARPORT_STATUS_... etc.
    > hmm. the same problem:
    > inttest.c:28: `PARPORT_CONTROL_nAck' undeclared (first use in this function)

    Look for the right constants in the header file.

    > > By the way, consider using libieee1284 rather than ppdev directly.
    > and whats the difference between ppdev and this libraray ?

    Port detection (including /proc parsing) done for you, proper IEEE
    1284 signal names instead of PC-style inverted ones, seemless use of
    direct I/O or /dev/port if /dev/parport* isn't available, possibility
    of working on other POSIX platforms, slightly better interface,
    slightly better documentation.


    -- To unsubscribe, send mail to: --
    -- with the single word "unsubscribe" in the body of the message. --

    This archive was generated by hypermail 2b29 : Wed Feb 27 2002 - 09:55:35 EST