Karl:
> I have a paralell port adapter as in the attached schematic,
> and I would like to make it work with urjtag.
...
I'm looking att src/tap/cable/wiggler2.c, and I'm wondering what
PARAM_SIGNALS (cable) is for...
It is defined in src/tap/cable/generic.h, which is only included from c
files within src/tap/cable directory, and the only users of that macro
is the various cable drivers and urj_tap_cable_generic_get_signal() in
src/tap/cable/generic.c and seems to be the default function for
get_signal() entry in the struct URJ_CABLE_DRIVER.
There is no default set_signal, instead that is handled by the driver
itself, possible because the driver code I seen push the signals out to
the interface.
Does that mean that I'm free to use the void *params entry in
struct URJ_CABLE as i see fit (as long as I provide for my version of
get_signal() in struct URJ_CABLE_DRIVER) ?
One possible use for this variable would be to enble the driver to
handle different kind of paralell port adapters and the void *params
could be a struct pp_driver { int type_index; int signal; } where
type_index is just to point to the right data for the adapter.
Regards,
/Karl Hammar
_______________________________________________
UrJTAG-development mailing list
UrJTAG-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/urjtag-development
