From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id v56IFmk7027900 for ; Tue, 6 Jun 2017 14:15:48 -0400 Received: by smtp.corp.redhat.com (Postfix) id C1FA2867EA; Tue, 6 Jun 2017 18:15:48 +0000 (UTC) Received: from mx1.redhat.com (ext-mx02.extmail.prod.ext.phx2.redhat.com [10.5.110.26]) by smtp.corp.redhat.com (Postfix) with ESMTPS id BD762867E9 for ; Tue, 6 Jun 2017 18:15:46 +0000 (UTC) Received: from smtp-out3.iol.cz (smtp-out3.iol.cz [194.228.2.91]) by mx1.redhat.com (Postfix) with ESMTP id A417280C1D for ; Tue, 6 Jun 2017 18:15:42 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com A417280C1D Authentication-Results: ext-mx02.extmail.prod.ext.phx2.redhat.com; dmarc=fail (p=none dis=none) header.from=volny.cz Authentication-Results: ext-mx02.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=janusz.chmiel@volny.cz DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com A417280C1D Received: from aa.iol.cz (aa.iol.cz [90.176.151.111]) by smtp-out3.iol.cz (Postfix) with ESMTP id 0716880907F2 for ; Tue, 6 Jun 2017 20:15:41 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by aa-iol4.iol.cz (Postfix) with ESMTP id 036F939911B for ; Tue, 6 Jun 2017 20:15:41 +0200 (CEST) X-Virus-Scanned: by SpamTitan at iol.cz Received: from aa.iol.cz (localhost [127.0.0.1]) by aa-iol4.iol.cz (Postfix) with ESMTP id 51CFF3990C4 for ; Tue, 6 Jun 2017 20:15:38 +0200 (CEST) Received: from [10.0.0.1] (20.108.broadband4.iol.cz [85.71.108.20]) (Authenticated sender: ELogV7EDXG) by aa-iol4.iol.cz (Postfix) with ESMTPA id 47B473990E8 for ; Tue, 6 Jun 2017 20:15:38 +0200 (CEST) Subject: Re: brltty support for the new Orbit braille display, is anyone looking at that? To: blinux-list@redhat.com References: Message-ID: <4d0fb9be-1b4f-1434-a37a-07ca8389f15d@volny.cz> Date: Tue, 6 Jun 2017 20:15:36 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender passed SPF test, Sender IP whitelisted by DNSRBL, ACL 203 matched, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.26]); Tue, 06 Jun 2017 18:15:44 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.26]); Tue, 06 Jun 2017 18:15:44 +0000 (UTC) for IP:'194.228.2.91' DOMAIN:'smtp-out3.iol.cz' HELO:'smtp-out3.iol.cz' FROM:'janusz.chmiel@volny.cz' RCPT:'' X-RedHat-Spam-Score: 2.179 ** (BAYES_80, DCC_REPUT_70_89, RCVD_IN_DNSWL_LOW, SPF_NEUTRAL) 194.228.2.91 smtp-out3.iol.cz 194.228.2.91 smtp-out3.iol.cz X-Scanned-By: MIMEDefang 2.78 on 10.5.110.26 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-loop: blinux-list@redhat.com From: Linux for blind general discussion X-BeenThere: blinux-list@redhat.com X-Mailman-Version: 2.1.12 Precedence: junk Reply-To: blinux-list@redhat.com List-Id: Linux for blind general discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jun 2017 18:15:49 -0000 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 >