public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Linux for blind general discussion <blinux-list@redhat.com>
To: Linux for blind general discussion <blinux-list@redhat.com>
Subject: Re: brltty support for the new Orbit braille display, is anyone looking at that?
Date: Wed, 7 Jun 2017 09:07:39 +0200 (SAST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1706070852210.14671@willempc.meraka.csir.co.za> (raw)
In-Reply-To: <alpine.DEB.2.21.1.1706061439080.3046@southernprince>

Thanks for all the responses regarding this.
I got the code from git and have built it.
In the README, the Orbit 20 is listed as supported.
I had a look at the git log, and it looks like Dave had a device to test 
with.

It looks like the Orbit 20 can emulate a number of different devices, but 
that it now has its own support in brltty.
For others interested, some work on the support was done as recent as 
April 2017, so one should get a very new version or brltty to get the 
most out of an Orbit 20.
I will have to do an update for the SA-Note so that it can include this 
support.
Kind regards, Willem


On Tue, 6 Jun 2017, Linux for blind general discussion wrote:

> Brltty is supporting the orbit in NVDA, so hopefully that'd translate over to linux.  Also, if the linux version of brltty supports refreshAbraille,
> orbit can imulate that.
> that's all the info I got.
>
>
>
> Mark Peveto
> Registered Linux user number 600552
> Everything happens after coffee!
>
> On Tue, 6 Jun 2017, Linux for blind general discussion wrote:
>
>>
>> Dear,
>> Driver development is not very easy. In most case, experienced driver
>> developer must have braille display to develop specific driver for it. And
>> because Braille display is not cheap as a mobile phone SIM cart or so cheap as
>> most cheapest mobile phone model on The market, driver developer must obtain
>> this device.
>>
>> Next problem. Braille display manufacturer must provide The necessary
>> technical informaton to The driver developer. In other case,
>> reverseengineering work based on analysis The communication between computer
>> and device is needed. By uswing special USB transfer monitoring apps. And this
>> is not easy.
>> Try to ask Dave Mielke on Brltty mailing list. Problem is, that by driving
>> Braille device incorrectly can cause hardware damage of the device. So kernel
>> driver development and eevice driver development is really not such kind of
>> experimenting like while debugging simple program which do not drive specific
>> device directly.
>> I have read one article, that first versions of Brltty had difficulty with
>> this. And that one Braille device have been accidentally damaged. So one
>> manufacturer has borrowed display Braille display to The responsible
>> developer.
>> I do not know, who has so big C or C++ knowledge that he is able to
>> incorporate new Braille device driver to Brltty package.
>> May be, MR Tibault and Dave Mielke? Or MR Mielke alone?
>> Linux for blind general discussion napsal(a):
>>> Hi,
>>> Many South Africans are eagerly awaiting the release of the Orbit braille
>>> display.
>>> Does anyone know if someone is working on adding support for this braille
>>> display to brltty?
>>> TIA, Willem
>>>
>>>
>>> --
>>>
>>> This message is subject to the CSIR's copyright terms and conditions, e-mail
>>> legal notice, and implemented Open Document Format (ODF) standard. The full
>>> disclaimer details can be found at http://www.csir.co.za/disclaimer.html.
>>> Please consider the environment before printing this email.
>>> _______________________________________________
>>> Blinux-list mailing list
>>> Blinux-list@redhat.com
>>> https://www.redhat.com/mailman/listinfo/blinux-list
>>>
>>
>> _______________________________________________
>> Blinux-list mailing list
>> Blinux-list@redhat.com
>> https://www.redhat.com/mailman/listinfo/blinux-list
>>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>
>

--

This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. 
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html. 

Please consider the environment before printing this email. 

      reply	other threads:[~ UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Linux for blind general discussion
 ` Linux for blind general discussion
   ` Linux for blind general discussion
 ` Linux for blind general discussion
   ` Linux for blind general discussion
     ` Linux for blind general discussion [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.20.1706070852210.14671@willempc.meraka.csir.co.za \
    --to=blinux-list@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).