From: Petr Mladek <pmladek@suse.com>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
Aleksey Makarov <aleksey.makarov@linaro.org>,
linux-serial@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Joe Perches <joe@perches.com>,
linux-kernel@vger.kernel.org
Subject: Re: Does braille console work?
Date: Fri, 17 Mar 2017 10:35:44 +0100 [thread overview]
Message-ID: <20170317093544.GN3977@pathway.suse.cz> (raw)
In-Reply-To: <20170317005355.xwym3zpamym3rwp6@var.youpi.perso.aquilenet.fr>
Hello,
On Fri 2017-03-17 01:53:55, Samuel Thibault wrote:
> Aleksey Makarov, on jeu. 16 mars 2017 17:02:53 +0300, wrote:
> >
> > So braille console registration should not work. What do I miss?
>
> Nothing, the code transformation was broken :/
> > So it looks like braille console has not been used for more than 3 years.
> > Should we remote it?
>
> Please, no :)
>
> It is indeed not often useful, since one would usually use a userland
> daemon to access the system, but when one's system does not boot
> properly or something similar, it's useful to have the braille
> console. That's just very not often useful.
I see the points. I would personally prefer to keep it even though
it is not much used and it complicates some code paths. Well, I do
not feel in the position to decide about it.
Anyway, the feature is not usable at the moment. Samuel, would
you be able to fix and test it, please?
Best Regards,
Petr
next prev parent reply other threads:[~2017-03-17 9:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 14:02 Does braille console work? Aleksey Makarov
2017-03-17 0:53 ` Samuel Thibault
2017-03-17 9:00 ` Aleksey Makarov
2017-03-17 9:16 ` Samuel Thibault
2017-03-17 9:35 ` Petr Mladek [this message]
2017-03-17 9:40 ` Samuel Thibault
2017-03-17 13:02 ` Steven Rostedt
2017-03-19 14:41 ` Samuel Thibault
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=20170317093544.GN3977@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=aleksey.makarov@linaro.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=samuel.thibault@ens-lyon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox