From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id v56JgQMW007507 for ; Tue, 6 Jun 2017 15:42:26 -0400 Received: by smtp.corp.redhat.com (Postfix) id 6CF5E77D46; Tue, 6 Jun 2017 19:42:26 +0000 (UTC) Received: from mx1.redhat.com (ext-mx08.extmail.prod.ext.phx2.redhat.com [10.5.110.32]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 62F6977D5B for ; Tue, 6 Jun 2017 19:42:24 +0000 (UTC) Received: from mail-it0-f42.google.com (mail-it0-f42.google.com [209.85.214.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 6CE1CC0587D3 for ; Tue, 6 Jun 2017 19:42:22 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 6CE1CC0587D3 Authentication-Results: ext-mx08.extmail.prod.ext.phx2.redhat.com; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: ext-mx08.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=southernprince73@gmail.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 6CE1CC0587D3 Authentication-Results: mx1.redhat.com; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="BRv7tUT/" Received: by mail-it0-f42.google.com with SMTP id m47so117074846iti.0 for ; Tue, 06 Jun 2017 12:42:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:date:to:subject:in-reply-to:message-id:references:user-agent :mime-version; bh=eKbTR0GQ6OjXIQZeA6DXYFacPInyxrvUilBVnNw1L5E=; b=BRv7tUT/f16UzW1TXN5HytbcIa9tN7uUHm367RFwsUWorvsVvulJ8hD0JsWmfLgzl6 vwTvhpRctBqq/SrDWMTwA5+60EI5RRASEERQ1YAWzyimRKPzDLxQbrKayQTrXJPbWBmQ 4wgFQRPMDvpq5tQoXAr8iU5ZvFBXCkJtdb0I3zZssSmTAWgG5YmxJjIl59TKQuCNdAEO 5AQFk8qL0C9URHAw2wFl7OnMvFyzH+a5Xt9ofH/PvuBsXIvowQJ64rOaB4+kzcBxYxvK C7a+9k9rFJtMw+1ocy0jSWr4bk14a49GRpdQcHvuIMrOhxJ+/Xcc1qn9EKkoKgF/FV1R XT4g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:date:to:subject:in-reply-to:message-id :references:user-agent:mime-version; bh=eKbTR0GQ6OjXIQZeA6DXYFacPInyxrvUilBVnNw1L5E=; b=b4Fwnw3MFSq6xVx920zJGuJwz0vtlhbzN78V1dG9FSfNK2LdH59oeTxZC28VZTxerd inqEYixt2O3mHAAJ6U9KQNV5qMz6yOSwWN8PMOY/Rp8jpZTHSM5P/w7lDIzeJiRhUzN/ NtaEqLYZSV6Pu6PafXvviNruzR24wjPlIX56jjtEVGV08tgF/QQVsvZXQsKxaSHvJMGe TgkM3H4zQcGXV4XX7cQOvyLn3kNf1kOFmkjZf0zfabVzimTcYQENO17tXsDjw4k+OunZ 8hmp/kk9vf6qU//bKOcGMwfv2OVXVNFR8LMy722W5neqhIjk0gsIK9jWXSSWBOW3jZxu 88ag== X-Gm-Message-State: AODbwcB9uJD5BCXtsMeDF7qQxo0rSHrgXzrgNfnZw5ecD0Hvr70HGdsA I9OidpWpTproDcCz X-Received: by 10.107.201.213 with SMTP id z204mr7851386iof.160.1496778136727; Tue, 06 Jun 2017 12:42:16 -0700 (PDT) Received: from [192.168.0.11] (97-127-184-126.cdrr.qwest.net. [97.127.184.126]) by smtp.gmail.com with ESMTPSA id u6sm6741427ita.17.2017.06.06.12.42.16 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 06 Jun 2017 12:42:16 -0700 (PDT) X-Google-Original-From: Mark Peveto Date: Tue, 6 Jun 2017 14:41:53 -0500 (CDT) X-X-Sender: markp@southernprince To: Linux for blind general discussion Subject: Re: brltty support for the new Orbit braille display, is anyone looking at that? In-Reply-To: <4d0fb9be-1b4f-1434-a37a-07ca8389f15d@volny.cz> Message-ID: References: <4d0fb9be-1b4f-1434-a37a-07ca8389f15d@volny.cz> User-Agent: Alpine 2.21.1 (DEB 211 2017-05-04) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.32]); Tue, 06 Jun 2017 19:42:22 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.32]); Tue, 06 Jun 2017 19:42:22 +0000 (UTC) for IP:'209.85.214.42' DOMAIN:'mail-it0-f42.google.com' HELO:'mail-it0-f42.google.com' FROM:'southernprince73@gmail.com' RCPT:'' X-RedHat-Spam-Score: 0.52 (BAYES_50, DCC_REPUT_00_12, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_PASS) 209.85.214.42 mail-it0-f42.google.com 209.85.214.42 mail-it0-f42.google.com X-Scanned-By: MIMEDefang 2.78 on 10.5.110.32 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 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 19:42:26 -0000 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 >