[quoted lines by S. Massy on 2014/10/23 at 14:33 -0400]
>What I have observed so far is that its USB ID seems to trigger the
>cdc_acm module which then attempts to claim the device, creating a
>conflict.
A CDC_ACM device has two USB interfaces. Since brltty only uses one of them, it
only claims
On Thu, Oct 23, 2014 at 05:03:23PM +0200, Mario Lang wrote:
> Additionally, I still seem to have issues initializing the B80 the
> first time I boot my Linux host. It can take me a few minutes, and
> roughly 15 retries, until it finally works. Reconnect also happens to
> fail most of the time, so
"S. Massy" writes:
> On Tue, Oct 21, 2014 at 06:39:38PM -0400, Dave Mielke wrote:
>> [quoted lines by S. Massy on 2014/10/21 at 17:45 -0400]
>>
>> >Am I correct in assuming support for this line of devices is only
>> >present in BRLTTY 5.0. I seem to be having no luck plug-and-playing with
>> >s
On Tue, Oct 21, 2014 at 06:39:38PM -0400, Dave Mielke wrote:
> [quoted lines by S. Massy on 2014/10/21 at 17:45 -0400]
>
> >Am I correct in assuming support for this line of devices is only
> >present in BRLTTY 5.0. I seem to be having no luck plug-and-playing with
> >systems currently utilising v
I had to reconfigure my kernel before I was able to support this device,
something about user space driver, if I remember correctly.
Dave Mielke wrote:
> [quoted lines by S. Massy on 2014/10/21 at 17:45 -0400]
>
> >Am I correct in assuming support for this line of devices is only
> >present in
[quoted lines by S. Massy on 2014/10/21 at 17:45 -0400]
>Am I correct in assuming support for this line of devices is only
>present in BRLTTY 5.0. I seem to be having no luck plug-and-playing with
>systems currently utilising version 4.4. Let me know if I'm missing
>something.
Those devices need
