public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH] Console events and accessibility
Date: Thu, 23 Aug 2007 13:30:35 +0200	[thread overview]
Message-ID: <20070823113035.GD3287@implementation.labri.fr> (raw)
In-Reply-To: <20070823100402.GB6742@kroah.com>

Greg KH, le Thu 23 Aug 2007 03:04:02 -0700, a écrit :
> > I mean: yes, with these three patches, speakup will work fine.
> 
> 3 patches?  I only saw 2.  Or do you mean the modifications of the 3
> files?

Maybe you missed the keyboard notification patch which is already in
-mm.

> The patches look sane but you should change the global symbols to play
> nicer in the namespace.  Care to respin them together with this change?

You mean inverse_translate and screen_glyph?

> > The biggest change we'll have to do in speakup is the way it accesses
> > the serial port, which is really dirty for now, but that's an internal
> > matter.
> 
> Yeah, that shouldn't be that tough to do.

Well, the biggest problem is that we'd like to output on serial _before_
/dev gets mounted.

> It doesn't look like these changes handle scrolling of the console, do
> they?

Ah, indeed, speakup doesn't seem to handle it, that's why I forgot it in
the patch.  I'll see what needs to be done.

Thanks,
Samuel

  reply	other threads:[~2007-08-23 11:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-21 21:29 [PATCH] Console events and accessibility Samuel Thibault
2007-08-22  5:48 ` Greg KH
2007-08-22  8:53   ` Samuel Thibault
2007-08-22 13:05     ` Samuel Thibault
2007-08-23 10:04       ` Greg KH
2007-08-23 11:30         ` Samuel Thibault [this message]
2007-08-23 16:33           ` Greg KH
2007-08-23 17:08             ` Samuel Thibault
2007-08-23 17:51               ` 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=20070823113035.GD3287@implementation.labri.fr \
    --to=samuel.thibault@ens-lyon.org \
    --cc=akpm@linux-foundation.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.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