Bug#521279: Bug#521280: acpid does support netlink, so the problem only affects thinkpad-acpi

2009-10-19 Thread Harald Braumann
Hi,

I was just wondering, why the Thinkpad special keys don't work when I
use a Debian kernel instead of my home-grown one and I stumbled over
this bug report ...

 Well, I just looked at the most up-to-date acpid, and it supports
 netlink.
 
 Therefore, the issue is just that thinkpad-acpi wants you to get
 hotkeys from the input layer since kernel 2.6.23, 
Fair enough. But who gets them?

 and now finally the
 borrowed time is over in Debian installs, with the procfs event
 delivery being shut off.
Which leaves users out in the cold.

 What I wrote about a thinkpad-apci backwards compatibility mode was
 slightly incorrect...  teaches me to trust memories over one year old
 about stuff I never had to look back at, before writing something.
 The non-hotkey events go over netlink, yes.  But hotkeys go only over
 the input device, where they belong, and there is no driver switch to
 mess with that.
That's wrong. The default as of 2.6.31 is still to deliver them as both,
input events and ACPI events (see the `hotkey_report_mode' parameter
of thinkpad_acpi). But the ACPI events are only delivered through the
legacy interface /proc/acpi/event and not through netlink.

 This means that all configs that use acpid to process thinkpad-acpi
 hotkeys will break, and need to be ported over to HAL or something
 else that binds to input devices.
You are kidding, right? You don't seriously suggest that I have to
install HAL, D-BUS daemons and what not to be able to hibernate or
switch WIFI on and off.

 I think these bugs can be tagged wontfix, and we just deal with it
 as the usual perils of using unstable and testing.  It is
 probably a good idea to leave them open in the BTS for a while, in
 hopes that people will read them before filing more bugs.
Thanks for that.

 I don't think it affects any Debian standard config, but it will
 affect most of the local configs by end-users.
I would like to use a Debian standard config, however there doesn't
seem to be any alternative to acpid handling these events (HAL is _not_
an alternative). So what is the standard? I haven't found any daemon
that listens to input events and executes actions on them, like acpid
does. The only thing available is inputlirc, but that just routes them
to a socket which doesn't really gain you anything.

So either acpid is extended to also listen to button events, or a
daemon is provided, that does this. Until then, the only
alternative is to support /proc/acpi/event so acpid can be used for
the extra buttons.

Cheers,
harry


signature.asc
Description: PGP signature


Bug#521279: Bug#521280: acpid does support netlink, so the problem only affects thinkpad-acpi

2009-10-19 Thread maximilian attems
On Mon, Oct 19, 2009 at 02:50:58PM +0200, Harald Braumann wrote:
 Hi,
 
 I was just wondering, why the Thinkpad special keys don't work when I
 use a Debian kernel instead of my home-grown one and I stumbled over
 this bug report ...

please *use* reportbug so that valid info on your bugreport get
submitted.
 

acpid from testing/sid just works fine on my x61s.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#521279: Bug#521280: acpid does support netlink, so the problem only affects thinkpad-acpi

2009-10-19 Thread Harald Braumann
On Mon, 19 Oct 2009 16:18:05 +0200
maximilian attems m...@stro.at wrote:

 On Mon, Oct 19, 2009 at 02:50:58PM +0200, Harald Braumann wrote:
  Hi,
  
  I was just wondering, why the Thinkpad special keys don't work when
  I use a Debian kernel instead of my home-grown one and I stumbled
  over this bug report ...
 
 please *use* reportbug so that valid info on your bugreport get
 submitted.

Sorry, here's the relevant information:
Thinkpad T42p
Linux 2.6.31
acpid 1.0.10-2

 acpid from testing/sid just works fine on my x61s.

Acpid can handle button events, but it only defines a handful of
them. So either you only use those or it works differently on x61s.
See #521280. I've added more information there.

As long as acpid is not fixed, users who depend on this functionality
are left out in the cold and there is no alternative (and please don't
mention HAL). So I think, until then, Debian's Linux kernel should
support the legacy /proc/acpi/event interface.

Cheers,
harry


signature.asc
Description: PGP signature


Bug#521279: Bug#521280: acpid does support netlink, so the problem only affects thinkpad-acpi

2009-05-22 Thread Henrique de Moraes Holschuh
On Thu, 21 May 2009, Michael Meskes wrote:
 On Thu, Mar 26, 2009 at 12:44:32PM -0300, Henrique de Moraes Holschuh wrote:
  never had to look back at, before writing something.  The non-hotkey events
  go over netlink, yes.  But hotkeys go only over the input device, where they
  belong, and there is no driver switch to mess with that.
 
 Could anyone enlighten me please, where these events are to be found? acpid 
 does
 not just read the netlink inteface but also the input layer and thus is
 *supposed* to also get events coming over an input device. You can use 
 kacpimon
 to try it out.

I very much doubt it processes input events like KEY_FN_F1, or
KEY_BLUETOOTH by default...  and it shouldn't, either.  No bugs on acpid
here.

-- 
  One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie. -- The Silicon Valley Tarot
  Henrique Holschuh



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#521279: Bug#521280: acpid does support netlink, so the problem only affects thinkpad-acpi

2009-05-21 Thread Michael Meskes
On Thu, Mar 26, 2009 at 12:44:32PM -0300, Henrique de Moraes Holschuh wrote:
 never had to look back at, before writing something.  The non-hotkey events
 go over netlink, yes.  But hotkeys go only over the input device, where they
 belong, and there is no driver switch to mess with that.

Could anyone enlighten me please, where these events are to be found? acpid does
not just read the netlink inteface but also the input layer and thus is
*supposed* to also get events coming over an input device. You can use kacpimon
to try it out.

Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: mes...@jabber.org
Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL!



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org