linux-kernel - Re: Does braille console work?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20170317090208.437d4e10@gandalf.local.home>
Date:   Fri, 17 Mar 2017 09:02:08 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Samuel Thibault <samuel.thibault@...-lyon.org>
Cc:     Petr Mladek <pmladek@...e.com>,
        Aleksey Makarov <aleksey.makarov@...aro.org>,
        linux-serial@...r.kernel.org, Joe Perches <joe@...ches.com>,
        linux-kernel@...r.kernel.org
Subject: Re: Does braille console work?

On Fri, 17 Mar 2017 10:40:51 +0100
Samuel Thibault <samuel.thibault@...-lyon.org> wrote:

> Petr Mladek, on ven. 17 mars 2017 10:35:44 +0100, wrote:
> > Anyway, the feature is not usable at the moment. Samuel, would
> > you be able to fix and test it, please?  
> 
> Sure, it's already on my TODO list, I will do when I get the time.
>

Yes please. There's no reason to keep that code if it's been broken for
3 years and nobody noticed. In fact, keeping it may actually make it
more difficult to add accessibility in the future. Methodologies may
change and the old broken code (that we've been complicating all other
code with), may actually become a hindrance to a new methodology.
Either keep it updated, or get rid of it. Getting rid of the
complications it adds to the core code, and let the core code become
more simplified may actually end up being easier to add accessibility
in the future, than keeping the old cruft around.

-- Steve