LKML Archive on
 help / color / Atom feed
From: Nicolas Pitre <>
To: Vito Caputo <>
Cc: Dmitry Safonov <>,
	Greg Kroah-Hartman <>,
	Jiri Slaby <>, Mark Rutland <>,
	Tetsuo Handa <>,
	Tycho Andersen <>, Dave Mielke <>,
Subject: Re: commit 83d817f410 broke my ability to use Linux with a braille display
Date: Fri, 11 Jan 2019 14:32:35 -0500 (EST)
Message-ID: <nycvar.YSQ.7.76.1901111426250.1647@knanqh.ubzr> (raw)
In-Reply-To: <>

On Fri, 11 Jan 2019, Vito Caputo wrote:

> On Fri, Jan 11, 2019 at 01:33:09PM -0500, Nicolas Pitre wrote:
> > I use Linux with the help of a braille display and the brltty daemon. It 
> > turns out that the latest mainline kernel I can work with comes from 
> > commit 231f8fd0cc. Anything past that and I lose the ability to read the 
> > console barely a few seconds after the system has booted as brltty is 
> > thrown a wrench and the braille display becomes completely inoperable.
> > 
> > Things get somewhat better with commit c96cf923a9 as brltty is not 
> > longer incapacitated, but some programs would randomly crash. Even the 
> > very first login attempt won't work as I soon as I hit enter after my 
> > user name the password prompt is skipped over, just like if the enter 
> > key had been hit twice. Then lynx (the text web browser) would crash as 
> > soon as I switch the virtual console with LeftAlt+FN. Mind you, this 
> > isn't easy to perform bisection in those conditions.
> > 
> > And the worst commit i.e. 83d817f410 is marked for stable!  :-(
> This all sounds familiar, and I suspect this is the fix:

Yep, I confirm this patch did solve all my issues.


  reply index

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-11 18:33 Nicolas Pitre
2019-01-11 19:11 ` Vito Caputo
2019-01-11 19:32   ` Nicolas Pitre [this message]
2019-01-11 19:32 ` Greg Kroah-Hartman
2019-01-11 20:10   ` Nicolas Pitre
2019-01-12  8:08     ` Greg Kroah-Hartman

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=nycvar.YSQ.7.76.1901111426250.1647@knanqh.ubzr \ \ \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

LKML Archive on

Archives are clonable:
	git clone --mirror lkml/git/0.git
	git clone --mirror lkml/git/1.git
	git clone --mirror lkml/git/2.git
	git clone --mirror lkml/git/3.git
	git clone --mirror lkml/git/4.git
	git clone --mirror lkml/git/5.git
	git clone --mirror lkml/git/6.git
	git clone --mirror lkml/git/7.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 lkml lkml/ \
	public-inbox-index lkml

Newsgroup available over NNTP:

AGPL code for this site: git clone public-inbox