All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Mattia Dongili <malattia@linux.it>
Cc: Norbert Preining <preining@logic.at>,
	Matthew Garrett <mjg@redhat.com>,
	linux-kernel@vger.kernel.org,
	ACPI Devel Mailing List <linux-acpi@vger.kernel.org>
Subject: Re: regression since 2.6.36: backlight in sony-laptop not working
Date: Tue, 16 Nov 2010 09:41:50 -0800	[thread overview]
Message-ID: <20101116174150.GA31851@core.coreip.homeip.net> (raw)
In-Reply-To: <20101116141849.GB2111@kamineko.org>

On Tue, Nov 16, 2010 at 11:18:50PM +0900, Mattia Dongili wrote:
> On Tue, Nov 16, 2010 at 02:16:42PM +0900, Norbert Preining wrote:
> > On Fr, 12 Nov 2010, Mattia Dongili wrote:
> > > You will need an updated input-kbd to set the scancode map.
> > 
> > Ouch.
> > 
> > > > Does that mean that 2.6.37rc is too new for the user space?
> > > 
> > > Maybe. Anyway if evtest reacts positively to key presses then it's a
> > > userspace issue and not the driver's.
> > 
> > What is strange that there *WAS* a change in the kernel that triggered
> > that. Old kernels still work fine. I just tried 2.6.36 and it was working.
> > 
> > I always thought that kernel changes should not break user space
> > (well, without good reason).
> 
> it's the same as this:
> https://bugzilla.kernel.org/show_bug.cgi?id=23022
> 

Right, we up-revved evdev protocol version to reflect the fact that it
supports large scancodes but the procotocl is backwards-compatible and
older userspace should have no problems talking with evdev and do
remaps. For example, udev's keymap utility workds just fine here.
Unfortunately input-kbd insists on working with only one version of the
protocol instead if checking if the protocol "at least N". This shoudl
be fixed in input-kbd.

Thanks.

-- 
Dmitry

  reply	other threads:[~2010-11-16 17:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-04 14:29 regression since 2.6.36: backlight in sony-laptop not working Norbert Preining
2010-11-10  3:58 ` Mattia Dongili
2010-11-11 23:50   ` Norbert Preining
2010-11-12  3:44     ` Matthew Garrett
2010-11-12  3:50       ` Norbert Preining
2010-11-12  3:57         ` Matthew Garrett
2010-11-12  4:14           ` Norbert Preining
2010-11-12  4:22           ` Mattia Dongili
2010-11-12  4:39             ` Norbert Preining
2010-11-12 12:17               ` Mattia Dongili
2010-11-16  5:16                 ` Norbert Preining
2010-11-16 14:18                   ` Mattia Dongili
2010-11-16 17:41                     ` Dmitry Torokhov [this message]
2010-11-17  6:30             ` Norbert Preining
2010-11-17  6:33               ` Norbert Preining
2010-11-17  6:52                 ` Dmitry Torokhov
2010-11-18 11:04                   ` Mattia Dongili
2010-11-18 13:34                     ` Mattia Dongili
2010-11-18 18:06                       ` Dmitry Torokhov
2010-11-17  7:12               ` Dmitry Torokhov
2010-11-12  7:38         ` Zhang Rui
2010-11-12 10:10           ` Norbert Preining

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=20101116174150.GA31851@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=malattia@linux.it \
    --cc=mjg@redhat.com \
    --cc=preining@logic.at \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.