ACPI generic hotkey working on SONY (was: sony vaio pcg-k45 hell)

[Stefan Seyfried <seife-T+3qhDtrTvDv8lqoKu5MV4HBZQ1bDw0s@public.gmane.org>]

[-- Attachment #1: Type: text/plain, Size: 1676 bytes --]

On Fri, Nov 25, 2005 at 01:05:22PM +0100, Stefan Seyfried wrote:

> > If so, acpi is fully responsible for hotkey function by keystroke.
> > If not, please verify http://bugzilla.kernel.org/show_bug.cgi?id=4876#c4 works 
> > or not. This is proc file stuff for hotkey function by issuing command from 
> > shell. 
> 
> I'm trying this out but may only get to it on monday or tuesday next week.

setting brightness works on the vgn-f115b with the patch after fixing it up
for 2.6.14.2 (attached, the most nasty one was the missing
EXPORT_SYMBOL(acpi_scan_ids) :-)

I have of course some other questions:
- what will happen on other machines if i load the hotkey module and issue
  echo "10001:1:1:0" >/proc/acpi/hotkey/action
  - will it crash?
  - will it just not work?
  - will it just work, so this is a generic solution?
- will it also work on my panasonic which right now needs pcc_acpi?
  (i will check this one out soon)
- if the "10001:1:1:0" is not a generic string for all machines (i am afraid
  it isn't), how do i find out what to put into /proc/acpi/hotkey/action?

Another problem is that for distributions to be able to use this stuff, it
must not depend on the "acpi_generic_hotkey=1" parameter. Can't we decide at
module load time if we want to use the generic or the vendor specific hotkey
interface?
Having the user select which machine he has _before_ installing with some
cryptic boot parameter is something i'd like to avoid.

Also i see that now some sony-specific stuff is in the generic hotkey driver.
Will we have to add specific stuff for all other vendor specific drivers if
we want to merge their functionality into hotkey.c?
-- 
Stefan Seyfried

[-- Attachment #2: hotkey-sony-2.6.14.2.patch.gz --]
[-- Type: application/x-gunzip, Size: 3669 bytes --]