[BRLTTY] Humanware driver and USB HID

[Justin Pospical]

Yep, looks like the driver actually isn't starting at all, even when manually specified. Here's the entry for the USB device:


T:  Bus=01 Lev=02 Prnt=02 Port=02 Cnt=02 Dev#=  5 Spd=480  MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=1c71 ProdID=c101 Rev= 4.14
S:  Product=APH Chameleon 20
S:  SerialNumber=65-0200-100389
C:* #Ifs= 3 Cfg#= 1 Atr=80 MxPwr=  2mA
I:* If#= 0 Alt= 0 #EPs= 2 Cls=03(HID  ) Sub=00 Prot=00 Driver=usbhid
E:  Ad=81(I) Atr=03(Int.) MxPS=   8 Ivl=1ms
E:  Ad=02(O) Atr=03(Int.) MxPS=   8 Ivl=1ms
I:* If#= 1 Alt= 0 #EPs= 2 Cls=03(HID  ) Sub=00 Prot=00 Driver=(none)
E:  Ad=83(I) Atr=03(Int.) MxPS=   8 Ivl=1ms
E:  Ad=04(O) Atr=03(Int.) MxPS=   8 Ivl=1ms
I:* If#= 2 Alt= 0 #EPs= 3 Cls=06(still) Sub=01 Prot=01 Driver=(none)
E:  Ad=85(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=06(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=87(I) Atr=03(Int.) MxPS=  28 Ivl=4ms

I'll attach the debug log, in case there's something relevant even though the driver didn't start (it did find the device). Hope it helps.

Justin
On Thu, Mar 4, 2021, at 15:02, Dave Mielke wrote:
> [quoted lines by Justin Pospical on 2021/03/04 at 14:24 -0800]
> 
> >I have an APH Chameleon 20 (which I believe is actually a rebranded Brailliant BI20x) that uses the Humanware driver. I read the recent discussion about the Mantis (same driver/protocol) so am aware bluetooth HID is not currently supported and the display therefore won't work using bluetooth. 
> 
> Yes, that's correct.
> 
> >I've tried connecting via USB, and that also does not seem to work; 
> 
> It should. I've tested that with a Humanware BrailleOne, which is effectively
> the same device.
> 
> >brltty starts via the udev rule, but I get no output. 
> 
> Perhaps you could capture additional information by logging with:
> 
>    -ldebug,brldrv,inpkts,outpkts
> 
> >The following is logged repeatedly after connecting:
> 
> Repeated logging would mean that the driver startup isn't succeeding.
> 
> >Mar 04 14:21:02 p1 brltty[402]: USB configuration set error 16: Device or resource busy
> 
> This is usually not a problem. When it fails with busy as the reason then
> brltty detaches the device from the kernel's driver so that it can use it.
> 
> >Mar 04 13:59:52 p1 brltty[384]: USB: endpoint descriptor not found: 84
> 
> This is the actual problem. Could you please post (or send to me directly) a
> copy of the file /sys/kernel/debug/usb/devices while your device is connected?
> 
> -- 
> I believe the Bible to be the very Word of God: http://Mielke.cc/bible/
> Dave Mielke            | 2213 Fox Crescent | WebHome: http://Mielke.cc/
> EMail: Dave at Mielke.cc  | Ottawa, Ontario   | Twitter: @Dave_Mielke
> Phone: +1 613 726 0014 | Canada  K2A 1H7   |
> _______________________________________________
> This message was sent via the BRLTTY mailing list.
> To post a message, send an e-mail to: BRLTTY at brltty.app
> For general information, go to: http://brltty.app/mailman/listinfo/brltty
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: brltty.log
Type: application/octet-stream
Size: 20355 bytes
Desc: not available
URL: <http://brltty.app/pipermail/brltty/attachments/20210305/8c62e16a/attachment.obj>