From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Alexander Epaneshnikov <aarnaarn2@gmail.com>
Cc: qemu-devel@nongnu.org, brltty@brltty.app
Subject: Re: baum: NVDA does not detect usb-braille
Date: Sun, 18 Oct 2026 21:10:39 +0200 [thread overview]
Message-ID: <atUZr1LP8k5b78I8@end> (raw)
In-Reply-To: <atUU4HpVVI59QcLJ@alex-pc>
(splitting the actually-unrelated questions)
Alexander Epaneshnikov, le dim. 18 oct. 2026 21:52:44 +0300, a ecrit:
> On Sun, Oct 18, 2026 at 06:26:53PM +0200, Samuel Thibault wrote:
> > Ah, that is a requirement of the protocol? Then we need to do that
> > indeed. What is the value of the uint8_t protocol field when it
> > expects to receive 0x01 and 0x84?
>
> It is 1 (on). For serial displays, NVDA's Baum driver
> (source/brailleDisplayDrivers/baum.py) first sends 0x15 with 0 to make
> sure the protocol is off, then sends 0x15 with 1 twice, "in case the
> display misses the first one". After that it waits for the cell count
> and the device identity. According to the comment in that driver, a
> real display answers only when the protocol goes from off to on. On
> that transition it sends its device identity, its serial number and
> its cell count, and it sends nothing if the protocol was already on.
> NVDA itself only waits for the cell count and the identity.
Does the device sends the cell count first or the device identity first?
Samuel
next prev parent reply other threads:[~2026-10-18 19:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <atNoDNz0dQucxzFN@alex-pc>
[not found] ` <atNo9sk_7jCAi98u@end>
2026-10-17 19:13 ` baum: NVDA does not detect usb-braille, and following the input-linux grab Alexander Epaneshnikov
2026-10-18 16:26 ` Samuel Thibault
2026-10-18 18:52 ` Alexander Epaneshnikov
2026-10-18 19:10 ` Samuel Thibault [this message]
2026-10-18 19:35 ` baum: NVDA does not detect usb-braille Alexander Epaneshnikov
2026-10-18 20:49 ` Samuel Thibault
2026-10-18 19:17 ` baum: NVDA does not detect usb-braille, and following the input-linux grab Samuel Thibault
2026-10-18 19:26 ` Alexander Epaneshnikov
2026-10-18 19:30 ` Samuel Thibault
2026-10-18 19:39 ` Alexander Epaneshnikov
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=atUZr1LP8k5b78I8@end \
--to=samuel.thibault@ens-lyon.org \
--cc=aarnaarn2@gmail.com \
--cc=brltty@brltty.app \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.