From: Laurent Pinchart (laurent.pinchart@capflow.com)
Date: Tue Jun 12 2001 - 03:53:27 EDT

  • Next message: Tim Waugh: "Re: [PARPORT] ECP FIFO residue"


    I'm working parport_pc to store ECP FIFO read residues, and I was
    wondering where I should save them.

    My first idea was to add 2 fields in the struct parport (a pointer to
    the fifo residue, and the size of the residue). That shouldn't be a
    problem for muxes, cause each mux creates a clone of the physical
    parallel port, but what about daisy chains, mechanical parport switches,
    ... ? Saving FIFO residue for a peripheral and giving back that residue
    to another peripheral driver doesn't seem to be a good idea.

    My second idea was to save it in struct pardevice. That solves the
    problem of 'sharing' residues among several devices, but how can I
    access that struct pardevice when in parport_pc_ecp_read_block_pio ?

    I'm waiting for your comments.


    Laurent Pinchart

    -- To unsubscribe, send mail to: linux-parport-request@torque.net --
    -- with the single word "unsubscribe" in the body of the message. --

    This archive was generated by hypermail 2b29 : Tue Jun 12 2001 - 03:55:07 EDT