On Mon, Jun 02, 2014 at 01:11:37PM -0400, Mike Remski wrote:Johan,
On 06/02/2014 12:49 PM, Johan Hovold wrote:You really should try this before anything else. :)
On Mon, Jun 02, 2014 at 12:24:44PM -0400, Mike Remski wrote:Not yet, next on the list.
On 06/02/2014 12:20 PM, Johan Hovold wrote:Not just their own ID's it seems.
On Mon, Jun 02, 2014 at 12:02:40PM -0400, Mike Remski wrote:Johan,
On 06/02/2014 11:40 AM, Johan Hovold wrote:The third interface lacks endpoints and crashes the ftdi_sio driver.
[ Please avoid top-posting. ]
On Mon, Jun 02, 2014 at 11:16:11AM -0400, Mike Remski wrote:
This shouldn't happen (even if you're forcing the wrong driver to bind),
so I'll fix it up if still broken in v3.15-rc.
Thanks again. Yes, the device does indeed have an FTDI embedded in it;
they've programmed in their own ids. They supply a Windows driver for
it, but that doesn't do me any good. :)
Have you tried just using the cdc-acm driver? The ports should up as
/dev/ttyACMx instead of ttyUSBx.
I'm suspecting that bNumEndpoints == 0 is causing endpoint.desc toYeah, the code is obviously broken (also in v3.15-rc). It should
stay at NULL (line 1567 in 18.104.22.168 source), so by the time it gets used
later on, I'm hitting the NULL dereference.
probably work to just return from ftdi_set_max_packet_size if
num_endpoints is 0 if you want to try that (or you can use your ?:
construct), but I should be able to fix this up properly on Wednesday.