Re: [PARPORT] PATCH: parport_device_id support + bloat, "version 2.2"

From: Tim Waugh (
Date: Mon Feb 05 2001 - 14:22:31 EST

  • Next message: Adam J. Richter: "Re: [PARPORT] PATCH: parport_device_id support + bloat, "version 2.2""

    (Sorry for the delay. I've been a bit busy..)

    On Sun, Jan 21, 2001 at 04:51:09AM -0800, Adam J. Richter wrote:

    > OK, here is a patch that restores the "compatability" routines
    > that I believe are never used. I wanted to have all of the unneeded
    > code in a separate file which would build a separate module in the
    > modularized case, but exporting the "topology" variable, with its
    > own structure format, from daisy.c was just too ugly. So, a small
    > helper routine, parport_find, is in daisy.c.

    This looks excellent. Thanks a lot.

    > Is it generally true that devices that have IEEE-1284.3 device ID's
    > are also accessible through this daisy chaining mechanism?

    Yes. That is, IEEE 1284.3-compatible daisy chaining devices generally
    have IEEE 1284 Device IDs.

    > If so, then it would probably make sense to add a paramaeter to
    > parport_driver->attach to indicate which device on the chain to
    > attach to. Since old drives could just ignore the parameter, it
    > would be compatible.

    (It wouldn't even be source compatible.)

    > If other devices on the daisy chain are generally
    > not accessible, then only then only parport.probe_strings[0]
    > should be considered.

    Device IDs can be obtained from all devices on an IEEE 1284.3 chain.


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

    This archive was generated by hypermail 2b29 : Mon Feb 05 2001 - 14:25:08 EST