From: Samuel Thibault <samuel.thibault@gnu.org>
To: Teemu Kuusisto <teemu.kuusisto@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: Braille device (chardev/baum.c) is unable to detect the TTY correctly and does not act on graphic console connect/disconnect
Date: Thu, 14 Nov 2019 14:27:12 +0100 [thread overview]
Message-ID: <20191114132712.rpqzq7jvl32beduu@function> (raw)
In-Reply-To: <20191114130841.kxgorkvtinyaahdm@function>
Samuel Thibault, le jeu. 14 nov. 2019 14:08:41 +0100, a ecrit:
> The way to properly fix it is to add a brlapi channel to spice:
And that would be workable through a spice agent as well, so that
braille management from orca running inside the guest could talk
directly through to brltty running on the host instead of having to go
through the emulation layers.
Samuel
next prev parent reply other threads:[~2019-11-14 13:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 12:09 Braille device (chardev/baum.c) is unable to detect the TTY correctly and does not act on graphic console connect/disconnect Teemu Kuusisto
2019-11-14 13:08 ` Samuel Thibault
2019-11-14 13:27 ` Samuel Thibault [this message]
2019-11-14 13:31 ` Samuel Thibault
2019-11-15 8:27 ` Teemu Kuusisto
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=20191114132712.rpqzq7jvl32beduu@function \
--to=samuel.thibault@gnu.org \
--cc=qemu-devel@nongnu.org \
--cc=teemu.kuusisto@gmail.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 NNTP newsgroup(s).