[BRLTTY] link to screen source

[Cheryl Homiak]

Actually, if this is usb-serial, is the cable itself a usb cable or usb-serial? There may actually be a way to do this.

(1) if usb: is being used, an actual device identifier may be present that is to be used;
(2) there may be something in /dev that starts with cu. that would be available.

I actually think this may be like the handy Tech I posted about back a few months ago, where I was told usb should work but I actually had to treat it as usb-serial.

John: can you do:

ls /dev/cu.* and send the list of what shows up. Do this when you have the braille display plugged in; I can't remember whether it matters if voiceover is on or not. Note the period after the cu.


On Sep 3, 2017, at 8:44 PM, Dave Mielke <dave at mielke.cc> wrote:

[quoted lines by John Covici on 2017/09/03 at 18:30 -0400]

> I sent the log to Dave privately.  I am getting device or resource
> busy on the usb.

The Screen screen driver is successfully starting without incident, so no 
problem with shared memory segments.

The prhase "no path for address' isn't in the log, so it's still a mystery.

The device is using a CDC ACM chip for its USB to serial adapter. This is a 
standard serial protocol, so the Mac kernel undoubedly has a driver for it, and 
that driver has undoubedly, therefore, claimed the braille device. That's why 
it's "busy" and brltty can't claim it for itself. Linux does the same thing 
except that, on Linuxk we know how to tell the kernel to release it so that we 
can grab it. I've no idea how to do this on Mac OS X. Until we can do it, you 
may need to use Bluetooth.

-- 
Dave Mielke           | 2213 Fox Crescent | http://Mielke.cc/
Phone: 1-613-726-0014 | Ottawa, Ontario   | http://Mielke.cc/bible/
EMail: Dave at Mielke.cc | Canada  K2A 1H7   | The Bible is the very Word of God.