Jason Thorpe <thor...@me.com> writes: > I should be able to do this with OpenOCD (pkgsrc/devel/openocd), but > libfdti1 fails to find the device because libusb1 only deals in > "ugen".
Is that fundamental, in that ugen has ioctls that are ugen-ish that uftdi does not? I am guessing you thought about fixing libusb1. > The desire to use "ugen" on "interface 1" is not a property of > 0x0403,0x6010, it's really a property of > "SecuringHardware.com","Tigard V1.1". Unfortunately, there's isn't a > way to express that in the kernel config syntax. > > I think my only short-term option here is to, in uftdi_match(), specifically > reject based on this criteria: > > - VID == 0x0403 > - PID == 0x6010 > - interface number == 1 > - vendor string == "SecuringHardware.com" > - product string == "Tigard V1.1" > > (It's never useful, on this particular board, to use the second port as a > UART.) That seems reasonable to me. It seems pretty unlikely to break other things.
