martin f krafft wrote:
also sprach Bart Samwel <[EMAIL PROTECTED]> [2008.03.10.1014 +0100]:
It just doesn't, there's no events for it in the current package.
So if the behaviour currently works, then somebody else handles
it, apparently. And if somebody else is handling it, I can't
change the behaviour in acpi-support, since the behaviour isn't
part of acpi-support!
Why not? It's an ACPI event and it's laptop-specific what to do
about it. That sounds a lot like what acpi-support does.
Acpi-support only exists to make work what doesn't work, and usually
just as a "glue layer" to let other packages do the actual work. This
actually works without any help from acpi-support, so some other package
or driver is already handling it without requiring a glue layer from
acpi-support. If you want the behaviour changed, I suggest you find out
who's currently handling these keys, and file a bug report with them. I
don't have a means of fixing your bug since it's not in my package, and
I have no means of finding out who it should go to. Sorry. :-/
Cheers,
Bart
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
