linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: benh@kernel.crashing.org
To: Matthias Grimm <joker@cymes.de>
Cc: LinuxPPC-Dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: [PATCH] PowerBook button device control back to user space
Date: Tue, 5 Feb 2002 14:18:55 +0100	[thread overview]
Message-ID: <20020205131855.29699@mailhost.mipsys.com> (raw)
In-Reply-To: <3C5EE8D9.1000408@cymes.de>


>
>Hi Ben,
>
>The following patch removes a unlucky shortcut from keyboard device to
>the PMU backlight
>device from the kernel and gives control back to user space.
>
>The Apple PowerBooks have a special button device to control special
>functions like
>display brightness, speaker volume, etc. The Keys for volume control
>generate keycodes,
>which were sent to user space. The keys for controlling the display
>brightness were
>directly handled by the kernel. This is not consequent and additionally
>an unlucky
>cross reference between different and independent parts of the kernel.

Hi Matthias. The presence of direct backlight handling in the kernel
is an artifact of old days ;) Actually, other controls (sound, CD eject)
of new powerbooks are sent to the even device and a userland daemon
already exist (ikeyd) for taking care of those events.

The problem currently is that not all powerbook models send those
as ADB keycodes, some are obtained via special PMU events directly
in via-pmu. So before backlight handling is moved to an ikeyd-like
daemon, we should first fix the kernel to properly send those
events on all models. I don't suggest changing this in the 2.4
timeframe though.

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2002-02-05 13:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-04 20:02 [PATCH] PowerBook button device control back to user space Matthias Grimm
2002-02-05 13:18 ` benh [this message]

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=20020205131855.29699@mailhost.mipsys.com \
    --to=benh@kernel.crashing.org \
    --cc=joker@cymes.de \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).